Except...I'm a Chrome user. Have been for maybe nine years. On a whim I gave Firefox 57 a shot and it feels great, so I'm using it.

Really, what is the chip on your shoulder?

What is this, FUD?

I installed Firefox 57, headed over to /., and the render speed was jarring. I gave Firefox Sync a round of testing and found it wildly superior to Chrome's sync strategy (FSync actually keeps track of changes, whereas Chrome merely does a set union on your current running instance and the remote server - meaning that any sort of deletion action requires interesting gymnastics). The dark bar took a moment to get use to, but in the end feels great (too many websites shoot for the pure-white-elegance look and having the browser do that as well just hurts the eyes by the end of the day).

Servo failed? Servo is a testbed for Firefox, and ported chunks of it are what makes Firefox 57 so fast.

Rust failed? People are having serious discussions on how a kernel written in Rust would play out.

Firefox has no say? I mean...in what regard? UI? User tracking? Sure. In other fields, such as cryptography policies, Mozilla plays the flute.

Come on, now. Don't be so dramatic.

I like the look of the Autofill API. Using Lastpass on Android always felt a little slow, iffy, and like they hacked together a solution that "technically" works but is not officially sanctioned (nothing against the engineers, it's just that you do the best you can with what you got). I can imagine the current code being some sort of pre-amble to detect the type of activity that is on the top of the stack and dispatching to the appropriate hack du jour.

Being proud of your lack of sleep is like being proud of the monthly balance that you've been carrying on your high interest credit card for the past decade. You're not more successful due to your lack of sleep - you're successful despite it.

Sleep more and see how the speed and quality of your work improves, thus making more time for the very sleep that enabled such work (not to mention the overall quality of life improvements).

...1/10th of a second is freaking huge! There are plenty of gamers out there that would bitch and moan endlessly at that latency.

I thought that was a good idea, but one thing that goes wrong is that you need an, at least, semi-charged battery to pull this off. I reckon the common use cases for something like this actually see a lot of value in being able to burn a dead phone without having to find a battery for it first. Makes me wonder if an analog solution would be preferred.

Oh, no, wait, I they did try Requests and it mostly passed EXCEPT for revocation. I simply checked the github repo that was posted and only saw the urllib/ssl test.

For Python they used urllib and ssl which, yeah, are in the standard library, but Requests is kind of the de facto HTTP library. Requests does do SSL cert verification, although it doesn't mention revocation specifically.

This is just wrong. A human is a vibrant, strong, and brilliant creature. To that end the pursuit of health is a humanistic endeavor. We were meant to live days that are both many in count and excellent in nature. You're proposing that living fewer days in relative sickness and malaise is preferable to a long and energetic life, so long as certain indulgences are more frequently met.

Life on the Dew and Doritos is so much shorter, and worse, than life on the avocado and deadlift.

Slashdot tries to read the pulse of the community in order to fulfill the "Stuff that Matters" mantra. Classically, these "off-topic" topics have been religious, civil, political, etc.. In the past several years there has been a huge uptick of interest in dietary matters within Slashdot. Hence...eggs.

The God damned Batman! ...

Just vigilantism.

Well, probably closer to the weight reduction seen when you have a parasite. Exercise is a fair bit more nuanced than just being an energy sink.

Well, this scheme would effectively make it impossible for any party to complete the key. As each organization embarks on the quest to collect the shattered fragments of the key they will all invariably get stuck at the Water Temple and just give up.

Where t is the time for a problem size of 1
speed = (t(n^m))/hardware_speedup

A bit of algebra and we get...
((speed*hardware_speedup)/t)^(1/m) = n

That is, for, say, an order n^2 algorithm your speedup from hardware on a similar sized problem gets thrown under a big-ol square root. Such that, if your code sucks, "...aiming to use the power of the modern consoles to push the game engine as far as it would go" won't get you nearly as far as you would hope.

The thing about a statement like this is that, regardless of how correct it may be, it is completely, and flaccidly, useless.

Let's switch the analogy to something like a CPU scheduler.

Say that we have an OS and it habitually lags ass. Tasks quickly begin to accumulate within our OS, CPU utilization drops precipitously, and we eventually hit a deadlock. This is a front and center problem. All of the project's developers have been shuffled into the main hall to address this one issue, because if this doesn't work then we have nothing.

The hall is buzzing with discussion. People are pouring over profiles and usage patterns. Real progress is being made. Then, suddenly, from the back of the hall comes a booming voice.

"It's tasks in, tasks out. We're just taking in more tasks than we're finishing." ...

You'd be able to hear a pin drop. Okay, yes, technically. But...and?