What language is the majority of startups using today? • Hacker News Board

Re: What language is the majority of startups using today?

#61

Post by staunch » Thu, Aug 09, 2007, 12:14 AM UTC

randallsquared wrote: post #56

staunch wrote: post #32

Perl with Catalyst, DBIx::Class, and Template Toolkit. All the actual every-day code is really simple because all three are designed for extensibility. I just write little plugins that abstract away the repetitive stuff. I also write lots of long-lived systems daemons. They do all the asynchronous tasks in a super efficient way. Not enough people use this technique in my experience.

I just use cron for asynchronous tasks, because it's less complex to write for (just write the script to do the task once, after all), and any unix will already have cron running for other things.

Yeah cron works for lots of stuff. Some things need to happen asynchronous but more quickly than is convenient to do with cron. Not enough people use cron jobs though either.

Re: What language is the majority of startups using today?

#62

Post by steve » Thu, Aug 09, 2007, 4:26 PM UTC

Keios wrote: post #42

nostrademons wrote: post #31

Earlier quoted context omitted.

I've found that I had to gradually replace large parts of web.py as my webapp evolved. For instance: I had to drop the built-in DB library once I needed to connect to multiple databases. Global DB connections = bad. I suspect that if I'd kept using it, I would've had problems with transactions too. I had to replace some of the request dispatching when I wanted to add code that triggers on every request (eg. logging,…

I use Python-Pylons/JS and Schevo for the backend. I have some experience with Django. Pylons is much better for serious programming - Django is better if you want to make a run of th e mill app like a blog. Using Pylons is like working with Lego bricks - stuff is swappable easily - not so with Django.

Yes, that's what I need and pretty much what webpy feels like to me.

If I were to switch to anything else, I'd probably try plyons first.

Re: What language is the majority of startups using today?

#63

Post by edgeztv » Fri, Aug 10, 2007, 8:06 PM UTC

vlad wrote: post #43

edgeztv wrote: post #40

Earlier quoted context omitted.

There are a few misconceptions about GWT in the above comment: "most frameworks are evolving FAR quicker than GWT is." GWT is only a year old and has had 4 major releases. It just went open-source recently, so it's too early to tell how fast it will evolve. "GWT does not have anywhere near the community or IRC users that most frameworks do." GWT community is huge - there are over 600 posts a week on its Google Group.…

You used the word misconceptions, but I don't think I was wrong about anything I said if you read what I wrote carefully. I'm not sure where you disagree since you are defensive about GWT, when I never said it was bad, just that using a web framework is a much better idea, especially at first. How can you predict how many users GWT might have in the future when Adobe Flex and Apollo are around the corner? On the othe…

Adobe Flex a very different approach to the rich client model. GWT will be on the same side as Prototype, Dojo, etc. if there is a showdown with Flex. Flex is not an alternative to GWT but rather an alternative to AJAX. I suspect both sides will continue to coexist peacefully.

Keep in mind that GWT is not a full web framework. So it's pointless to argue which is better, web framework or GWT, just like apples and oranges. You can use GWT with whichever back end framework (e.g. Rails) you want if you choose to go that route. Like I said earlier, GWT is an alternative to JS frameworks like Prototype, not server frameworks like Rails. What GWT does allow you to do is not use a web framework at all since its server-side calls are very easy to implement. But if you require a DB, etc, you can still use Rails and GWT.

Re: What language is the majority of startups using today?

#64

Post by luismg » Tue, Aug 28, 2007, 10:05 PM UTC

niels wrote: post #50

steve wrote: post #18

Earlier quoted context omitted.

I'm using webpy for a few sites and it seems great to me. Are there many reasons for the switch? Or did you just want to try something new/better supported? I'm thinking of taking a look at django just because guido tells me to, but I don't see any strong reason to switch.

I really like webpy and its open ended approach, but Django is just a more complete framework, and thats what I need for rapid development. django.contrib contains user/auth and other things I'd need to roll my own in webpy. And the middleware, like session stuff - beeing written for django - ties nicely in with all the helpers (generic views, etc..), while still being loosely coupled. Initially I thought that Django…

I really appreciate these comments about webpy. I recently started using it and I love it for its simplicity, but at the same time I wondered about the advantages/disadvantages of its "anti-framework" philosophy against the full features of a mega framework ala Django, Pylons or TG.

I still find it very appealing, because 99% of the time, it is used for common, simple websites. And in these cases, its simplicity pays off. I like that I don't have to fiddle with multiple files or configurations, since everything can be contained in a single file in a very clear way, and just adding "web.run" to your script converts it into a running website.