Things I like and somewhat advocate for:
- Linux, Emacs, Nyxt browser
- Rust, Scheme, Common Lisp
- HTMX, Coalton
- FP, Metaprogramming, PLT
- Split keyboards
- Tinkering and having fun with computers
- Not using AI to think/post for you
you?
@hajimehoshi It's issue number 12854. The issue has not been closed, but it has the proposal accepted tag since April 15 this year. As of now they plan to release it for version 1.28
@hajimehoshi It's true that it's already supported for certain declarations. I think it's a good thing for slices of structs to prevent "stuttering". There is a newer proposal that will allow the following code to compile, which I think harms readability.
@hajimehoshi A good answer to this probably deserves more preparation on my end. Shooting from the hip, however, I am really apprehensive about the type elision for composite literals that was recently approved.
@ThePrimeagen's latest video about Go exactly mirrors my feelings about the direction in which it is evolving. Additionally, @valyala's post about Go evolving in the wrong direction was featured in the video.
Recommended for watching https://t.co/dLvYY9gnAn
and @valyala's post https://t.co/mQbq3dTI80
I feel the same way. Yet, whenever I see somebody voice caution or skepticism about some unnecessary proposal, they are met with an avalanche of angry emojis. Those concerned about the current direction of Go need to get louder. Otherwise the language will continue to be influenced by those who don't even like or know what Go originally stood for.
@ForrestPKnight If you find something, let it be known. I need to replace the keyboard of a family member, which currently sounds like a clacky waterfall.