Whenever I read a story about MS I'd always feel something change within me. It was a sort of nervous tremor, a rush of energy over me. However, it would be gone as quickly as it came. Normally, I don't think too much about it. But after reading this list, I was thrown into a blind fury, consumed by unadulterated rage the likes of which I have never unleashed from my mother's basement. Raising my fist high, I stabbed in the general direction of Redmond with a force of approximately 4.76lb of sheer brutality. The resulting shockwave from my outburst surely disrupted the evil Redmond campus, if but momentarily.
Brothers, we must join together. Let us never forget the list of endless sins that this company has perpetuated. Egregious, dastardly sins that would make their grandmothers cry when they heard them. We must continue to fight this war! Our main offensive shall be the posting of vehement rants on community-driven websites, such as Slashdot. The sheer number of these pointed essays shall bowl over our enemies in no time! This is a battle of numbers: do not feel the need to invoke mighty weapons of logic at every turn! And, also remember, your own stories of woe relating to Microsoft are worth as much, if not more, than logical arguments.
That explanation is REDICULOUS(sic). I have a far more reasonable one, so allow me to elaborate.
Everyone *KNOWS* that Microsoft enjoys being evil precisely because they are evil! Or, at least, that is what people around here have told me. I have a feeling the people in Redmond drive into work like everyone else, but once they get into work, they start smiling. When they finally start working, they are chuckling to themselves: "Haha, its time to SCREW OVER THE WORLD! I can't wait to subtly break everything we've made, and inconvenience hundreds of thousands of users!" Because evil has this amazing ability to attract other forms of evil, thus allowing it to compound faster than one would expect, evil alliances are formed with alarming regularity: "Hmm, its Thursday, we should find a KKK club to sponsor since its been rather quiet this week." Naturally, everyone drives cool cars around the campus. Bill Gates is known to be able to fly, teleport, and destroy someone with a single thought of the mind. But few actually get close enough to him to observe these things, unfortunately.
I am sorry that this information is so long in coming. But I am glad I decided to post it on a site that is a beacon of truth, logic, and unbiased opinions.
Obviously, the last choice is the prudent one here, actually. If you think about it, #1 won't happen at all, #2 is a pain, and #3 is boring. The least this guy can do is buy himself some Internet popularity with the "all-information-except-GPL-based-information-want s-to-be-totally-free" crowd.
Indeed, it is a real shame nobody sees this sort of deception for what it is. There is someone running around defending the fact that the JRE system libraries will be memory resident regardless of whether a Java application is actually used. This is not an optimal solution: the real solution is to reduce the enormous size of the JRE libraries to something more reasonable.
Sun doesn't think much can be done evidently, seeing as they added splash screen support into Java 6 instead of actually fixing the problem. The problem being that they need to load megabytes of code to support the runtime environment when most of it doesn't get used. There's one word for that: bloat.
Awesome, just what I've always wanted. Parsing XML is an extremely important requirement in determining the expressiveness of a language, mind you. Except, they're gonna be screwed when CSV files come back. And don't even get me started on what a pickle they'll be in when those.DAT files return to claim their rightful place!
As such, I move to recommend that Java incorporate support for parsing CSV and DAT files into the language.
It is obvious you don't work in this industry if you say things like that. Fired for writing code that hogged processor resources? What sort of parallel universe do you inhabit? Rarely are programmers fired for making egregious mistakes.
That is pretty nifty. Of course, you have to have the WAVs laying around. That said, I tend to undercompress my music well beyond the perceptual threshold so I won't have to re-rip it in the future.
Funny how if you replace all instances of Java with Microsoft, your comment wouldn't be so well received, and several people would be pointing out your bandwagon fallacy.
Did you try a blind test? If you play the CD with the expectation that it will sound better and be less tiring, that's most likely what you will experience. You need to get two copies of the same song (an older one and a modern, squashed remastering), sample them to lossless audio files and get a friend to adjust the volume so that the newer remastering is not obviously louder. Then write a short program to play one of the two at random and ask you which one you think it is. Then you will find out whether you can reliably distinguish between them.
No, I didn't. The amount of work required to pull off such a feat isn't worth the Internet-credibility I'd get for having said, "I double-blind tested this with N = 500, theta =.395, and $RandomGreekLetter = $TechnicalLookingNumber." If I felt the need to prove this sort of thing, I could have simply forged the test results already. (And if I had that sort of time to waste, I'd be on HydrogenAudio.)
Dynamic range is easily apparent to all but the worst ears, and for those it isn't apparent to, you can simply look at how saturated the Winamp spectrum analyzer is on average. No matter how bad your ears are, you should be able to see the difference between Californication and a good classical recording.
I listen mostly to modern rock. I was curious to see how much I'd gotten used to the compression of modern albums. After reading the Wikipedia article, I saw they mentioned that Superunknown, so I pulled it up. Keep in mind I haven't listened to it in several years.
Wow! I'd forgotten music could sound this good! And I'm not even a huge fan of grunge these days. The lack of compression in the music seems to make it less tiring to listen to. The soundstage is bigger, the music seems to breathe a little more, and it generally ebbs and flows more. I'm listening on a pair of $30 Sennheiser headphones, not audiophile-grade equipment by any means.
Once again, we see the danger of pandering to the lowest common denonimator: you end up pissing everyone off eventually. It is a shame that we persist in thinking this is necessary. Of course, it is difficult to be surprised by it, given that the music industry is about selling the performer as a product instead of producing art.
Why are you using code generation tools to write code that is performance sensitive? Of course you avoid indirection at all costs in code that has to be fast. It would have been equally as slow if you had used pure OO code in C.
Using existing schemas makes things more complicated sometimes. But don't even try to tell me that coding up the XML configuration file and setting up inheritance in Hibernate is somehow more intuitive than just doing it yourself with JDBC. If someone else had to support the raw JDBC code, they could at least step through what you wrote. This isn't quite the case with Hibernate, you just see the end result.
Need to use multiple database vendors with one code base? Fine, use stored procedures, standard SQL, or abstract the difference away.
I enabled this on my Linux box, and it completely flies! Vista can't hold a candle to the speed I'm experiencing now! Just another great reason to use Linux!
Somebody needs to drag the people who make these things in a room, erase their memories, and make them use what they have created. Perhaps then they can start to feel how asinine they can be sometimes. It is as if they get off on how many design patterns, random XML config files, and other "best practices" they can cram into a single framework. "We're switching to using a BuilderFactoryGatewayStrategyFacade." Thanks for the heads-up guys, we were all dying to know exactly how you implemented it! (Don't forget to scatter pattern names all over your code. People have to know you're using them!) All I want to do is integrate such and such framework in with my program. But, no, I have to read the documentation that describes the problem and how exactly to use the framework. Inevitably, they begin spouting off about how "elegant" it is that you can configure exactly which IntFactory to use by hard-coding the classname in a mandatory configuration file that is prone to getting lost at deployment time. (Remember, making objects with just the new operator is a classic beginner's mistake, don't fall prey!)
The end result is you end up with what should be a fairly simple task (like OO-relational mapping) have 400 page manuals because it ends up doing every little thing that people want to do. In the time it takes you to choose the right framework, download and install the binaries, wade through the required config files, sift through the quickstart, and actually get familiar with how it is done, you could have just written and tested the tedious JDBC code to load and unload an object from the database.
But, why do that? There's no hype around that! You're not REALLY an enterprise architect until you have twenty different config files that need to be present just to run your product! If it is an enterprise product, it shouldn't be simple to configure!
All of these products do serve legitimate needs. But the obsessive over-engineering that surrounds them and the religious fervor by which they are declared Good (despite violating the principle of least surprise at every turn) point to fear. A fear that the code you're writing just isn't good enough somehow. The fear that your code is too simple, too straightforward. A worry that that requirement you're meeting is mission-critical, and, mishandled, could threaten the stability of the entire system. This isn't usually the case. It would seem that Java's simplicity sort of drives its hardcore users mad after awhile. What it lacks in expressiveness, people try to make up for by inane configuration and extensibility instead of just sitting down and Getting The Damn Thing Done. Sure, the code is boring. The best code is anything but glamorous.
Fallacy-ridden arguments and ridiculous drawn out appeals to emotion is a more accurate representation. Remember: you should be able to do whatever you want with information, except if its the GPL! Then you have to follow the GPL!
Slashdot Mirror
A dreadful version of Netscape Navigator?
Actually, it was entirely random and supposed to denote a very small amount of force. YMMV when you try this at home, but IANAL.
Whenever I read a story about MS I'd always feel something change within me. It was a sort of nervous tremor, a rush of energy over me. However, it would be gone as quickly as it came. Normally, I don't think too much about it. But after reading this list, I was thrown into a blind fury, consumed by unadulterated rage the likes of which I have never unleashed from my mother's basement. Raising my fist high, I stabbed in the general direction of Redmond with a force of approximately 4.76lb of sheer brutality. The resulting shockwave from my outburst surely disrupted the evil Redmond campus, if but momentarily.
Brothers, we must join together. Let us never forget the list of endless sins that this company has perpetuated. Egregious, dastardly sins that would make their grandmothers cry when they heard them. We must continue to fight this war! Our main offensive shall be the posting of vehement rants on community-driven websites, such as Slashdot. The sheer number of these pointed essays shall bowl over our enemies in no time! This is a battle of numbers: do not feel the need to invoke mighty weapons of logic at every turn! And, also remember, your own stories of woe relating to Microsoft are worth as much, if not more, than logical arguments.
I trust you will not let me down.
That explanation is REDICULOUS(sic). I have a far more reasonable one, so allow me to elaborate.
Everyone *KNOWS* that Microsoft enjoys being evil precisely because they are evil! Or, at least, that is what people around here have told me. I have a feeling the people in Redmond drive into work like everyone else, but once they get into work, they start smiling. When they finally start working, they are chuckling to themselves: "Haha, its time to SCREW OVER THE WORLD! I can't wait to subtly break everything we've made, and inconvenience hundreds of thousands of users!" Because evil has this amazing ability to attract other forms of evil, thus allowing it to compound faster than one would expect, evil alliances are formed with alarming regularity: "Hmm, its Thursday, we should find a KKK club to sponsor since its been rather quiet this week." Naturally, everyone drives cool cars around the campus. Bill Gates is known to be able to fly, teleport, and destroy someone with a single thought of the mind. But few actually get close enough to him to observe these things, unfortunately.
I am sorry that this information is so long in coming. But I am glad I decided to post it on a site that is a beacon of truth, logic, and unbiased opinions.
Sure thing, Sparky.
Obviously, the last choice is the prudent one here, actually. If you think about it, #1 won't happen at all, #2 is a pain, and #3 is boring. The least this guy can do is buy himself some Internet popularity with the "all-information-except-GPL-based-information-want s-to-be-totally-free" crowd.
Who can blame him?
Indeed, it is a real shame nobody sees this sort of deception for what it is. There is someone running around defending the fact that the JRE system libraries will be memory resident regardless of whether a Java application is actually used. This is not an optimal solution: the real solution is to reduce the enormous size of the JRE libraries to something more reasonable.
Sun doesn't think much can be done evidently, seeing as they added splash screen support into Java 6 instead of actually fixing the problem. The problem being that they need to load megabytes of code to support the runtime environment when most of it doesn't get used. There's one word for that: bloat.
Awesome, just what I've always wanted. Parsing XML is an extremely important requirement in determining the expressiveness of a language, mind you. Except, they're gonna be screwed when CSV files come back. And don't even get me started on what a pickle they'll be in when those .DAT files return to claim their rightful place!
As such, I move to recommend that Java incorporate support for parsing CSV and DAT files into the language.
It is obvious you don't work in this industry if you say things like that. Fired for writing code that hogged processor resources? What sort of parallel universe do you inhabit? Rarely are programmers fired for making egregious mistakes.
Evidently my point was too subtle for you. Pity.
It must suck to bring that sense of resignation to your job everyday.
That is pretty nifty. Of course, you have to have the WAVs laying around. That said, I tend to undercompress my music well beyond the perceptual threshold so I won't have to re-rip it in the future.
Funny how if you replace all instances of Java with Microsoft, your comment wouldn't be so well received, and several people would be pointing out your bandwagon fallacy.
Just something to think about.
No, I didn't. The amount of work required to pull off such a feat isn't worth the Internet-credibility I'd get for having said, "I double-blind tested this with N = 500, theta =
Dynamic range is easily apparent to all but the worst ears, and for those it isn't apparent to, you can simply look at how saturated the Winamp spectrum analyzer is on average. No matter how bad your ears are, you should be able to see the difference between Californication and a good classical recording.
I listen mostly to modern rock. I was curious to see how much I'd gotten used to the compression of modern albums. After reading the Wikipedia article, I saw they mentioned that Superunknown, so I pulled it up. Keep in mind I haven't listened to it in several years.
Wow! I'd forgotten music could sound this good! And I'm not even a huge fan of grunge these days. The lack of compression in the music seems to make it less tiring to listen to. The soundstage is bigger, the music seems to breathe a little more, and it generally ebbs and flows more. I'm listening on a pair of $30 Sennheiser headphones, not audiophile-grade equipment by any means.
Once again, we see the danger of pandering to the lowest common denonimator: you end up pissing everyone off eventually. It is a shame that we persist in thinking this is necessary. Of course, it is difficult to be surprised by it, given that the music industry is about selling the performer as a product instead of producing art.
Godspeed to you! I heard he was eagerly awaiting RobBebop's opinion on his choice of distro!
What was with all that? You're not supposed to take twitter seriously. Everyone around here just smiles and nods whenever he posts something.
Yeah, but most slashdotters don't know what a context switch is. :)
Hahaha, this is so dead-on.
Too many programmers out there that think they can write middleware, when oftentimes the best thing to do is just to Finish The Damn Project.
Why are you using code generation tools to write code that is performance sensitive? Of course you avoid indirection at all costs in code that has to be fast. It would have been equally as slow if you had used pure OO code in C.
Using existing schemas makes things more complicated sometimes. But don't even try to tell me that coding up the XML configuration file and setting up inheritance in Hibernate is somehow more intuitive than just doing it yourself with JDBC. If someone else had to support the raw JDBC code, they could at least step through what you wrote. This isn't quite the case with Hibernate, you just see the end result.
Need to use multiple database vendors with one code base? Fine, use stored procedures, standard SQL, or abstract the difference away.
I enabled this on my Linux box, and it completely flies! Vista can't hold a candle to the speed I'm experiencing now! Just another great reason to use Linux!
Ugh, Java frameworks.
Somebody needs to drag the people who make these things in a room, erase their memories, and make them use what they have created. Perhaps then they can start to feel how asinine they can be sometimes. It is as if they get off on how many design patterns, random XML config files, and other "best practices" they can cram into a single framework. "We're switching to using a BuilderFactoryGatewayStrategyFacade." Thanks for the heads-up guys, we were all dying to know exactly how you implemented it! (Don't forget to scatter pattern names all over your code. People have to know you're using them!) All I want to do is integrate such and such framework in with my program. But, no, I have to read the documentation that describes the problem and how exactly to use the framework. Inevitably, they begin spouting off about how "elegant" it is that you can configure exactly which IntFactory to use by hard-coding the classname in a mandatory configuration file that is prone to getting lost at deployment time. (Remember, making objects with just the new operator is a classic beginner's mistake, don't fall prey!)
The end result is you end up with what should be a fairly simple task (like OO-relational mapping) have 400 page manuals because it ends up doing every little thing that people want to do. In the time it takes you to choose the right framework, download and install the binaries, wade through the required config files, sift through the quickstart, and actually get familiar with how it is done, you could have just written and tested the tedious JDBC code to load and unload an object from the database.
But, why do that? There's no hype around that! You're not REALLY an enterprise architect until you have twenty different config files that need to be present just to run your product! If it is an enterprise product, it shouldn't be simple to configure!
All of these products do serve legitimate needs. But the obsessive over-engineering that surrounds them and the religious fervor by which they are declared Good (despite violating the principle of least surprise at every turn) point to fear. A fear that the code you're writing just isn't good enough somehow. The fear that your code is too simple, too straightforward. A worry that that requirement you're meeting is mission-critical, and, mishandled, could threaten the stability of the entire system. This isn't usually the case. It would seem that Java's simplicity sort of drives its hardcore users mad after awhile. What it lacks in expressiveness, people try to make up for by inane configuration and extensibility instead of just sitting down and Getting The Damn Thing Done. Sure, the code is boring. The best code is anything but glamorous.
Fallacy-ridden arguments and ridiculous drawn out appeals to emotion is a more accurate representation. Remember: you should be able to do whatever you want with information, except if its the GPL! Then you have to follow the GPL!
Well done, you win.
But, know this: you haven't seen the last of me! You shall rue the day you caught me in my own logic trap!