Hacker News Reader

If there was a legitimate reason to need to migrate off of coffeescript, that would probably be a planning failure. Anything of significance that's built on top of any technology and intends to have longevity will need to factor this eventuality in. Could be said of React, Angular, Bootstrap, Foundation, Svelte, Ember, jQuery. But if it's worth doing, and it isn't always, there's money on the table for someone

View on HN

If you have long running projects, e.g. 10-15+ years you will likely migrate from A to B (sometimes because A is so legacy you cannot even google its docs anymore and/or because B is super easy to hire for compared to the legacy A), it's based on requirements and scale.

Though in this example migrating to something else from tailwind will likely have the tooling (codemods) ready (or should have at least).

Yes exactly, that's what I guess I meant to imply. If a project is expected to have a long tenure, it would have been an odd choice to pick Coffeescript (just talking out of my ass a bit here, never used it, it seemed to come and go quickly) as the backbone since it was more of a short-lived novelty and maybe not worth betting so heavily on. Tailwind as well should be considered thoughtfully based on the project, and maybe it's the right choice long-term for a substantial project or maybe better for short-lived sites that favor quick turnaround over longevity.

Reply on news.ycombinator.com