31–40 of 97 posts
Downvoting everyone answering the title question and not reading the article. You guys should be better than this. It's not about cowboying or NIH. It's about using a library called Turbolinks https://github.com/turbolinks/turbolinks to render static pages server-side and swap the content out with js.
Downvoting everyone answering the title question and not reading the article. You guys should be better than this. It's not about cowboying or NIH. It's about using a library called Turbolinks https://github.com/turbolinks/turbolinks to render static pages server-side and swap the content out with js.
It seems like most people are more interested in discussing the question posed by the title than discussing the product the article is advertising.
JSON to html5 content is now at a few thousand SLOC, but still easy to maintain - by me, but honestly not by others. Would it be better with a framework? No, because my employee is a C.S. company with an entirely different focus (applying some corner theory stuff to industrial products): no one here is an expert in PHP Frameworks, instead we have some pretty good C++ and ocaml masters.
I don't think you'll find anyone who thinks it's hard to build 1 SPA without a framework. The thing is that if you build 2, 3, 100, you'll find yourself doing the same stuff over and over again (and always better than the previous time, so that you'll want to replace all your old code, which is now obsolete), and that's when frameworks are useful.
and when you hire and work with others, it's better if they already know and agree with how to do things rather than having to learn your custom SPA.
The title is misleading since this is basically a TuboLinks article and doesn't really explore the problems of building an SPA without a framework.
I know they are trying to promote their own Front-End Framework (while trying to pretend that it isn't one), but with regards to the question on the title, my experience is: you can, but please, don't. It actually isn't THAT hard, but what will happen is that you'll end up reinventing the wheel badly, and you'll be chasing bugs and fixing platform inconsistencies for months. It won't be optimized and it won't work in…
.. and paying AWS for it.
Earlier quoted context omitted.
I think we've had some of this on the backend too. I've seen "you don't need a framework" a few times outside of the current JS atmosphere. Seems like the easier it is to get going, the more frameworks you'll get. PHP is similar - a good whack of frameworks. The community has banded together, producing a group of developers, one from each major library or framework just so they can figure it out. It's called the Fram…
I actually prefer coding by myself as I get to do my own thing but when it comes to working with teams, I strongly prefer a framework because its kind of like how religion helped form alliances or like how a river flows in the same direction. Its all arbitrary bullshit but helps reduce collisions and arguments. After all, highly documented, well tested bullshit, is much better than highly untested, no-documented bull…
I know they are trying to promote their own Front-End Framework (while trying to pretend that it isn't one), but with regards to the question on the title, my experience is: you can, but please, don't. It actually isn't THAT hard, but what will happen is that you'll end up reinventing the wheel badly, and you'll be chasing bugs and fixing platform inconsistencies for months. It won't be optimized and it won't work in…
I think this is a bit short-sighted. While building a framework from scratch is certainly not for everyone, there's definitely value in building one. You say things like `you have to maintain your poorly cobbled-together "framework"` but when you think about it, this was true of authors of major frameworks at some point as well.
Remember when React added id's to every single DOM element? Or when Ember was dog slow? Framework authors and maintainers learn lessons over time and with each project iteration they become more valuable due to their skillsets.
> If someone DOES pick it up after you, (the poor bastards), they are going to be bothering you day and night, or go insane after 2 weeks
Again going back to skillsets: this is part of what makes large OSS project developers desirable: they've been through the process of passing-the-baton and they know the importance of things like documentation, maintainability, etc and can take concrete steps to further goals in those areas.
The title is misleading since this is basically a TuboLinks article and doesn't really explore the problems of building an SPA without a framework.
Agreed. TurboLinks itself seems unnecessarily heavy. So you avoid a full page reload, but you do still have to fetch the whole page over the network and render it. Just without the browser loading icon spinning.