I feel the need to provide a flip-side to your story. I also moved into a new house in Northern California last year and decided to use SBC for my DSL service. I experienced no problems whatsoever getting it installed. The service was up and running in under a week and hasn't gone down since.
On that same note, I consider that as one of the better arguments against OO code - It simply does not map well to real-world CPUs, thus introducing inefficiencies in the translation to something the CPU does handle natively.
You're missing one of the most important goals of high-level programming concepts such as OO: to make things easier for the programmer, not the computer. Yes, it's probably less efficient in terms of speed, size, etc., but programmers want tools that are easy for us to map into the actual problem domain we're trying to solve. That's where the real value comes into play.
I've been using Rhapsody for several months now. It's fast, has a decent selection, and you don't have to worry about the RIAA. It also feels more "right", since you're paying for something that obviously has value (10 bucks a month) instead of just getting it for free.
Re:Offtopic post about terminology
on
The Post-OOP Paradigm
·
· Score: 4, Informative
Refactoring is not the same thing as code maintenance. It's actually more akin to code meddling, but done in well-defined, discrete steps, coupled with unit tests so as to minimize the risk.
What grid object? JTable comes close to what you're talking about, but it isn't sortable by default. At any rate, you're right about the speed issue. The claim that Java is dog-slow is simply a myth.
Slashdot Mirror
I'm quite pleased with SBC, but of course YMMV...
On that same note, I consider that as one of the better arguments against OO code - It simply does not map well to real-world CPUs, thus introducing inefficiencies in the translation to something the CPU does handle natively.
You're missing one of the most important goals of high-level programming concepts such as OO: to make things easier for the programmer, not the computer. Yes, it's probably less efficient in terms of speed, size, etc., but programmers want tools that are easy for us to map into the actual problem domain we're trying to solve. That's where the real value comes into play.
I've been using Rhapsody for several months now. It's fast, has a decent selection, and you don't have to worry about the RIAA. It also feels more "right", since you're paying for something that obviously has value (10 bucks a month) instead of just getting it for free.
Refactoring is not the same thing as code maintenance. It's actually more akin to code meddling, but done in well-defined, discrete steps, coupled with unit tests so as to minimize the risk.
What grid object? JTable comes close to what you're talking about, but it isn't sortable by default. At any rate, you're right about the speed issue. The claim that Java is dog-slow is simply a myth.