Re:Taming Go’s memory usage, or how we avoided rewriting our...
by pjmlp on Tuesday September 21, 2021 @05:02PM
(#28609906)
To be fair, that is now the common "I rewrote X in Y" theme, which followed upon the Y ∈ { Ruby, Clojure, Scala, Kotlin,.... } from previous years.
[ Parent
| on HN ]
Re:Taming Go’s memory usage, or how we avoided rewriting our...
by Zababa on Tuesday September 21, 2021 @05:39PM
(#28610336)
And Go too! It's always fun to see posts from around 2014/2015 complaining about how every submission to Hacker News is now "I wrote X in Go", while now Go is the boring stuff and Rust is the hot new thing. I wonder what will be the next Rust though.
Re:Taming Go’s memory usage, or how we avoided rewriting our...
by tptacek on Tuesday September 21, 2021 @05:42PM
(#28610378)
BPF-verified C.
Re:Taming Go’s memory usage, or how we avoided rewriting our...
by SAI_Peregrinus on Tuesday September 21, 2021 @10:27PM
(#28612518)
Naw, BPF-verified BF. Or someone will make "BrainFuck Plus" so we can get BPF-verified BFP.
Re:Taming Go’s memory usage, or how we avoided rewriting our...
by pjmlp on Tuesday September 21, 2021 @06:20PM
(#28610745)
Some GC based language with dependent types.
Re:Taming Go’s memory usage, or how we avoided rewriting our...
by square_usual on Tuesday September 21, 2021 @09:10PM
(#28612045)
Nim is on the way up in HN posts...
Re:Taming Go’s memory usage, or how we avoided rewriting our...
by Zababa on Wednesday September 22, 2021 @02:40PM
(#28620056)
Nim has dependent types?
Re:Taming Go’s memory usage, or how we avoided rewriting our...
by klyrs on Tuesday September 21, 2021 @10:25PM
(#28612504)
Write it in Malbolge?
Slightly less silly, modern C++ and modern Python are evergreen.
Re:Taming Go’s memory usage, or how we avoided rewriting our...
by Zababa on Wednesday September 22, 2021 @04:44PM
(#28621537)
They are, but they also are too big, so at some point people will want to replace them with something simpler/smaller. Go has been used for this for some projects in C++ and Python.