Breaking News

http://steve-yegge.blogspot.com/2010/07/wikileaks-to-leak-5000-open-source-java.html
Wikileaks founder Julian Assange, who coined the term "Opened Source" to describe the jailbroken open-source Java code, fears he may be arrested by campus security at Oracle or possibly IBM. The Wikileaks founder said: "Today the Eclipse Foundation put out a private briefing calling me a 'non-thread-safe AbstractKeywordRemovalInitiatorFactory'.

>>22
It's Apple's extension to C and Objective-C for implementing closures.

http://developer.apple.com/mac/articles/cocoa/introblocksgcd.html

Also, why does everyone sage anything interesting? Did you just not want an answer to your question? Well TOO FUCKING BAD, you got one.

>>24
Ah. That's actually fairly retarded. I don't see why that needs new syntax.

Also, learn how to use sage, imageboard effluent.

>>25
Also, learn how to use sage, imageboard effluent.

this is hardly what he implied, i think what >>24-san meant was that you should not sage interesting threads as this reduces the quality of /prog/.

>>26
Yeah, bumping good threads so the imageboard effluents can shit all over them really increases the quality of /prog/.

>>26
There's nothing keeping a thread from being interesting and discussions going on just because it isn't on the front page.

>>27
Yeah, bumping good threads so the imageboard effluents can shit all over them really increases the quality of /prog/.

if you would sage any thread it would hardly stop them.

and the point is that imageboard scum MAKES shitty threads instead of shitting inside existing one. by bumping them you keep the good threads on the top and the "less interesting" ones go to the bottom.

>>29
It means that any time you see someone not using sage you can safely ignore the post.

>>29
Sometimes, if a thread is interesting, it gets bumped by a post with actual content once it's off the front page so others can continue to reply. The rest of us know to look at the entire front page for real content, because the first few threads are usually there because they've been bumped by idiots. They're not idiots for bumping, of course, just for not knowing to sage (and for the content of their posts).

Sometimes, if a thread is interesting, it gets bumped by a post with actual content once it's off the front page so others can continue to reply.
A thread doesn't need to be on the front page for people to reply to it.
I probably shouldn't be telling an idiot from the imageboards that. Oops.

>>32
You're quite persistent that I'm from the image boards (see the other thread in which you(?) assume that too) - perhaps you are overcompensating for something, as you seem to have pointed out something quite unimportant as an excuse to appear as the one here who shouldn't go back to /b/.
I'm quite aware of that. I said `so others can continue to reply' because it's not always noticed when a thread has been replied to with a sage post. Unless, of course, you are an autistic person who specialises in remembering over 22 numbers between browser sessions.

I don't know about others, but this is how I troll browse /prog/:

- Load front page.
- Skim threads, load interesting looking ones in tabs
- Close front page.
- Reload threads occasionally (maybe a couple times a day?)
- Trim ones that haven't had activity in a while, or ones where the topic got boring
- When running low on threads, goto step 1

Usually I end up with about 8 threads at a time this way. Sometimes conversations will exist for a good amount of time beyond when the thread has left the front page; these are the best threads because the people are actually interested in the core topic, and the possibility of someone hijacking the topic or threadshitting is much lower.

Note that any useful browser is entirely capable of remembering which threads you have open if you have to close it for some absurd reason. I haven't closed my web browser for weeks, and that was to reboot for a kernel upgrade. I pretty much have a separate desktop dedicated to looking at textboards.

I have thought about the possibility of a board with no visible thread list or front page. Instead, it could be built with a system like (e.g.) last.fm where each thread is prefixed with a set of links to "similar" threads, determined by the number of unique participants in both. Maybe it could be weighted in favor of those who have posted more than once, in an attempt to eliminate garbage posts from people looking at a thread and then not actually reading it afterward.

Although I have a suspicion that such a scheme would inevitably deteriorate into WEB TWO POINT OH garbage, if properly set up, it could actually be worthwhile.

you seem to have pointed out something quite unimportant
Using sage properly is not ``something quite unimportant".

remembering over 22 numbers between browser sessions.
Modern browsers can save and restore sessions. If you're still using '90s abandonware, you can use bookmarks.

>>35
No, you moron, the unimportant thing was that you can reply to a thread once it's left the front page.
Also the numbers were how many posts each thread has, for which Shiıchan conveniently doesn't highlight changes since your last visit. That isn't a browser issue, unless you're a chump like >>34, in which case you've made it one.

>>33
Faggot quote fail.

>>36
See that link at the bottom of every thread that says "newer posts"? Click it. You don't have to remember shit.

I was writing under the belief that your comment was indeed referring to browser inadequacies in keeping track of what tabs you had open. Unfortunately it appears that you're stupider than I thought.

>>38
What are you on? You see that link below the Reply box that say ``Entire thread''? Click it. Holy shyt, you can see the entire thread! Now press End on your keyboard AND YOU'RE AT THE END OF THE THREAD! THE NEWEST POSTS ARE HERE.

I don't want to waste my fuqin time by having to go through each thread I remember was interesting in order to click your fuqin link. That's one extra link to waste my fuqin time on. Oh, and does this ``newer posts'' link tell you about new posts while you were away? NO IT FUQIN DOESN'T! That was what I was complaining about. Now go back to reading Comprehension 101, please.

>>39
You're a goddamn fucking retard. Use your "entire thread" button on this thread, and keep clicking that until you manage to grasp the blindingly obvious purpose of "Newer Posts". Until then, you can fuck right off.

/prog/ at its best!

>>34
Here's what I do:

- Load list of unread posts.
- Read unread posts.
- Sometimes I have to read a few earlier posts if I forgot what the thread was about.
- Then I do something else for a while until I refresh my list of unread posts.

tldr

>>42-43
lol

>>44
IHBT.

*bump*

>>1
Dey shud have written it in CLANG.

>>48 `
>implying Clang existed in 2010

>>49
[spoiler]back to /b/, please.

Apple chose to develop a new compiler front end from scratch, supporting only C99, Objective-C and C++. This "clang" project was open-sourced in July 2007.

[spoiler]
Damn, Shii^tchan's broken BBCODE parser strikes again.

Clang. Clang, clang, clang, clang, clang, clang.
http://www.youtube.com/watch?v=E8CHnbdEXgQ#t=0m27s

>>13
I like final variables.  I wish there was a way to make all variables final by default, and instead mark mutable variables as mutable.