Hacker News new | past | comments | ask | show | jobs | submit login

I suspect they've just deprioritized it for other work.

But I think that was the wrong strategic move - they should have opened it up, together with some 'Tesla AI' demo models, in a colab environment. They can hire new employees to do that - it is separate work from that involved in making the self driving car, and will not block or interfere.

The only reason I think they might not is that they don't want to step on Googles toes - there are very close links between Musk companies and Google, and a direct competitor to Googles TPU product might hurt that relationship more than it generates in revenue.




What makes you think they deprioritized “it”?


>and a direct competitor to Googles TPU product might hurt that relationship more than it generates in revenue.

There is approximately zero chance that this is a consideration.

My guess would be that, like a lot of things under the Elon Musk umbrella, what they claim they are able to do in theory diverges far from reality. We've seen similar slideshows.


> They can hire new employees

The bottleneck isn't employees, it's chips.


If that were the case, they'd have already launched a 'demo' version with very low usage limits. Users can start building/porting their models, and then run them in a few months when the next batch of chips arrives.


Sometimes R&D just takes time.


The idea of having it publicly accessible has been public for 3 years. Maybe internally for more than that.

Yet, building a basic colab-like interface, using opensource tools, shouldn't take more than a few people a few months.

Obviously, they might not want to launch that before their hardware is ready, but their hardware has been in production for over a year now.

Clearly something hasn't gone to plan.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: