Servo Night Builds Begin, Linux Packages Coming

[liam]

You mean "to blatantly steal all Chrome's extensions in one simple swoop" right?

Anyway that's a good move. Less NIH crap and more shared standards. We all need that.

Is that an accusation that people have been throwing around?
The browser landscape seems to be, SLOWLY, crystallizing around a few key ideas. Adhering to standards (de facto or otherwise) is a good idea (INTERNET EXPLORER!!!). Providing a common(ish) extension api. Making the browser a key platform target for development.
That last idea is still being heavily researched because there is some legacy crap that the web has foisted upon us that is making things difficult, but there are some ideas of there (personally, I'd love to see movement away from css to a constraints based layout scheme --- that alone would make web sites consistently predictable and more performant).
ANYWAY, this was a bit of a ramble, but servo has its role to play, if it is able.

[starshipeleven]

The goal isn't to lose the power of extensions, but to create a MINIMAL interface to the desired functionality.

You mean "to blatantly steal all Chrome's extensions in one simple swoop" right?

Anyway that's a good move. Less NIH crap and more shared standards. We all need that.

[liam]

Firefox team already said in the blog that they are designing their API to make sure the usual suspect addons (noscript, umatrix, and so on) can work with it, as a way to distinguish themselves from Chrome.

What's more, they have said that their extension API will be a strict superset of Chrome's (so, it will evolve, as necessary, to ensure chrome extensions work in Firefox).
The goal isn't to lose the power of extensions, but to create a MINIMAL interface to the desired functionality.

[starshipeleven]

i doubt it, Addons will be similar to Chrome's/Safari for Servo Browser. so a lot of them will be Limited in what they can do

Firefox team already said in the blog that they are designing their API to make sure the usual suspect addons (noscript, umatrix, and so on) can work with it, as a way to distinguish themselves from Chrome.

[kmare]

Nightly builds don't work in Fedora (openssl library is too new)

Yeah, it's a shame. But at least it looks like they're working on it in the form of a FlatPak for fedora users.

https://github.com/servo/servo/issues/12102

[Duve]

Sorry for the double post.

[Duve]

Interesting. I wonder if Firefox add-ons will work with it eventually.

As they are currently, with xul... no.
They will likely port web extensions from Firefox proper, part of the reason for the move to it was servo and narrowing security issues involved with kepting xul alive.

i doubt it, Addons will be similar to Chrome's/Safari for Servo Browser. so a lot of them will be Limited in what they can do

By the time that servo is in production use.... I am no so sure that will app

[Anvil]

Interesting. I wonder if Firefox add-ons will work with it eventually.

i doubt it, Addons will be similar to Chrome's/Safari for Servo Browser. so a lot of them will be Limited in what they can do

[Zan Lynx]

Modify runservo.sh and remove "-b" from the arguments, it should work then. It's just complaining about a lack of symbols, those aren't fatal errors.

Or you can do what I did, git clone the repository and do a ./mach build --release then cd target/release, then you can use the same runservo.sh script in the nightly build.

It does take a while to build, and about 5 GB of disk space.

[microcode]

Nightly builds don't work in Fedora (openssl library is too new)

Modify runservo.sh and remove "-b" from the arguments, it should work then. It's just complaining about a lack of symbols, those aren't fatal errors.