upvote

points

by simonw2 days ago |
comments
upvoteby mrbonner1 days ago|
next
[-]
Cool! I checked the source and noticed that even LLM prefers simplified, high level Rust coding styles: use value types such as String, use smart pointers such as reference counting, clone liberally, etc… instead of fighting the borrow checker gatekeepers.

It is the style I prefer to use Rust for. Coming from Python, Typescript and even Java, even with this high level Rust, it yields incredible improvement already.

reply
upvoteby andrepd1 days ago|
parent|
[-]
> Cool! I checked the source and noticed that even LLM prefers simplified, high level Rust coding styles: use value types such as String, use smart pointers such as reference counting, clone liberally, etc… instead of fighting the borrow checker gatekeepers.

Yeah that tracks because the AI is dumb as a bag of bricks. It can apply patterns off stackoverflow, but can hardly understand the borrow checker.

reply
upvoteby echelon2 days ago|
prev|
next
[-]
This is super useful! I have immediate use for this.

Do you know if Servo is 100% Rust with no external system dependencies? (ie, can get away with rustls only?)

Can this do Javascript? (Edit: Rendering SPAs / Javascript-only UX would be useful.)

Edit 2: Can it do WebGL? Same rationale for ThreeJS-style apps and 3D renders. (This in particular is right up my use case's alley.)

reply
upvoteby simonw2 days ago|
parent|
next
[-]
It depends on stuff like SpiderMonkey so not pure Rust.

It should be able to render JavaScript but I've seen it throw bugs on simple pages, no doubt because my vibe-coded thing is crap not because Servo itself can't handle them.

reply
upvoteby minimaxir2 days ago|
parent|
prev|
next
[-]
I have been building/vibecoding a similar tool and unfortunately came to the conclusion that in practice, there are just too many features dependent on the full Chrome stack that it's just more pragmatic to use a real Chromium installation despite the file size. Performance/image generation speed is still fine, though.

In Rust, the chromiumoxide crate is a performant way to interface with it for screenshots: https://crates.io/crates/chromiumoxide

reply
upvoteby ospider1 days ago|
parent|
next
[-]
> there are just too many features dependent on the full Chrome stack

Do you mind elaborating on what features are missing?

reply
upvoteby mnutt1 days ago|
parent|
prev|
[-]
I think you could in theory have a similar webkit-based stripped down headless crate that might have a good tradeoff of features, performance, and size.
reply
upvoteby lastontheboat1 days ago|
parent|
prev|
[-]
Servo does execute JS and does support webgl (and some but not all of webgl2 if you enable the feature: https://book.servo.org/design-documentation/experimental-fea...).
reply
upvoteby ghusbands1 days ago|
prev|
next
[-]
I wonder why most of the "g" characters are cropped.
reply
upvoteby stefs1 days ago|
parent|
next
[-]
good catch
reply
upvoteby scrame2 days ago|
prev|
[-]
That's pretty cool. I'm guessing it would need some tweaking to handle things like cookies, or does it just need a pointer to the cookiejar? I'm not too familiar with servo,
reply
upvoteby simonw1 days ago|
parent|
[-]
It's a VERY simple initial demo, I expect things like cookies would require quite a lot more work.
reply