imageboard

I want to write a good imageboard engine with clean code, to be the preferred choice instead of 4chan's shitty codebase (admit it, it's true) and derivatives. What I am having trouble with, is what language/environment to do it in. Every one has ups and downs. Here are some I can program in:

* C with CGI is very fast (except for fork overheads), but development times are going to be absolute shit.
* C with FastCGI runs even faster than CGI, but the development times are the same as above, and I don't like the added complexity compared to plain old CGI.
* Python is just shit. Period.
* node.js is a cool concept, but I am worried about performance/scalability, as well as the fact that it doesn't seem like a solid platform to bank on; I always feel that in ten years, no one will care about it, and my imageboard will be dead.

There are other options, like perl, but I don't know them yet, so learning overhead must be taken into account.

What should I do, /prog/?

corporations default to php (for web programming) because php programmers are cheap and plentiful. most OSS is written in php for the same reason and also because php hosts are cheap and plentiful.

>>41
sounds like "worse is better"

>>42
That's how it works.

>>1
This is the easiest framework for web services i know.

http://perldancer.org/

>>41-43
I don't agree. Sounds more like "worse is cheaper"

>>45
cheap = inferior.
example: x86 is "cheaper" than lisp-machine.

>>46
example: x86 is "cheaper" than lisp-machine.
Terribly bad example. http://yosefk.com/blog/the-high-level-cpu-challenge.html

>>47
Supporting dynamic typing and/or numeric tower would require more transistors for every basic operation, wich arent required for C/C++. Hardware assisted JIT and garbage collection would require global changes to MMU and stuff like write barrier isn't cheap.

>>47-48
Lispers are such bad coders, they can't adapt their shitty language to better non-obsolete CPUs.  They should've died along with the lisp machines.

>>49
Enjoy your declare unsafe pointer segmentation fault stackoverflow.

>>50
Writing 99% my code in a fast and safe language, fagstorm.

Only shitty programmers worry about what language to use. Programmers who actually get shit done (like moot, Mark Zuckerburg, Jimmy Wales, etc) use PHP.

Don't worry about speed optimization when you haven't even wrote a single line of code!

>>52
moot? Getting shit done? Look at this piece of shit imageboard software. IHBT

Only shitty programmers worry about what language to use. Programmers [...] use PHP.
;_;

moot, Mark Zuckerburg, Jimmy Wales

Programmers

Programmers [...] like moot, Mark Zuckerburg, Jimmy Wales
Mommy, am I not a programmer anymore?

Racket
Erlang
Objective BBCode

Aim high and go for C directly and don't kid yourself with small 10K tests, that's just going to set you on the wrong path from the start. Go for some serious numbers, like 10 million concurrent connections and design everything between your production environment to your test suit around that.

Why not use C++? The development times will be much faster.

>LLLEEEEEEEEEEEEEEEEEEEEEEEEEEEELLLLLLLLLLLLLLLLLLLLLLLLL
>LE
>EGWINGOINGOIN' GROSKI
>LEL

Speed doesn't mean jackshit for ``web apps'', it's all about IO. As >>40 suggests, go try Heroku or one of those free cloud enterprise bullshites for the hosting.

* node.js is a cool concept
IHBT