It costs next to nothing to bring on a new customer since there's no widget to make and ship.
Growing marketshare is *the* priority. Give it away for free. Pay people to use it if you must.
Then once they're hooked, start charging licensing fees. Just a little. More for bigger customers. Maybe keep a free tier for personal use. A little times a huge userbase is enormous cashflow for a little bit of nre.
It's great cuz the customer supplies his own platform, pays for training his own people, and even pays for the electricity to run your product on premises.
Now about this building full of expensive and power-hungry silicon needed to deliver the ai hotness...
Their grid collapse a few winters ago would (probably) not have happened if they were connected to the big grid like everyone else is.
Citation needed. Nobody actually thinks that but it seems you're making it up to make your anti-Texas hopes seem more realistic.
There isn't that much interconnection because Texas (mostly ERCOT) runs its own grid to avoid federal regulation (FERC oversight) since lines don't cross state borders much. This dates to the 1930s. It gives more local control, faster renewable buildout (Texas leads in wind, big in solar), and a competitive market.
What I'm seeing here is a very good possibility that this will end up being a year round problem for Texas.
What I'm seeing is someone who is always lefty-style-hateful and probably also jealous of Texas's success while hoping they'll have problems they probably won't have (recent changes improved weatherization and other grid countermeasures) in order to feel morally smug or vindicated while simultaneously offering no real evidence for a flaw-filled thesis.
It is not cross-API compatible because it is an API.
While that's technically true, what I'm asserting is that it's being used by other API's (various game and GL libraries) across platforms in a way that actually works.
you seem to be forgetting there are a lot of API specific functions functions
There are only a handful of ways to implement something like Vulkan across so many different display strategies. Frankly, I think they've adopted the most sane and straightforward solution: do first class support for all of them as best you can and abstract those behind your API. If Khronos were selling Wayland or X11, they'd be stuck in the same divide as all the 'next gen' solutions that are busy failing or building a walled garden.
Because he's a communist. He never saw a business or asset he didn't want to pocket "for the people."
If I ran any kind of business, I'd have my money in various kinds of places that balanced risk, return, and liquidity against my perceived need for keeping the lights on, paying vendors, and and anticipated revenue. Same as everyone.
I wouldn't operate like I had a fountain of money nor do I believe I would be perceived as having one.
Hospitals don't have a fountain of money. They purchase malpractice insurance on behalf of their providers and the premiums for that insurance pay for these jury awards.
Insurance companies don't print their own money either. They redistribute the costs of these payouts over their risk pool. And those premium hikes is one of several reasons why your emergency room visit costs 10k if you had to pay for it out of pocket.
The other reason it costs 10k is that enough of these lawsuits and jury awards have forced hospitals into doing medically unnecessary (but expensive) tests for everyone, rather than coming up with some kind of cost-conscious criteria, to cover their bases and their asses so they don't get sued.
Say it with me now: tort reform. The lawyers don't like it, which is how you can tell it's a good idea.
But why is the traffic so bad and why does stuff cost so much?
Yes, and in general it's just a lot easier when the whole world, including your would-be adversaries, use technical standards, software, and electronics that your own private sector sells to them.
A corollary is that it's less easy when your would-be adversary makes moves to undercut your industry and/or try to assert their own dominance in any such domain. One might even read it as a strategic prelude to conflict.
Your program is sick! Shoot it and put it out of its memory.