Readit News logoReadit News
VoxPelli commented on Ladybird adopts Rust, with help from AI   ladybird.org/posts/adopti... · Posted by u/adius
jvillasante · 21 days ago
> We’ve been searching for a memory-safe programming language to replace C++ in Ladybird for a while now.

The article fails to explain why. What problems (besides the obvious) have been found in which "memory-safe languages" can help. Do these problems actually explain the need of adding complexity to a project like this by adding another language?

I guess AI will be involved which, at this early point in the project would make ladybird a lot less interested (at least to me).

VoxPelli · 20 days ago
Rust was pretty much created to help solve security issues in browsers: https://en.wikipedia.org/wiki/Rust_(programming_language)#20...
VoxPelli commented on Ladybird adopts Rust, with help from AI   ladybird.org/posts/adopti... · Posted by u/adius
jonkoops · 21 days ago
This is also the case for Servo, so it makes sense to collaborate.
VoxPelli · 20 days ago
Servo has a distinct design goal that sets it apart from its predecessor within Mozilla and has already had offsprings that has made its way directly into Firefox.

Its purpose is not to reinvent everything. It’s not a hype project.

VoxPelli commented on Ladybird adopts Rust, with help from AI   ladybird.org/posts/adopti... · Posted by u/adius
nicoburns · 21 days ago
Very happy to see this. Ladybird's engineering generally seems excellent, but the decision to use Swift always seemed pretty "out there". Rust makes a whole lot more sense.
VoxPelli · 20 days ago
Servo makes a whole lot more sense: https://servo.org/
VoxPelli commented on Ladybird adopts Rust, with help from AI   ladybird.org/posts/adopti... · Posted by u/adius
norman784 · 21 days ago
Javascript is a self contained sub system, if the public API stays the same, then they can rewrite as much as they want, also I suppose this engine now will attract new contributors that will want to contribute to Ladybird just because they enjoy working with Rust.

Don't forget that the Rust ecosystem around browsers is growing, Firefox already uses it for their CSS engine[0], AFAIK Chrome JPEG XL implementation is written in Rust.

So I don't see how this could be seen as a negative move, I don't think sharing libraries in C++ is as easy as in Rust.

[0] https://github.com/servo/stylo

VoxPelli · 20 days ago
Not only is Firefox using it for their CSS engine but Mozilla created Rust to build Servo and sadly only the CSS engine and maybe some other parts is what they kept around when they offloaded Rust.

“the Rust ecosystem around browsers is growing” – in the beginning pretty much 100% of the ecosystem around Rust was browser oriented

Thankfully Servo is picking up speed again and is a great project to help support with some donations etc: https://servo.org/

VoxPelli commented on Ladybird adopts Rust, with help from AI   ladybird.org/posts/adopti... · Posted by u/adius
nicoburns · 21 days ago
It doesn't have to all-or-nothing. Firefox has been a mixed C++ and Rust codebase for years now. It isn't like the code is written twice. The C++ components are written in C++, and the Rust components are written in Rust.

I suspect that'll also be what happens here. And if the use of Rust is successful, then over time more components may switch over to Rust. But each component will only ever be in one language at a time.

VoxPelli · 20 days ago
Firefox was special in that Mozilla created Rust to build Servo and then backported parts of Servo to Firefox and ultimately stopped building Servo.

Thankfully Servo has picked up speed again and if one wants a Rust based browser engine what better choice than the one the language was built to enable?

https://servo.org/

VoxPelli commented on Bunny Database   bunny.net/blog/meet-bunny... · Posted by u/dabinat
VoxPelli · a month ago
Main positive with bunny.net:

Its European rather than from USA so its less dependent on that orange guy in that white/golden house

VoxPelli commented on Anthropic: Developing a Claude Code competitor using Claude Code is banned   twitter.com/SIGKITTEN/sta... · Posted by u/behnamoh
VoxPelli · 2 months ago
Sounds like standard terms from lawyers – not very friendly to customers, very friendly to company – but is it particularly bad here?

I remember when I was part of procuring an analytics tool for a previous employer and they had a similar clause that would essentially have banned us from building any in-house analytics while we were bound by that contract.

We didn't sign.

VoxPelli commented on GOG is getting acquired by its original co-founder   gog.com/blog/gog-is-getti... · Posted by u/haunter
eterm · 3 months ago
I had the opposite takeaway.

Companies with strong financial performance don't tend to use words like "encouraging". That is the language you get from companies that are in trouble and hoping for recovery.

Talking about people's enthusiasm for their mission is just straight up dodging the question itself.

VoxPelli · 3 months ago
This goes for publicly traded companies much more than privately owned ones.

GOG is now becoming private like Valve rather than publicly traded.

VoxPelli commented on GotaTun – Mullvad's WireGuard Implementation in Rust   mullvad.net/en/blog/annou... · Posted by u/km
embedding-shape · 3 months ago
I think the general consensus is that it improves security of the protocol, but obviously that won't matter much if the implementation gets something wrong or has worse security by itself.

Issues in the protocol itself would need all implementations to change, but issues in the implementation would obviously be isolated to one implementation. For something like Wireguard, I'd wager a guess that issues in the implementations are more common than issues in the protocol, at least at this stage.

VoxPelli · 3 months ago
If the implementation gets it wrong that can also be a sign of ambiguity in the protocol / standard and as such result in clarifications and an overall more well specified protocol
VoxPelli commented on GotaTun – Mullvad's WireGuard Implementation in Rust   mullvad.net/en/blog/annou... · Posted by u/km
saidnooneever · 3 months ago
dont fix if it ain't broken. look at sudo-rs and other rust ports.

ofc, thats a cynical view.

i personally think its a bad idea to duplicate efforts. better combine them. otherwise u risk making mistakes that were already solved. missing lessons already learnt.

VoxPelli · 3 months ago
sudo-rs itself is not a bad idea, Canonical’s premature shipping of it in Ubuntu was the bad idea. sudo-rs was transparent with how far it had gotten in compatibility and feature parity

u/VoxPelli

KarmaCake day761November 24, 2009
About
[ my public key: https://keybase.io/voxpelli; my proof: https://keybase.io/voxpelli/sigs/RUQr8ARfVmQun2quBbB3NY9DmUEcTqWfA0NQZYhR1zc ]
View Original