4 ms·
> it's a seriously underrated benefit. It is not without a cost, the cost being an lack of standard ways to accomplish things. For long running projects where
by babyrainbow 10y ago
> it's a seriously underrated benefit.
It is not without a cost, the cost being an lack of standard ways to accomplish things. For long running projects where devs may come and go, having a standard way to do things is an incredible advantage, and will result in a much more consistent code base.
For real world front end project, this is a much more important concern, imho, than ease of picking up. For your particular use case, I agree something like Vue is a better fit.
- subbu 10y agoLong running projects in JavaScript may not be that long really. If you leave any codebase for a couple years, things would have changed so drastically, new devs may not even recognize the code. An year old JS project may be using React, a 2-year-old project could be using Angular, a 4-year old project might be using Backbone, a 6-year-old could have $("#el").bind() all over while 8 year-old project could have been in Prototype.js.
- postcarnival 10y agothats an interesting reflection thank you
- edwinnathaniel 10y agoSince I've gone through the same experience like this, I'd like to know if this is a norm :D. I've seen people do write-up of how they re-write the front-end from jQuery to Angular|Ember|React so it's not like there are many long-running JS projects that require solid structure. 3 years old (small-medium size) projects tend to get re-written. Here's another one that I've seen and experienced before: 10 years old product where some section of the products are written in pure JS, some section in jQuery, some section in BackboneJS + Marionnete, some section using EmberJS.
- seangrogg 10y agoI've heard this argument before and I find it fascinating. Why can't we have something that is both standardized and easy to pick up? Is there something inherent to one that blocks the other? Any ideas? Disclaimer? I don't use Vue, but I've seen this argument made for Ember (against Angular 1.x) and Angular 2 (against React).
- babyrainbow 10y ago>Why can't we have something that is both standardized and easy to pick up? Simply because one has to learn the standards in the former case. In the latter, it is mostly left to the users imagination and their own sensibilities, which differ from person to person.
- seangrogg 10y agoBut does being "easy to pick up" intrinsically mean things are left to the user's imagination? Can't we make something that is standardized AND easy to learn?
- paulddraper 10y agoBecause "easy to pick up"/"easy to learn" means "most ideas aren't new to me", i.e. "it adapts to my particular way of thinking".