/top/
/new/
/best/
/ask/
/show/
/job/
^
slacker news
login
about
←back to thread
Zig breaking change – Initial Writergate
(github.com)
228 points
Retro_Dev
| 1 comments |
04 Jul 25 04:11 UTC
|
HN request time: 0.21s
|
source
Show context
zwnow
◴[
04 Jul 25 06:46 UTC
]
No.
44461773
[source]
▶
>>44461067 (OP)
#
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]
▶
>>44461773
#
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]
▶
>>44461858
#
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
#
1.
skybrian
◴[
04 Jul 25 17:14 UTC
]
No.
44466246
[source]
▶
>>44461901
#
Static types help to find what needs to be fixed. Something like 'go fix' would be useful for fixing them. Apparently something like that is being considered for zig.
ID:
GO
↑