zgiber

I wonder what makes someone go such a great length to bash a language, any language. I say bashing, because even the few valid points in the post are not written in a constructive style. After all is there a language that can't be criticised?

Is the post written to make one feel better having a failed a project the language? (It's not me, it's the language) Or is it the failure to understand that not everyone thinks / works the same and what one finds unacceptably bothersome, others barely notice? Languages that do not cater for a real need would likely vanish on their own, they rarely need help.

As for Go, despite the differences compared to "more sophisticated" languages it works brilliantly for the projects I've encountered. I hope the author is not forced to work with Go though. For the rest of the community, we keep churning out services, giving our feedback to the Go team and seeing the slow evolution of the language without breaking our stuff in production.

That should not be an issue, unless the code is written in notepad. As for interfaces, a better approach is to return struct and accept interface in your functions wherever it is possible.

It may not be a good tool for communicating between services implemented in different languages. But i’d happily use it to save stuff to disk where database is overkill.

Thanks for the great write up! I’d watch this as a series or movie

Britain isn’t really poor as a country if we look at all the money/wealth in it. The distribution of the wealth is very one sided though. Recent decades of law making favouring the top few percent. Giving more to the wealthiest few doesn’t seem to trickle down apparently.. eroding middle class and diminishing purchasing power is what bothers me most. Privatised energy, water, public transport aren’t serving the public’s interest anymore but the shareholder’s. Housing prices getting out of reach of the average workers is rubbing salt on the wound. These are mostly symptoms.

You can live in London and never miss a car, but try it anywhere outside of big cities and it’ll be a different story. Not to mention the brutal train ticket prices.

“Forgot” to read the reviews before starting to watch.. no review can change my mind now: I like the show very much. Epic.

Log the things that require a human to fix something every time they happen (Include useful info that’s needed for fixing). Create metrics of the rest: things that show patterns. Trace a percentile of actions that span over multiple components.

I believe all the three: logging, metrics, tracing have their own uses, one can’t replace the other.

I get the convenience part but the waste reduction itself is already worth the switch. Yeah your shaving cartridge or flaking teflon pan might be a drop in the ocean (perhaps literally) but when there are billions of humans around we should think about what inconvenience does it worth to keep our environment lovable.

I had bad luck with the top spec 13" DELL XPS (2021) - Fan was loud, and audio jack randomly failed to detect headphones. Webcam was mediocre, audio quality was really really poor. It was ok for a machine that was only used for coding, but wasn't great for remote work / conferencing. Replaced with the M1 equipped 13" macbook which was about £400 cheaper (although also lower spec) and I'm very happy since. Despite the lower spec it does almost everything much faster. The only nuisance I had was a few Terraform providers not being released for ARM, and the occasional Docker woes with a few obscure images. The Macbook's overall quality and versatility beats the XPS by a good margin for my purposes.

“in LIFO order” - made my lunch break

I feel that the comparisons are quite one dimensional (crushes Rust, Go etc..) picking one or two metrics. Why is the memory footprint almost fully ignored in the article? Application speed is rarely the bottleneck in platforms I work with, but it does matter a lot how many instances you can run in a cluster where memory is often a limitation. For me personally it's also important how easy is to write concurrent code to work around IO bottlenecks.

Please don’t specify ISO8601 as the date format. That standard embodies dozens of formats. Use one specific format instead like RFC3339.