rubnogueira
Joined 1 year ago
Joined 1 year ago
Those devices are forced to use an ancient Safari version of WebKit which includes tons of vulnerabilities that are not patched anymore, and same time doesn't support modern ECMAScript functionalities.
With a modern browser engine, those old devices can be used for valid browser usage.
This is usually a good example of a test case that the upstream project is not covering and can be contributed back.
Parity should be bidirectional, so definitely it is possible for both parties to benefit from it.
I had some issues regarding that.
That is what made Bun popular, and tools like uv/pip, oxlint/eslint, orbstack/docker desktop, and the list goes on. Drop-in replacements where we get 10x with little effort.
https://aube.en.dev/package-manager/jailed-builds.html
But this feels like a cat/mouse game.
Most of the reviews are not required if this is enforced.
I wanted to check memory usage and limitations of building such react app without depending on Electron or Tauri.