News for hackers. Stuff that matters.

A comment on A 'CSS reset' for TypeScript, improving types for common JavaScript API's. Parent comment

Re:A 'CSS reset' for TypeScript, improving types for common ... by gl-prod on Friday March 03, 2023 @03:04AM (#35007013)
So many libraries depends on TS and a PR like that would break a lot of them. I would say they need to put it under a flag.
[ Parent | on HN ]
Re:A 'CSS reset' for TypeScript, improving types for common ... by ocimbote on Friday March 03, 2023 @03:15AM (#35007073)
So... a PR with a flag? :)
[ Parent | on HN ]
Re:A 'CSS reset' for TypeScript, improving types for common ... by makkesk8 on Friday March 03, 2023 @04:39AM (#35007587)
* * *
[ Parent | on HN ]
Re:A 'CSS reset' for TypeScript, improving types for common ... by rgoulter on Friday March 03, 2023 @05:05AM (#35007737)
In theory, yes.

In practice, here are a couple of examples:

A thread in relation to "replace `fgrep` with `grep -F`": https://news.ycombinator.com/item?id=33189503

How people feel about Python's handling of Python 2 vs Python 3: https://news.ycombinator.com/item?id=34227760

[ Parent | on HN ]
Re:A 'CSS reset' for TypeScript, improving types for common ... by undefinedzero on Friday March 03, 2023 @05:58AM (#35008051)
Semantic versioning isn’t really usable for typed languages as the majority of fixes would be considered breaking changes.
[ Parent | on HN ]
Re:A 'CSS reset' for TypeScript, improving types for common ... by hombre_fatal on Friday March 03, 2023 @08:18AM (#35009173)
Being able to declare major changes in a version number says nothing about whether it's a good idea to make them.
[ Parent | on HN ]
Re:A 'CSS reset' for TypeScript, improving types for common ... by purge on Friday March 03, 2023 @05:10AM (#35007770)
they made the change from any to unknown in the catch handler so its not without precedent
[ Parent | on HN ]