We are running an account deficit. That said, it's not to the same people whose paper we hold (in most cases; there are some, such as Britain, where both sides hold a chunk of the other's paper, and you can't just write it off).
Russia doesn't have the economic infrastructure or, these days, the world standing to be a real economic superpower. (They weren't much of an economic superpower during the Cold War, either, when compared to the United States.) And frankly, I don't think Europe has the steel in the spine to stand up to their threats (Russia, China-to-a-lesser-extent, Muslim immigration and the recent problems therewith, and even the United States) in any significant capacity.
China--there, you have something. But it's not going to be "divided across China, Europe, and Russia." If anyone "fights," it's going to be a fight between the United States and China, and the rest of the world, like it or not, are the chess pieces. But even then it's not going to be the drag-out fight, because it is mutually beneficial for China and the United States to stay very close trading partners. (For more on this, I suggest Tom Friedman's The World Is Flat--I don't agree with all his conclusions, but it's worthwhile for sure.)
Everybody owes the United States money and the United States owes everybody money. That means a U.S. recession will be a global problem for a very, very long time. Do you realize that China had something like 10% of GDP in Freddie Mac and Frannie Mae? Everybody's money is here.
I think you need to learn more about modern politics and economics before you make sweeping statements.
I believe they're dropping one of their database connectors because another one's better. I'm still stuck in.NET 2.0 land where I am, so I'm not sure. (Not that I like LINQ to begin with. The one.NET feature I really dislike.)
The anti-twitter! Except I don't sockpuppet and point out valid issues and...oh, right, I develop Linux-based open-source software! Holy shit, ain't that amazing?
"Unwanted"? Bullshit. Windows is a better choice here because the teachers and the students are already accustomed to it. How many teachers and students out there want Linux? Very few, I'd wager. The cost savings would fall under the problems of retraining and user resistance/pushback. It's just not a smart move.
Now, if you lot did less evangelization and more making Linux an excellent desktop, maybe people would want it. The contribution of code is worth a lot more than "BAWWW NOBODY WANTS OUR SHIT!".
spend whatever you're saving on some Tux-savvy teachers.
And how many of those exist, exactly? The answer is "not very many."
Face it--Linux remains difficult to use (I say this as an OSS contributor, myself, with a lot of *nix time under my belt). The retraining would be expensive, quite potentially more expensive than any Microsoft infrastructure, and the users would still in all likelihood complain that it's Not Windows. You'd have to have a very compelling reason to force a switch to something nobody uses and nobody wants in order to justify user pushback and retraining costs.
That reason does not, at present, exist. Maybe it will in the future, and I hope it does, but at present it simply isn't there. Sorry. Quit evangelizing and get back to improving the product and maybe that reason will be there.
The only people who "lose" in such a situation are the people who want the kids forced to use Linux instead of what they'd like. Personally, I don't really care what OS people use. If they want OS X, great. Windows, fine. Linux, sure.
Here's the big question, though: do you really think the people who would use these laptops would rather have Linux? Or do you think they'd rather have the Windows environment that they are used to? And if they'd rather have the latter, who the hell are you to try to shove Linux down their throats? You're no better than the Microsoft you insist that you hate, if you're doing that.
Let 'em use what they want, not what makes your nerd penis happy.
I'm not saying GIMP hasn't improved. But it's simply not on the level of Photoshop for professional work when you keep in mind that professionals are accustomed to Photoshop, its workflow, and its quirks. (And until you get an MDI interface for GIMP that doesn't suck ass, it's not gonna get far on Windows at all.) GEGL is nice, but not a winner, at least not yet.
Inkscape has made strides, too. But it isn't Illustrator; that alone is a massive demerit from a professional graphics perspective (fair or not, it's still the case). The workflow sucks in comparison, too--the biggest plus of Adobe is how tightly integrated logical parts of the system are. The Unix Way sucks for desktop apps, I think, and tight integration is good. Workflow is everything.
OpenMoko, Symbian, and Android seem to have much better terms for developers. If you have a killer app and someone will buy the phone for your app, why put yourself at Apples mercy?
The latter part of your "if" statement will revaluate as "false" the vast, vast majority of the time. You go where the market is, and that's Apple (whether we like it or not--I don't like it, but I also don't do handheld development).
For crunching, yes, Linux tends to be used (in part because it makes the boxes doing the crunching cheaper). But the individual artists' workstations are extremely rarely Linux-based, sorry.
I mean--are you seriously going to try to say that Linux beats either platform capable of running Adobe's software when it comes to actually doing the graphics design part of the job? (And if you say GIMP, I'm just going to laugh at you. It's nice if you haven't got anything better, and that's about it. Cinelerra is okay for what it does, but unfortunately for your argument it runs on OS X, too. I'm not enough of a video editing guy to say whether I prefer it over Premiere/After Effects, though. And I will call the men in white coats to take you to be fitted for a very long-sleeved jacket if you try to compare Inkscape with Illustrator.)
There should be both. If somebody doesn't exit college with understanding about the "vocational" stuff, then they won't get hired. I'm not saying it's right, I'm saying how it should be.
And my school, at least, doesn't teach students how to code at all. One kid out of ten might really know why his code broke instead of trying to shotgun debug.
The new IL engine for Mono is a considerable increase in speed. It's not in release, yet.
That said, I am amused that you would consider tracking exact types to be a worse design than Java, which can accidentially shed generic data quite easily...
Well, since I have been using Linux for 10 years, and enjoying the benefits of the contributions of MANY other programmers, I find NOTHING wrong with GPL'ing any application that I write, and have done so.
I consider the GPL unethical, and so I would not do so.
"Internal development" can involve working with contractors, etc., which could very well may be considered distribution. Unlikely, yes, possible, also yes. Better not to bother with the hassle.
I love how disagreeing with you must be trolling though.
I agree that it's not that complex, but I also feel that you should be learning how to think about programming when learning, not how a specific language interacts with the metal.
The 'compile to native' is meaningless. That code is still full of metadata and assorted crud that slows it down, and the optimisations are limited (as the JIT doesn't have much time to work on them).
Go tell that to JRockit or any of the other performance VMs. Take a gander at their benchmarks against C.
Its also stupid (as all software is) so can never know how to generate code as efficiently as I can
Because people don't learn by shooting off their foot, as much as the old graybeards might want them to. Add complexity by adding, say, pointers ("pointers are just manipulable references") later on in the process--don't front-load it with crap that's an artifact of fighting a language rather than learning the principles.
All that crap is meant to be done by the compiler, not by the programmer.
C runs like blue light out of the box, without the tedium you describe. The day that Java does likewise, you'll finally be able to say it's fast.
You AOT your code by passing a flag to javac. Thanks for playing, we have some lovely parting gifts for you.
Meanwhile, it's over a hundred times slower than C.
And it actually has the conveniences and features of a modern language to boot! Holy shit, a tradeoff between features and speed, who'd have thunk it?
Newsflash: speed is no longer everything. It is very much possible to get "good enough" given modern hardware. And save us all your holier-than-thou "YOU ARE ACCEPTING INFERIOR PERFORMANCE YOU CRETIN"--performance doesn't mean much when you've hit that "good enough" plateau and the benefits of writing code in a modern language (runtime checking, exceptions, cross-platform operation) outweigh the extremely minor "MY BENCHMARKS ARE SO OH MY GOD DAMN FAST!" benefit of C.
We are running an account deficit. That said, it's not to the same people whose paper we hold (in most cases; there are some, such as Britain, where both sides hold a chunk of the other's paper, and you can't just write it off).
Russia doesn't have the economic infrastructure or, these days, the world standing to be a real economic superpower. (They weren't much of an economic superpower during the Cold War, either, when compared to the United States.) And frankly, I don't think Europe has the steel in the spine to stand up to their threats (Russia, China-to-a-lesser-extent, Muslim immigration and the recent problems therewith, and even the United States) in any significant capacity.
China--there, you have something. But it's not going to be "divided across China, Europe, and Russia." If anyone "fights," it's going to be a fight between the United States and China, and the rest of the world, like it or not, are the chess pieces. But even then it's not going to be the drag-out fight, because it is mutually beneficial for China and the United States to stay very close trading partners. (For more on this, I suggest Tom Friedman's The World Is Flat--I don't agree with all his conclusions, but it's worthwhile for sure.)
Everybody owes the United States money and the United States owes everybody money. That means a U.S. recession will be a global problem for a very, very long time. Do you realize that China had something like 10% of GDP in Freddie Mac and Frannie Mae? Everybody's money is here.
I think you need to learn more about modern politics and economics before you make sweeping statements.
Well, yeah, I just assumed that nobody would be that dumb, I think. I mean, it isn't even a QUESTION if it's all being routed over a central router.
I would think that "and to each other" would mean connections to other stores as opposed to a central router, but the summary does kind of suck.
I believe they're dropping one of their database connectors because another one's better. I'm still stuck in .NET 2.0 land where I am, so I'm not sure. (Not that I like LINQ to begin with. The one .NET feature I really dislike.)
The anti-twitter! Except I don't sockpuppet and point out valid issues and...oh, right, I develop Linux-based open-source software! Holy shit, ain't that amazing?
It's simple, Linux = free. Windows = cost.
Now when did retraining suddenly become free?
"Here's a government contract to make the FOSS equivalent of Reader Rabbit for students for our schools. We are now taking bids."
So...in other words, Linux isn't free.
I'm kind of curious how much OSS code you actually contribute, as opposed to whining about how bad Microsoft is.
"Unwanted"? Bullshit. Windows is a better choice here because the teachers and the students are already accustomed to it. How many teachers and students out there want Linux? Very few, I'd wager. The cost savings would fall under the problems of retraining and user resistance/pushback. It's just not a smart move.
Now, if you lot did less evangelization and more making Linux an excellent desktop, maybe people would want it. The contribution of code is worth a lot more than "BAWWW NOBODY WANTS OUR SHIT!".
spend whatever you're saving on some Tux-savvy teachers.
And how many of those exist, exactly? The answer is "not very many."
Face it--Linux remains difficult to use (I say this as an OSS contributor, myself, with a lot of *nix time under my belt). The retraining would be expensive, quite potentially more expensive than any Microsoft infrastructure, and the users would still in all likelihood complain that it's Not Windows. You'd have to have a very compelling reason to force a switch to something nobody uses and nobody wants in order to justify user pushback and retraining costs.
That reason does not, at present, exist. Maybe it will in the future, and I hope it does, but at present it simply isn't there. Sorry. Quit evangelizing and get back to improving the product and maybe that reason will be there.
The only people who "lose" in such a situation are the people who want the kids forced to use Linux instead of what they'd like. Personally, I don't really care what OS people use. If they want OS X, great. Windows, fine. Linux, sure.
Here's the big question, though: do you really think the people who would use these laptops would rather have Linux? Or do you think they'd rather have the Windows environment that they are used to? And if they'd rather have the latter, who the hell are you to try to shove Linux down their throats? You're no better than the Microsoft you insist that you hate, if you're doing that.
Let 'em use what they want, not what makes your nerd penis happy.
I'm not saying GIMP hasn't improved. But it's simply not on the level of Photoshop for professional work when you keep in mind that professionals are accustomed to Photoshop, its workflow, and its quirks. (And until you get an MDI interface for GIMP that doesn't suck ass, it's not gonna get far on Windows at all.) GEGL is nice, but not a winner, at least not yet.
Inkscape has made strides, too. But it isn't Illustrator; that alone is a massive demerit from a professional graphics perspective (fair or not, it's still the case). The workflow sucks in comparison, too--the biggest plus of Adobe is how tightly integrated logical parts of the system are. The Unix Way sucks for desktop apps, I think, and tight integration is good. Workflow is everything.
OpenMoko, Symbian, and Android seem to have much better terms for developers. If you have a killer app and someone will buy the phone for your app, why put yourself at Apples mercy?
The latter part of your "if" statement will revaluate as "false" the vast, vast majority of the time. You go where the market is, and that's Apple (whether we like it or not--I don't like it, but I also don't do handheld development).
For crunching, yes, Linux tends to be used (in part because it makes the boxes doing the crunching cheaper). But the individual artists' workstations are extremely rarely Linux-based, sorry.
I mean--are you seriously going to try to say that Linux beats either platform capable of running Adobe's software when it comes to actually doing the graphics design part of the job? (And if you say GIMP, I'm just going to laugh at you. It's nice if you haven't got anything better, and that's about it. Cinelerra is okay for what it does, but unfortunately for your argument it runs on OS X, too. I'm not enough of a video editing guy to say whether I prefer it over Premiere/After Effects, though. And I will call the men in white coats to take you to be fitted for a very long-sleeved jacket if you try to compare Inkscape with Illustrator.)
This is hands-down the best post I've ever seen on the topic of high schools and colleges. Excellent post.
AOT your code. Problem solved, and you still get further on-the-fly speed optimizations via the JVM.
There should be both. If somebody doesn't exit college with understanding about the "vocational" stuff, then they won't get hired. I'm not saying it's right, I'm saying how it should be.
And my school, at least, doesn't teach students how to code at all. One kid out of ten might really know why his code broke instead of trying to shotgun debug.
The new IL engine for Mono is a considerable increase in speed. It's not in release, yet.
That said, I am amused that you would consider tracking exact types to be a worse design than Java, which can accidentially shed generic data quite easily...
My code. ;-) Unlike some folks around here, I fully acknowledge that I don't write perfect code.
(I consider an uncaught exception to be a "crash," such as variable set to null. If it abnormally and abruptly ends the program, it crashed.)
Well, since I have been using Linux for 10 years, and enjoying the benefits of the contributions of MANY other programmers, I find NOTHING wrong with GPL'ing any application that I write, and have done so.
I consider the GPL unethical, and so I would not do so.
My open source code is BSD-licensed.
"Internal development" can involve working with contractors, etc., which could very well may be considered distribution. Unlikely, yes, possible, also yes. Better not to bother with the hassle.
I love how disagreeing with you must be trolling though.
I agree that it's not that complex, but I also feel that you should be learning how to think about programming when learning, not how a specific language interacts with the metal.
The 'compile to native' is meaningless. That code is still full of metadata and assorted crud that slows it down, and the optimisations are limited (as the JIT doesn't have much time to work on them).
Go tell that to JRockit or any of the other performance VMs. Take a gander at their benchmarks against C.
Its also stupid (as all software is) so can never know how to generate code as efficiently as I can
So you don't use gcc -O, right?
Because people don't learn by shooting off their foot, as much as the old graybeards might want them to. Add complexity by adding, say, pointers ("pointers are just manipulable references") later on in the process--don't front-load it with crap that's an artifact of fighting a language rather than learning the principles.
Conspiracy theories are fun.
All that crap is meant to be done by the compiler, not by the programmer.
C runs like blue light out of the box, without the tedium you describe. The day that Java does likewise, you'll finally be able to say it's fast.
You AOT your code by passing a flag to javac. Thanks for playing, we have some lovely parting gifts for you.
Meanwhile, it's over a hundred times slower than C.
And it actually has the conveniences and features of a modern language to boot! Holy shit, a tradeoff between features and speed, who'd have thunk it?
Newsflash: speed is no longer everything. It is very much possible to get "good enough" given modern hardware. And save us all your holier-than-thou "YOU ARE ACCEPTING INFERIOR PERFORMANCE YOU CRETIN"--performance doesn't mean much when you've hit that "good enough" plateau and the benefits of writing code in a modern language (runtime checking, exceptions, cross-platform operation) outweigh the extremely minor "MY BENCHMARKS ARE SO OH MY GOD DAMN FAST!" benefit of C.