4 ms·
I like the Tracers concept. As for "everything is legacy a week later" - why not stick with boring but proven technology and frameworks for software that is cr
by 20years 10y ago
I like the Tracers concept.
As for "everything is legacy a week later" - why not stick with boring but proven technology and frameworks for software that is crucial and you plan to have around for awhile? That may mean not using most of the JavaScript frameworks that are being pushed today. Sure, play with them for smaller or non business crucial stuff but why risk building a business on that instability?
There are so many other important things that a business or startup has to focus on, spend money on, etc. I guess I prefer to put a lot of resources into those things vs worrying about having to update or re-write my tech stack every few months on the latest shiny framework.
- noir_lord 10y agoI picked knockout about 3 years ago because it seemed stable then, officially supported IE and had good docs. 3 years later I'm still using code I wrote against it (though now with browserify) with no changes. The switching cost when you can dump the old framework on every new project is much lower than the "This will be around for 3-7 years". Now I follow what is happening in the JavaScript community but I don't consider using anything until its been out a year and is still active/growing. Much of the churn seems to be throwing out everything for an incremental theoretical improvement, that rarely pays off in my domain.