Why hasn't /prog's look been updated
Because it doesn't need to be.
/thread
Name:
Anonymous2013-08-11 10:01
>>8
That's not what ENTERPRISE web developers think. /prog/ isn't web 2.0TM enough. If it works without Javascript enabled, it's not Web 2.0TM. It also needs more gradients.
>>9
But /prog/ is the very definition of Web2.0 - user contributed content is more important that content created by the webmaster (lel, long time since I used that word).
Name:
Anonymous2013-08-11 19:03
>>11
Web 2.0 is a bullshit term, carrying no real meaning. It's not like the web got an update. It's just a different kind of website, and the user-contribution style website has been around just about forever (BBS). People like to use it to refer to a large amount of graphical styles that have their own names anyway.
tl;dr "web 2.0" is meaningless.
Name:
Anonymous2013-08-11 19:16
I prefer the term ``sysop''.
Name:
Anonymous2013-08-12 3:53
>>8
You're telling me that shitty faded brick texture is fine?
>>14
It is fine. If you don't like it, use your own CSS.
I am toying with a /prog/ command-line client, but it needs a lot more work and I have to fix a bug in the HTTP client library before posting will work. I worry about releasing it, it's too scriptable and it would probably get abused for auto-shitposting.
>>15
The same thing prevents me from making a cli to /prog/. Maybe if you obfuscate the posting code, and hard code it to have timing restrictions and only read from user input via a terminal with curses, making pipes harder to do. Then people that could write it themselves could deconstruct it and make it pure.
Name:
Anonymous2013-08-12 6:37
>>17
It's not pipe-friendly, but it's written in a prototype oo language where prototypes are well-used (unlike javascript).78
I might publish the read-only version. The language ships with an HTTP client lib that is completely broken for POST. While fixing it on my local copy (it's still broken as fuck but works for some things) I found the POST method was planned and partly implemented in a way that will never work.
i think this site is nice, works perfectly even with terrible connection, with disabled pictures and javascript. Telling-nothing-titles like "why" and retards are more serious problems.
Name:
Anonymous2013-08-12 8:33
Ironically, /prog/ is one of the harder boards to create a standalone client for. I wrote an ncurses client for the imagereddits (which sucks and is read-only, plus I never got the image-displaying code from w3m to work just right, so I never published it), and the formatting almost took care of itself - replace <br> with a linejump and transform the text coloring for spoilers and quoting. For enhanced BBCODE, it would would be extremely painful to try and deal with sub/sup, and aa would be a nightmare.
>>21
Oh yeah, and the biggest thing is that the JSON interface doesn't handle textboards, so you'd have to deal with the messy subject.txt parsing, which can be trivially broken by people fucking around with title/subject/name.
Name:
Anonymous2013-08-12 12:30
>>22
Explain how it's "trivially broken", or even better, show me an example post.
Name:
Anonymous2013-08-12 12:36
What's wrong with web 2.0? JS has its place. You don't have to go full neckbeard nor drink all the koolaid. HTML is flawed because its not realtime. JS fixes this glaring flaw, albeit in a hacky way.
>>25
Think what you want about my posting status. "<>" get converted to </> and I believe MrVacuumCleaner-kun-sama-tan fixed the bug you're talking about.
Name:
Anonymous2013-08-12 13:40
It's a textboard, so the design is out...
Name:
Anonymous2013-08-12 14:09
>>26
There's still one thread in subject.txt that breaks this, at least. Split it and try it yourself.
Name:
Anonymous2013-08-12 14:16
>>24 What's wrong with web 2.0? JS has its place.
What? No. Go back to /g/. You don't have to go full neckbeard nor drink all the koolaid.
Yes, neckbeard is an e/g/in meme. GO BACK TO /G/.