go-nil-why

6 ms·

1.
by go-nil-why 2y ago
The intention of the password entry dots isn’t to prevent folks with unrestricted physical access to the machine from exfiltrating information, it’s to stop it from appearing in screenshares and casual “over the shoulder” observations. Hone
2.
by go-nil-why 2y ago
> i don't see many new, small trucks Right, because the EPA has made them illegal in favor of larger, less fuel efficient trucks. This paper covers the topic well^, you can also see many examples searching online for “EPA Small Truc
3.
by go-nil-why 2y ago
No, and even if it were to happen car manufacturers can’t make 4+ year plans based on policies the next bonehead in chief might just revert. We need a mass popular movement to dismantle the EPA as they stand and rebuild them with an actual
4.
by go-nil-why 2y ago
Issue is that isn’t generated by protoc. Looking at the go ecosystem you’d think static nil traceability is some sort of Very Hard Problem…
5.
by go-nil-why 2y ago
We’ll need to fire all the industry plants in the EPA before we can legally have a small (fuel efficient) truck here in US. Our emissions laws were written by Big Truck.
6.
by go-nil-why 2y ago
Clearly, we don’t work at the same company. What I claimed applied to my company, exactly as I said. If it doesn’t apply to yours… ok? Congrats? Looking back, maybe you didn’t understand the shell variable syntax?
7.
by go-nil-why 2y ago
No… I’m sorry I don’t have time to explain TS now. But that’s not what’s happening at all. What you’re proposing would be the equivalent of ‘var foo = new Foo()’. The default value in TS is undefined, which behaves generally isomorphically
8.
by go-nil-why 2y ago
There is no practical difference between function useFoo(f: Foo) { f.Use() } var foo: Foo useFoo(foo) and func useFoo(f *Foo) { f.Use() } var foo *Foo useFoo(foo) in this context. References vs pointers ar
9.
by go-nil-why 2y ago
The issue isn’t the services that stay up forever, it’s the ones subject to a huge amount of churn where maintainers lose context on what is or isn’t possibly nil, and get loose with their checks. Edit, responded to pointer vs reference dow
10.
by go-nil-why 2y ago
The fact that Go is considered a “modern” language and nil pointer exceptions are downright common blows my mind every day. Is there a static checker config that folks use to reduce this risk? Because coming from a TS background it’s legiti