Check against Can I Use, all of the APIs, except for the following are supported by major browsers:
- Synchronous Clipboard API only Safari has full support, the rest have partial
- Temporal only currently supported in Chrome and Firefox
Powerful AIs might escape containment by releasing themselves as open-weight models
(www.seangoedecke.com)
Weaponizing And Defending The React Flight Protocol: Deserialization Sinks In RSCs
(www.smashingmagazine.com)
The fact that people even bring javascript as the backend is a bit crazy to me.
To clarify do you mean replacing JavaScript just on the backend? This article is about using JavaScript on the front end.
I'm intrigued, what would you replace it with?
What are your thoughts on this 2023 comparison?
So to confirm, you don't trust blogs where the company is selling a product or service, even if they don't mention it in the article? If so, that would cover a lot of articles shared on this instance.
For what? I don't see any products or services being promoted in this article.
People who care about performance are using loops
Well that depends, generators are faster than loops when you're using Bun or Node.
The conclusion aligns with my own belief, which is that it's better to create a minimal context by hand than get agents to create it:
We find that all context files consistently increase the number of steps required to complete tasks. LLM-generated context files have a marginal negative effect on task success rates, while developer-written ones provide a marginal performance gain.
When I have got Claude to create a context, it's been overly verbose, and that also costs tokens.
However in this case the opposite is true, as Chromium currently doesn't support this feature.
Do you mean features only currently available in Chrome?
Well spotted, the article states:
The :heading pseudo-class is currently available in nightly builds only. You can test it now in:
- Firefox Nightly (behind a flag)
- Safari Technology Preview
There are some really good tips on delivery and best practice, in summary:
Speed comes from making the safe thing easy, not from being brave about doing dangerous things.
Fast teams have:
- Feature flags so they can turn things off instantly
- Monitoring that actually tells them when something’s wrong
- Rollback procedures they’ve practiced
- Small changes that are easy to understand when they break
Slow teams are stuck because every deploy feels risky. And it is risky, because they don’t have the safety nets.