we've come full circle. they've invented rust to do servo with it.
Servo is now available on crates.io
81–90 of 155 posts
Re: Servo is now available on crates.io
#82Earlier quoted context omitted.
No, it's explicitly not. Semver says: > Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable. Cargo is explicitly breaking with Semver by considering 0.3.5 compatible with 0.3.6.
To go further, semver provides semantics and an ordering but it says nothing about version requirement syntax. The caret operator to describe a range of versions is not part of the spec. It was introduced by initial semver-aware package managers such as npm or gem. Cargo decided to default to the caret operator, but it's still the caret operator. In practice, there's no real issue with using the first non-zero compon…
Thank you.
Eventually this will get cleared up. I’m close than I’ve ever been to actually handling this, but it’s been 9 years already, so what’s another few months…
Re: Servo is now available on crates.io
#83Earlier quoted context omitted.
I disagree. Thorough testing provides some level of confidence that the code is correct, but there's immense value in having infrastructure which some people understand because they wrote it. No amount of process around your vibe slop can provide that.
I somewhat agree, but even then would argue that the proper level at which this understanding should reside is at the architecture and data flow invariants levels, rather than the code itself. And these can actually be enforced quite well as tests against human-authored diagrammatical specs.
I disagree. The code itself matters too.
Re: Servo is now available on crates.io
#84Earlier quoted context omitted.
We do not need vibe-coded critical infrastructure.
If you're trusting core contributors without AI I don't see why you wouldn't trust them with it. Hiring a few core devs to work on it should be a rounding error to Anthropic and a huge flex if they are actually able to deliver.
I trust people to understand the code they write. I don't trust them to understand code they didn't write.
Re: Servo is now available on crates.io
#85Is Servo production-ready enough to replace or embed alongside engines like WebKit or Blink?
It doesn't crash as often as it used to few years ago. JS heavy sites might not work, and layout issues too. And internet gatekeepers cloudflare turnstile doesn't work.
Re: Servo is now available on crates.io
#86Earlier quoted context omitted.
I disagree. Thorough testing provides some level of confidence that the code is correct, but there's immense value in having infrastructure which some people understand because they wrote it. No amount of process around your vibe slop can provide that.
I somewhat agree, but even then would argue that the proper level at which this understanding should reside is at the architecture and data flow invariants levels, rather than the code itself. And these can actually be enforced quite well as tests against human-authored diagrammatical specs.
If you don't fully understand the code how do you know it implements your architecture exactly and without doing it in a way that has implications you hadn't thought of?
As a trivial example I just found a piece of irrelevant crap in some code I generated a couple of weeks ago. It worked in the simple cases which is why I never spotted it but would have had some weird effects in more complicated ones. It was my prompting that didn't explain well enough perhaps but how was I to know I failed without reading the code?
Re: Servo is now available on crates.io
#87feels like we're actually getting new browser engines this decade and it's kind of strange
Re: Servo is now available on crates.io
#88Earlier quoted context omitted.
We do not need vibe-coded critical infrastructure.
If you're trusting core contributors without AI I don't see why you wouldn't trust them with it. Hiring a few core devs to work on it should be a rounding error to Anthropic and a huge flex if they are actually able to deliver.
It's extremely tempting to write stuff and not bother to understand it similar to the way most of us don't decompile our binaries and look at the assembler when we write C/C++.
So, should I trust an LLM as much as a C compiler?
Re: Servo is now available on crates.io
#89feels like we're actually getting new browser engines this decade and it's kind of strange
Servo has been on-the-go for a while though. It hasn't been a lightning speed development, it's just getting a bit more visible.
Re: Servo is now available on crates.io
#90Earlier quoted context omitted.
I dont think that will ever be possible. At some point security becomes - the program does the thing the human wanted it to do but didn't realize they didn't actually want. No amount of testing can fix logic bugs due to bad specification.
Well, yes, agreed - that is the essential domain complexity. But my argument is that we can work to minimize the time we spend on verifying the code-level accidental complexity.
Sure, but that is what we've been doing since the early 2000s (e.g. aslr, read only stacks, static analysis, etc).
And we've had some succeses, but i wouldn't expect any game changing breakthroughs any time soon.