Shiichan sucks and is written in PHP. Kareha sucks and is written in Perl (which causes more issues than anything else ever could when trying hard to do so).
Is there any sane BBS software out there or do I have to try and do it myself, despite not being an EXPERT PROGRAMMER?
>>4
He said "may", not "have to." In other news, if I was thinking of a proper implementation, then I'm thinking Python (with web.py or no framework, everything else is too bloated) or Haskell.
Name:
Anonymous2011-02-05 10:19
It's not that difficult for fuck's sake. The most difficult part will be the relative IDs of posts if you use a proper database (and seeing how you complained about those two, it's clear you will).
>>7
It's just that most people are familiar with procedural languages and Python is reasonably fast and looks more elegant to me.
Name:
Anonymous2011-02-05 10:54
PHP sucks. Django or Jinja2 with Python are pretty sweet. Unfortunately, it doesn't have the scalability of PHP. Meaning, if you're trying to make a huge site with lots of visitors, Python probably isn't the way to go. Ruby is even worse off than Python in this regards.
Unfortunately, PHP is pretty much the only modernesque game in town unless you want some ASP.NET dicks rammed down your throat.
Name:
Anonymous2011-02-05 10:55
Reddit is written using Python and web.py, I don't see it having too many issues. Either there's no real issue or they just have an oversized server park because of the resources being munched away.
All anonymous BBS implementations are doomed to suck, regardless of what language the're written in, and that's a fact. That's because people who would want to waste their time writing anonymous BBS software, which will result in anonymous BBSs with more or less the same features the ones already being used have, are usually amateurs with nothing better to do.
>>37
Sticking a shitload of parens on a single line is unreadable, and whenever I close them on separate lines (like you would close blocks in C), other lispers look down on me. So fuck that.
>>38 Sticking a shitload of parens on a single line is unreadable
You're not supposed to close them by yourself, you know. and whenever I close them on separate lines (like you would close blocks in C)
Looks like shit and it's a waste of lines.
>>52
love this one: http://www.parashift.com/c++-faq-lite/lang-comparisons.html
In 99% of the cases, programming language selection is dominated by business considerations, not by technical considerations. Things that really end up mattering are things like availability of a programming environment for the development machine, availability of runtime environment(s) for the deployment machine(s), licensing/legal issues of the runtime and/or development environments, availability of trained developers, availability of consulting services, and corporate culture/politics. These business considerations generally play a much greater role than compile time performance, runtime performance, static vs. dynamic typing, static vs. dynamic binding, etc.
Anyone who argues in favor of one language over another in a purely technical manner (i.e., who ignores the dominant business issues) exposes themself as a techie weenie, and deserves not to be heard. Business issues dominate technical issues, and anyone who doesn't realize that is destined to make decisions that have terrible business consequences — they are dangerous to their employer.