←back to thread

Zig breaking change – Initial Writergate

(github.com)
228 points Retro_Dev | 2 comments | 04 Jul 25 04:11 UTC | HN request time: 0.419s | source
Show context
zwnow ◴[04 Jul 25 06:46 UTC] No.44461773[source]▶
And this is exactly why you do not use shiny new languages for your projects. Hope tigerbeetle won't have too much trouble with this
replies(5): >>44461853 #>>44461858 #>>44462043 #>>44462061 #>>44462171 #
Hamuko ◴[04 Jul 25 07:04 UTC] No.44461858[source]▶
Are people deploying production code in a language that is still in its 0.x version?
replies(3): >>44461880 #>>44461901 #>>44462078 #
cenamus ◴[04 Jul 25 07:10 UTC] No.44461901[source]▶
I mean, what's the difference to the python 2/3 debacle? People were writing/extending in python 2 long after it was declared obsolete
replies(3): >>44461971 #>>44462086 #>>44466246 #
Hamuko ◴[04 Jul 25 07:17 UTC] No.44461971[source]▶
Not having breaking changes every N months?
replies(1): >>44463222 #
1. flohofwoe ◴[04 Jul 25 10:30 UTC] No.44463222[source]▶
Each new minor Python 3.x version has plenty of deprecations followed by removals in the stdlib though.
replies(1): >>44464194 #
2. Hamuko ◴[04 Jul 25 13:06 UTC] No.44464194[source]▶
I don't think even those are particularly short periods. TestCase.assertEquals() was deprecated in Python 3.2 (February 2011) and removed in Python 3.12 (October 2023). 12 ⅔ years to get rid of a silly alias because it's a breaking change (of a single character).