Ridiculous because it's absolutely guaranteed to fail. Irresponsible because if it does succeed against all odds, the internet will actually become a worse place.
If you can't implement most of the web standards (not even all, just most of them), then one of the following will happen:
- your engine will never catch on (best case scenario)
- your engine will be forever known as "this browser where nothing works" and will be perpetually ignored in all discussions about cross-browser compatibility, nullifying any positives that could come from its existence
- worst possible outcome: your engine gains market share, gets treated seriously, and the global development of all new web standards stagnates until you can catch up, which means over a decade of zero innovations.
And you CANNOT implement most web standards[1]. There's too many of them, they all interact with each other too much, the engineering effort required is comparable with rewriting all of Linux from scratch.
And of course there's security. A massive project like that will have massive code complexity, which leads to enormous number of security holes. Chrome and Firefox are mostly secure because their maintainers spent literal decades fixing the holes. They have 20 year headstart over you in making it secure, and they don't have to play catch up with web standards like you do. Everybody using your engine is therefore at a much greater risk of getting hacked than if they sticked with Chrome. And that's assuming you use Rust. If you don't use Rust, then security would be so bad it's not even funny.
None of it matters if you're just making a personal project for the heck of it, of course. Go do it! Have fun! It doesn't matter if you use Rust or not because nobody will use it anyway, so pick whatever tech stack you like the most. Node sounds like a fun choice - it solves the problem of running JS scripts basically for free!
[1] https://waspdev.com/articles/2025-04-07/will-there-be-a-new-...