Okay, I didn't realize it'd require a port. However, I take offense to your "hostile to free software" comment. Windows has an extensive freeward community, and just because a person prefers to work in Windows rather than deal with the POS that is POSIX and X (its entirely a matter of preference, I can't stand non-OO GUI environments and four letter function call names offend my sense of cleanliness) doesn't make that person in any way hostile to free software. OSS software does not need to run on an OSSOS.
You forget. The majority of computers run an OS that is not case sensitive. Thus, there is a very good chance that at the trademark office, Qt.tm == QT.tm
I'd like to see how they define UNIX platform. Does NT's POSIX count as a UNIX platform? Does BeOS count as a UNIX platform? This UNIX bigotry has got to stop! Making it free for OSS and pay for commercial is one thing. Doing the same for UNIX and Windows is just punishing a developer for not liking *NIX.
I think he was talking printing of screenshots. To tell the truth, ANY OS will have this problem, so I have no idea WTF he is talking about. And who prints screenshots anyway?
Maybe the Mac truetype renderer is just better? Either way, the best truetype renderer out there seems to BitStream's FontFusion. QNX RtP's text looks AMAZING.
How the f*ck is this flamebait? DB's are basically OSs in themselves, given how much of their own memory allocation and FS stuff they do. They're basically the only reason raw I/O exists at all. Since DOS has no real overhead, I wouldn't be surprised if a database performed faster under DOS.
It also blows goat nuts when it comes to *real* 3D performance (3D Studio), even though it costs a huge amount more than a 1.2GHz Athlon ($306/w mobo on Pricewatch!) and isn't available in SMP. Right now, the P4 is a Quake proc, nothing more.
Let's not repeat this again. Mindcraft revealed REAL problems with Linux on high end hardware. These issues were duly noted and fixes have/are being done. Have a bad experience and learn from it. If you actually have 4 procs and 4 NICs, then you're happy that Linux now scales to that level, and the prodding by Mindcraft didn't hurt any in this respect.
Ahem, Mindcraft. It's a sad fact, but the majority of people have that reaction. Some, when they see bad news, try to hide it, others try to fix it. The only difference between the Linux and MS communities in this respect is that at MS, the former are in charge, while with Linux, the latter are.
I just realized. You're going to need at least 10MB on your vid card to run this at full-res full color! And if Carmack gets his way (64bit floating point color) then I couldn't even run this monitor on my computer!
I was being sarcastic. My point was that if you get rid of the dildo industry (like if you get rid of a sports franchise) you don't suddenly have a bunch of surplus money saved by not making dildos. You lose the revenue, and thus end up wit NO money.
Exactly. I'm out to get Linux. I wake up in the morning and think, hmm, I haven't flamed Linux today. Look, jackass, I have nothing against Linux. I actually kinda like the system. Still, I don't find any use in being one of the me-too monkeys who go around espousing the greatness of the platform. Linux has serious problems and lots of them. Every OS does. Talking about them is a lot more useful and ignoring them and pretending they don't exist.
BTW> "chances are you broke "ls" because you did something stupid. Thanks alot for blaming it on the glibc maintainers, you prick" --- right out of Microsoft tech support. I didn't do anything wrong. All I did was run the install script for the package. The actual problem was due to the fact that the package had a bad interactaction with something in the system, and admirably the problem was fixed in a few days. I was not trying to blame the glibc maintainers, I was simply pointing out that shit happens, almost as often on Linux as on Windows (yes! and even BeOS!).
Java bindings for GUI environments is an interesting idea. I once read several years ago that the average application spends about 90% of its time in windowing toolkit routines. I'm sure the real figure, at least today, is a good bit lower, but even at, say, 50%, implementing toolkit routines in native code could have a big performance boost for Java applications. Still, I don't really know if Java is the way to go for quick/easy apps. C++ really isn't hard at all to do, and Java isn't appreciably easier. Sure there less ways to break things, but you can program buggy Java just as easily as buggy C++. I think the main benifet of Java is the huge class library that comes with it. Maybe if a class library like this were created in native code, and put up as kind of a GUI complement to POSIX, the dreams of quick-to-write and portable GUI apps could be realized without resorting to interpreted languages like Java.
50MB? What's in there! Seriously, one has to admit 50MB is getting pretty hefty for a system. The entire BeOS core directory is about 30MB of binaries (including drivers and the whole bit). This isn't a plug for BeOS, just a point of reference. What is GNOME stuffing in there?
Let's see, 1.3 trillion dollar tax cut over 5 years, about 250 billion per year. Get rid of the $5 billion per year you're giving Gates and Buffet in tax cuts, and voila, NASA budget problem solved.
Problematically, sports money doesn't come out of thin air. The only reason they spend so much money on sports stadiums and all that is because people are willing to *spend* lots of disposable income on those things. If you get rid of sports league, you also get rid of your source of revenue. (It would be great if we could get rid of the dildo industry and spend all the money we save by not having to make dildos on the space program!) Basic economics my friend.
PS> If anything goes, its the NBA. You're not TOUCHING the NHL!
I doubt you can upgrade without reformating. Still, it would be no trouble at all to copy data over to a spare partition, format with ReiserFS (or if you have the balls, XFS!) and copy stuff back over. ext3 essentially exists to save the user the trouble of two copies. Kinda silly.
Actually, the PCI spec is a very expensive "open" bus. If you have ever tried to write an PCI code, you'll find that they charge several hundred dollars for the specs.
Actually, I have the excat OPPOSITE problem. I can't stand all the i386 packages floating around. And I can't find any i686-only distros (although Gentoo should have i686 builds when it hits rc4.) Either way, think about this logically. What's the point of releasing i386 packages as the standard format? You release standard packages for standard machines (i686 would probably be the most common at the moment) and then release special packages for special cases (i386 and i486 should, by this time, be considered a special case.) If the majority of users run on a particular platform, you should optimize for that platform first, then optimize for boarder cases. The "critical path" and all that.
A) There is nothing inherently wrong with "Windows characteristics." There are bad characteristics and Windows characteristics. An item in one set is not necessarily in the other.
B) What's wrong with beta builds? Linux has had beta builds ever since I can remember (except they call it a -test) RedHat beta builds have been called.0 releases, everything has beta builds. Its an essential part of a software release. The problem isn't releasing Betas, but releasing Betas and pretending they are final products.
C) Try Gentoo Linux It's nice and light, has a lot of the cool package management features of Debian, and is well-thought-out. It also has something like a ports tree. It might be a little cutting edge for many people's tastes (a comment once accompanied a package "package x.y.z merged. Did we beat freshmeat?" It's still a development product, but its manual installation isn't really any harder than installing some other Linux distros, and gives you a lot more control. When this thing reaches 1.0, RedHat watch out!
Slashdot Mirror
Okay, I didn't realize it'd require a port. However, I take offense to your "hostile to free software" comment. Windows has an extensive freeward community, and just because a person prefers to work in Windows rather than deal with the POS that is POSIX and X (its entirely a matter of preference, I can't stand non-OO GUI environments and four letter function call names offend my sense of cleanliness) doesn't make that person in any way hostile to free software. OSS software does not need to run on an OSSOS.
You forget. The majority of computers run an OS that is not case sensitive. Thus, there is a very good chance that at the trademark office, Qt.tm == QT.tm
I'd like to see how they define UNIX platform. Does NT's POSIX count as a UNIX platform? Does BeOS count as a UNIX platform? This UNIX bigotry has got to stop! Making it free for OSS and pay for commercial is one thing. Doing the same for UNIX and Windows is just punishing a developer for not liking *NIX.
I think he was talking printing of screenshots. To tell the truth, ANY OS will have this problem, so I have no idea WTF he is talking about. And who prints screenshots anyway?
Maybe the Mac truetype renderer is just better? Either way, the best truetype renderer out there seems to BitStream's FontFusion. QNX RtP's text looks AMAZING.
How the f*ck is this flamebait? DB's are basically OSs in themselves, given how much of their own memory allocation and FS stuff they do. They're basically the only reason raw I/O exists at all. Since DOS has no real overhead, I wouldn't be surprised if a database performed faster under DOS.
It also blows goat nuts when it comes to *real* 3D performance (3D Studio), even though it costs a huge amount more than a 1.2GHz Athlon ($306 /w mobo on Pricewatch!) and isn't available in SMP. Right now, the P4 is a Quake proc, nothing more.
Let's not repeat this again. Mindcraft revealed REAL problems with Linux on high end hardware. These issues were duly noted and fixes have/are being done. Have a bad experience and learn from it. If you actually have 4 procs and 4 NICs, then you're happy that Linux now scales to that level, and the prodding by Mindcraft didn't hurt any in this respect.
Ahem, Mindcraft. It's a sad fact, but the majority of people have that reaction. Some, when they see bad news, try to hide it, others try to fix it. The only difference between the Linux and MS communities in this respect is that at MS, the former are in charge, while with Linux, the latter are.
I just realized. You're going to need at least 10MB on your vid card to run this at full-res full color! And if Carmack gets his way (64bit floating point color) then I couldn't even run this monitor on my computer!
I was being sarcastic. My point was that if you get rid of the dildo industry (like if you get rid of a sports franchise) you don't suddenly have a bunch of surplus money saved by not making dildos. You lose the revenue, and thus end up wit NO money.
Exactly. I'm out to get Linux. I wake up in the morning and think, hmm, I haven't flamed Linux today. Look, jackass, I have nothing against Linux. I actually kinda like the system. Still, I don't find any use in being one of the me-too monkeys who go around espousing the greatness of the platform. Linux has serious problems and lots of them. Every OS does. Talking about them is a lot more useful and ignoring them and pretending they don't exist.
BTW> "chances are you broke "ls" because you did something stupid. Thanks alot for blaming it on the glibc maintainers, you prick" --- right out of Microsoft tech support. I didn't do anything wrong. All I did was run the install script for the package. The actual problem was due to the fact that the package had a bad interactaction with something in the system, and admirably the problem was fixed in a few days. I was not trying to blame the glibc maintainers, I was simply pointing out that shit happens, almost as often on Linux as on Windows (yes! and even BeOS!).
Java bindings for GUI environments is an interesting idea. I once read several years ago that the average application spends about 90% of its time in windowing toolkit routines. I'm sure the real figure, at least today, is a good bit lower, but even at, say, 50%, implementing toolkit routines in native code could have a big performance boost for Java applications. Still, I don't really know if Java is the way to go for quick/easy apps. C++ really isn't hard at all to do, and Java isn't appreciably easier. Sure there less ways to break things, but you can program buggy Java just as easily as buggy C++. I think the main benifet of Java is the huge class library that comes with it. Maybe if a class library like this were created in native code, and put up as kind of a GUI complement to POSIX, the dreams of quick-to-write and portable GUI apps could be realized without resorting to interpreted languages like Java.
50MB? What's in there! Seriously, one has to admit 50MB is getting pretty hefty for a system. The entire BeOS core directory is about 30MB of binaries (including drivers and the whole bit). This isn't a plug for BeOS, just a point of reference. What is GNOME stuffing in there?
That's debatable. NT's service packs have never broken anything for me, but upgrading glibc (2.2.2-pre -> 2.2.2-final) once broke 'ls' of all things!
Let's see, 1.3 trillion dollar tax cut over 5 years, about 250 billion per year. Get rid of the $5 billion per year you're giving Gates and Buffet in tax cuts, and voila, NASA budget problem solved.
Problematically, sports money doesn't come out of thin air. The only reason they spend so much money on sports stadiums and all that is because people are willing to *spend* lots of disposable income on those things. If you get rid of sports league, you also get rid of your source of revenue. (It would be great if we could get rid of the dildo industry and spend all the money we save by not having to make dildos on the space program!) Basic economics my friend.
PS> If anything goes, its the NBA. You're not TOUCHING the NHL!
Damn, this PII is getting slow. Is GNOME getting slower by the day, or does Intel build timers into its chips that halves the clock-rate very year?
I believe he meant from ext2.
I doubt you can upgrade without reformating. Still, it would be no trouble at all to copy data over to a spare partition, format with ReiserFS (or if you have the balls, XFS!) and copy stuff back over. ext3 essentially exists to save the user the trouble of two copies. Kinda silly.
X.10 and X.11. Can you say trademark violations?
Actually, the PCI spec is a very expensive "open" bus. If you have ever tried to write an PCI code, you'll find that they charge several hundred dollars for the specs.
Actually, I have the excat OPPOSITE problem. I can't stand all the i386 packages floating around. And I can't find any i686-only distros (although Gentoo should have i686 builds when it hits rc4.) Either way, think about this logically. What's the point of releasing i386 packages as the standard format? You release standard packages for standard machines (i686 would probably be the most common at the moment) and then release special packages for special cases (i386 and i486 should, by this time, be considered a special case.) If the majority of users run on a particular platform, you should optimize for that platform first, then optimize for boarder cases. The "critical path" and all that.
Why would you want to do that? ReiserFS is faster, more stable, and HERE NOW!
A) There is nothing inherently wrong with "Windows characteristics." There are bad characteristics and Windows characteristics. An item in one set is not necessarily in the other.
.0 releases, everything has beta builds. Its an essential part of a software release. The problem isn't releasing Betas, but releasing Betas and pretending they are final products.
B) What's wrong with beta builds? Linux has had beta builds ever since I can remember (except they call it a -test) RedHat beta builds have been called
C) Try Gentoo Linux It's nice and light, has a lot of the cool package management features of Debian, and is well-thought-out. It also has something like a ports tree. It might be a little cutting edge for many people's tastes (a comment once accompanied a package "package x.y.z merged. Did we beat freshmeat?" It's still a development product, but its manual installation isn't really any harder than installing some other Linux distros, and gives you a lot more control. When this thing reaches 1.0, RedHat watch out!