On my main FreeBSD/amd64 desktop box, I not only make the point of not having Flash on it, I don't even have the choice, as it is not supported by Adobe. So much for accessibility.
Well, when you made the choice of what OS to use you weighed the advantages and disadvantages of each. In particular, you considered the fact that the particular one that you chose was a very small portion of the market and was commonly not supported as well (or not at all) as your other options.
Now, any site that requires flash is making the decision that you are not important enough to support.
Point is, don't blame Adobe, blame yourself and those companies (and others) who require flash.
First of all, DDR RAM is not cheap (at least, not compared to NAND RAM). It costs significantly more per gigabyte than even the most expensive of Intel's offerings for SSD's.
Not actually true. Based on pricing at newegg.com, a 2GB stick of DDR2 can be had for $24. A 32 GB Intel X25-E is $420. That is, DDR2 costs $12/GB and the X25-E is $13.1/GB.
Now, for the ddr drive, you have to consider the cost of the drive itself and other factors. For example, for a ddr ram drive to be practical, I think it needs at least 32GB of space. That is 16 2GB sticks (which probably won't fit in a normal sized drive enclosure) or requires using the much more expensive 4GB sticks. So yeah, in my opinion, there's not really a place for ddr ram drives in the market.
return (n*n+1)/2
You mean n*(n+1)/2
No, he means (int)(n*((n+1)/2.0))
No he means n * (n + 1) / 2.
For those unable to follow at home, n * (n + 1) is always divisible by 2. Let's not convert to and from floating point just for fun.
Best book ever written on leading software development projects. Personally, I don't think students should graduate with a CS degree until they've read it.
I agree, knowing how to lead software development projects is very important to a computer science degree.
array-reversal was the _hard_ question. Granted, it had to be in-place array reversal using constant space and linear time.
hard? I will be graduating in from a CS program in the spring and I can barely believe what you are saying. It blows my mind that such an easy problem can stump so many people that it could be considered a "hard" problem.
Then again, just recently we had what I considered to be a relatively simple programming assignment and many people just couldn't do it. I looked at some of my classmate's code and they were all just complete messes.
But still, you (and others) are saying that many graduates have basically learned nothing.
My worry is that, because of all these incompetent graduates, companies are unwilling to pay what a good programmer is actually worth. That is, since any company who hires a graduate has to consider the fact that their new hire might be incompetent, they will not be willing to pay as much as they would for someone that they knew was good. So, basically, all the bad programmers drag down the prospects of the good ones.
Anybody who is in charge of hiring or such, is this true? Is there any way that you can tell if a candidate is actually good? Is there anything that a good candidate could do to prove that you wouldn't be taking a risk hiring them?
It is illegal to discriminate against anyone for whatever reason other than the job qualifications, including age.
Actually is is only illegal to discriminate against someone on the basis of race, color, religion, sex, national origin, or disability.
See here.
Those who can, do; those who can't, write. Those who can't write work for the Bell Labs Record.