Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?
Note: You can take 10% off all Slashdot Deals with coupon code "slashdot10off." ×

Comment Re:Fixed it for you. (Score 2) 438

I'm mid-40s, my wife's a little older, our two kids are in their teens. No apparent loss of interest in sex from either of us. There was a period of reduced interest, but we got through it.

Two differences from your story: 1) my wife doesn't work right now (hopefully soon). 2) We're Christians, and regular sex is a commitment (1 Corinthians 7).

Comment Re:Mozilla, please stop destroying yourself! (Score 1) 187

C++14 is good in many ways. We have adopted many modern C++ features in Firefox, like closures. (STL features are unfortunately limited due to the crappy STL situation on Android.) However, it just doesn't provide any of the safety guarantees of Rust. You *can* write safe code in C++, but it's always very easy to accidentally write unsafe code that corrupts memory.

The Rust compiler is slow, but that's being worked on. The actual generated code is good. Servo benchmarks show it crushing Webkit, Blink and Gecko (even on single-core) --- mostly due to better algorithms, but it wouldn't win if Rust was a performance problem.

"2100 open Github issues" is a meaningless statistic. Compared to what? Zero issues would just mean it's a dead project.

Comment Re:Mozilla, please stop destroying yourself! (Score 2, Insightful) 187

"The Rust debacle"? Rust is doing great!

There's a lot of "post hoc ergo propter hoc" reasoning going on here. Your claims about how Mozilla's actions influence market share are completely unsubstantiated, and you completely ignore the effects of Google's actions (e.g. massive Chrome marketing spend).

Comment Re:Great, I just switched BACK (Score 2) 152

Amazon recently started doing something pathological where they restyle and relayout their search results page every 100ms. The particular restyling and relayout scenarios happened to be very well optimized in Chrome, but not Firefox, so less noticeable in Chrome (though still waking up and doing unnecessary work every 100ms). The optimizations are mostly implemented in Firefox nightly, and will be completely implemented very soon, but obviously it takes a little while for them all to reach the release channel :-(. (And would take even longer if we didn't have that rapid update cycle that other people complain about in the comments in this article!)

Comment Re:Never mind run Chrome extensions... (Score 2) 152

PPAPI is dying.

PPAPI has two main use-cases: supporting Flash and other browser plugins, and being the API for (P)NaCl applications --- C/C++ applications compiled to run on the Web, which have no more privileges than Web content.

"Browser plugins", i.e. native code that you can download and install in the browser, that runs content from the Web and has access to the same OS APIs at the same privilege level as the browser itself, are going away and not coming back. Flash is the last significant hold-out, but it's on a path to extinction.

WebAssembly, not (P)NaCl, is the future of compiling C/C++ to run on the Web, and WebAssembly uses the standard Web APIs, not Pepper.

Comment Re:Commendable (Score 2) 152

You are confused.

The problem of extensions breaking due to Firefox updates requires the solution of having a stable supported API for extensions to use. That is exactly what this announcement is about!

Mitchell Baker was never the CEO.

XUL was never great and almost everything good in XUL has been incorporated into Web standards supported across browsers (e.g. CSS flexbox).

Comment Re:So what's the point of Firefox anymore? (Score 3, Informative) 152

The Pocket issues had no effect on Firefox users not actually using Pocket, i.e. you (I assume). Furthermore the Pocket integration code in Firefox is open source.

The Adobe DRM module is closed source but integrated in the best way possible given the DRM requirements. You can delete the module without breaking anything except DRM. If you don't, the module is very tightly sandboxed so it can do nothing but decode video and audio. It is thus much more privacy and security friendly than, say, Flash. (You have already removed Flash, right?) I'm glad you don't want to watch Netflix, but it turns out a lot of people do, and "can't watch Netflix!" is not a great feature.

The new Firefox extensions model will support extensions like Tree Style Tabs and better ad blocking than Chrome's API provides. We're not limiting ourselves to Chrome's API.

Comment Re:Never mind run Chrome extensions... (Score 3, Informative) 152

The old addons model isn't going away until the new model is as capable as the old model supports NoScript, the better-than-Chrome AdBlock, Tree Style Tabs, etc at least as well as the old model currently does. Although the new model is largely based on Chrome's extension API, we're not limited to that API; we're adding the features those extensions need even though Google didn't want to add them to Chrome.

UNIX is hot. It's more than hot. It's steaming. It's quicksilver lightning with a laserbeam kicker. -- Michael Jay Tucker