Articolul e bun de citit, dar e subiectiv si poate lasa foarte usor o impresie gresita.
In esenta, articolul greseste generalizand prea mult, presupune ca (toata) lumea in general foloseste the wrong tool for the job.
Do I use frameworks? Only when it’s not required to maintain a product in future. But it’s a complete suicide to use them in a service that will live and grow for at least a year or two.
During this time, you will write more code, than that of the entire framework, and face its limitations more than once
Deci toate framework-urile sunt rele, indiferent la ce le folosesti?
In cele din urma, da totusi un exemplu:
But what if I want to fetch Backbone models according to my API, or not fetch them at all? Or maybe I want to get them from the localStorage? What if there’s a complex logic of updates, depending on the date and flags, and we should send a pool of the same model to another server after the fetch? You never know. Should we use Backbone in such situations? There will be only 5% of its functionality. The rest will be workarounds and custom logic.
Asta e altceva totusi, si intr-adevar este wrong tool for the wrong job.
Deci pana la urma nu orice framework e o alegere proasta si de fapt totul tine de context?
In final, a cui e vina, a framework-ului sau a celui care nu a stiut dinainte daca Backbone e bun sau nu pentru ce se implementeaza?
P.S.: The article is intentionally provocative. Of course, frameworks have certain advantages, but still, they cultivate ignorance. It’s a shame when someone can not solve a problem without a framework and gets stuck in work for days and weeks.
E problema fiecaruia in parte ca e ignorant, si nu a framework-ului. Daca tu nu cunosti si nu intelegi design pattern-uri, nu e problema nimani, decat a ta.
Alegerea unui framework pentru urmatorul proiect e o mare responsabilitate.
Cel care o face trebuie sa ai experienta necesara sau daca nu o are, sa petreaca ceva timp studiind framework-ul si scriind cod proof of concept.
I had a job interview for a company in Spain, where I had to finish a test within an hour, in the live-coding mode. The task was to create a single page application for documentation. I performed the task in JavaScript, using module libraries only. I even had time to write tests.
They couldn’t understand how I implemented routing, as well as complex interactive elements, and plenty of other things, without using frameworks. They are the guys who have been in the industry for 10 years, just like me, but they studied specific solutions rather than principles.
Funny, pai exact de asta e bun framework-ul.
De ce ar fi stat angajatorii sa incerce sa-i inteleaga la interviu propriul lui router, cand un framework are deja asta implementat, testat si para testat de ani de zile, si care poate a luat in considerare diverse aspecte pe care propriul sau router nu le-a luat?
Orice framework ia timp ca sa-l intelegi, atat cu rele cat si cu bune. Daca scriem noi framework-ul propriu, altii tot vor trebui sa petreaca un timp intelegandu-l.
Pot fi framework-uri care incearca sa faca prea mult, nu sunt flexibile in a le putea inlocui unele componente cu altceva.
Dar poate chiar si asa, sunt OK pentru unele proiecte, chiar si pentru un proiect mare, la care se dezvolta de-a lungul anilor de catre o echipa.
It’s all about the right tool for the right job.
Generalizarea e naspa.