141–150 of 160 posts
Earlier quoted context omitted.
Have you tried Java EE 6 ? JAX-RS in particular is a splendidly designed api for RESTful services. And then you can make single page apps instead of JSF. This method is even going have ide support in Netbeans 7.3 with wizard-driven Backbone/Angular app generation.
Lots of real world apps don't compose nicely down to a bunch of REST bullshit.
Earlier quoted context omitted.
Like the Django patch that was released yesterday? ( https://www.djangoproject.com/weblog/2013/feb/19/security/ ) The fact that the Rails team quickly responds to vulnerabilities should be reassuring not a disincentive to use the framework. All software is subject to vulnerabilities - the recent issues with YAML are a class of exploit common across many frameworks in different ecosystems (Django's TastyPie had a simi…
Yes, Django took a solid step to properly fix the underlying issue, rather than apply many small sticky-plasters over several days instead, leaving the same basic vector open in the meantime. In fact, the Django issue reported was posted on HN yesterday and the comments on that posting underline what I just said here. Remember - Python for Pros, Ruby to pose.
Earlier quoted context omitted.
I've been using Play every since 2.0 came out and I'm a huge fan. It's just fun to work with.
Are you using Java or Scala with Play 2.0? Play looks like an excellent framework, but my perception is that Play 2.0 is very Scala oriented. Scala seems a bit daunting.
That said, you can start with Scala as "better Java" and ramp up to its advanced features. That's how I began. At first you're just replacing for-loops with map/reduce, eventually you'll start passing around implicit variables and using for-comprehensions all over the place.
Earlier quoted context omitted.
You have an app with multiple Ruby versions?
Yes. I take it you've never worked at an enterprise company before ? Every time a new developer comes on board they just love to add new technology X and then in the years to come other developers add Y and so on. Of course there are developers who have to manage this.
Earlier quoted context omitted.
Curious, what other web dev frameworks offer a unified stack (ORM, deployment, dependency management, testing, project structuring)?
Offering all of those things is nice, but tightly coupling them all together is where Rails goes wrong many/much of the time.
Better yet, what framework do you believe offers all of these things and does a significantly better job at decoupling than rails?
The pushback against Ruby/Rails has been building for a long time. There's always been jokes about Ruby being slow: http://harmful.cat-v.org/software/ruby/ But there was a stretch from around 2005 to maybe 2008 where Rails seemed to defy criticism. It grew and grew, despite the criticism. I tried it for a project in 2006 and I became a fan. The easy use of 3rd party code, via gems, was much easier than anything I had…
> And even now, in 2013, when I have to set up a new server with Rails, even with Nginx and Unicorn and all the other systems to help me, I find Rails annoying to set up, especially compared to the simplicity of PHP running on Apache or a Clojure app bundled up with something like "lein uberjar".
Then don't pick Unicorn. Yes, Unicorn is a fantastic app server, but it requires that you know the app server very well, and as with all stand-alone app servers, the configuration is more complex.
Instead, pick something like Passenger. Passenger runs as an Apache module and is just as easy to get running as PHP.
Lua.
With the LuaVM, you really can fulfill the absolute promise of 'write codebase once, run anywhere', where "anywhere = wherever you've got your LIBS+LuaVM host code running", of course.
You can do it in a compact, highly performant manner. One host binary for each supported platform, much work at the vendor layer to adopt to a common Lua dictionary/table, and the rest is .. as they say .. fat city. All nice app case logic in a comfortable, friendly language.
Java long ago become an unweildy beast replete with inane dependencies and insensitive amounts of hassle to get things in and out, whereas with the Lua stack, it seems, one need only know how to do things at least with a C stack, first, to gain immense benefit.
I daily dream, in my idle moments, of a complete OS based on a selected set of normal/plain-ol' /usr/lib C-libraries, but booting directly to Lua, for GUI and all higher-layer goodness. Such fancies are already tickled in places like LOAD81 and MOAI, and so on, and I think sort of prove the point, a little, that the VM is no longer something a vendor controls, but rather .. the developer.
Earlier quoted context omitted.
Surely you don't think that Rails is better than everything else in every single respect? There are plenty of frameworks that are simpler (Flask/Sinatra), faster (Play, etc.), support lightweight concurrency better (node.js based, Play too, etc.), have much better IDE support (ASP.NET MVC), support client/server partitioning (Meteor/Opa), and so forth.
What you just said is very different from the first sentence of the comment I replied to. Let me repeat it, "Rails ... is no longer better than the competition." I think rails is better than the competition if my goal is to make fairly standard websites. It would be a rare exception where I think something else is more suitable.
The thing is these frameworks have caught up so much on the expressiveness front that their other advantages can easily start to outweigh the small advantage that Rails has there. But if you are building a low traffic CRUD site (like most sites), then yeah use Rails. If you are building say a chat application, I wouldn't use Rails.
Earlier quoted context omitted.
What you just said is very different from the first sentence of the comment I replied to. Let me repeat it, "Rails ... is no longer better than the competition." I think rails is better than the competition if my goal is to make fairly standard websites. It would be a rare exception where I think something else is more suitable.
"No longer better than the competition" doesn't mean "Worse than the competition for ALL use cases". The thing is these frameworks have caught up so much on the expressiveness front that their other advantages can easily start to outweigh the small advantage that Rails has there. But if you are building a low traffic CRUD site (like most sites), then yeah use Rails. If you are building say a chat application, I would…