@xanf_ua Корень всех проблем в том что низкоуровневый control flow отдан на откуп LLM, а должен быть строго детерминирован для каждого конкретного класса задач, которые не труют креативности. Так и про код ревью на каждом шаге не забудем и тесты вначале написать на воспроизводимые баги.
@evanyou It's quite complex but can be done using this branch: https://t.co/3OTiAcdNxQ
After 'yarn vite-prod' you'll see tons of tiny chunks that are not combined into bigger shared chunks.
@jaffathecake So .finished resolves exactly 1 frame before the styles return back to initial state or do we get a 1 frame jump before the styles are committed?
@RyanCarniato@EOlonov You might've encountered the uncontrolled behaviour. Vue doesn't fully control the input, even with v-model. You have to use $forceUpdate() in some cases.
https://t.co/SM2PrEFt7v
@TheAlexLichter@gitlab@rolldown_rs I am still verifying the 100x claim, it might be that the other processes are not tracked like sass compilation. Will experiment more, including disabling CSS assets completely.
@evanyou Vanilla JS most definitely can scale with the project. But only if you have well designed architecture, excellent documentation, knowledge sharing across the whole team, automated protection rules, etc. And at this point you're just building your own framework.
@LeaVerou A modern revision of the document.write for streaming. That can accept readable streams (with backpressure handling) and also start at any element without the need for creating a new document.
@NickADobos@diabrowser Obvious next step: 'fix the website for me' action. When the form won't send, when the buttons won't click, etc. Would be even more useful for mobile browsers that lock you out of inspector.
@evanyou @devigner96 @mjackson This is rarely mentioned but every big project eventually stumbles upon a Chrome bug that randomly breaks network requests when serving thousands of files in parallel. Can only be solved by bundling for now.
https://t.co/sQmawa1Pml
https://t.co/S3mX6bVeoo