41–50 of 64 posts
We use Ruby on Rails with a lot of JavaScript for Ajax-y thingies. So far there's only 2 of us, but looks like here in NYC there's more than a few RoR devs.
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'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,…
Earlier quoted context omitted.
I disagree. I believe the opposite: GWT is a bad choice, mainly because GWT has to be compiled every time. It's much better to use a framework, including ones for PHP, since PHP is faster than Ruby and most popular frameworks have memcached support, and a great community. Also, most frameworks are evolving FAR quicker than GWT is. Thirdly, GWT will still require server-side coding. You might as well use a framework w…
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.…
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 other hand, the server-side coding won't change from PHP, Python, or Ruby for most startups over the next year, however, and their web frameworks are much easier to use and integrate than GWT.
I like GWT, but I think it requires at least one or two additional orders of magnitude of time to get something going. Plus, you'd still have to write server-side code to handle the ajax calls, so you may as well need to start with a web framework anyway!
And remember, you don't have to compile all the time with web frameworks.
Finally, the "major" releases you mention have been very minor. For example, One of the VERY few releases GWT has had in the past 8 months involved Google changing their source to be open source, without making any improvements that I can remember.
If you started with a toolset, you should stay with it. But if you're starting a new project, use a web framework.
What would be great is if this prediction comes true:
http://getahead.org/blog/joe/2007/05/11/googles_next_open_so...
In terms of programming languages, Ruby all the way, with some Java (j2me) and Hecl thrown in.
Can someone please tell me why everyone is so anti-php these days. I'm been working on my web project this summer in php, and it seems like every self proclaimed web 2.0 site is choosing either python or ruby. I feel like I'm on the wrong side of the road, and php is web 1.0. I wonder though, do users care what language the site is made in? And has usuability and quality of a site become determined by programming lan…
To answer your question, the only thing users care about is what your site does and if it does it well. The only people who care are the other people who are developing websites as well. Basically I see the PHP backlash coming out of many painful personal experiences that hit the limitations/drawbacks of PHP. I've maintained a large social networking site written by someone else and I can tell you it was a stinking p…
RoR is great for making a prototype, but just wait until you try to find other good rails hackers. they're scarce.
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'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 had to replace some of the request dispatching when I wanted to add code that triggers on every request (eg. logging, transactions, custom session management, "who's online?", traffic analytics).
can u share these
I used webpy for my last site, but recently changed development to django. Django is really easy to learn, and provides a full stack of components that integrates really well together. I used AJS javascript library, but has changed to JQuery this time. Mostly because of JQuery's numerous plugins.
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.