Well, it speaks volumes that you believe that human beings, who are the most generalized species in the world, should sit down, shut up, and do a narrow-minded--regardless of how brain-intensive your job--set of tasks for something like 8-12 hours per day consecutively. If you have a job where you're required to use that stuff between your ears, it's better to take breaks, stop focusing, and think about other things in life once in a short while.
Why should I have to compartmentalize my entire personal life and shove it in a corner? Who says that work is priority #1? That's an unhealthy viewpoint, and one that's likely to turn you into a scrooge.
Leaving your personal issues at the door is about as ridiculous as saying you're not going to be thinking about work over the weekend or on your drive home. Clearly there's overlap in all sorts of areas in your life.
You're too extreme the other way.
It really does depend on what you're using Ajax for, like you sort of said. Google Suggest was the "first" very noticeable public demo of what Ajax was, and it's a very good application. However, a lot of developers found their proverbial hammer and decided that Ajax to refresh most or all of the page is somehow better, where in fact there's the additional steps of variable evaluation and DOM insertion before you even get to a browser render.
Rendering one large page in response to a request, rather than 10 smaller requests, does not really decrease load
This really depends on what's happening behind the scenes. Small requests would be completed quicker, so more could be done in parallel, which of course decreases queueing and potential locking problems. Also, if you implement some sort of donut hole caching for your Ajax scheme, those small requests could come from memory instead of doing heavy processing on the back end. If you do it right, and you have a server with multiple cores (hopefully you do), you'll end up ahead with Ajax in this case.
Except loading a page is handled MUCH differently from dynamic changes to an existing page, such that loading a full page is faster
This is just blatantly not true unless the developer is a talentless hack that's recursively attaching nodes to the DOM at the outset of an Ajax response, rather than when the dynamic node tree is fully built. During a full page load, the browser is going to be rehashing the parse/render routine over and over as more data downloads, while an Ajax call is going to batch it together through a single parse (hopefully a strict XML parse) and render once the DOM branch is attached to the renderable tree.
If the site's developer is refreshing too much of the page, then what you're saying could be true. Most of the time, heavy Ajax is used on web apps that make more sense with a desktop sort of feel to them. Nothing's more annoying than full page refreshes every time I click a button in a web app.
That's ok, nobody feels smart implementing a Java interface
Mod +5, Troll
What I'm saying is that C++ and
I'm not disagreeing that they should at some point learn these tools, I just think it's a disservice to start a brand new student out with them.
The sad part is that the author of that ACM article complaining about bad developers is also the inventor of C++, the impending doom of students who need to learn how to program through problem solving, not fiddle with language-specific configs and compiler BS. Why is it that CS professors feel like C++ should be the very first language students should dive into? Are they trying to destroy their passion?
And no, I'm not recommending VB as a replacement.
Back when that kernel was first written, it was done by a bunch of young coders that learned kernel development by developing the kernel. They didn't have some huge insight right off the bat, they learned from experience, like the rest of us. As the kernel became mature, coding maturity and experience became more of a requirement (in theory) as well.
There are plenty of young coders with a lot of passion, intelligence, and problem solving abilities that haven't been spoiled by the admittedly poor quality formal education system. Are they developing a Linux kernel? No, but they're in the garage tinkering with their language of choice, becoming smarter.
As the field of software development has opened up, there are a lot more dummies that joined the ranks that need their hands held, but that certainly doesn't preclude very smart developers from joining in.
P.S. I've met a lot of really stupid old coders twice my age that can't answer basic problem solving and programming questions during interviews.
There's a difference between officially supporting every possible browser version and combination known to man, and supporting several of the popular ones but allowing anything you want. I've grown used to not having official support for Opera in any of our internal applications, but that's OK: we support IE, Firefox, Safari, and Chrome, so Opera always works anyway.
It's basically just fear-mongering that says "oh gee whiz there are so many different types of X program". Any IT person will be able to spend a few minutes figuring out software specific problems 99% of the time, or they can just leave the user to figure it out for themselves if they are using something non-standard.
A guy I work with used to work with a lady who wouldn't call him Mexican, because "that would make her sound racist". He's from Mexico.
Why are people so sensitive to this stuff, when it's just not a big deal? Most people don't care if you point out their race, or even use a minor slur (i.e. those damn Mexicans!). It's when you're degrading their character or their race in a way that implies serious inherent inferiority that people can and should get pissed.
An authority is a person who can tell you more about something than you really care to know.