3 ms·

if language is hard to read, hard to write, and slow to compile it creates problems when you need to push fix to prod ASAP, or when you need to train new emplo

if language is hard to read, hard to write, and slow to compile it creates problems when you need to push fix to prod ASAP, or when you need to train new employees reason why go is popular and is the cloud native language there is still the need of a go like language for native world, i personally believe Zig is the answser, another close one is Odin, it's definitely not rust

pkolaczk 4y ago
If you need to push a fix ASAP to production, you definitely want a language with very strong static typing offering confidence that the fix doesn't accidentally break something.
planetis 4y ago
Nim is closer to become Go killer with it's capability to target both native and JS. There are multiple async implementations offered as packages, since async is not part of the language. SPAs frameworks and bindings of popular libraries like nodejs. Databases and web frameworks, ORMs and migration tools. Multithreaded could obviously be improved in order to have better servers. But it's already looking promising.
shirogane86x 4y ago
If I had to push a fix to prod ASAP, I'd personally rather it take more time but go in production safely. Especially in a case like that with not enough testing to really be sure if everything's okay or not, the stricter the compiler the better. And if I had to train employees, I'd rather them fight the compiler more in the beginning but write better code later, than be able to write code quickly but make a horrible mess. I've seen the "fast and loose" approach fail miserably and turn into a nightmare enough times that I now advocate for strict languages whenever I have a say in things. (which is why, with the state of programming languages right now, I will almost never suggest zig or go for a project). I think developers in generals should trust themselves less, to be honest. I feel like it would avoid a lot of issues down the road.

pkolaczk 4y ago

If you need to push a fix ASAP to production, you definitely want a language with very strong static typing offering confidence that the fix doesn't accidentally break something.

planetis 4y ago

Nim is closer to become Go killer with it's capability to target both native and JS. There are multiple async implementations offered as packages, since async is not part of the language. SPAs frameworks and bindings of popular libraries like nodejs. Databases and web frameworks, ORMs and migration tools. Multithreaded could obviously be improved in order to have better servers. But it's already looking promising.

shirogane86x 4y ago

If I had to push a fix to prod ASAP, I'd personally rather it take more time but go in production safely. Especially in a case like that with not enough testing to really be sure if everything's okay or not, the stricter the compiler the better. And if I had to train employees, I'd rather them fight the compiler more in the beginning but write better code later, than be able to write code quickly but make a horrible mess. I've seen the "fast and loose" approach fail miserably and turn into a nightmare enough times that I now advocate for strict languages whenever I have a say in things. (which is why, with the state of programming languages right now, I will almost never suggest zig or go for a project). I think developers in generals should trust themselves less, to be honest. I feel like it would avoid a lot of issues down the road.