SQLite already does this but hasn’t stopped the rust /go clones from popping up .
These are toy projects with no serious interest in maintaining the port long term. and even with things like bun where the port is merged it remains to be seen on maintainability over time.
> 4. Many formerly open source infrastructure components like Redis and Elastic Search have Apache equivalents, but they still command healthy margins.
Elastic just had round of layoffs[1]. Elastic still runs operating losses till Q1 2026 [2], albeit a small one, however just breaking even in operating income is hardly "healthy margins". A P/E of 17 is not exactly signaling confidence given they are growing ~20% y-o-y.
That too has precedence , there is long history of controls of cryptographic algorithms up until the 90s. It wasn't abstract either, older greybeards would remember browsers like Netscape had two versions International and U.S. for this reason.
If you classify AI as a weapon which seems to be the direction that we are all heading towards, they yes first amendment rights won't likely apply.
Wikpedia has more info, plus WNN and other industry publications usually are more up-to date.
Kori[1] has 7 operational units today and 1 commissioning and 1 under construction
Hansul[2] has 8 operational units and another 2 more under construction.
All 4 new units are APR-1400 reactors ~1400 MW capacity. Kori should retains its top position, Saeul-3 in Kori Phase II has already reached criticality in April.
Tianwan in China will come close but its 7/8 units are slightly behind in construction than Saeul-3/4 in South Korea, plus the plant is also bit smaller at 6600MW now . The Russian VVER-1200 design China are using is also slightly smaller than Korean APR-1400.
Kashiwazaki-Kariwa ? It has been not in full commercial service for close to two decades now. Only one unit recently restarted this year. 6 units are offline now
There are two South Korean plants (Kori, Hangul) larger than Bruce
There are git clients for perforce, hg, svn and so on[1]. Oak' developer (or the community) could always develop a git frontend for users who prefer that .
Hardly the fault of anyone is it for not reading a 100+page document meant for investors when it literally in the name .
If they don’t want us to think of them as a Space company they could have taken the xAI name (like how grammarly did with superhuman) or called it Musk Inc or whatever else.
> game is to turn knobs until you get a benchmark run that shows an improvement, then ship it
i.e reinforcement learning against a weak reward function - benchmark is insufficiently complex and is not representative of the real world sufficiently.
The "game", i.e. decision tree can be modeled as a multi-arm bandit problem, to deploy finite resources ( compute) toward exploitation/exploration .
The main issue is each training / fine-tune is very expensive so number of chances at the slot so to speak is pretty limited today.
It would be feasible to change something like that without breaking security now.
Google can hardly start allowing/routing a new account for [email protected] when you were getting it for years even though your account is [email protected] and sensitive communication like say from your bank would routed there.
The main llm will refuse to scan for issues flagged or not, and the cheap model not do a good enough scan on its own.
For models designed/marketed for cybersecurity defensive uses, any predictable refusal mechanism is a vulnerability. It is like being able to cause a kernel panic or segmentation fault .
Even if the gate is fail-reject, an attacker can overwhelm HITL reviews with many false positives and use DoS vectors here.
> by spending more time on the project and testing it yourself
> a human would generally spend a lot of time here,
This was always the hard part - game engines, asset libraries and all other services / SDKs were always making code-generation cheaper every generation.
Releasing a bug-free, thoughtfully built product requires a lot of attention and product skill.
Apple will deploy the same security/ privacy / ease of use /packaging strategy they have done for every other product.
Same reason developers continue to use Apple payments even when they have to shell out 30% of the revenue.
I can see Apple, setting App store rules around declaring AI usage, or could start labeling apps not using their models with strong language designed to amplify the increasing user concerns around AI and so on.
The product strategy has to be better the product itself does not have to be objectively better for the developer for them to have to choose it.
Backrooms was a quite successful web series on YT which in turn originated in 4chan boards.
Only the medium being sourced from is changing from successful Broadway shows, popular novels or comic books in the years past. The calculus remains the same - properties with name recognition even from other formats tend to be green-light.
Trust of a project long term always was and continues to be of concern when choosing a critical dependency .
The concern basically boils down to how large and serious is the team and what if they abandon the project in few weeks or months .
These were always the risks, many here have been burned by betting years of their career building against promising but what turned out to be weak projects
OP is alluding to the fact that today commit frequency, lines of code or how active the contributors in the issue trackers are no longer good signals to use as proxy.
When the underlying project to yours is few million lines of code written by machines only it is not going to be feasible fork and maintain or in-house it if the maintainers abandon it
To be clear users of a library or a tool aren’t owed anything when it available gratis and fully open source .
However not everyone has access to unlimited tokens to disregard the quality (in terms of history and usage ) or size of the underlying project completely
These are toy projects with no serious interest in maintaining the port long term. and even with things like bun where the port is merged it remains to be seen on maintainability over time.