I was super confused as to why good tools and IDEs would require typing. A bunch of typed languages do have great IDEs but I feel like that's mainly because programming in a typed language can be considerably more difficult which puts more emphasis on creating great tools to help deal with it.
This reminds me of the ES4 discussion around typing being a requirement of making the language more performant, that clearly wasn't true. I'm going to throw out a crazy idea. Maybe the language is fine in this regard and creating better tools is done by *creating better tools*, not by changing the language. Maybe changing the language has a negative effect on creating better tools because it increases the surface area and complexity those tools need have to solve. I'm not saying changing the language is universally bad, only that some problems are better solved outside of ECMA and that there is a big community out here that is working to solve this problem and they don't need anything from ECMA to do it. -Mikeal On Sep 12, 2011, at September 12, 201112:22 PM, John J Barton wrote: > On Mon, Sep 12, 2011 at 12:00 PM, <es-discuss-requ...@mozilla.org> wrote: > > Some of the discussion on this thread amounts to "IDEs work great for > typed languages so let's make JS typed". What if we started with > "What would be great for JavaScript developers"? Then we would not > waste a lot of time talking about static analysis. It's the wrong > tool. > > jjb > _______________________________________________ > es-discuss mailing list > es-discuss@mozilla.org > https://mail.mozilla.org/listinfo/es-discuss _______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
