Live data from Hacker News

Servo’s new home

blog.servo.org

221–230 of 326 posts

Re: Servo’s new home

#221
post #175

Earlier quoted context omitted.

You missed Android. Firefox for mobile is so far behind Chrome, it’s unusable for me, most plugins don’t work. I would vote for HTML/CSS based browser (React / React Native?), though I know that a lot of operating system specific code needs to be written.

I find Firefox more usable than Chrome on Android. uBlock Origin works perfectly, and that's part of the reason.

I use kiwi which provide uBlock Origin for chromium

Re: Servo’s new home

#222
post #196

Earlier quoted context omitted.

You missed Android. Firefox for mobile is so far behind Chrome, it’s unusable for me, most plugins don’t work. I would vote for HTML/CSS based browser (React / React Native?), though I know that a lot of operating system specific code needs to be written.

Chrome on Android doesn't even have plugins and never will.

You can with e.g kiwi browser

Re: Servo’s new home

#223

We've been cagey about this over the months since the Servo team at Mozilla was disbanded, since there were various moving pieces that needed to fall into place. We're excited about the possibility for Servo to continue growing and evolving in its new home, though!

I looked for a list of projects currently embedding Servo, or planning to, but didn't find one. Is any software embedding it now?

Servo is not production ready yet. We don't even know how may years it will take for 1.0. So no software would use it for now.

Re: Servo’s new home

#224

While this is great news on one hand, on the other hand, how could Mozilla manage to lose its browser engine project ? If a web browser company can't even keep its browser engine project, what is really Mozilla working on these days ?

It's really a classic situation, the greenfield project is stopped and the historical "old" project keeps going on.

Re: Servo’s new home

#225
post #142
post #110

Earlier quoted context omitted.

Because they wanted to "put a crisper focus on new product development and go to market activities."[1] I'm sure that explains it well... [1] https://blog.mozilla.org/wp-content/uploads/2020/08/Message-...

I'm guessing that the "new products" are not the browser.

They just launched a VPN Service

Re: Servo’s new home

#226

Is WebGPU part of Servo? I know the guys at Mozilla were developing WebGPU API in Rust. Looking to see where it's going (I assume Firefox has to use it too. Chrome already has experimental support) Any idea?

We had a summer of code student implementing support in Servo: https://blog.servo.org/2020/08/30/gsoc-webgpu/

Excellent news. Thank you!!

Re: Servo’s new home

#227

Earlier quoted context omitted.

> Can people please stop this latent homophobia? Mozilla fired a person who donated money to a deplorable cause. You can try to hide behind free speech, but we all know what this is about. He quit. And I don’t agree with it, but I wouldn’t exactly call his cause deplorable. People with those views can believe they’re being completely ethical. That was also in 2008, a different political climate, and nobody allowed hi…

>He quit. And I don’t agree with it, but I wouldn’t exactly call his cause deplorable. The purpose of Proposition 8 was to remove the right to marry from gay couples - yes remove - because the courts had already granted them that right. If I was a gay Mozilla employee and I learned that my CEO wanted to remove rights which the legal system had already granted me, I would be so incredibly demoralized and pissed. Regar…

It was a really weird and messy situation, and unpleasant to live through.

I agree that Brendan's Prop 8 donation was bad. But he did it privately, and never (AFAIK) made anti-LGBT comments in public. People who had worked with him for many years were surprised to find he had these views. It was only found out because of political donation public disclosure laws.

Some Mozilla employees publicly criticized Brendan for the Prop 8 donation, but some defended him, because of the aforementioned privateness of it. A number of the defenses came from LGBT employees.

The pile-on at the time was intense. It lasted more than a week. It reached the front page of my local paper. Crazy stuff.

Brendan chose to stand down as CEO and also quit Mozilla. He wasn't fired, and Mozilla leadership asked him to stay.

All this nuance was lost. Lots of left-leaning people concluded that Mozilla had knowingly promoted a proudly anti-LGBT guy to CEO. Lots of right-leaning people concluded that Mozilla had fired their CEO for his political views. Both conclusions were greatly over-simplified. Almost everyone found a reason to hate Mozilla. Bad times!

Re: Servo’s new home

#228

I am confused. I thought it is the raison d'être of Mozilla to develop a browser. So how does it come that the brand new browser engine they developed is being given away? I mean, even if they need to cut costs, isn't Servo part of the team they should keep until the end?

That seems to be what everyone was wondering about when they laid off a large portion of their web teams

Re: Servo’s new home

#229

Earlier quoted context omitted.

Look at the corporate sponsors (that include Samsung and Huawei) - they may provide paid contributors.

I strongly believe that you could get funded by Google if you attempted to port stylo to chromium. Firefox still has state of the art css performance I believe, thanks to stylo.

The same Google that suffers from "Not Invented Here" syndrome? We're talking about a company that literally tried to supplant the defacto language of the web!! Highly doubt it.

Besides, nothing's stopping them from porting it without funding the project.

Re: Servo’s new home

#230

Earlier quoted context omitted.

Well, to be honest though, a lot of the criticism of Electron stems from the fact that it's more than just a rendering engine. There are a lot of applications where you'd want to take advantage of a browser view or a renderer or a JS engine, but not the rest of the stack. There are native apps where you might want a well-sandboxed JS engine for extension support, or where you're writing all of your core logic in C/Ru…

> or where you're writing all of your core logic in C/Rust but you want to use HTML/CSS for your interface DOM is highly intertwined with JavaScript, so that wouldn't be possible.

This is clearly not true, since the DOM interface is implemented in something like C++ (or Rust, in this case) in browser engines, so you could write your logic in the same language, or even write a binding for any language you like.
Post reply on HN