This this this! Finally - someone points out the elephant, the pot calling the kettle black. For once I'd like the GPL community to admit this. The tactics and business models supported by GPL-style licenses is why I never have, and never will, release my software with one of their licenses. It's either free - or it's not.
Either give it away free like you intended, or follow the GPL rabbit hole down and just guess what GPL 4, 5 and 6 will look like...
Here are the salient hardware points:
-Intel SSD drives now carry a 3 year warranty. Now as good as any platter drive (sadly).
-Drives have built-in error correction and failure tolerance with replaceable blocks if one cell dies.
-Newer processing techniques have greatly improved reliability
-Many bug fixes to early firmware problems. Things such as wear-leveling that prevents certain cells from getting hammered while the rest of the drive sits unused.
Some of the software points:
-OS's have long be optimized for the slow platter performance. Newer OS's (Win7 is one) detect the use of an SSD and turn off the features that actually hurt drives. What are those things? Turn off disk defragmenting, optimizing the use of the system so that caches and data live on a platter drive while the OS and programs you want mostly read access are on the SSD.
There are many good articles and write-ups on these topics. I finally made the jump and would never look back. I just got a 180gb Intel SSD for $129 and it's the single most trans-formative upgrade to my computing experience I've made since the Core line of processors were released. The sheer speed your machine runs at, how apps just instantly start and the system boots in a few seconds, is just mind boggling. You start feeling the power of modern processors like you never have before.
I swear that at times Slashdot feels like a bunch of stuffy comp-sci folks stuck in the 80's. You'll argue day and night about minor technical details, but it's none of those details/minutia that really make a product take off. Sure, flaws will kill a product, but beyond a very simple point, they are just a tool to get a job done. Steve Jobs understood that, maybe we should too and stop the language circle-jerks.
Finding *qualified* candidates is the key phrase. We get lots of interviews from recent graduates, but many of us lament at how bad a great number of them are. The ones that went to U of Pheonix or other trade schools are just not suitable as systems coders (jobs we pay very well for). I don't know if it's universities failing to educate, or standards going up. I would guess a little of both. We need device driver writers, multithreaded system programers, graphics, etc, and it's very hard to find event experienced coders that are good at that. Most fail our screenings. It's not good enough anymore just to show up with a sheepskin in CS. You need to demonstrate you can actually build and debug something. For candidates that show initiative with personal projects and can demonstrate solid coding/debugging and can talk intelligently about architecture - we'll hire you in a MINUTE with some of the highest salaries in the industry. If you can't, then you're one of the 10,000 other global coders anyone can get. We do hiring lots of promising newbies all the time - but they have to show that initial spark and understanding at least. You can't just show up and be gimme a job cause I got a diploma.
I think this brings us to a great career point. You don't want to be floating in the middle as one of the masses in engineering - following just the trend lines. Sure, you need relevant skills so don't run out and become the ADA expert; but perhaps an example. If you were a Java/web coder in the very early 2000's when the bubble popped - a great number of those people never found work again and left the field. I felt bad for all the CS grads from my school that had just taught them Java (they don't know, they primarily teach C/C++ again and now we hire them). Unfortunately, when you're part of the big crowd, you're career and pay is driven much by the crowd and you must be really, really exceptional to stand out.
What will make you OODLES of money in engineering is being a master of certain much needed, but not well peopled, technique. I knew several guys that were above average coders but commanded insane amounts of money to come in and deliver a certain kind of feature. They went the contracting themselves out route and simply re-regurgitated the 1 of the 5 or so techniques they had implemented for this task really well, picked up a fat check, wash, rinse and repeat. I know personally of at least 2 different sets of people doing this with 2 completely different technologies. Sure, every year or two needed to spend some time updating and revamping the codebase, but they worked about 2-3 jobs a year and then took 3-6 mo off - and made large 6-figure salaries. Those are the people that get rich in engineering. You simply won't get rich working for a company unless you've got some kind of share of the sales.
So it is possible to get a job even as a new grad, but you need to stand out more now than before.
It helps if you have 3 months salary in reserve for emergencies like you should so you don't end up entering a bad situation out of desperation.
Currently, I would recommend people have 6-12 months saved up. Jobs report in August said the AVERAGE length of unemployment is 40.4 weeks. Granted, that's including all industries; but the reality is that it's worse out there than people think.
There are two kinds of egotists: 1) Those who admit it 2) The rest of us