bugmen0t

The link is terrible. Maybe the article should link to https://arewefastyet.com or maybe the Speedometer selection at https://arewefastyet.com/win10/benchmarks/raptor-desktop-spe...

There's also @ for steering the browser to a specific search engine (e.g., wikipedia search).

The canonical URL for how the address bar short cuts is https://support.mozilla.org/en-US/kb/address-bar-autocomplet...

Would be kinda funny if the lone bananas have been removed from the training dataset because they are not part of the depicted item but are merely in the picture for scale :)

So, what's the solution to pairing socks? Buying many pairs from the same. Sure. That makes sense. But what happens when half of them are lost or damaged and you can't buy the same kind?

Do you end up as someone pairing socks again or do you throw away half of your socks?

write a backdoor :) A kernel module that drops the user into a root shell if they call an obscure kernel functionality with a secret value in some registers.

This should be somewhat easy to start and self-contained. If you want, you can easily extend it if you want things to become more fancy. E.g., hiding the secret constant. Implementing a challenge response protocol, limiting access to other global state (hardware dongle? ip address?) and so on.

Frankly, it's surprising how long they managed to drag it along given they build on top of a weird fork of Firefox ESR. Their foundation is crumbling for years and years. They really need to get off of it.

Surprising there is no mention of the wasm/rust-implemented flash player https://ruffle.rs/ in the article.

MDN is documentation for the web, not Firefox.

ESLint does not even support the browser. I think your first sentence is (I'm assuming accidentally) creating a straw man argument.

The web platform was mostly piecemeal and happenstance. Not careful, coordinated design.

You'll find that it is unnecessarily and necessarily complex unless you adopt a framework that makes design decisions for you.

Those who were involved with the Mozilla open source project or the company in the years of ~2013-2014 will heavily disagree.

There was a strong and long debate about the pros and cons. One of the strongest argument against was this here, including interoperability. I believe Cory Doctorow has also written multiple articles against DRM. I agree that DRM is generally bad.

However, the arguments for implementing it were the following: at least two other browsers will adopt the tech and that will allow it (per W3C process) to graduate from a Candidate Recommendation to a full Recommendation, making it part of the web platform.

On top, what would it mean for marketshare if people had to install a second browser just for watching movies? Would the non technical users accept and understand this without switching to a browser that they’d consider "actually feature complete"?

Can’t they run an open collective just to pay the bandwidth bill?

Why are other browsers allowing access when Firefox is not?

Isn’t this a security issue?

Nice idea. Out of curiosity, which song inspired you to build this site?

template does HTML parsing. The `content` attribute returns a DocumentFragment.

Do you have a link to the template instantiation proposal?

Yup. Like on a casio. If I remember correctly the modes were normal time, stop watch, timer and .beats

I had a "beats" watch in the late 90s. Something with "internet" in the name was super appealing to me, when I knew I couldn’t have the actual internet with me.

I guess back then, as a teenager I didn’t even know how much of a nerd I was :-)

These APIs were synchronous and thus blocking. People blamed Firefox being slow when in fact, it was mostly extension APIs and the extension code.

the old APIs were actually the only existing, internal and synchronous APIs which does not work in a multi-process, site-isolation architecture.

The internal APIs also had to go. What else would you do?

Rust has very strong backing at Meta, Microsoft, Google, AWS and others. I wouldn't worry about corporate backing.

You can call into the Windows APIs (there's a windows crate) and if you want to call into something that isn't there, `cbindgen` and friends are amazing.

Use a linter, a formatter or any other tool that complains early and often. Have a starting setup for each programming language. Being surrounded by a supporting environment helps. You don't have to start with a blank document in a dumb editor.

Pick an IDE that you like. I really like PyCharm but vscode is also quite great.

To that extend you might even go further and have some specific visual clues per programming language. Whether that's different editors, editor profiles / themes depends on you.

It shouldn’t be. IMAP doesn’t have to download all of them.

Given the new DOM API, it’s also relatively easy to forbid the "bad APIs" using something like eslint (at the source level) or Trusted Types (at runtime).

The hope is to also cater to frontend frameworks enough that they will adopt it. There are already some conversations.

It’s a risk. That’s why there are bug bounty programs and open processes for the specification.

Browsers have a track record of being able to ship security bugs for severe issues within a day or two. Compare that to patching every individual website.

That’s pretty much the exact use case of a sanitizer.

The most prevalent type of security vulnerability in all of software is XSS. (If you count CVEs, which is admittedly a bit problematic).

I’m collaborating on an attempt to shift the responsibility for XSS from the developers and towards the browser. The current stage focuses on getting the use case "insert HTML but without any scripts" right.

There’s a public specification and prototype implementations in Firefox and Chrome. You can play with it here https://sanitizer-api.dev/

We think that we’ve made the best of many different tradeoffs, but we’re also keen to hear wide feedback.

I recommend you take a look at co2.js. This was just mentioned in the latest issue of branch magazine (https://branch.climateaction.tech/issues/issue-4/co2js/) and I haven't played with it myself yet. Code is linked from the article but also https://github.com/thegreenwebfoundation/co2.js/