anth_anm

and no one gets to make money except Amazon.

It's open source meets the real world. We aren't all hippies who can sit around at MIT.

Amazon patented 1 click checkout.

meh, amazon sues over the patents and gets them tossed out then introduces a compatible API anyway.

You can't beat Amazon. You can't beat google. You can't beat Microsoft.

FOSS devs have the same bills as anyone else.

Hot take, the future of open source is just massive companies sponsoring projects to get free dev hours.

You can try to fight it, but if Amazon wants your project they will either take the code or build a compatible API. There is no defense, IP rights only favour proprietary software.

> Panasonic makes battery cells. Think AAA battery

or think "the individual cells that make up the tesla battery pack".

and other car companies have been securing that supply chain.

> No OTA systems

That's a strong selling point.

> Crappy entertainment systems

are android auto and carplay crappy?

I just want my music controls. I don't need to be entertained beyond that. Massive safety issue.

> Poor self-driving tech and almost zero data

Tesla doesn't have good self driving tech.

For acceleration.

That's 1 part of driving, it's just the part Tesla chosen to highlight because it's where electric cars have an advantage.

They are also heavier and tend to overheat if pushed.

Even in a 1/4 mile the Tesla is somewhere in the 10-11 second range. That's insanely fast, but it's not reaching the levels of purpose built drag racers or even some production cars.

The I-Pace competitor would be the model X.

It also starts at double the listed price of the Model 3.

I'd rather have an I-pace.

> to a goal that he views as essential to the survival of humanity

Can we have a take that doesn't start with "Elon is the messiah"?

Apparently NTFS is too integrated to replace it.

The second group doesn't exist, it's just people in the 3rd group lying (to themselves even).

Google learned from Microsoft's mistake.

You pay your bribes or the justice department comes knocking. Google made antitrust investigations just vanish into thin air.

Google is effectively has monopolies on search and online advertising.

They should be broken up.

Just skimmed it, but using a good parser combinator library sounds like a lot of what the author wants.

Their argument is based on a very privileged person who had every option and chose the one he liked best.

That's great. Good for him.

But my concern is that people get pushed towards trades for a variety of bad reasons. It's not that trades are bad, but a lot of them are pretty brutally hard work. You end up destroying your body. In exchange you get a working environment that seems continually more and more worker hostile.

Making recaptcha worthless by making it so intrusive no one will use it.

I love this idea. Recaptcha is god awful.

Makes more sense to have them in go stores, whole foods, etc...

I bought my parents an echo because they had them on sale at whole foods around christmas.

So microsoft should just ignore all the lessons that we've learned over and over about being data driven?

> compelled to prioritize shareholder value and profit has much higher impact on that than ethics

No, this is just an excuse.

Investors could sue. They could also sue because they think the ethical violations cost google money. They could sue for any other stupid reason.

Companies have a lot of leeway in maximizing shareholder value. Amazon has pursued growth over short term profits for decades.

It's the internal structure of the files.

Is this based on the same JS code editor as VS Code?

Thread finishes work

grabs lock

writes to file

writes to index

releases lock

That's not a race condition. The output order doesn't matter, but it is nondeterministic.

Right, that's not a bit for bit reproducible builds.

Think of it as absent a cache I should get bit for bit identical out (perhaps ignoring logs and such).

I can do a build off of year old code.

Would you rather you get a timestamp embedded that tells you it was built today, or take the hash and be able to find the exact revision.

Knowing when something was built is more useful than having better verification of exactly what code went in?

Besides, it's a deterministic build. You can use a lookup table with the hash to find out exactly what revision it is.

You fix the tools so that they work properly. You modify the compiler to always produce deterministic output (e.g. dummy timestamps).

what if you have a multi-threaded backend to the compiler that happens to lay down data in different orders?