/prog/ sucks

I used to visit /prog/ a year or two ago, and this place was great. Now it's just faggots arguing about bugs and feature enhancements. I remember all the great memes like hax my anus and ENTERPRISE coders and HAVE YOU READ YOUR SICP TODAY? I for one dislike this new /prog/ and would like the old one back!

You mean its actually useful as opposed to imitating /b/?

trust me, no matter what, we can't have nice things.

Actually, /prog/ always sucked. The difference was that at least some people cared to make a good thread now and then, as we didn't have enough dedicated retards to keep fucking it up. And there's no variety either, the jokes are the same and they latch onto whatever thread has the most posts and proceed to create response threads as nauseum. How many C is teh awesum/ C is shit lol threads do we need?

>>5
How many C is teh awesum/ C is shit lol threads do we need?
I don't know that, but I can say there's not enough yet.

No more of that fucking SICP shit.

>>1
Hax my anus was never good.

>>6
You will never achieve satori with that attitude.

>>7
I am past satori.

>>7

RETALIATE MY ANUS

Let's review the front page right now:
- “How do I work Linux?”
- A link to a Facebook fan page for our favourite Belgian. 5 people are fans, including his wife.
- Kopipe about gayness.
- “C Help - I cannot program! Help!”
- Hello World. Again. PHP; lacks proper [code] tag usage.
- Another C/++ thread. Turns into another discussion about garbage collection.
- Shitpost repeat thread.
- Another meta-thread complaining about the `decline' in quality that it is actually contributing to.
- “How do I install Linux?”
- Another C thread.
- Javascript thread. No [code] tags. PHP is mentioned. A solution is mentioned once.
- Another C thread. No [code] tags.
- Something about a man-in-the-middle attack by someone who doesn't know what the hell they're on about.
- Another Javascript/Greasmonkey thread. [code] tags optional.
- Variation on “How do you pronounce ``[x]''?” format thread. No new content.
- Another tripcode thread from 2007. Still not dead, or forgotten.
- Thread “pointing out” the inadequacies of an OS written several decades ago in a basement.
- “I'm a /anus/rider who's been employed for about a year.”

>>7
Have you read your Zen mind, beginner's mind today?

I think you will find it a far better aid to achieving enlightenment than sick-pee

>>10
By describing them as ``C threads'' you've made them sound a lot more interesting than they actually are.

>>12
or you just have an overly optimistic view of what a "C thread" is like

>>13
``C threads'' are usually awesome.

>>14
Except on [spoiler]/prog/[spoiler].

http://i.imgur.com/rutGR.jpg

>>16
Both of those wolves are worthless douchebags who add nothing to conversation. Maybe that's why Reddit is in the state it's in.

>>1
Honestly I haven't seen much change over the past 2 years.
This board have nothing to do with programming and haven't been in the time I've been here.

/prog/ isn't a social site. The time between interesting threads is long and the people who post here are generally unhelpful.
The only alternative I have is /pr/, consisting of people who wants to be helpful but never are.

When I have a solution to a problem that I get the feeling could be done better and I am unable to find the better solution, I can post the problem here or on /pr/.

If I post it on /pr/ I'll get a lot of replies from proud posters thinking they've invented the space elevator. Each solution is horribly worse than anything I could ever dream of.

If I post it on /prog/ I will receive replies urging me to read SICP, instructions on how to hax my anus, replies discussing how much better everything would be in LISP and general trolling.
However, at rare occasions someone will condescendingly criticize my solution and provide a better one.
These are the best times on /prog/ because this is when I get a chance to learn something new.
When no such post is made, I feel more confident in my solution as I am certain that if a simple, better solution existed, someone would be there to slap my face with it.

>>18
If it's ever a Java, JavaScript, or Python question, it's probably me.

>>19
If it's ever a Java or Javascript question, you should fuck right off.

>>18
Hey, how about you learn how to learn by yourself?

>>20
I'd rather be helpful.

>>22
But you never get any substantial thanks. It's like working in IT, but you're unemployed anyway