3 ms·
Sciter doesn't even come close to a fraction of what Gecko or WebKit offers or does, and it still took the author many years to get to that point, so I'm not su
by aseipp 6y ago
Sciter doesn't even come close to a fraction of what Gecko or WebKit offers or does, and it still took the author many years to get to that point, so I'm not sure what you're trying to get at. The "JS-like engine" is an excellent example. It turns out, you need an actual JS engine to run real websites, not a "JS-like" engine. The difference between 80% and 100% of that problem is massive, and it also turns out running that fast is a ridiculously complex project on its own. (And, unsurprisingly, the recent Sciter FOSS Kickstarter announced that it would pivot to QuickJS instead. It might be educational to think about why they would do that.)
This doesn't even get into things like translations, technical writing (manuals, help pages, etc), infrastructure needed to actually deliver updates and downloads, collaboration on web standards, etc.
- badsectoracula 6y ago> Sciter doesn't even come close to a fraction of what Gecko or WebKit offers or does It is close enough to show that a web engine can be made by a single person even if it doesn't fully adhere to the standards and its functionality is certainly not less than 1/49th of what you'd need to go there. > The "JS-like engine" is an excellent example. It turns out, you need an actual JS engine to run real websites, not a "JS-like" engine. Fabrice Bellard has written (among many other things) a full modern JavaScript interpreter, again showing you do not need a "dozen" people (like another commented mentioned) to make such an interpreter.