bywaterstreet

4 ms·

1.
by bywaterstreet 6y ago
Good write-up. I write a lot of Go on my Mac at home. The first run is _always_ slow, but I've never measured it or bothered to find out why. This is a real "lightbulb moment" for me. I just built a Go executable and timed it
2.
by bywaterstreet 6y ago
I used to do a commute of around 1.5 hours each way, every day, for years. This was justified by my (at the time) reasonable salary, and all the self-reflection and podcast listening I could do. This was foolish in hindsight (speaking perso
3.
by bywaterstreet 6y ago
That's pretty cool. How much is that? "Costa Coffee" (a UK chain) machines are in lots of petrol stations nowadays, but I'm not aware of any kind of subscription.
4.
by bywaterstreet 6y ago
Great work, Simon, and a very interesting talk too. Off to read the linked Wolfram article: https://writings.stephenwolfram.com/2019/02/seeking-the-prod...
5.
by bywaterstreet 6y ago
> It turns out that in the current version of the macOS, the OS sends to Apple a hash (unique identifier) of each and every program you run, when you run it. Hang on, this only happens on first run of the binary, right? It caches the has
6.
What’s so great about Go?(stackoverflow.blog)
5 points by bywaterstreet 6y ago|1 comments
7.
by bywaterstreet 6y ago
Go has nothing on Python in this regard. I write Go every day, and come from a Python background. I often describe Go as the strongly-typed, more performant version of Python. I say this mostly because my Go code isn't too dissimilar f
8.
by bywaterstreet 6y ago
Thanks for the ref. I'll bring this up the next time somebody questions my "let's clean up these flags in prod".