I really hope web assembly will be used more widely. I really dislike this slow web apps. If that you could be compiled down to something more static it would be much faster.
Announcement
Collapse
No announcement yet.
Servo Driving Modularity To Support Different JavaScript Engines
Collapse
X
-
Originally posted by patrick1946 View PostI really hope web assembly will be used more widely. I really dislike this slow web apps. If that you could be compiled down to something more static it would be much faster.
Comment
-
Originally posted by Mathias View PostI wonder if this could be used as a guide on how to port V8 to Firefox.
I'm not saying it should be done. But it is *interesting* how this small non-profit tries to compete with the biggest players, while all others gave up on their own development... I can totally see them switching to V8 or Blink or both for financial reasons...
- Likes 2
Comment
-
Originally posted by bug77 View PostThis is probably a stupid question, but why does a layout engine need to integrate with a JS engine in the first place? I know there's Ajax, but even that is just a collection of events.
Several tags also have Javascript APIs (like the video tag) so that's a thing, too. Lots of sites also depend on JS to load contents, handle layout, provide shims, handle scroll events, etc... Real-world testing would be impractical, since the vast majority of sites wouldn't work without JS. You'd be limited to only a handful of extremely simple (and outdated) sites to test against.Last edited by Kver; 15 April 2024, 12:46 PM.
- Likes 4
Comment
-
I think a restricted JavaScript / EcmaScript with less functionality and access, just with some basic functionality would be enough for most websites. That would help reduce the attack vectors, bloat at runtime and possibly other useful things. Or define official API Levels for JavaScript, where each level is more complex and has more features, bloat, privacy and security risks. In example with the most simple form of JavaScript API Level 1 would not allow the download anything or whatever else (I'm not a web developer).
- Likes 1
Comment
-
Originally posted by byteabit View PostIt's probably too late for Steam to replace the internal browser and UI engine of Steam from Chromium to Servo.
- Likes 3
Comment
-
Originally posted by Kver View PostNot a stupid question. Probably the best example is HTML5 components (custom elements), where custom tags are registered by Javascript. So if I wanted to make, say, a <my-cool-graph> tag, I'd need to register it with JS which builds a shadow-dom, which also affects the CSS rendering and even CSS pseudo-classes and state functions.
Originally posted by Kver View PostSeveral tags also have Javascript APIs (like the video tag) so that's a thing, too. Lots of sites also depend on JS to load contents, handle layout, provide shims, handle scroll events, etc... Real-world testing would be impractical, since the vast majority of sites wouldn't work without JS. You'd be limited to only a handful of extremely simple (and outdated) sites to test against.
Comment
-
Originally posted by byteabit View PostIt's probably too late for Steam to replace the internal browser and UI engine of Steam from Chromium to Servo.
- Likes 2
Comment
Comment