Durn, my RedHat9 CDs won't install on my Mac! So much for run on anything out of the box.;-)
I really don't agree with this one-Linux-fits-all approach. Separate RedHat's (or whatever) for Desktop and Server use would be great. Which they do now, I suppose; perhaps in RedHat X we'll see better optimizations for desktop usage.
Of course, as I advocate this splitting of distros, I also hate the way we have 20 distros to do the same thing, and they all do it half-assed...;-) Lindows/Xandros/Lycoris/Ark/etc. merge would be nice, since they all do the same thing but just fragment the market. Same goes for Mandrake/RedHat/SuSE/etc.
One can argue they each have strengths and weaknesses, but that's mostly because they haven't merged. ~,^
I'd love to see one primary distro for each class of device/use, along with the plethora of hobby linuxes (which I rather enjoy using from time to time). In the commercial world, tho, the fragementation isn't helping with anything other than increased competition, but we all have enough of that from Microsoft/Sun/Apple already, don't we?
It'd also be great financially to have fewer commercial entities. Take Mandrake and SuSE for example; they both employ developers. How many of those developers end up doing the exact same thing for their companies? Two installer dev teams, two config tool teams, etc. Imagine, if they merged developers, they'd have the income from both companies to pay these developers, but now they can stop duplicating. You get more for the money. And Linux distros aren't exactly a high income source, they need to waste as little as possible.:(
Of course, why I'm wasting time to say this to a bunch of Slashdot users that will, over all, have absolutely no effect on the situation, is beyond me. ~,^
This may be the encoding - AAC(Mpeg4) is a lossy codec, just like MP3/Ogg, so it will not be a perfect copy of the original mastered track. Of course, it's many many many times smaller tho.;-)
Slashdot has a previous article on the quality comparisons of AAC/MP3/Ogg, you might want to check that and see if it has any info on your specific problem.
Templates are only bloat when misused. In many cases, your options are to write a template, or cut-and-paste then modify a class/function over and over.
You can also write classes that only have template members, so if most of a class is the exact same no matter the data type, you're fine.
Templates also let you do things you simply can't do in this low level of a language otherwise (and many high level languages also don't allow) - take a look at what the BOOST library does.
There comes a point when you have speed/efficiency/code-size vs. taking 6 years or 6 weeks to code something, and with today's hardware, the later is usually the best choice.
Also, templates can be used to generate data, not just code, so where you might have before needed a function call in order to compute a value, a template could turn it into the actual value at compile-time (look at how modern games use templates to generate sin/cos/tan/etc. values for constant inputs).
Slashdot Mirror
Durn, my RedHat9 CDs won't install on my Mac! So much for run on anything out of the box. ;-)
;-) Lindows/Xandros/Lycoris/Ark/etc. merge would be nice, since they all do the same thing but just fragment the market. Same goes for Mandrake/RedHat/SuSE/etc.
:(
I really don't agree with this one-Linux-fits-all approach. Separate RedHat's (or whatever) for Desktop and Server use would be great. Which they do now, I suppose; perhaps in RedHat X we'll see better optimizations for desktop usage.
Of course, as I advocate this splitting of distros, I also hate the way we have 20 distros to do the same thing, and they all do it half-assed...
One can argue they each have strengths and weaknesses, but that's mostly because they haven't merged. ~,^
I'd love to see one primary distro for each class of device/use, along with the plethora of hobby linuxes (which I rather enjoy using from time to time). In the commercial world, tho, the fragementation isn't helping with anything other than increased competition, but we all have enough of that from Microsoft/Sun/Apple already, don't we?
It'd also be great financially to have fewer commercial entities. Take Mandrake and SuSE for example; they both employ developers. How many of those developers end up doing the exact same thing for their companies? Two installer dev teams, two config tool teams, etc. Imagine, if they merged developers, they'd have the income from both companies to pay these developers, but now they can stop duplicating. You get more for the money. And Linux distros aren't exactly a high income source, they need to waste as little as possible.
Of course, why I'm wasting time to say this to a bunch of Slashdot users that will, over all, have absolutely no effect on the situation, is beyond me. ~,^
This may be the encoding - AAC(Mpeg4) is a lossy codec, just like MP3/Ogg, so it will not be a perfect copy of the original mastered track. Of course, it's many many many times smaller tho. ;-)
Slashdot has a previous article on the quality comparisons of AAC/MP3/Ogg, you might want to check that and see if it has any info on your specific problem.
The Itanium2 is fricking fast. I mean, like, whoa kinda fast.
;-)
The Power5 might compete fovarably against the Itanium2, but not PPC 970.
PPC 970 is a consumer class chip tho, while Itanium2/Power5 are, well, not anything you'll find in a consumer's living room.
I'm thinking perhaps we made a mistake releasing this bit on April 1st... ;-)
(Gods I hate this "holiday")
Templates are only bloat when misused. In many cases, your options are to write a template, or cut-and-paste then modify a class/function over and over. You can also write classes that only have template members, so if most of a class is the exact same no matter the data type, you're fine. Templates also let you do things you simply can't do in this low level of a language otherwise (and many high level languages also don't allow) - take a look at what the BOOST library does. There comes a point when you have speed/efficiency/code-size vs. taking 6 years or 6 weeks to code something, and with today's hardware, the later is usually the best choice. Also, templates can be used to generate data, not just code, so where you might have before needed a function call in order to compute a value, a template could turn it into the actual value at compile-time (look at how modern games use templates to generate sin/cos/tan/etc. values for constant inputs).
Bah, you don't belong here, quit wasting our time with your ramblings, you aren't a part of our elite group, you know. ;-)