criyztalizea is better than listening to crap that went through dynamic range compression.

Haha, you say that as if compressors haven't been around for decades. Have you ever heard a Frank Zappa record?

HAHAHAHA!

Oh, you were being serious.

I believe 2.6.36 introduced a problem with DRI on intel and some other video chipsets which led to a shitload of kworker wake ups. One of my laptops running Arch benefitted from a kernel parameters suggestion over here but by that stage I had a menu.lst as long as your arm full of attempts at a functional system (e.g. kernel ... nohz=off highres=off pcie_ports=compat...) each with small, incremental improvements.

You can't catch every regression without owning all hardware and infinite time :)

Yep, that's right, a whole new distro... to enable something that not everybody thinks is a great idea... I mean, if you want to make 200 http connections per web page have at it, but do it on some other web, not the one that myself and others enjoy traffic from.

He's from Korea, but he's Big in Japan.

Precisely. Japan's latest rock star is a discovery of the Whitman Campaign. Jerry Brown knows what I'm talkin' 'bout.

"This video contains content from Vevo, who has blocked it in your country on copyright grounds" - that is a good-ass movie.

Have you ever even seen a zombie movie?

Hint: Few feature the grave.

Nah, Intel actually bought HP - McAfee just came bundled.

So get someone higher to publish a mandatory coding standard... advised by you, of course.

Troll, eh? Is that because winsock2 is actually good or because I didn't close the bracket?

Haven't tried C# express but I did use SharpDevelop in a previous gig when doing a little windows dev - it struck me as very polished.

I ended up doing what I needed with Win32 API calls and building with wxDev-C++ but I don't like talking about it... (Because of Winsock2 rather than wxDev-C++.

Plenty of money in COBOL but there is a need to suit up (physically and mentally) - not for everyone.

I have found a small but significant niche in embedded *nix programming. Small yet powerful systems requiring every scintilla of juice tempered with a familiar API - C Systems programming work is common enough (yet not common enough!). This is where I hope to spend the next while.

An "old school" approach to knowing the architecture inside-out and attention to detail is clouded by the bizarre abstractions of C# and Java. PHP isn't even an abstraction, it's a distraction (I grew tired of the inconsistency so no longer practise).

Perl is unfashionable in some circles and has a reputation for having magic constants (or whatever it is the detractors call "I don't want to learn this language") but I recommend it if you want dynamically typed "chops".

I find these "chops" are overrated. I enjoy low-level thinking so don't need to bloat up with virtual machines[1] (the real ones work fine for me), OO[2] (I know how to pass a pointer to my data to a lib) or design patterns[3] ("ways to do things" - if you learn one way as "the way" you may be unlikely to think there may be a better way)

[1] I use virtual machines but it's perverse running the dozens of MB JVM (and waiting around for it) for a browser bound animation or trivial desktop app. There may be a better case for this messing on the application server, but I don't care.

[2] OK, I will make an argument for OO in GUI programming - a large and complex library of heterogeneous components is difficult to arrange sensibly in a procedural manner. gtk_status_icon_set_from_file(foo_icon, "bar.png") or fooIcon.fileSet("bar.png")? There may be a similar argument to be made for other systems but for the most part I find the OO model a needless abstraction.

[3] Right... most programmers aren't brilliant - I know I'm fucking terrible for the most part - so having established methods for common situations is no bad thing... just don't get too attached.

I have... and I'm not even that old.

I once worked writing COBOL for VMS and Mainframe systems in various government departments. It's the job that inspired me to go get a degree.

Aye, junk it. One of the considerations now in my bang for buck considerations in running home servers is the power bill. Sure, it was cool to have my old P3 tower sitting there as a little slackware workhorse doing mail, web, shells and everything else for me but at the same time it's sucking up 200W... I could get a dual core atom box which runs on 50W for little money.