This is a feature, not a bug.

Build all your queries as parameterized queries (or better yet, stored procedures) and you will never have "type safety" problems. In fact the posting barely makes sense to me. How would you ever end up trying to date-range a string field? That query would never run! Oh right, there are still idiots out there that build queries at runtime. Well, don't fucking do that!

Besides, parameterized queries are 100% immune to SQL injection. You'd think people would care more about that these days.

I mean, seriously. There is no mechanism by which Do Not Track can actually be made to work as it is currently being proposed. This is more important than whether you think it's a good idea.

If you want to be able to opt out of being tracked, you need to built it in to browser behavior and/or web protocols themselves. You can't simply ASK sites not to track you and expect anything to happen, nor can you rely on a law to do this for you.

Why try to save it? If it's failing the market test, it should die. Rescind the Federal monopoly that the USPS enjoys, and let UPS, Fedex, etc. figure out a profitable way to deliver letters.

"One of the most dreaded hurdles on the PC upgrade path is the CPU socket. If socket design changes then you'll almost certainly need a new motherboard when you do upgrade."

This is a complete red herring. I have been building my own PCs since 1997. I have not once, ever, been able to re-use a motherboard when upgrading. Yes, some of that is due to sockets changing, but not all of it. Sometimes you need a new board to support the newest memory technology, or to support the changed voltage requirements of the new chips. Bottom line is, unless you're an early-and-often adopter, buying new CPUs the day they're released (which historically has meant spending $900+), you just won't ever get two CPUs' worth of life out of one motherboard, regardless of whether the required socket has changed.

Jesus fuck, people. It's not rocket surgery.

If you use bind variables, you CANNOT be SQL-injected.

If you don't, you can be.

It's that fucking simple. Do The Right Thing.

OOP should absolutely not be taught at the freshman level, because it gets in the way of understanding more basic concepts like, oh I dunno, variables, branching, looping, subroutines, I/O, etc. Their claim that OOP is "anti-modular" is of course absurd. "Anti-parallel" is probably arguable, but how that's relevant at an undergraduate level of instruction is highly questionable.

At any rate the real problem is that colleges offer degrees in "computer science" but not "software engineering". How many of these students will finish their degrees without ever having committed to source control? Without coding to a 3rd-party API? Connecting to a database? Performing maintenance programming? Working in an honest-to-god team?

I mean if you don't listen to Pink Floyd albums as ALBUMS, you're doing it wrong.