11 ms·
Most of the 'mess' I see is the current state of Javascript frameworks, which are in the Cambrian explosion phase of things. I'd just use Rails as a default fo
by davidw 14y ago
Most of the 'mess' I see is the current state of Javascript frameworks, which are in the Cambrian explosion phase of things.
I'd just use Rails as a default for most things I do these days, and if it's not a good fit, evaluate other technology.
- lifeisstillgood 14y agoI was just about to post "Cambrian explosion" as an metaphor for the state of javascript libraries. There are good reasons to get the HTML formatting off the server and into the client, so the new style JS is all going in the right direction. So another metaphor: All these frameworks are trying to solve the right problem in the right direction - which one will win out eventually - who knows, but even if you hitch a ride on one that stops half way, you are half way closer to the right destination than if you wait.
- redeemedfadi 14y agoWhat will be funny is when we move everything back to server-side once we don't have network latency/bandwidth issues.
- lifeisstillgood 14y agoReally? transmitting just the data and letting the client handle the display and interaction seems a much more natural split. It alos makes my server software conceptually simpler - which is always nice
- metaphorm 14y agoI agree. Separation of concerns is a very good design pattern. MVC server frameworks (like Rails and Django) have already separated out the concern of displaying data to the user with their template systems. its a very reasonable next step to just migrate the entire template system off the server and let the client do it. This has gigantic performance increases for servers under heavy load, and it puts the display logic in a domain that is more naturally suited to dealing with it (JavaScript and the DOM instead of treating HTML as just a string). The pattern also promotes the use of RESTful APIs for data access from the server, which has the wonderful bonus of allowing you to make your data publicly accessible for free if you want to.
- davidw 14y agoTemplates... ok - that's fairly convincing. I'm less convinced about keeping the model and controller client side, because they end up replicating stuff that still has to live on the server anyway, to some degree. That just seems to make things harrier than they were to begin with.
- lifeisstillgood 14y agoI think if you are trying to replicate the same functions you are right. But if I have, say, a User model then it is merely a conveniently name for two groupings of functions. My client side user should know nothing about Dbase lookups or persona verification - just as server model should not care about displaying addresses. Overall I think getting the crap out of the server makes it much much easier to reason and architect
- rwallace 14y agoIn the absence of a way to transmit information faster than light, we will always have network latency issues.
- Cthulhu_ 14y ago> I'd just use Rails as a default for most things I do these days, and if it's not a good fit, evaluate other technology. But ZOMG RAILS IS INSECURE, quick, switch to something else! [/sarcasm]. Evaluating other technology is the opening of the rabbithole.
- blablabla123 14y ago+1 for ZOMG
- static_typed 14y agoGiven the constant flood of Ruby and Rails security problems of late, it would seem better to start new projects with something a bit better engineered.
- sergiotapia 14y agoI understand where you're coming from. But don't you feel that the security fixes are coming out in a timely fashion and once they're shut, they're gone for good? (At least that particular exploit) Slowly but surely Rails will become robust because of this.