- Feature Articles
- CodeSOD
- Error'd
- Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
Nice.
BTW, nice avatar ;-)
Admin
Why does it bother you? I see no reason for this not to be a thing. It's kind of the point of HTML and the WWW anyways, to be able to link to relevant information.
Admin
Because one of the things about this place, to be honest, is the series of memes that go on here.
When I first started reading, there were references I didn't get, and I had to go away and read the archives. There's a certain level of self-discovery there. If it's handed to you, it's not the same as discovering it for yourself.
Admin
No one's forcing you to click on a link. Feel free to take all the time you want to figure it out for yourself, while others who don't have or want to spend the time use the extra information that was helpfully provided.
Admin
I realise this. I'm just mindful on the other hand that this particular community is a special level of insular and familiarity with all the memes is generally buttumed around here without there being helpful links all the time.
Admin
Dumb question. Why is it desirable to link directly to the last post, especially if you haven't read the thread yet? If you have read some of the thread already, the link without /[post#] or /last it will take you to the last read post automatically. If you haven't read any, it will take you to the first post, which is surely the desired behaviour?
Admin
Admin
well i'll not speak to the actuall correct behavior. the behavior as implemented is attempting to bring you to the last post in the thread. My PR fixes it so that it's no longer a target for this community to try and abuse.
As i noted in my PR it should be rejected if another issue (the exact one you are referring to ) is accepted.
https://github.com/tdwtf/WtfWebApp/issues/74
Admin
I don't think the performance issue has much to do with the SQL being run, its more to do with the fact that he is busy-waiting on threads:
while (city.isRunning());
will use 100% CPU