Live data from Hacker News

Mozilla's abandoned web engine 'Servo' project is getting a reboot

news.itsfoss.com

51–60 of 140 posts

Re: Mozilla's abandoned web engine 'Servo' project is getting a reboot

#51
post #14
post #12

Earlier quoted context omitted.

> And I was particularly disappointed when Mozilla laid off the Servo team, I feel they let go of the most important thing they had. Gotta pay out those CEO bonuses somehow. In a sick plot twist Mozilla gets shocked back to its senses, re-hires the team, restarts the effort to replace Gecko with Servo, and Firefox finally lives up to its potential. (I wish.)

[flagged]

Because somehow 20 years old WebKit/KHTML bugs are better than 20 years old gecko bugs?

Re: Mozilla's abandoned web engine 'Servo' project is getting a reboot

#52
post #49
post #31

Earlier quoted context omitted.

Thunderbird is developed on top of Firefox.

Yep, but it seems to be a PITA. They endure whatever changes happen on Firefox UI, which are well tested on Firefox, but not on Thunderbird and Thunderbird has much more UI to manage than Firefox. See this interesting Thunderbird talk at FOSDEM on visual change that mentions this issue [1]. You also kinda have to fork Firefox to do this. It would be good to be able to #include and build the UI from there. XULRunner s…

[deleted]

Re: Mozilla's abandoned web engine 'Servo' project is getting a reboot

#53
post #22

They have a video of Servo running on a Raspberry 400 faster than Chromium. However there are no downloads or build instructions specifically for the Raspberry in the repository on GitHub or in the issues. Maybe it's just build for Linux. Googling servo and raspberry together gives a lot of hardware projects with motors, even when including mozilla in the query. Did anybody here made it run on a Pi?

I haven't messed with it yet but from looking into it, this should absolutely work. https://github.com/servo/servo/wiki/Building-on-ARM-desktop-...

I totally missed that page. Thanks!

Re: Mozilla's abandoned web engine 'Servo' project is getting a reboot

#54

Servo is a waste of time. If we want a fast rendering engine, Mozilla already has it. If we want a secure rendering engine we could leverage code checks. It's all there. The meme of Rust equals safety (or C equals I safety) has to go away.

Servo was about parallelism.

Mozilla tried multiple times to parallelize CSS style calculation in Gecko which is written in C++, and failed all of them. When they tried again in Servo with Rust, they succeeded first time.

They integrated Rust-written parallel CSS style calculation to Gecko. As a result, to this day, Firefox is the only web browser which can parallelize CSS style calculation, and beats every other browser in CSS style calculation performance.

The meme that Rust is easier to parallelize is true.

Re: Mozilla's abandoned web engine 'Servo' project is getting a reboot

#55
post #51
post #14

Earlier quoted context omitted.

[flagged]

Because somehow 20 years old WebKit/KHTML bugs are better than 20 years old gecko bugs?

People arguing this usually mean they want to deal with only one set of bugs, and since Chrome won't die, Firefox must die.

Re: Mozilla's abandoned web engine 'Servo' project is getting a reboot

#56
post #30

I would like to see Positron rebooted. Positron is to Firefox what electron is to chromium. https://mykzilla.org/2017/03/08/positron-discontinued/

Yeah, it's an awesome idea to waste few hundred megabytes of RAM to run your app. This browser-in-a-box cancer needs to die a painful death.

And you won't get Skype, Slack, Teams and many other applications people use on a daily basis on Linux, at all. Features on Mac will be limited compared to Windows version, because the team prioritizes work on the platform with the largest userbase. There will be more inconsistencies in feature and UI for "desktop" version vs web version, if companies still bother to maintain two versions.

That's the future you want to see, huh?

Have you developed a cross-platform desktop application in the last few years and make sure everything works on every platform? Probably not. If there is a way to make it easy, cheap, reliable to support multiple platforms and the solution takes little system resources, I'm sure everyone will want to do that. Before that happens, stop your wasting complaining about the Electorn mode of making apps. This will not change. It is the only thing that makes business sense and make developers' life easy at this time.

Or to put it simply, are you going to pay for the extra cost used for developing "native" applications for each platform? Put your money where your mouth is.

Re: Mozilla's abandoned web engine 'Servo' project is getting a reboot

#57
post #30

Earlier quoted context omitted.

Yeah, it's an awesome idea to waste few hundred megabytes of RAM to run your app. This browser-in-a-box cancer needs to die a painful death.

According to Chrome, this tab alone uses over 200mb.

Eight Megabytes and Constantly Swapping.

This too, shall pass. The minimum amount of memory for a double buffered fullscreen surface at 8bpc on a 4k monitor is 48MB. RAM is meant to be used, and if it was not for memory hogs, the DRAM industry would be a decade behind where it is today.

Re: Mozilla's abandoned web engine 'Servo' project is getting a reboot

#59
post #44
post #39

Earlier quoted context omitted.

Until there's a viable solution for desktop native GUI, this trend will continue.

Native UI has been there for decades before. Yes, cross-platform requires extra effort. Hell even Wine is more efficient an approach for cross-platform distribution.

> Yes, cross-platform requires extra effort.

Aaand you lost most companies.

> Hell even Wine is more efficient an approach for cross-platform distribution.

I'm sure that customers will be willing to install and run Wine.

Re: Mozilla's abandoned web engine 'Servo' project is getting a reboot

#60
post #30

I would like to see Positron rebooted. Positron is to Firefox what electron is to chromium. https://mykzilla.org/2017/03/08/positron-discontinued/

Yeah, it's an awesome idea to waste few hundred megabytes of RAM to run your app. This browser-in-a-box cancer needs to die a painful death.

I agree it's disappointing to think I've found a native app only to realize it's just an Electron app. But I don't need the idea to die, I just want better transparency in app stores so I can know ahead of time whether an application is native or just a wrapped webapp.

> This browser-in-a-box cancer needs to die a painful death.

That depends on what you think the result would be.

What do you think companies who use Electron, CEF, embedded web views, etc today would do if those technologies all died tomorrow? For example, do you think GitHub, WordPress, Figma, Discord, Whats App, Slack, Trello, Skype, or Spotify would hire native Windows desktop development teams? (Or even Mac/Linux desktop development teams?)

Personally I doubt that there would be any increase in native app development. Any developer who cares about this is already making native applications, Electron just makes web apps slightly more convenient.

Post reply on HN