srer

11 ms·

31.
by srer 4y ago
I presume as a method of manually constructing backtrace, as the same error may occur in multiple places it's helpful to understand the context. I too would label it a preference. To get out of the error handling tedium in our platform
32.
by srer 5y ago
It's not from a founder, but I like this paragraph from the preface of The Go Programming Language : Go has enough of a type system to avoid most of the careless mistakes that plague programmers in dynamic languages, but it has a sim
33.
by srer 5y ago
I would say yes. And I would go a step further, I owe my career to the Free Software and Open Source movements. It's not that I couldn't have made my way in a world of proprietary software, but that world of money, license restric
34.
by srer 5y ago
It certainly does for me. It ties into this quote: > Why not use the syntax F<T> like C++ and Java? A great number of us are used to seeing <> rather than [] for generics. It would seem limitations in Go's parser outrank
35.
by srer 5y ago
Spent about a decade on-call...It is an interesting and perhaps even worthwhile experience to do it for a little bit. IMHO there are two angles to achieve higher reliability: 1. Build systems which go down less on their own (which is quite
36.
by srer 5y ago
I work as a programmer. I'm not very good. But then hardly anyone is. There are certainly exceptions, but I think as a whole we're still working everything out. And that's why it's so fast moving, we can easily find bett
37.
by srer 5y ago
We largely had similar experiences, but formed different conclusions. Like you, with Go I was up and running rather quickly. I didn't have to think very hard. It was easy because I didn't have to pick up new concepts, only new syn
38.
by srer 5y ago
One supposes horrifically slow might be a bit subjective. I notice in a VM on my laptop establishing the initial connection to postgres seems to take 2-3ms, and running a trivial query takes 300-1000us. I routinely involve the database in u
39.
by srer 5y ago
There's a statement that Rust is a systems programming language, but that in most cases one doesn't need this, and that Go or Kotlin are thus in most cases better alternatives. This image of Rust as lower level than Go isn't
40.
by srer 5y ago
> ...edit your gnupg config file to exclude all the crypto from the 90s... Personally, I would suggest leaving Rijndael (AES winner) in ;).
41.
by srer 5y ago
I use pass, and have no desire to move away from gpg. I think gpg still provides "pretty good" privacy, I don't see any benefit that age would afford me with pass. (There are sore points to the OpenPGP user experience, integr
42.
by srer 5y ago
I had wonderful teachers, I've spent countless hours with K&R, Friedman, Abelson & Sussman and many others. Of course it was a distinctly one way street of communication, but fortunately my questions could almost always be answ
43.
by srer 5y ago
In no way comparable in sophistication, but I did find making an n-body simulation to be unexpectedly profound. My universe started as a uniform random distribution of small stationary objects, the only rules that existed were gravity (F=gm
44.
by srer 5y ago
A large concern in civil design loads is rain, wind and earthquakes. These are all probabilistic in nature, you do not generally seek to build something to be flood proof. You instead design it to survive perhaps a 1 in 100 year flood, or p
45.
by srer 5y ago
I can't speak for your computing experience, but for mine: There are significant differences in performance, admittedly SSDs temper these differences but there are plenty of systems with large HDDs. This isn't an abstract performa
46.
by srer 6y ago
We could build such libraries, and people have built some. However the task at it's heart is a vast duplication of work, and while Go has a lot of things going for it, it doesn't seem enough to sway many data scientists into reinv
47.
by srer 6y ago
Years ago (linux-kernel 2.6 days) I found Red Hat was somewhat at odds with FSF values. Red Hat does abide by the letter by the GPL by releasing source as legally required, but in a form that's inconvenient to work with: https:/&
48.
by srer 6y ago
Wonderful news! I recall https://guix.gnu.org/blog/2019/joint-statement-on-the-gnu-pr... happening at the same time as the FSF incident, which fortunately didn't pan out. It felt to me that we were attempting