nasretdinov3 hours ago
I'm really looking forward to SIMD becoming standard in Go. It might sound very niche, however SIMD intrinsics (which is different from how they are available now, which is via non-inlinable assembly) allow to generate similar vector code to C intrinsics, with very little in terms of overhead due to bounds checking, etc. This allows to write programs that are highly optimised for modern CPU and get maybe 80% of performance compared to the same variant in C. This is much better than the current state where C typically outperforms Go by at least 2x/3x, and SIMD typically allows you to get 10x or more speedup already, which gives UNLIMITED POWER to Go when CPU performance is a bottleneck
losthobbies20 minutes ago
I bought Alex's "Let's Go Further" book a while back, I really should spend some time with it.
I want to learn Go.
jiehong3 hours ago
Perhaps the Go community should take a look at JEP or PEP to better document features and their life cycles and statuses overall.
p2detar24 minutes ago
It depends. I read JEPs quite often as part of my job. They are nice as a sum up of the intent behind the feature but they kind of hide the discussion and commits. Also one Java feature may encompass multiple JEPs.
Go‘s github discussions on the other hand, give me live-view of the latest state of the experiment. I find both useful and don‘t prefer either.
pjmlp2 hours ago
That would be asking too much, learning from older languages experience.
ktpsns4 hours ago
I find the arena experiment very interesting. If done right, whole programs can be structured as as a set of arenas. I've read some things on arenas here such as https://news.ycombinator.com/item?id=37670740
b33j0r3 hours ago
I am a low-level zig guy right now too. I have been around for a long time, and it’s funny to see arenas come back into vogue as a solution to nearly everything.
Arenas are great for avoiding allocations per tick/request/frame/layer. No symmetric free() to bracket lifetimes! They have a purpose, and we always knew that.
But by definition, your program is over-allocating as a tradeoff. Makes a ton of sense in certain use cases. However, we didn’t invent garbage collection and borrow-checking and realloc() just to publish papers ;)
Half of my time programming zig is spent considering allocation strategies. That’s a feature. “Where are the bytes?”
fredrikholm4 hours ago
Once allocators in general click, memory management in C becomes a total breeze.
Combined with typed fat pointers (slices and strings), typed hashmaps and stack-trace-assertions, C in general becomes quite nice. The rest is compiler flags.
Go solves this by being a better language out of the box, but with the Wirthian aspects removed they feel very similar. Perhaps not so surprising.
yjftsjthsd-h5 hours ago
So, these are feature flags by any name, right?
hnlmorg3 hours ago
No. Feature flags are a mechanism for enabling some of the experiments. But what’s being discussed here are the features themselves.
yjftsjthsd-h3 hours ago
Hm, that's interesting; chrome://flags does seem to be titled "Experiments"... After, of course, you type "flags" into the address bar to get there. I guess I can see a distinction there, but it's pretty subtle.
verdverm2 hours ago
CUE, originally starting as a fork of Go, has the experiments capability too and even extended it to per-file scoping. This makes trying out changes like `try { a: b?.c }` in isolation really nice
Go remains my favorite language for the tooling alone (while not forgetting about so many other great features)