Hope that you fix that before the EE reservation...cool F5-o-meter by the way!
"Let's push this minor string change directly to production", I said. "It'll be fine", I said.pic.twitter.com/oUEXIIUSuk
-
-
-
Site was down for about a minute. I'm fast on the revert button.
End of conversation
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This has nothing to do with type checking. It's a broken format string in i18n resources. This would've exploded in any language.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I'm not a fan of Go. It's not truly memory-safe, cannot be sanely embedded, severe NIH, not truly RT, and is getting bloatier. Try Rust :)
-
(Basically I used Go once, found a nasty bug in the runtime, debugged it, fixed it, but after seeing the innards I lost most interest)
End of conversation
New conversation -
-
-
Go's big advantage is goroutines, but they come at a massive design cost for everything else (e.g. GC, stack splitting, terrible C interop).
-
So Go makes it easy to write good-performance, simple, sharing-light network servers and clients... but that's about it IMO.
- Show replies
New conversation -
-
-
I was hoping to take advantage of Go's easy networking and defer to C stuff for self-contained number crunching, but... impedance mismatch.
-
(well, I say C stuff, but the libraries I used also had optimized assembly, of course, further widening the gap vs. pure Go alternatives)
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.