Wayland and its never-ending stream of stories seems to be going the way pulseaudio did. It's heavily criticized, cuts down some features or is somehow buggy, but seems to give many users what they want, or at least that's what all these crazy stories point to.

As long as I can still run X atop Wayland, I don't really care. I loved pulseaudio when it was being bashed already. Maybe I'll love Wayland too? Has anyone here actually seriously tried this thing before bashing it?

He means he wants to be able to pass an instance, an isolated component which can not only be spawned as part of a thread, but keep an internal state during program existance, and across different thread spawnings. And he doesn't want to do it by using variables defined in another, outside scope (functions, globals...).

Diversity does not mean tolerating bigotry directed at minorities. It's crazy that you talk about tolerating disagreement when Eich is the one who donated money to criminalize what he disagrees with.

And do you think this is specific to HTTPS, or rather a problem with most encryption techniques as we use them (given that we're not zero-padding input data to make it all rougly the same size, that is, pretty indistinguishable)?

The bug was found due to observed behavior, not due to a code review.

Already upgraded to Mavericks? I'm still waiting some months before all the fucktards finish complaining about what does and does not work.

Except it did.

Slashdot now looks like an old Blogger page. I hate blogger pages, they're last decade thing. If Beta becomes all I can have, I'm leaving slashdot. They weren't getting anything from me anyway, so I guess it's one less connection to their crappy servers anyway.

A POSIX mutex can be initialized via a call to a library function or, alternatively, it can be "statically initialized" with the constant value of PTHREAD_MUTEX_INITIALIZER, which initializes it and sets default attributes. It's not exactly "clearing the memory to 0", but it's along the lines of that train of thought

Could you elaborate on that kind of knowledge? I'm genuinely interested.

To me, it isn't about writing that weird code. It's about knowing what happens, so that I DO know when I really need to optimize and so that I DO know what's going on under the hood. I find it very important to understand the CPU and memory, how it all works. Many programmers still think of this as magic, and that's why they're programmers, not engineers. But this post mentions software engineering, not mere programming.

I've tried all versions of that picture that I could find and I've analysed the GIF. what you see is a tampered picture (first GIF frame) which has seen red pixels (red "noise") added in the shape of a possible HL3 logo. It's fake.

My "woosh!" was in agreement with the AC's response! I totally agree with it, and find it somewhat ironical that parent, the one with the mistake, stated that gp should "brush up on problem analysis 101".

woosh!