zlacker

[parent] [thread] 4 comments
1. 0x696C+(OP)[view] [source] 2025-08-22 17:48:56
[flagged]
replies(1): >>jack_h+yD
2. jack_h+yD[view] [source] 2025-08-22 21:18:10
>>0x696C+(OP)
It’s not about making zero mistakes, it’s about learning from previous languages which made mistakes and not repeating them. I decided against using go pretty early on because I recognized just how many mistakes they were repeating that would end up haunting maintainers.
replies(1): >>0x696C+IN
◧◩
3. 0x696C+IN[view] [source] [discussion] 2025-08-22 22:17:51
>>jack_h+yD
[flagged]
replies(1): >>achier+ch1
◧◩◪
4. achier+ch1[view] [source] [discussion] 2025-08-23 02:09:38
>>0x696C+IN
This isn't an issue of intelligence, and GP didn't imply that it was.
replies(1): >>0x696C+YS1
◧◩◪◨
5. 0x696C+YS1[view] [source] [discussion] 2025-08-23 09:50:22
>>achier+ch1
They very much did imply that.
[go to top]