Right, this was a supercomputer at the time but the context has changed considerably. I read a small book once from the late 60s that declared interpreters impossible for efficiency reasons.
-
-
5. Today's JS tooling is by far better than anything that these other systems have done *for JS*, especially on the static analysis front, despite very significant efforts in those systems to support JS.
-
The issue is one of standardization, both around the "spec" (which could use some improvement) and shared abstractions (so people tend to build compilation stages that produce high fidelity output).
-
Low level tools like jscodeshift/recast do a good job at this, but small details do us in. One example of a small detail is inconsistency in tooling about where to put the sourcemap, and how to communicate where you want it to go
-
(inline vs alongside, and if alongside, based upon which root directory). This is a small detail, and one that would benefit from standardization, but not a consequence of failing to review Eclipse and Visual Studio closely enough.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.