4 ms·
> Some variables may have changed slightly without documentation updates, but we're sure you can figure it out I hope they're not hoping for mass adoption with
by bilekas 2y ago
> Some variables may have changed slightly without documentation updates, but we're sure you can figure it out
I hope they're not hoping for mass adoption with an attitude like that. Not exactly inspiring confidence in the longevity and maintainability.
- serf 2y agoit feels more like a way to sweep liability away rather than a real warning.. ..which also does not inspire confidence.
- glzone1 2y agoWhy does this not inspire confidence in Tesla. Their internal software stack is available to their own developers who can review what is actually there. Why does it have to be perfectly documented in a public github? Are all other car companies "properly" publically documenting things in github? Does it inspire more confidence in VW's software stack if they don't share it? Is VW's confidential stack some big competitive advantage? I've used a VW ID electric vehicle. I did not come away that impressed.
- Fidelix 2y agoBecause Tesla and Musk bad... or something of the sort. This is the way it goes here in HN for anything related to Musk.
- bilekas 2y ago> Because Tesla and Musk bad... or something of the sort. No, spec bad. Protocol unknown. Poof edit: > This is the way it goes here in HN for anything related to Musk. Nobody mentioned Musk ... Except you.
- Sysreq2 2y agoI don’t think mass adoption is their goal. They had a problem. They solved that problem. They shared how they solved said problem. Every engineering company releases stuff like this. It’s not meant to change the world. It’s marketing to recruit other engineers who would find that problem interesting.
- bilekas 2y ago> I don’t think mass adoption is their goal. I'm not so sure about that.. FRom the repo : > Tesla also announced joining the Ultra Ethernet Consortium (UEC) to share this protocol and work to standardize a new high-speed/low-latency fabric (be that TTPoE or otherwise) for AI/ML/Datacenters Also it's a protocol, personally I will only use a protocol that's fully spec'd. It's a pain sometimes to have consensus among all contributors but it's valuable. > edit : I will only use a protocol that's fully spec'd IN PROD
- renewiltord 2y agoNah, it's the base thing that a standard can be built out of. This is how things usually get done.
- bilekas 2y agoYup, for all the specs I've contributed towards, I should have just said : "but we're sure you can figure it out" That's how things usually get done right ?
- RajT88 2y agoAt least they're honest about it. This is currently the state of much modern documentation from huge tech companies.
- deleted 2y ago[deleted]