Oh, I've crossed the barrier. As I said, my app is running on thousands of desktops and most of them do not know it's a Java app. It's actually a Java-Cocoa app and was working just fine until Apple removed the Java-Cocoa bridge from Snow Leopard. Even with the extra pain of now writing JNI code to bridge from Objective-C to Java using Interface Builder is a lot more fun and gives better results than NetBeans/Matisse.
The point, though, is that it is not easy to write a Java desktop app that people don't want to run away from. Sun has been pushing this Write Once, Run Everywhere idea for years now and it's a retarded idea for commercial developers. The only reason Sun pushes it is that they hope that if they can sucker people into writing an app that "runs everywhere" that just maybe it will run on Solaris because who would target Solaris for a desktop app otherwise?
Java has so many advantages over C/C++/Objective-C that it's a damn shame that it takes so much work to make a decent desktop app.
I like Java. I do a lot of work in Java. I even ship an application written in Java that is installed on thousands of desktops worldwide. So, you can probably count me as a Java fan boi but I gotta ask:
Why the hell is it that after 14 years of Java we still can't get a Java app that looks and feels like a native app on Windows or Linux or even Solaris for god's sake. Why does anyone trying to ship a Java app either have to make the user jump through hoops installing JRE's and JDK's and other nonsense or has to code up special installers and.exe's to launch the JVM?
I ship an app on the Mac written in Java. Despite Apple's current pull back on their Java support, at least a Java app gets packaged up the same way as a native app and the Java runtime is installed as part of the OS.
Now, I understand that Sun has no control over Windows, but could we at least define a standard location for the JRE? Could we have a standard Java launcher that doesn't involve command line goo?
And as for Solaris - you still have to launch Java apps by running "java" from the shell or inside a script. Bourne shell scripts have been executables for 30 years, why the hell can't Java apps be executables as well? Solaris is Sun's OS. Java should shine and be the recommended language for everything.
And don't even get me started on "Java Web Start". Half the browsers leave little.jnlp turds all over your download folder or desktop.
Sun has simply fallen down with Java as a desktop platform. It's hard to deliver apps written in Java to customers, period. Swing is *still* ugly - and that's comparing it up against Windows UI's.
And there's still not a decent GUI builder for Swing. The NeXTStep GUI builder in 1997 worked better than Netbeans does today. Every time I add a component things it's a 50-50 chance that my whole layout will be destroyed as Netbeans moves things around randomly.
Sun, you have just failed so badly at making Java a viable desktop language. Maybe Oracle can clean up your mess but I doubt it.
One would think. I used to work at a major defense contractor that dealt with nuclear materials. There was a five foot high fence around the facility and I knew people who had jumped it (without triggering a security alert) when they had forgotten their badges. Oh, and cars used to get stolen out of the "secure" parking lot on a regular basis.
Gambling games can be defined as being "zero-sum" along with the random chance part. Zero-sum means that the amount of money that comes out is the same as the amount of money that goes in.
Stocks are supposed to be non-zero-sum, preferable a positive-sum game in that more money can come out than was put it (this is why it's called investment).
However, this positive-sum aspect requires either dividends to be paid or stock buybacks or some other mechanism that transfers money from the company coffers back to the stockholders. Tech companies have avoided dividends like the plague for a long time, arguing that they are "growth stocks" where the payback comes in the growth in the value of the company. However, in order to get the benefits of that growth you have to sell the stock to someone else. You do not actually share in the earnings of the company.
Stocks that do not pay dividends or have stock buybacks are a zero-sum game and I would argue that they are no better than gambling and possibly could be defined as a Ponzi scheme.
Sounds like 100Base-T since you only have a 20 Mbit connection coming in. You can practically run that over tin cans and string.
If you're doing a run of any length it's usually pretty hard to estimate just how long it's going to be so cutting the cable to length makes more sense to me than buying a much longer pre-terminated cable and either having a bunch left over coiled in the overhead or underestimating and coming up short.
I don't need to because there are hundreds of code reviews ongoing on the Linux kernel code all the time.
The key word here is Open Source. There are enough paranoids out there using the Linux kernel that I'm sure just about everything gets plenty of scrutiny. If you are a party with something to worry about, like the Tibetan Gov't in Exile you could get a few people together to vet the code that goes into your own build and monitor the patches that go in. That is something you cannot do with Windows or any other closed source product (that include Mac OS X, really, as what comes from Apple has a bunch of closed source extensions). Doing your own security review would be difficult but it is possible.
If I had to bet my life on something it sure wouldn't be Windows.
Kernel internals don't get mucked with all the damn time. I don't do as much kernel work as I used to (and I've done it on 4.3 BSD, Unicos, IRIX, SunOS, Solaris, Linux, Mac OS X) but I hit it often enough with Linux. I was trying to get some slightly older Linux drivers to work but some genius had decided to rename all of the logging macros so that drivers that weren't being actively maintained had been broken.
Cisco's trying to become a server company. Sun has a lot of credibility in that market, some interesting hardware and, yes Virginia, Solaris is more stable than Linux.
Heh - I worked for Celerity and then FPS. I left when Cray purchased FPS. We were saying, during the negotiations with Cray, that if we couldn't sell the SPARC machines with a Cray label on them....
Turned out that the only way to sell SPARC boxes was to put a Sun label on them and that's not even true anymore. Unfortunately the Intel boys have won. I wouldn't mind so much if the x86 instruction set wasn't such an abortion.
Yes, the policy directive should take effect immediately. However, policy is just that, policy. It's a series of directives that are then carried out by people. It's not like pushing a patch out to a bunch of computers. Each of those people carrying out the policy will bring their own interpretation, prejudices, etc. to their execution.
Now, the next step after you make policy is enforcing policy. This is where Rahm Emmanuel or one of his subordinates (we don't have a Commerce Secretary at the moment) comes by and applies the hammer to Ms Sudo-Bredie and says get in line with the policy or you can go down to the unemployment office this afternoon.
Policy without enforcement is just hot air. I'm not apologizing for Obama, I'm observing the reality of the world. Absolutely looking at what Obama does is the way to judge him. We just haven't seen if this is the White House yet or just bureaucratic intertia.
The FOIA denial letter is signed by Camen Suro-Bredie. From what I can find, she has been in the USTR office since at least 2004. While President Obama has sent down an executive order that FOIA requests should be responded to in preference to withholding information, that is a new policy and it is going to take some time to get everyone in line with it.
It will be instructive to see how this is handled now that it has been brought out into the daylight. If the Obama Administration overrides Ms Suro-Bredie and releases the treaty that would be a very positive step.
Kanji input on the iPhone is as good as the other cell phones.
Sorry, that should have been isn't, not is.
Typing in Japanese is damn weird and requires a lot of software support to be anywhere near usable.
As you may know, Japanese has four different symbol sets that are mixed together. There are hiragana and katakana which are syllable based. One character represents a syllable, for example "ku". Hiragana covers all of the syllables needed for Japanese words. Katakana is used for "foreign words" and emphasis and could be looked at like capital letters in English except that it has some extra syllables that foreign words use but Japanese never does. Also, the English alphabet is used and is called "Romaji". Then, there's Kanji which are ideographs and are basically Chinese characters, but used with Japanese words and I'm sure there are some that are only used in Japanese.
In constructing a sentence it's quite common to mix all four of these together. Generally any Japanese sentence will mix hiragana and kanji unless it's very simple.
When inputting kanji you can't just push a key for the character since there are thousands of them. The common solution is to enter the word as it is pronounced, in either English characters or hiragana. I have seen English characters used the most but I may be prejudiced since the people I work with are very used to using computers and English text. As you enter the word, the computer starts looking up possible matches and shows you a popup list you can choose from if you like. To additionally confuse things, Japanese has a *lot* of homonyms. So, you typically get quite a few possible characters.
So, if you watch someone typing Japanese on a Mac (Windows is similar but uses some different keys I think) you'll see them typing English letters which are not echoed on the screen, reading back hiragana characters initially, whacking the space bar every now and then to have the computer show a list of possible kanjis, and then the enter key to accept the kanji and move to the next one. In addition you'll see them switching character sets since they may want to enter something in Roman characters, etc.
So, especially on something where you're typing with your thumbs, the ability of the computer to track what you're writing about and present you with the right kanji as the first pick in the list can make your typing a lot more pleasant. Unfortunately, even full-blown Mac OS does not have the best dictionary - it's available as an after-market add-on. I don't think anything similar has surfaced for the iPhone yet.
Also, as some other people mentioned, Japanese cell phones have an array of cutesy characters that people here love to insert into their text messages. My wife exchanges emails with all of the other moms at our kids' kindergarten. My wife learned to use email as part of her job in a US corporation and refrains from smiley faces, hearts, etc. The other moms said that her email was "too harsh" and she really needed to include those. I'm pretty sure the iPhone was missing those cutesy characters initially and I'm not sure if they've been added yet.
And, of course, there's still the problem that the iPhone can be a sucky phone. One of my friends has an iPhone here in Tokyo but he has kept his DoCoMo phone because it works a lot better as a phone.
Kanji input on the iPhone is as good as the other cell phones. Given that text messaging is a major use for cell phones, this is a big problem.
The UI on the iPhone blows away Japanese cell phones (I live in Japan and I use them all the time). The reason the iPhone isn't taking off as well in Japan is the kanji support and Softbank's piss poor marketing support. They have not done a good job of differentiating the iPhone from the other touch screen phones and, in fact, SoftBank carries several other touch screen phones which is confusing.
A friend of mine had a mouse problem and bought some glue traps. Well, she gets a mouse stuck in one but it's not dead, of course. The things struggling and squeaking and just generally being miserable and she can't figure out what to do with it. She finally took it out and ran it over with her car.
As we consume more IT resources the number of workers per resource unit has to fall - or we're going to wind up spending our entire budget on IT. The question for IT workers is whether the amount of IT workers has peaked or not. I don't think it has yet.
The first computer I worked with was a PDP 11/70. Less than 1 MIP and we had a dedicated operator. By that measure my laptop needs several thousand support personnel.
However, we spent close to $500,000 (in 1981 dollars) for that system. It supported 32 terminals. Today, I could put together 32 desktops plus a server system for less than $100,000 but would probably still want to have a dedicated IT support person for that many desktops (given that it's a small company and that's all of our IT infrastructure - larger companies get by with fewer desktop support people due to economies of scale).
My wife worked at Oracle here in Japan for a while. The director of the Oracle certificate program once set a long term goal of, I think, 5 million certified Oracle DBA's in Japan. Now, Japan has a total population of about 128 million so he was setting a goal of 4 out of every 100 people to be Oracle DBA's. Absolutely ludicrous.
Personnel are now the largest cost in IT. Anything that reduces IT costs will be reducing personnel costs. The real question is whether the IT budget overall is shrinking or growing.
The interesting long term question is whether IT will mature like power or plumbing to the point where an average company does not keep IT specialists on staff but just calls them in as needed. I would argue that it is different since IT done properly is a strategic asset customized to your company somehow but time will tell.
Interviews are a very limited block of time. Most people don't block more than an hour per interviewer. Subtract out time for pleasantries, wrapping up and you're down to 45 minutes. Those are very important minutes. Besides, you might actually learn something in university. I know I did.
One of the reasons why employers are often unwilling to hire people without degrees is that a lot of people who believe they are "too smart for college" really aren't.
By the time I graduated from college I had a number of years as a senior developer at a well respected company. When I went to my first job after college I doubled my salary. I think my time in school paid off well, and I enjoyed it.
I've known many people who were great sys admins or developers who did not have degrees so it is possible. However, it is much easier to get a job if you have the degree. Every time you do a job interview you will spend 5-10 minutes explaining why you don't have a degree - that is, if they even bother to call you in. That's 5-10 minutes that you're spending getting yourself up to the level of the other applicants that you could have spent putting yourself above the level of the other applicants.
Your pay level may suffer throughout your career as well. When I was in college, I had a job as a developer at a computer company. I switched from a full-time student, part-time developer to being a part-time student, full-time developer. They even asked me once to drop out to devote more time to the job. One day they hired a new developer, fresh out of college. She was quite sharp but had 0 experience. One day it came out over lunch how much she was making and it was more than me. I asked my boss why and he replied "She has her degree". Needless to say, I didn't entertain any more requests to drop out and work more.
Slashdot Mirror
Oh, I've crossed the barrier. As I said, my app is running on thousands of desktops and most of them do not know it's a Java app. It's actually a Java-Cocoa app and was working just fine until Apple removed the Java-Cocoa bridge from Snow Leopard. Even with the extra pain of now writing JNI code to bridge from Objective-C to Java using Interface Builder is a lot more fun and gives better results than NetBeans/Matisse.
The point, though, is that it is not easy to write a Java desktop app that people don't want to run away from. Sun has been pushing this Write Once, Run Everywhere idea for years now and it's a retarded idea for commercial developers. The only reason Sun pushes it is that they hope that if they can sucker people into writing an app that "runs everywhere" that just maybe it will run on Solaris because who would target Solaris for a desktop app otherwise?
Java has so many advantages over C/C++/Objective-C that it's a damn shame that it takes so much work to make a decent desktop app.
I like Java. I do a lot of work in Java. I even ship an application written in Java that is installed on thousands of desktops worldwide. So, you can probably count me as a Java fan boi but I gotta ask:
Why the hell is it that after 14 years of Java we still can't get a Java app that looks and feels like a native app on Windows or Linux or even Solaris for god's sake. Why does anyone trying to ship a Java app either have to make the user jump through hoops installing JRE's and JDK's and other nonsense or has to code up special installers and .exe's to launch the JVM?
I ship an app on the Mac written in Java. Despite Apple's current pull back on their Java support, at least a Java app gets packaged up the same way as a native app and the Java runtime is installed as part of the OS.
Now, I understand that Sun has no control over Windows, but could we at least define a standard location for the JRE? Could we have a standard Java launcher that doesn't involve command line goo?
And as for Solaris - you still have to launch Java apps by running "java" from the shell or inside a script. Bourne shell scripts have been executables for 30 years, why the hell can't Java apps be executables as well? Solaris is Sun's OS. Java should shine and be the recommended language for everything.
And don't even get me started on "Java Web Start". Half the browsers leave little .jnlp turds all over your download folder or desktop.
Sun has simply fallen down with Java as a desktop platform. It's hard to deliver apps written in Java to customers, period. Swing is *still* ugly - and that's comparing it up against Windows UI's.
And there's still not a decent GUI builder for Swing. The NeXTStep GUI builder in 1997 worked better than Netbeans does today. Every time I add a component things it's a 50-50 chance that my whole layout will be destroyed as Netbeans moves things around randomly.
Sun, you have just failed so badly at making Java a viable desktop language. Maybe Oracle can clean up your mess but I doubt it.
Sounds like that is what he did. But you have to start somewhere and he wasn't up to going to and from work on the bike.
Maybe he didn't want to get to work all sweaty?
Unix guru to Wally: Here's a nickel kid, get yourself a better computer
http://tomayko.com/writings/that-dilbert-cartoon
There is a lens in the plastic case but nothing behind it.
That doesn't sound very useful. How can you tell the camera has been removed quickly?
One would think. I used to work at a major defense contractor that dealt with nuclear materials. There was a five foot high fence around the facility and I knew people who had jumped it (without triggering a security alert) when they had forgotten their badges. Oh, and cars used to get stolen out of the "secure" parking lot on a regular basis.
Gambling games can be defined as being "zero-sum" along with the random chance part. Zero-sum means that the amount of money that comes out is the same as the amount of money that goes in.
Stocks are supposed to be non-zero-sum, preferable a positive-sum game in that more money can come out than was put it (this is why it's called investment).
However, this positive-sum aspect requires either dividends to be paid or stock buybacks or some other mechanism that transfers money from the company coffers back to the stockholders. Tech companies have avoided dividends like the plague for a long time, arguing that they are "growth stocks" where the payback comes in the growth in the value of the company. However, in order to get the benefits of that growth you have to sell the stock to someone else. You do not actually share in the earnings of the company.
Stocks that do not pay dividends or have stock buybacks are a zero-sum game and I would argue that they are no better than gambling and possibly could be defined as a Ponzi scheme.
Sounds like 100Base-T since you only have a 20 Mbit connection coming in. You can practically run that over tin cans and string.
If you're doing a run of any length it's usually pretty hard to estimate just how long it's going to be so cutting the cable to length makes more sense to me than buying a much longer pre-terminated cable and either having a bunch left over coiled in the overhead or underestimating and coming up short.
Earthlink? AOL? "...the late '90s"? Where the fuck were you in 1990 when I was downloading pr0n from a Usenet dialup BBS? Huh?
Laughing at the johnnie-come-latelies and enjoying our Ethernet net link to CERFnet on the floor above us.
I don't need to because there are hundreds of code reviews ongoing on the Linux kernel code all the time.
The key word here is Open Source. There are enough paranoids out there using the Linux kernel that I'm sure just about everything gets plenty of scrutiny. If you are a party with something to worry about, like the Tibetan Gov't in Exile you could get a few people together to vet the code that goes into your own build and monitor the patches that go in. That is something you cannot do with Windows or any other closed source product (that include Mac OS X, really, as what comes from Apple has a bunch of closed source extensions). Doing your own security review would be difficult but it is possible.
If I had to bet my life on something it sure wouldn't be Windows.
Kernel internals don't get mucked with all the damn time. I don't do as much kernel work as I used to (and I've done it on 4.3 BSD, Unicos, IRIX, SunOS, Solaris, Linux, Mac OS X) but I hit it often enough with Linux. I was trying to get some slightly older Linux drivers to work but some genius had decided to rename all of the logging macros so that drivers that weren't being actively maintained had been broken.
Cisco's trying to become a server company. Sun has a lot of credibility in that market, some interesting hardware and, yes Virginia, Solaris is more stable than Linux.
Heh - I worked for Celerity and then FPS. I left when Cray purchased FPS. We were saying, during the negotiations with Cray, that if we couldn't sell the SPARC machines with a Cray label on them....
Turned out that the only way to sell SPARC boxes was to put a Sun label on them and that's not even true anymore. Unfortunately the Intel boys have won. I wouldn't mind so much if the x86 instruction set wasn't such an abortion.
Being a bureaucrat for 30 years marks her as a career bureaucrat.
Obviously you've never managed people.
Yes, the policy directive should take effect immediately. However, policy is just that, policy. It's a series of directives that are then carried out by people. It's not like pushing a patch out to a bunch of computers. Each of those people carrying out the policy will bring their own interpretation, prejudices, etc. to their execution.
Now, the next step after you make policy is enforcing policy. This is where Rahm Emmanuel or one of his subordinates (we don't have a Commerce Secretary at the moment) comes by and applies the hammer to Ms Sudo-Bredie and says get in line with the policy or you can go down to the unemployment office this afternoon.
Policy without enforcement is just hot air. I'm not apologizing for Obama, I'm observing the reality of the world. Absolutely looking at what Obama does is the way to judge him. We just haven't seen if this is the White House yet or just bureaucratic intertia.
The FOIA denial letter is signed by Camen Suro-Bredie. From what I can find, she has been in the USTR office since at least 2004. While President Obama has sent down an executive order that FOIA requests should be responded to in preference to withholding information, that is a new policy and it is going to take some time to get everyone in line with it.
It will be instructive to see how this is handled now that it has been brought out into the daylight. If the Obama Administration overrides Ms Suro-Bredie and releases the treaty that would be a very positive step.
Kanji input on the iPhone is as good as the other cell phones.
Sorry, that should have been isn't, not is.
Typing in Japanese is damn weird and requires a lot of software support to be anywhere near usable.
As you may know, Japanese has four different symbol sets that are mixed together. There are hiragana and katakana which are syllable based. One character represents a syllable, for example "ku". Hiragana covers all of the syllables needed for Japanese words. Katakana is used for "foreign words" and emphasis and could be looked at like capital letters in English except that it has some extra syllables that foreign words use but Japanese never does. Also, the English alphabet is used and is called "Romaji". Then, there's Kanji which are ideographs and are basically Chinese characters, but used with Japanese words and I'm sure there are some that are only used in Japanese.
In constructing a sentence it's quite common to mix all four of these together. Generally any Japanese sentence will mix hiragana and kanji unless it's very simple.
When inputting kanji you can't just push a key for the character since there are thousands of them. The common solution is to enter the word as it is pronounced, in either English characters or hiragana. I have seen English characters used the most but I may be prejudiced since the people I work with are very used to using computers and English text. As you enter the word, the computer starts looking up possible matches and shows you a popup list you can choose from if you like. To additionally confuse things, Japanese has a *lot* of homonyms. So, you typically get quite a few possible characters.
So, if you watch someone typing Japanese on a Mac (Windows is similar but uses some different keys I think) you'll see them typing English letters which are not echoed on the screen, reading back hiragana characters initially, whacking the space bar every now and then to have the computer show a list of possible kanjis, and then the enter key to accept the kanji and move to the next one. In addition you'll see them switching character sets since they may want to enter something in Roman characters, etc.
So, especially on something where you're typing with your thumbs, the ability of the computer to track what you're writing about and present you with the right kanji as the first pick in the list can make your typing a lot more pleasant. Unfortunately, even full-blown Mac OS does not have the best dictionary - it's available as an after-market add-on. I don't think anything similar has surfaced for the iPhone yet.
Also, as some other people mentioned, Japanese cell phones have an array of cutesy characters that people here love to insert into their text messages. My wife exchanges emails with all of the other moms at our kids' kindergarten. My wife learned to use email as part of her job in a US corporation and refrains from smiley faces, hearts, etc. The other moms said that her email was "too harsh" and she really needed to include those. I'm pretty sure the iPhone was missing those cutesy characters initially and I'm not sure if they've been added yet.
And, of course, there's still the problem that the iPhone can be a sucky phone. One of my friends has an iPhone here in Tokyo but he has kept his DoCoMo phone because it works a lot better as a phone.
You mean those USB ports that the iPod dock connector connects to?
Kanji input on the iPhone is as good as the other cell phones. Given that text messaging is a major use for cell phones, this is a big problem.
The UI on the iPhone blows away Japanese cell phones (I live in Japan and I use them all the time). The reason the iPhone isn't taking off as well in Japan is the kanji support and Softbank's piss poor marketing support. They have not done a good job of differentiating the iPhone from the other touch screen phones and, in fact, SoftBank carries several other touch screen phones which is confusing.
A friend of mine had a mouse problem and bought some glue traps. Well, she gets a mouse stuck in one but it's not dead, of course. The things struggling and squeaking and just generally being miserable and she can't figure out what to do with it. She finally took it out and ran it over with her car.
http://en.wikipedia.org/wiki/Quark_(TV_series)
As we consume more IT resources the number of workers per resource unit has to fall - or we're going to wind up spending our entire budget on IT. The question for IT workers is whether the amount of IT workers has peaked or not. I don't think it has yet.
The first computer I worked with was a PDP 11/70. Less than 1 MIP and we had a dedicated operator. By that measure my laptop needs several thousand support personnel.
However, we spent close to $500,000 (in 1981 dollars) for that system. It supported 32 terminals. Today, I could put together 32 desktops plus a server system for less than $100,000 but would probably still want to have a dedicated IT support person for that many desktops (given that it's a small company and that's all of our IT infrastructure - larger companies get by with fewer desktop support people due to economies of scale).
My wife worked at Oracle here in Japan for a while. The director of the Oracle certificate program once set a long term goal of, I think, 5 million certified Oracle DBA's in Japan. Now, Japan has a total population of about 128 million so he was setting a goal of 4 out of every 100 people to be Oracle DBA's. Absolutely ludicrous.
Personnel are now the largest cost in IT. Anything that reduces IT costs will be reducing personnel costs. The real question is whether the IT budget overall is shrinking or growing.
The interesting long term question is whether IT will mature like power or plumbing to the point where an average company does not keep IT specialists on staff but just calls them in as needed. I would argue that it is different since IT done properly is a strategic asset customized to your company somehow but time will tell.
Interviews are a very limited block of time. Most people don't block more than an hour per interviewer. Subtract out time for pleasantries, wrapping up and you're down to 45 minutes. Those are very important minutes. Besides, you might actually learn something in university. I know I did.
One of the reasons why employers are often unwilling to hire people without degrees is that a lot of people who believe they are "too smart for college" really aren't.
By the time I graduated from college I had a number of years as a senior developer at a well respected company. When I went to my first job after college I doubled my salary. I think my time in school paid off well, and I enjoyed it.
I've known many people who were great sys admins or developers who did not have degrees so it is possible. However, it is much easier to get a job if you have the degree. Every time you do a job interview you will spend 5-10 minutes explaining why you don't have a degree - that is, if they even bother to call you in. That's 5-10 minutes that you're spending getting yourself up to the level of the other applicants that you could have spent putting yourself above the level of the other applicants.
Your pay level may suffer throughout your career as well. When I was in college, I had a job as a developer at a computer company. I switched from a full-time student, part-time developer to being a part-time student, full-time developer. They even asked me once to drop out to devote more time to the job. One day they hired a new developer, fresh out of college. She was quite sharp but had 0 experience. One day it came out over lunch how much she was making and it was more than me. I asked my boss why and he replied "She has her degree". Needless to say, I didn't entertain any more requests to drop out and work more.
Nobody is going to donate millions of man-hours to write the software for the F-22 out of the goodness of their heart.
Sure they would. First, though, someone has to donate a couple of F-22's to test the software on :-)