reindeerer

They are so entrenched on gerrit, it's so uniquely terrible. Should have bought Gitlab when there was the moment

Yes, but the schema def is still in protobuf

The first issue is that protobufs arent a standard. That inherently limits anything built on top of them to not be a standard either, and that limits their applicability

Also depending on the environment you run in, can code size bloat vs alternatives can matter

Give me something that isn't based on protobufs at wire / request level. CBOR with CDDL for a fully standards based approach that can work at any size of the stack

That's the whole point, source tars when properly versioned don't change. And you can get unchanged versions from any mirror in the world. sha256 of linux-2.6.10 release is 404e33da7c1bf271e0791cd771d065e19a2b1401ef8ebb481a60ce8ddc73e131, it wont change

That norm still exists, and it's offered by Github in form of Github Releases feature as well.

It's the downstream tooling ( i.e. all the builds and package managers ) that need to clean their act up.

This is a false choice. "Vendoring" is much more of a mess than this is, and second, there's no reason to rely on these on the fly tarballs for anything, when proper versioned software releases exist.

Github has pretty much a one-click ( or one API call ) workflow to create properly versioned and archived tarballs. Just because lots of people try to skirt proper version management doesn't mean you should commit the world into your repo

github had subversion support ??? :)

CHAdeMO / GB/T were harmonized into a new connector ( CHAdeMO 3.0 aka ChaoJi )

> What legal guarantee is there that Tesla won't reverse course in the future?

None. There would have to be a governing body set up for this to have any legs

Are you trying to imply that just calling something is a standard doesn't make it a standard ? Hmmmm

Yep but incentives haven't shifted, and the organizational inertia to fight in their fiefdoms is super strong

You could actually go to space several times for this cash

I've lost count how many misguided bids of taking x86 to low-power they made. Also the apparent unshakeable confidence that ARM will never become viable on server and desktop.

ABI with a clear major version number would solve this. It's what C++11 should have done with CoW strings.

You just ship 2 version compiled targets of std libs

Those rendering frameworks are being written as well, for no other reason than promo

Somehow those promos have to get done right ? Couple of OKRs, a few perf cycles, launch, and move on. Also great perf stories for people who took care of sunsets

Are they trying to put trained monkeys out of the job there ?

Here's a battle that Google lost

Nah, this is bunk. The cost of code sharing on top of something like Ionic is next to nothing. And for every platform specific feature you can just plumb in whatever plugins you want.

It's very much a focus and resource allocation problem. Double the number of engineers working on the keyboard and it doesn't happen

Rust has also embraced the very small packages mentality more and more, and it's already showing, things turn far more brittle quickly

Also, your average npm module packages incredibly small amounts of functionality, making dependency trees huge and hence also very brittle.

> how potentially complex it can be

Welp, time to go back to BASIC everyone. Or Go

Powerful tools can be complex, who would have thought

That's a very confused take on how things work. Celery functions run async, and Django frontend view responses are normally lighting fast

Moxie Marlinspike came up with the concept of trust agility some time ago. I think it's imperative that the agility of the trust network is guaranteed, because this can be a fast changing situation.

Two things: they normally have a mass market / volume counterpart that is not rad-hard.

Second, they actually are full of bugs, and take a ton of money to qualify. Qualification, among other things, means thoroughly documenting the bugs.

AM335x PRUs are exactly the reason why its under ITAR. Hard-realtime running alongside general-purpose OS