News for hackers. Stuff that matters.
Re:Rhombus Language by hnlmorg on Tuesday March 18, 2025 @05:01AM (#43397071)
Curious to read that because I’ve always had the opposite opinion of the above:

Typescript looks nice to work with but the tool chain is horrible (this isn’t really Typescripts fault though, more a synonym of it having to compile to JS).

Go looks horrible to work with (too simplified syntax) but is actually really nice because the tooling is (mostly) spot on and it’s simplified syntax weirdly helps with maintainability for large projects that have evolved over multiple years.

I guess this just goes to show how much personal preference can be a driving force behind our platforms of choice.

Re:Rhombus Language by frou_dh on Tuesday March 18, 2025 @08:14AM (#43398477)
> Typescript looks nice to work with but the tool chain is horrible (this isn’t really Typescripts fault though, more a synonym of it having to compile to JS).

It's not even inherent to TS that the toolchain must be a morass of moving parts and multiple config files, as shown by Deno in contrast to Node.

Re:Rhombus Language by frontfor on Tuesday March 18, 2025 @07:06AM (#43397983)
I’m not sure about Go being full of footguns, but for one, a panic in any goroutine forcibly terminates the entire application.
Re:Rhombus Language by noisy_boy on Tuesday March 18, 2025 @07:36AM (#43398215)
The constant incantation of if err != nil is bad for my aging hands and frankly hurts even more when you see Rust's single-character error marshalling using ? operator.
Re:Rhombus Language by shikck200 on Wednesday March 19, 2025 @07:56AM (#43410757)
I have aliases for these kinds of general things (in vim) for most languages i use. Eg. if im inside a typescript file i have a mapping produces if ($obj) { $ } and i tab to enter the next "$" to insert the correct things.

The same goes fo Go. I have a mapping for if err != nil { ... } and the cursor is places inside the block.

I dont understand why people dont use this kind of thing for the most common programming constructs.

Re:Rhombus Language by noisy_boy on Wednesday March 19, 2025 @10:09AM (#43412232)
I would suppose they do and are free to do it - however, liberally having to spread it all over the code hurts readability. I'm sure people can say in response to that after a while you stop noticing or that their favorite IDE can collapse it and so on. It can be excuses all the way down instead of admitting that it is a shortcoming of the language.
Re:Rhombus Language by hnlmorg on Wednesday March 19, 2025 @07:10PM (#43418202)
You say it hurts readability but most of the time I want the unhappy paths to be visible.

Coding software that works when conditions are met is easy. Coding software that works when things break is hard. So I want error handling to stand out because it forces errors to be handled visibly and properly.

All too often I see Python programs drop to a stack trace under normal execution or JavaScript return cryptic errors that don’t mean much to anyone bar the core maintainer. But I seldom see 3rd party Go software bomb out in quite the same way. And I think that’s in large part because Go doesn’t try to hide errors away as an inconvenience that we shouldn’t be looking at.

So I’ll agree Gos approach is ugly. But sometimes good software does just look ugly. And the way I see it, it’s the quality of the compiled software that matters more than the beauty of the combination of characters that built it.

Re:Rhombus Language by noisy_boy on Wednesday March 19, 2025 @09:15PM (#43419015)
I am not questioning it's effectiveness. I have written Go code that is chugging along without issues in Production. My point is ergonomics and effectiveness are not mutually exclusive - hence the example of Rust's ? operator - effective and ergonomic (Rust also has issues with difficult to read lifetime+trait annotations).

The sad part is that people have been talking about this for years but Go team stubbornly refuses to make error handling more ergonomic.

Re:Rhombus Language by Kamq on Saturday March 22, 2025 @11:00AM (#43446150)
> Rust's ? operator - effective and ergonomic

It is, but it's also subtle, and if you want branches (especially sad-path branches) to be explicit, that's not a good thing.

Re:Rhombus Language by bbkane on Tuesday March 18, 2025 @02:30PM (#43402993)
https://100go.co/ has a great list of Go footguns
Re:Rhombus Language by hnlmorg on Tuesday March 18, 2025 @03:52PM (#43404205)
Most of the stuff on there is just talking about general programming mistakes. Eg overly nested code is a problem a developer can make in any language.

Sure there are some Go specific stuff in there. But the whole thing reads more like someone preaching an irrational hatred for something rather than a fair breakdown of genuine footguns.

Re:Rhombus Language by fileeditview on Tuesday March 18, 2025 @03:11PM (#43403606)
I think that's the intention of a panic.. however there is still recover if you need to "catch" it.
Re:Rhombus Language by frontfor on Tuesday March 18, 2025 @10:27PM (#43407723)
The issue is you need to explicitly recover each goroutine just so a nil dereference or a panic from a library you have no control over doesn’t bring down the whole application. Maybe this is the way it has to be, but it is a little known fact that might bite you.
Re:Rhombus Language by hnlmorg on Wednesday March 19, 2025 @03:57AM (#43409264)
The only time a library should be panicking is if they’ve reached a state they cannot continue from.

I’d be interested to know which libraries you’re working with where this has been a problem because I’ve only ever experienced one occasion where a 3rd party library panicked unnecessarily.

Re:Rhombus Language by odyssey7 on Tuesday March 18, 2025 @09:38AM (#43399294)
JS isn’t breaking, it’s the layers between there and Typescript.
Re:Rhombus Language by eitland on Tuesday March 18, 2025 @11:27AM (#43400580)
JS the ecosystem is amazing, kind of.

JS the language isn't breaking.

JS the language is broken. I'm not aware of a single foot gun from PHP that it does not share in some form - but I am sure there are some.

However I am also fairly certain that JS has some unique footguns that PHP doesn't have.

So I am really impressed with what people manage to create with such a language, but in kind of the same way I am impressed at how people built rail infrastructure before lasers, gps, modern dynamite and excavators existed.

That said, I am still impressed that it was written in three weeks. I just think it is tragic that it became the backbone of client side web development.

Re:Rhombus Language by timkq on Wednesday March 19, 2025 @06:40AM (#43410267)
Simplified syntax helps with maintainability for large projects? You're talking about a "modern" language which had no generics for the better part of its life? The language filled to the brim with "if err != nil"? Go is horrible to work with.
Re:Rhombus Language by hnlmorg on Wednesday March 19, 2025 @07:00PM (#43418137)
I repeat:

I guess this just goes to show how much personal preference can be a driving force behind our platforms of choice.