This is not which one is better but which one is easier for someone who has never approached this style of web application development before. I'm coming from a PHP and Perl background but I'm looking at jumping on the MVC bandwagon, the problem is that I'm not very familiar with either of these frameworks and was wondering which one is easier to get your head around. I've looked at starting guides for both and i'm equally lost for both.
I never really liked web development frameworks. Shit just inserts useless stuff left and right, adding unneeded complexity, etc.
That being said, try Ruby, I hear it's fasSLOW AS FUCK.
Name:
Anonymous2009-05-30 11:37
use PHP its based on purely functional lambda calculus so it's obviosu the best
Name:
Anonymous2009-05-30 12:00
Mongrel is a server. You are thinking about rails.
Ruby is SLOW AS FUCK, which is actually fast enough for web development. The community is comprised of 30% of very cool people and 70% of insufferable idiots/mac hipsters/aspies/dickheads with a jesus complex. The rails stack is easy to get started with, but to reach a decent level you'll have to talk to dumbshits on IRC. It's not simply that the always outdated documentation sucks, it's more that it doesn't always exist to begin with.
Python is faster, which does not matter for the web. The community is comprised of 40% of decent guys and 60% of annoying guys. Django is harder to learn, and the documentation isn't great, but it's not as horrible. You will be slightly less productive with Django than you would be in the rails religion.
Neither is better. Web development sucks in general. Sometimes I wish I didn't make web sights.
>>5
Are you starting to regret not learning something real when you were young?
Name:
Anonymous2009-05-30 12:34
>>5
>Web development sucks in general. Sometimes I wish I didn't make web sights.
I agree, web development is incredibly frustrating and not very rewarding especially when 90% of the shit I work on is not so much actual development from the ground up, but fixing shit that never worked to begin with because it was originally outsourced to india with shit code.
>>8
Maybe you (and 99.99999% of people like you) are doing something that wasn't orginally intended. HTML was originally intended as a language for documentation (such as reports) that was to be easily linked, and parsed.
I know that people evolve technology to fit their needs but I find that it's often better to design tools to fit your needs rather than hack functionality onto existing tools. I guess what I'm trying to say is that you people are just making things too complex simply because you have never learned anything more than superficial facts about your tools.
Name:
Anonymous2009-05-30 13:11
>>12 superficial facts about your tools
Like rain on you‘re wedding day.
>>14
No. I'm just sick of people complaining when they struggle to use tools to perform tasks not particularly intended when the tool was originally conceived.
In this case, I am talking about web apps. I have problems with web apps that are far better served as Java applets or stand alone binaries; this would be the vast majority of these so called ``web apps''. Use HTML as it was intended, a way to disseminate textual information, not as a way to deliver some sort of turn-key application.
use tools to perform tasks not particularly intended when the tool was originally conceived.
That basically describes any development ever.
And while it may be more convenient for you to develop for ugly unstable slow-as-fuck applets or dangerous nonportable hey-here's-some-more-trivial-shit-to-clutter-your-hard-drive native code, your users will in turn find it convenient to take their money to someone who actually gives a damn about usability.
Is there really anyone who has serious experience with both Ruby/Rails and Python/Django? I thought the two languages attracted diametrically opposite hipsters. (Pro-FIOC/anti-FIOC, pro-magic/anti-magic, pro-perl/anti-perl, etc.)
>>26
Few people have experience with both, not just here but in general. Each does the job nicely, so switching is a hassle more than an opportunity.
If you really have no idea which one is best for you, here's the easiest way to choose correctly:
Do you have a Mac running OS X? Use Ruby.
Do you have a PC running Linux? Use Python.
Do you have a PC running Windows? Play videogames.