3 ms·
follow-up post : https://debugged.it/blog/20000-lines-under-the-go-cean/ https://debugged.it/blog/20000-lines-under-the-go-cean/
by nassimsoftware 5y ago
follow-up post : https://debugged.it/blog/20000-lines-under-the-go-cean/ https://debugged.it/blog/20000-lines-under-the-go-cean/
- kvnhn 5y agoThanks for sharing this. It's very hard to lend credence to this series after reading this follow-up. Quoting from the link: "There are certainly many reasons to hate Go, from the unusual syntax to the half-arsed way they decided to implement the programming model. On the other hand you can go all fanboy over how cool Go is because it makes it so simple to write microservices. (No, it doesn’t. It really, really doesn’t if you want to do it properly.) If you jumped on either of these bandwagons, I would recommend getting off as soon as possible. Neither of these approaches are very professional and are telling signs of inexperience in software development." There is an upsetting level of hypocrisy in patronizing your readers for consuming the clickbait-titled articles _you authored_.
- deleted 5y ago[deleted]
- jgrant27 5y agoMost applications I tend to see don’t even use concurrency because they are so small and simple that they don’t need it. Sorry but I just can't take your opinion of any language seriously or that you have much practical experience at all because of statements like this.
- mst 5y agoHaving once replaced a sixteen core go program with a single-process perl script that completed the same task 4x faster, I think remembering that a lot of the time we (as a profession) manage to overengineer things is worthwhile.