Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Servo is now available on crates.io

servo.org

Post reply on HN
Print view View original

131–140 of 155 posts

Re: Servo is now available on crates.io

#131

Post by steveklabnik »

mort96 wrote: post #129
steveklabnik wrote: post #103

Earlier quoted context omitted.

There is additional subtlety here. For example, sometimes projects that have a 0.y version get depended on a lot, and so moving to 1.0.0 can be super painful. This is the case with the libc crate in Rust, which the 0.1.0 -> 0.2.0 transition was super painful for the ecosystem. Even though it should be a 1.0.0 crate, it is not, because the pain of causing an ecosystem split isn't considered to be worth the version num…

Oh hey I recently saw a comment which discussed this exact issue: https://news.ycombinator.com/item?id=47752915

99% of the time this situation is okay, because Cargo allows you to have both 0.1 and 0.2 in the same project as dependencies. It's just packages that call out to external dependencies, like libc, where it enforces the single version rule.

Re: Servo is now available on crates.io

#132

Post by mort96 »

rl3 wrote: post #130
mort96 wrote: post #54

Earlier quoted context omitted.

We do not need vibe-coded critical infrastructure.

>> ...give him unlimited model access > We do not need vibe-coded critical infrastructure. I think when you have virtually unlimited compute, it affords the ability to really lock down test writing and code review to a degree that isn't possible with normal vibe code setups and budgets. That said for truly critical things, I could see a final human review step for a given piece of generated code, followed by a hard l…

The availability or lack thereof of compute has absolutely nothing to do with my opinion. More vibe coded tests doesn't fix the problem.

Re: Servo is now available on crates.io

#133

Post by rl3 »

mort96 wrote: post #132
rl3 wrote: post #130

Earlier quoted context omitted.

>> ...give him unlimited model access > We do not need vibe-coded critical infrastructure. I think when you have virtually unlimited compute, it affords the ability to really lock down test writing and code review to a degree that isn't possible with normal vibe code setups and budgets. That said for truly critical things, I could see a final human review step for a given piece of generated code, followed by a hard l…

The availability or lack thereof of compute has absolutely nothing to do with my opinion. More vibe coded tests doesn't fix the problem.

It might when an individual function has 50 different models reviewing it, potentially multiple times each.

Perhaps part of a complex review chain for said function that's a few hundred LLM invocations total.

So long as there's a human reviewing it at the end and it gets locked, I'd argue it ultimately doesn't matter how the code was initially created.

There's a lot of reasons it would matter before it gets to that point, just more to do with system design concerns. Of course, you could also argue safety is an ongoing process that partially derives from system design and you wouldn't be wrong.

It occurred to me there's some recent prior art here:

https://news.ycombinator.com/item?id=47721953

It's probably fair to say the Linux kernel is critical infra, or at least a component piece in a lot of it.

Re: Servo is now available on crates.io

#134

Post by mort96 »

rl3 wrote: post #133
mort96 wrote: post #132

Earlier quoted context omitted.

The availability or lack thereof of compute has absolutely nothing to do with my opinion. More vibe coded tests doesn't fix the problem.

It might when an individual function has 50 different models reviewing it, potentially multiple times each. Perhaps part of a complex review chain for said function that's a few hundred LLM invocations total. So long as there's a human reviewing it at the end and it gets locked, I'd argue it ultimately doesn't matter how the code was initially created. There's a lot of reasons it would matter before it gets to that p…

I do not care how strong your vibes are and how many claudes you have producing slop and reviewing each others' slop. I do not think vibe coding is appropriate for critical infrastructure. I don't understand why you think telling me you'd have more slop would make me appreciate it more.

Re: Servo is now available on crates.io

#135

Post by mort96 »

steveklabnik wrote: post #131
mort96 wrote: post #129

Earlier quoted context omitted.

Oh hey I recently saw a comment which discussed this exact issue: https://news.ycombinator.com/item?id=47752915

99% of the time this situation is okay, because Cargo allows you to have both 0.1 and 0.2 in the same project as dependencies. It's just packages that call out to external dependencies, like libc, where it enforces the single version rule.

You can have both 0.1 and 0.2 in the same project, but you really don't want to.

Re: Servo is now available on crates.io

#136

Post by rl3 »

mort96 wrote: post #134
rl3 wrote: post #133

Earlier quoted context omitted.

It might when an individual function has 50 different models reviewing it, potentially multiple times each. Perhaps part of a complex review chain for said function that's a few hundred LLM invocations total. So long as there's a human reviewing it at the end and it gets locked, I'd argue it ultimately doesn't matter how the code was initially created. There's a lot of reasons it would matter before it gets to that p…

I do not care how strong your vibes are and how many claudes you have producing slop and reviewing each others' slop. I do not think vibe coding is appropriate for critical infrastructure. I don't understand why you think telling me you'd have more slop would make me appreciate it more.

Fair enough. I respect the commitment to purity.

In the not so distant future you'll probably be one of the few who haven't had their actual coding skills atrophy, and that's a good thing.

Re: Servo is now available on crates.io

#137

Post by mort96 »

rl3 wrote: post #136
mort96 wrote: post #134

Earlier quoted context omitted.

I do not care how strong your vibes are and how many claudes you have producing slop and reviewing each others' slop. I do not think vibe coding is appropriate for critical infrastructure. I don't understand why you think telling me you'd have more slop would make me appreciate it more.

Fair enough. I respect the commitment to purity. In the not so distant future you'll probably be one of the few who haven't had their actual coding skills atrophy, and that's a good thing.

A terrifying thought but not implausible. IMO, the world needs more people with a deep understanding of how stuff works, but that's not the direction we're moving in.

Re: Servo is now available on crates.io

#138

Post by steveklabnik »

mort96 wrote: post #135
steveklabnik wrote: post #131

Earlier quoted context omitted.

99% of the time this situation is okay, because Cargo allows you to have both 0.1 and 0.2 in the same project as dependencies. It's just packages that call out to external dependencies, like libc, where it enforces the single version rule.

You can have both 0.1 and 0.2 in the same project, but you really don't want to.

Most of the time, it works so well people don't even notice.

The only time you run into a problem is if you try and use values with a type from 0.1 with a function that takes a 0.2 as an argument, or whatever. Then you get a type error.

Re: Servo is now available on crates.io

#139

Post by mkl »

andriy_koval wrote: post #99
mayama wrote: post #85

Earlier quoted context omitted.

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.

why did it crash? Rust is supposed to be memory safe?..

The JS engine is SpiderMonkey, which is C++.

Re: Servo is now available on crates.io

#140

Post by sebsebmc »

phaistra wrote: post #5

Is there a table of implemented RFCs? Something similar to http://caniuse.com where we can see what HTML/JS/CSS standards and features are implemented? If it exists, I can't seem to find it. Closest thing seems to be "experimental features" page but its not quite detailed enough.

There's a lot of work between the WPT team and web-features/web-features-mapping that should allow this to work automatically based on WPT results.
Post reply on HN