Part of the difficulty is striking the balance between new user friendliness and power user friendliness. Both are important, the former for growing a community and bringing in new users, and the latter so that the program is useful for complex production tasks. These two goals are often at odds with each other.

• /v/opengl
• /v/git

That's a large, complex topic, but since this is /v/programming here are a couple tips from a coding perspective:

• Even if you don't use it, pay attention to what the OpenBSD project is doing. New techniques are born there and are first used there before adoption by other operating systems (W^X, ASLR, reallocarray and friends, entropy system call). The only problem is that they frequently pick awful names!

• Learn how to exploit common software vulnerabilities (return oriented programming, stack smashing, integer overflows, buffer overflows, etc.). You'll learn what sorts of things to watch for in your own code. Imagine what sorts of inputs would put your program in a bad state, and protect it against those inputs.

I haven't used this myself for anything and I view it as an educational project. On that other website, the author said, "Similar to WavPack, though worse than FLAC (FLAC uses joint channel coding which I haven't implemented yet)."

Couldn't agree more. If you're frequently getting useful information from Stackoverflow, you're only performing at a very basic student level since you probably lack the fundamentals. When you're working productively on something more niche and more advanced, you'll more frequently find Stackoverflow frustrating due to missing answers, incomplete answers, incorrect answers, and badly-researched questions.

I'm a fan of Modern C. It's free, extremely precise in its language, and covers all the latest language features.

http://i.imgur.com/c7NJRa2.gif

Yeah, .kkrieger is an amazing feat.

I've avoided /r/programming for years because it can often be needlessly hostile, especially when presented with the controversial or unconventional. "Why would anyone want to do this?" or "You know you can do XYZ instead, right?" They'll pick at the slightest inaccuracy in a post and dismiss the whole thing. Instead I've stuck to smaller communities of the same topic, like /r/coding or the language-specific subreddits, and now /v/programming.

Personally I'd prefer a ban on obvious homework questions. Some subreddits get drowned in that noise (example: /r/matlab) and I end up unsubscribing to avoid it. But maybe that's not the right choice for a catch-all name like /v/programming.

Seems to mirror reddit in some ways, particularly the authoritarian moderatorship.

C++ is in a rather unique position that its abstractions tend to boil away to nothing by being fully realized at compile-time.

What do you mean by "idle games"? Turn based? Casual games?

It's definitely wrong about requiring an RGBA buffer format. Just use the base format RED, unsigned integer, 8-bit so that only the first channel is used.

On WebGL this would make the framebuffer attachment incomplete and it wouldn't be allowed as a render target. That's where the "must be RGBA" comes from when implemented in WebGL.

The difference is that the breadth-first horizon is searched in parallel, exploiting the GPU's architecture, rather than pushed out one square at a time as a CPU would normally do it.

What's your advice to open source developers being targeted by these people?

Mine is primarily a low-powered BitTorrent (transmission-daemon) server and network file server, but I occasionally also use it to test some of my code out on ARM.

GPUs get their parallelism via SIMD: a single instruction operating on an array of many elements all at once. If a kernel/shader branches a lot, so that pieces of data must be acted upon individually, the GPU can't parallelize the work effectively. For example, Dijkstra's algorithm is queue oriented and isn't really amenable to parallel operation and a different approach must be taken to map the problem onto the target hardware.

The project itself was banned from GitHub, where it was originally hosted.

Hey, Mortoray came to Voat! It's nice to have familiar faces appearing around here.

Best practice today is to immediately begin migrating to a more recent generation of source control. Subversion is just an artifact of an intermediate learning stage.

For C I stick to K&R but put function names on their own line apart from the return type.

GDB has a massive number of features. Learning it all takes years. I only wish there was a really solid front-end GUI to GDB to make it easier to use in the general case. The existing ones don't really cut it yet, though Emacs gdb front-end isn't too bad.