jakevn

One time when returning from an overseas country, I was in one of two lines: One for foreigners, and one for US citizens. It was quite the line.

After a few minutes, I was pulled aside and whisked through customs. As I was nearing the exit, a staff member said "welcome home".

It hadn't hit me until later that I was likely skipped ahead due to having a military surplus duffel bag.

No particular point here aside from how silly the whole thing is.

I wouldn't even agree that it's not an issue. It's something the README doesn't cover.

I suppose Toyota / Lexus is black magic, then?

Basic knowledge of cats, most likely. A high number of outdoor cats I've known would hunt animals and bring the complete flailing bodies or corpses indoors. It's just an understood part of cats, kind of like how humans will do things even though it isn't necessary for survival.

This reflects my experience with Go to a tee. (Well, minus being a prolific library contributor, thanks for that!)

Prior to using Go professionally, I scoffed at the language and wrote it off as an extreme form of Blub paradox. Having worked in languages with generics, as well as languages with advanced type systems (Haskell, Rust, Scala), it seemed like a huge step back.

Initially, I did have a problem with the lack of generics, because I leaned on the feature regularly when writing software. Four years of professional use later and I can say that I am very much glad for the lack of generics. It is almost always straightforward and easy to read and understand Go code that someone else has written. The same cannot be said for the other languages I've mentioned.

For the problem domain we are using it in (devops), it has been a godsend. The company makes use of many different languages from various paradigms, yet anyone can pick up Go quickly if they want/need to contribute to or deeply understand our tooling.

Personally, my issue with Electron is that, in practice, it is hugely inefficient. The up-side to Electron, IMO, is that it doesn't try to straddle the uncanny valley of native GUIs. In GTK, usually everything _looks_ like a normal GUI, but behaves/looks just a little (or, often times, a lot) bit different than what is expected.

Blockchain does not provide any verification of trust, nor can it. It provides verification of number crunching transactions alone, as well as an immutable store of that number crunching. It's actually notoriously poor for trust compared to traditional systems, as there is no way to mediate in the case of fraud once a transaction has occurred.

None of which you have listed can be proven by blockchain as it has proofs for today. All would rely on external sources of truth which entirely live outside the verification of the blockchain. The blockchain in these cases would be an immutable chain of unverified facts.

Processed is not a bad word when it comes to health. What matters are the ingredients. I'm not aware of any consensus on canola being anything but healthy, but am interested in learning more as canola oil is what I use for cooking.

That being said, like any meat or meat-substitute, I wouldn't consider it a "health food".

Do you honestly believe that someone that is living on the streets, shitting in the open, is thinking about the spread of disease or homelessness PR?

I got the number from the website you linked.

However, using Google Maps, I found 4. I'm not sure how many bathrooms you'd normally allocate per person, but I imagine the number of homeless and those out and about would necessitate more than that. How many bathrooms per person are in the typical office building? Should the number of these loos not similarly match the homeless population?

Also, how is a timer in a bathroom at all dignified? If I need 15 minutes to relieve myself, will the Portland Loo kick me out?