Recommended Posts

I think mozilla is slowly becoming a closed source browser.

 

Please show me the parts of Firefox that don't have source code released for them. Otherwise, why on Earth do you keep making this ridiculous assertion?

  • Like 2

Apart from freezing the APIs indefinitely, there's not much they can do to improve add-on compatibility (And to be clear, we're talking about compatibility with abandoned add-ons)

And that type of backwards compatibility code incurs a cost, a lot of issues with add-ons and E10S involve add-ons using the old backwards compatibility APIs rather than the newer (Still like 3 years old though) APIs that work across processes, if those old APIs were aggressively deprecated then updates add-ons would work better, at the cost of breaking abandoned ones, etc.

  • 2 weeks later...

Almost 45MB last update :s

 

 

Did that to me too, looks like the partial update failed.

 

Full update installed fine though.

 

Yesterday they jumped Firefox Nightly to 38 bandwagon, so you might have missed yesterday respin for version pickup. So that's why with today's Nightly you get full update.

Mozilla's Servo Engine that's written in the Rust programming language and designed to be a highly parallel layout engine continues to be advancing very well and could see an alpha release this year.

Jack Moffitt of Mozilla talked at last week's Linux.Conf.Au 2015 conference about the work he and a dozen or so other Mozilla engineers have been doing on the experimental Servo engine.

As explained during a status update from November, Servo's performance has been very fast compared to Gecko and other web layout engines. As mentioned in that update and reaffirmed last week, Servo developers are indeed hoping to have an alpha quality release of the engine out in 2015.

Besides being fast and written to offer greater standards compliance, Servo should be more secure with being written in Rust. Servo has also been designed to be embeddable from the start. The first bits of Servo support in Firefox OS are now working in experimental form -- at least for booting to the ACID2 test. Jack said during his presentation that he hopes to have about 50% of standard web features implemented this year while the most popular web pages are all rendering well.

The performance of Servo has been described as "amazingly well" compared to Gecko and that even a single thread ofServo is faster than Gecko. However, the results for now should be taken for a grain of salt given that more functionality still needs to be implemented. CNN and Reddit were frequently mentioned as popular sites rendering well with Servo. The goal with Servo is to deliver better responsiveness and lower power use than Gecko (and alternatives).

With Servo coming along, the developers hope to eventually begin landing Servo and Rust support within Gecko to allow more developers to begin familiarizing themselves with the new engine. The first component likely to find its way implemented in Gecko/Firefox from Servo is probably the BMP decoder, given that it's a small piece of the puzzle and shouldn't cause too much fallout in the case of problems. Other Servo/Rust components likely to get green lit early on is also a new HTML parser and URL parsing library.


Those wishing to watch Jack Moffitt's LCA2015 presentation can find it embedded
 

Servo is very interesting, it's parallelism done right (Compared to the current multi-process implementation that IE/Safari/Chrome/Firefox do/want to do), it'll probably still end up running in multiple processes though because JavaScript has some crappy semantics (Which is the main reason why we do multi-process stuff currently)

 

I'm surprised they're going to replace something as simple as the BMP decoder with a Rust variant, but it does make sense considering the only thing it's really used for these days if site icons (And even then they're being replaced with PNGs over time). A new HTML parser would be interesting too, currently it's implemented as a machine translation of a Java parser and I think they're still actually keeping the old parser around just for the special "about:blank" page.

In 2015, we have two high-level goals for Servo:

 

Release an alpha-quality browser that uses Servo as its rendering engine

Land a Servo component that is authored in Rust into Gecko

Q1 2015

   

Extensive CSS property coverage (> 70%)
Android browser and APK
OSX and Linux platform daily builds of "miniservo"
Get the browser "safe enough" to use for basic browsing scenarios
Identify and begin building a Rust component inside of Firefox
Begin reporting and tracking Servo's Web Platform conformance, performance, and power usage over time
Initial fragmentation (multicol)
Initial flexbox
Upgrade SpiderMonkey
Zero-copy HTML & CSS parsing

Q2 2015

   

Create dynamic test suite
Add high impact platform features
Add a Rust component to Gecko

Critical 2015 work

Layout

   

variables
transforms
transitions
animations
tables: the rest of colspan,rowspan,percantage heights & web-compat bugs will-change

Other

   

Explore using Servo as a UI toolkit
Visualization support
multiprocess
multimedia
sandboxing
addons
prefs
bookmarks
history
cookies

ffs, what have they done to the search bar!?!?

I want the address bar to always use my default search engine, and the search bar to stay on whatever I have set it to for the time being.

Would be nice if the Right Click menu gave the option to search with the default and also the currently selected.

Wish I knew how to write addons :(

ffs, what have they done to the search bar!?!?

I want the address bar to always use my default search engine, and the search bar to stay on whatever I have set it to for the time being.

Would be nice if the Right Click menu gave the option to search with the default and also the currently selected.

Wish I knew how to write addons :(

No need for an addon, you can revert to the old search by going to about:config and setting browser.search.showOneOffButtons to false

  • Like 2

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Posts

    • AMD is supported out of the box in linux because of their open source driver. Nvidia does not. All my systems are amd and all of them work nicely on linux arch without doing anything.
    • Never had a problem with TPM and started using that many years ago in Win10. Through several motherboards and OS versions, it just does what it does without complaint. My games library doesn't even know it's there. Secure boot does a lot more than support anti-cheat, as it came along long before anti-cheat software. I've used it religiously since before I started using TPM, and I always liked it for being able to nullify virus contagions that try their best to come in underneath the firmware during boot, so that the OS doesn't see them, etc. That is its purpose, imo. I'll never understand why people who elect to use another OS feel compelled to run down Windows... I guess they need to do that to feel secure about their choices? I run Windows because it supports all the software (including games) natively that I want to buy, and I've never had to run down another OS to make me feel better about it. (Although it's certainly possible to do that, of course...) Win10 is on a ventilator atm, and Win11 is very close to being free, and I finally got to stop running StartAllBack as I moved to the Experimental/Dev channel and my 26300.8553 build supports the moveable taskbar and it's running fine at the top of the screen! Finally, my last major dislike of Win11 is being rectified! So, I'm not at all surprised to see Win11's share of the Steam survey hitting 70%.
    • I can answer about the Linux bit. I only used AMD GPUs. I currently have a 9060XT (8GB) that fits my needs, I'm not a gamer, so I don't need that much GDDR. But lately, NVIDIA has grown a lot in the recent years. Oh, the horrors of NVIDIA drivers not working. But they have been getting better. I know a lot of members onm here that are running cachyOS and other distros, and are fine with a 4090/5090 variants. Really, though, I would stick with AMD variants.
    • Everything they say you can already do yourself on the registry by changing some things.
    • Artist's renderings are so much nicer to view than the real thing, don't you think?
  • Recent Achievements

    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
    • Dedicated
      Mark Spruce earned a badge
      Dedicated
    • Collaborator
      conkir earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      479
    2. 2
      PsYcHoKiLLa
      252
    3. 3
      Steven P.
      71
    4. 4
      +Edouard
      69
    5. 5
      FloatingFatMan
      68
  • Tell a friend

    Love Neowin? Tell a friend!