3 ms·
In an earlier comment, you said you weren't a "framework guy". If you were you would have heard this cogent argument dozens of times already as it's fairly com
by jf22 7y ago
In an earlier comment, you said you weren't a "framework guy".
If you were you would have heard this cogent argument dozens of times already as it's fairly common knowledge to people who are into frameworks.
Consider trying to understand why frameworks are created before using them. Understanding the motivations behind a framework will help you navigate the api easily and could change your opinion about whatever frustrates you.
- Zelphyr 7y agoI've used every one of the frameworks that I mentioned with the exception of Svelte, and am surrounded by framework users. Not a single one has ever made that argument. It's always, "Look at this new shiny framework, we must use it!" And all of those frameworks were great right up until the point that my client or company had a product requirement that the framework designers hadn't though of and then, suddenly, the framework was working against me instead of for me.
- hardwaresofton 7y agoI'd also consider myself not a "framework guy" -- Spring is not my favorite, I pick flask/sinatra over rails/django, servant over yesod, vue + vue-router over ember (these days) etc. Maybe the distinction is that it really matters which framework, and how it's put together, and how much you have to commit to use any of it. I think the commenter's question was really more about the diaspora of these tools and why they all exist -- svelte is pretty decidedly not a framework (in fact I don't even think you can make it one, AFAIK there isn't like a "svelte data"). IMO the only full blown frontend frameworks are Ember, Angular and react/vue + react/vue-router + flux-y pattern data store.