4 ms·
> How has RoR's ever changing JS ecosystem impacted these organizations? As much as I think RoRs initial love for coffee script was a mistake (although it cert
by e12e 3y ago
> How has RoR's ever changing JS ecosystem impacted these organizations?
As much as I think RoRs initial love for coffee script was a mistake (although it certainly did help at a time when javascript was in a horrible, braindead place) - I'm not sure I'd like the js mess at Rails' feet.
I think that the team navigated js integration as well as could be expected - and everyone was happy in version 7 when js support in browsers had advanced to the point that most of the special handling could simply be ripped out.
The remaining issue IMNHO is that there's no browser support for typescript - and using ts dictates a build pipeline which would otherwise be needless complexity with modern js and js modules.
- arrowsmith 3y ago> javascript was in a horrible, braindead place was?
- e12e 3y agoBefore modules, "let"/"const", uniform APIs cross browsers (xmlhttprequest, anyone?) - js was much, much worse. Rails dates back to before 2005 - before chrome existed, and around the time Firefox emerged from Netscape.
- PH95VuimJjqBqy 3y agocoffeescript was an obvious deadend at the time it was created. The only thing that could have saved (maybe) is better tooling but the community had no interest in it (who knows why). Rust feels like this too.
- e12e 3y agoIf I remember correctly, the first version of coffee script was quite sane, but the second version was completely different, and IMNHO much worse? I think the initial version was a moderate enhancement on js, fixing some things like global scope etc?