I would take a guess that the next step M'soft would try is a Tar Baby stratagy. Each new generation/upgrade of product will introduce new features that will have to be reverse engineered. This way they can claim that OSS will always be behind the times etc. etc.
This is to imply that this is not their primary strategy already? And that it's starting to backfire as more and more companies demand open standards?
Re:Mozilla... Is it even worth the download?
on
Mozilla M6 released
·
· Score: 2
If the cache were shared, people would be screaming bloody murder about how everyone could see the pr0n that was dropped into the cache. That netscape CAN'T use a shared cache is something of a problem. That it DOESN'T by default is not.
Re:You don't know what you're talking about
on
CPU Cooling Insanity
·
· Score: 1
My motherboard registers about three degrees cooler when the case is on and the front face (which blocks airflow, alas) is off than when the face and case are off. Of course I don't have many heat problems to begin with because I don't have a 3dfx board. Riva TNT's got no heatsink and barely puts out heat.
In the great tradition of United States drug laws, they'll make thinking about it a crime. Or possessing the goods. Or possessing goods you could use to obtain, manufacture, or utilize the goods.
Nonsense. There is a big difference between a government controlling what people may say to each other and an admin controlling what content takes up space on his private property. Content that is in violation of the informal agreement to use the service. Usenet groups are not public property.
AOL does not need to destroy Usenet. It broke all by itself. Usenet was created in an era when the users were by and large, professionals. Personal civility was never at a premium, but attacks on the infrastructure itself were high crimes against the community.
Usenet simply has no strong protections against vandalism. The barbarians knocked down the gate a long time ago, it's time to leave them the ashes they've made of it.
Xemacs was able to be an Xt widget at one point, but the ability has been broken for years. jwz occasionally kvetches about that, but few people want to deal with Xt who might be inclined to embed emacs.
Re:KDE is not a corporate body!
on
The KDE Future
·
· Score: 1
Tried perlQt.. symbol relocation errors galore. Recompiled Qt with the same compiler perlQt used. Same errors. Tried it on linux. Core dump.
Tried python's kde bindings. segfault.
I get the feeling linkages to C++ libraries must only work for the people who develop them, if that. Not that I don't see the value in having widgets in C++ -- compare gnome's "hello world" with qt's tutorial 2 (which has the same equivalent function). I was sold on Qt immediately. But this ABI crap with C++, where you can't link anything from a foreign compiler or a compilerwith a different version or whenever it just doesn't feel like linking... it's really getting on my last nerve. Gtk-- is looking good to me these days, but then there's the matter of the utterly pathetic state of gtk's documentation.
I personally pronounce it "Kay-Oh-Emm". And since KOM is built on KORBA -- er, CORBA, you get the `D' from the start. Rather unlike DCOM, which is a hack over COM, and unlike COM which is simply a linker standard (and easily duplicated elsewhere, like XPCOM)
IE was ported to Unix with Software AG's porting toolkit, which has Linux as a target. It effectively runs the entire Win32 API on top of Unix, and is exactly the bloated monstrosity you think it is. Then to top it off they statically link it with Motif.
Why scary? No one is going to buy into a scheme that costs them more than the current one, and as long as competition still exists, your prices aren't going to go up as a result. Same argument applies to metered access.
Re:Excuse my ignorance but...
on
UK Linux Conf
·
· Score: 1
I never endorsed piracy in the first place. Let's be honest people, how many of you have ever seen a ROM image for an emulator that wasn't pirate? Ripping off the console makers is not a solution. But neither is supporting them.
Re:Excuse my ignorance but...
on
UK Linux Conf
·
· Score: 1
None of these tools would have to change, just the filesystem driver. All those packages you named compile using out of the box using cygnus on NT on an NTFS filesystem after all.
Re:Excuse my ignorance but...
on
UK Linux Conf
·
· Score: 2
This is called "metadata", and is absolutely critical for any modern filesystem to implement. The more OO your environment becomes, where you're looking at devices and resources and sockets and so on through the filesystem, the more you need to be able to attach arbitrary property sheet handlers. NTFS does this extremely well.
Unfortunately there are "file mode forever" people on linux-kernel who would rather keep linux a clone of a 70's OS than add anything people might actually use.
Many museums are online, and until Bill Gates buys exclusive digital rights to them ALL (which he really is doing), many fine works of art have extremely high-res photos of them. With an LCD projector (yes, this takes real money folks) and a slideshow program, a teacher can create an art appreciation curriculum without ever needing to maintain a bunch of slides, which fade, crack, and get lost.
Cursive always seemed to me a very archaic rococo form of writing that's only suitable for signatures and calligraphy. I imagine the only use in teaching it is to read it and to develop a signature. I work with dozens of people, we all go to meetings, and NOT ONE person I know takes notes or writes instructions in cursive. When I was in grade school, I could block print very neatly, but had to take remedial writing for years, and my teachers constantly marked me down for penmanship, because my cursive was so bad. Is it any damn wonder I hated writing papers and procrastinated writing them for the rest of my school years? They taught me that writing was an ordeal to be endured, not a craft to be honed. Any wonder I found school boring and not worthwhile? I could have been learning, but there I was writing lowercase "f"s for half a class. I still can't get some capitals right.
That last part actually turned out to be beneficial to me... school offered me nothing stimulating, so I learned to teach myself far more effectively than any school.
Slashdot Mirror
This is to imply that this is not their primary strategy already? And that it's starting to backfire as more and more companies demand open standards?
If the cache were shared, people would be screaming bloody murder about how everyone could see the pr0n that was dropped into the cache. That netscape CAN'T use a shared cache is something of a problem. That it DOESN'T by default is not.
My motherboard registers about three degrees cooler when the case is on and the front face (which blocks airflow, alas) is off than when the face and case are off. Of course I don't have many heat problems to begin with because I don't have a 3dfx board. Riva TNT's got no heatsink and barely puts out heat.
This guy had fans on the thing six ways to sunday then says he never had the cover on. Hello, covers speed up the airflow, they keep the thing COOLER.
> But are there any bits on the motherboard that would corrode?
Copper. Now you don't have pure water either.
Where's the headphone jack on a pilot? Or are you planning on playing it on that little piezo speaker?
Uhhh. USENET doesn't have the right to police USENET? Is that the argument?
> I should be free to view whatever content I want.
You are also free from being compelled to carry the content you do not want. Is your ISP violating your rights by not carrying every single newsgroup?
In the great tradition of United States drug laws, they'll make thinking about it a crime. Or possessing the goods. Or possessing goods you could use to obtain, manufacture, or utilize the goods.
Nonsense. There is a big difference between a government controlling what people may say to each other and an admin controlling what content takes up space on his private property. Content that is in violation of the informal agreement to use the service. Usenet groups are not public property.
AOL does not need to destroy Usenet. It broke all by itself. Usenet was created in an era when the users were by and large, professionals. Personal civility was never at a premium, but attacks on the infrastructure itself were high crimes against the community.
Usenet simply has no strong protections against vandalism. The barbarians knocked down the gate a long time ago, it's time to leave them the ashes they've made of it.
Not using AOL. Letting AOL know why.
kfm's really useless in some ways.
1. It doesn't do POST. Not correctly anyhow.
2. Doesn't do any auth at all.
3. Dragging randomly alternates between hilighting text and dragging out rubberbands, with no apparent way to switch behaviors.
4. Poor control over fonts. A case where integration is not what I want, I prefer larger fonts in my web browser than in my file manager.
5. Doesn't use the mousewheel. I can make netscape use it (oddly, it seems to have lost the ability just now though).
Xemacs was able to be an Xt widget at one point, but the ability has been broken for years. jwz occasionally kvetches about that, but few people want to deal with Xt who might be inclined to embed emacs.
Tried perlQt .. symbol relocation errors galore. Recompiled Qt with the same compiler perlQt used. Same errors. Tried it on linux. Core dump.
... it's really getting on my last nerve. Gtk-- is looking good to me these days, but then there's the matter of the utterly pathetic state of gtk's documentation.
Tried python's kde bindings. segfault.
I get the feeling linkages to C++ libraries must only work for the people who develop them, if that. Not that I don't see the value in having widgets in C++ -- compare gnome's "hello world" with qt's tutorial 2 (which has the same equivalent function). I was sold on Qt immediately. But this ABI crap with C++, where you can't link anything from a foreign compiler or a compilerwith a different version or whenever it just doesn't feel like linking
I personally pronounce it "Kay-Oh-Emm". And since KOM is built on KORBA -- er, CORBA, you get the `D' from the start. Rather unlike DCOM, which is a hack over COM, and unlike COM which is simply a linker standard (and easily duplicated elsewhere, like XPCOM)
IE was ported to Unix with Software AG's porting toolkit, which has Linux as a target. It effectively runs the entire Win32 API on top of Unix, and is exactly the bloated monstrosity you think it is. Then to top it off they statically link it with Motif.
Why scary? No one is going to buy into a scheme that costs them more than the current one, and as long as competition still exists, your prices aren't going to go up as a result. Same argument applies to metered access.
Are you saying that cp on BeOS is broken then?
I never endorsed piracy in the first place. Let's be honest people, how many of you have ever seen a ROM image for an emulator that wasn't pirate? Ripping off the console makers is not a solution. But neither is supporting them.
None of these tools would have to change, just the filesystem driver. All those packages you named compile using out of the box using cygnus on NT on an NTFS filesystem after all.
Why was this moderated up?
This is called "metadata", and is absolutely critical for any modern filesystem to implement. The more OO your environment becomes, where you're looking at devices and resources and sockets and so on through the filesystem, the more you need to be able to attach arbitrary property sheet handlers. NTFS does this extremely well.
Unfortunately there are "file mode forever" people on linux-kernel who would rather keep linux a clone of a 70's OS than add anything people might actually use.
Many museums are online, and until Bill Gates buys exclusive digital rights to them ALL (which he really is doing), many fine works of art have extremely high-res photos of them. With an LCD projector (yes, this takes real money folks) and a slideshow program, a teacher can create an art appreciation curriculum without ever needing to maintain a bunch of slides, which fade, crack, and get lost.
Cursive always seemed to me a very archaic rococo form of writing that's only suitable for signatures and calligraphy. I imagine the only use in teaching it is to read it and to develop a signature. I work with dozens of people, we all go to meetings, and NOT ONE person I know takes notes or writes instructions in cursive. When I was in grade school, I could block print very neatly, but had to take remedial writing for years, and my teachers constantly marked me down for penmanship, because my cursive was so bad. Is it any damn wonder I hated writing papers and procrastinated writing them for the rest of my school years? They taught me that writing was an ordeal to be endured, not a craft to be honed. Any wonder I found school boring and not worthwhile? I could have been learning, but there I was writing lowercase "f"s for half a class. I still can't get some capitals right.
... school offered me nothing stimulating, so I learned to teach myself far more effectively than any school.
That last part actually turned out to be beneficial to me