jakevn

This beef industry organization cites 3 studies: https://www.beefresearch.org/resources/beef-sustainability/f...

U.S. specific estimates put beef water use at 317, 441 and 808 gallons per pound of boneless beef when precipitation water is not accounted for in calculations.

So, let's just say around 400 gallons of water per pound of beef if you don't include rainfall use.

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".

I got the numbers from here: https://portlandloo.com/loo-locator/

I'd argue enough restrooms are provided when the number is population appropriate and within a one block distance.

I also didn't say that restrooms aren't provided, but it seemed like it wasn't obvious to everyone why inconvenience or lack of dignity leads to non-use.

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?

The former is preferable because you are providing a disservice to the community that will not allow you dignity, even though they can most obviously afford it.

If you're not going to give someone a dignified place to relieve themselves, why would they care about using such a thing?

Why would _one_ of these solve any problems?

If this has solved the issue of automatically proving that any C or C++ program has no buffer overflows, why do we still see CVEs for popular libraries and software that result from them?

I don't believe Alexa and others are malevolently spying, but if the data exists, you should expect nothing less than it to be public at some point, or at least be accessed by someone you'd not expect to share your life with.

You _should_ absolutely be allowed to buy a non-street legal vehicle to operate on private land. You _should_ be able to buy a recording device that has no privacy features. You should _not_ be able to sell a recording device that by default is streaming all audio all the time for common consumers without a big label saying "everything this device is within hearing distance of is now public data and you agree you are in violation of the law, where applicable, for using it".

We are no longer in the days where consumers can be expected to know what their devices are even capable of, let alone what rights are being trampled.

No, it's not. We can use facial recognition, we can use voice signatures. It doesn't even have to be recorded, as the device setup can record those signatures of consenting users and refuse to transmit or save any data that does not match those signatures.

Tell me, which of these do Alexa and the like perform?

Would it be more difficult? Yes! This is the reality for any company where rights and laws actually matter. If you can't abide, you can't release. Very simple.

Why is live-listening impractical at scale? How can Discord provide such a service? You seem to be conflating Amazon's intent with the unknowable intent of anyone that can touch such data, which is a common fatal flaw in reasoning.

Certainly, as long as the device does not trivialize the violation of those rights. If a car designed for road use by a human driver did not have a windshield to see out of, I'd say it is designed in a way to violate the rights of others.

Are Alexa and others designed to reasonably ensure only consenting users are being recorded?

What is a recording? Does a 10 millisecond delay mean it is a recording? What is the legally binding lock-out time for this audio stream before a human can listen to it?

Your dream type system is out there, yet not manifest in any popular or somewhat-popular language.

I've yet to see a strictly/strongly typed language that makes this easy to do. Through some combination of plugins, esoteric languages, macros, or boilerplate, sure.

We're decades behind what is possible due to the practical.

Then you should not use a general numeric when you really should be using Pixel and Age types.

CL UX is great, as both a buyer and seller.

It _could_ introduce more barriers to reduce scammers, but that would come at a cost to both buyer and seller UX.

There is value in simplicity, and the market thus far agrees.

Craigslist is the anti-thesis to the hubris-fueled notion that technology can and should solve every problem, including dishonesty. I've not yet been scammed on Craigslist because I've built up a valuable skill in identifying scammers in general rather than relying on an imperfect system implemented differently on all marketplaces. In return, I do not get scammed as a _seller_, which is something most marketplaces seem to neglect.

More broadly, we often blame human nature on software implementations, as if there was a software solution to (all of) such without trade-offs.

OpenStack has millions of lines of Python, I believe.

There are non-internet facing workloads that would benefit from the additional performance.

But with optimistic concurrency, why is this a gamble? It's an overhead that comes as a result of the trade-offs, sure, but it's a finite cost. Collision can be handled without breaking anything at the cost of implementation complexity.

I don't see how it is at all a gamble if you understand the trade-offs.

If there is no fatal flaw with the inaccurate/non-deterministic sorting that wall-clock prefix provides and one is utilizing optimistic concurrency (strict create on PK, abort/retry on conflict), I don't see how it is unsafe

Except for the fact that it is exactly the method that has been used to discover a large number of critical bugs in the most popular OSS projects (including SQLite): http://lcamtuf.coredump.cx/afl/