atopal

That's because Chrome on Android has a partial implementation of Web Serial. The banner on top is to get information at a glance vs the detailed breakdown of the compatibility table.

I was just correcting your numbers, but I also want to point out that power generated from solar has grown more than 30% in just two years and I think it's uncontroversial that we are in the early stages of the s curve for adoption. Negative prices are obviously an arbitrage opportunity that Battery Energy Storage Systems (BESS) are in the process of capitalizing on.

The maximum amount of energy generated from nuclear in Germany was 171TWh in 2001 [0]. In 2020 solar and wind generated 175TWh and in 2025 they generated 206TWh [1].

[0] https://en.wikipedia.org/wiki/Nuclear_power_in_Germany [1] https://www.smard.de/home/marktdaten?marketDataAttributes=%7...

It’s rare, unfortunately, and usually not in the typical bulb formats. Here’s one for example with an SSI of 89 for tungsten: https://amarancreators.com/products/amaran-100x-s?Title=Defa...

It’s called SSI, spectral similarity index. SSI is specified for a color temperature, eg 3200 or 5600. 100 is identical to tungsten or sunlight. Values above 85 are good.

It’s terrible discoverability, but a single click seems to do the trick, no long press necessary.

Anchor positioning is part of Interop 2025. Firefox committed to shipping support for it this year: https://wpt.fyi/interop-2025

After that, it should take about 2.5 years for the feature to become Baseline widely available, and depending on your audience[0], you might be able to use it even sooner.

[0]: https://web.dev/blog/whats-my-baseline

Reminds me of the hunger stones in Germany and neighboring countries: https://en.wikipedia.org/wiki/Hunger_stone

If you mean "driven or steered remotely": They were never teleoperated. I'm assuming that would be completely reckless given the nature of radio networks and possibly because of regulations. The car will call a service once it can't make a decision (this is only when the car is fully stopped), and a human will decide to send out a driver or make a decision in the moment.

It’s called learned helplessness and is a good indicator for pessimism. There is a book I enjoyed that discusses the issue in depth, called: Learned Optimism, by Martin Seligman. The second half of the book is about how to become less of a pessimist, by addressing learned helplessness.

I don't understand where the idea comes from that IKEA sofas fall apart after 5 years. All of their sofas come with a 10 year warranty, even the cheapest ones. Here's one at the $850 price point: https://www.ikea.com/us/en/p/uppland-sofa-blekinge-white-s19...

Their more expensive ones come with a 25 year warranty and still only cost $2,500: https://www.ikea.com/us/en/p/stockholm-sofa-seglora-natural-...

Unfortunately washing rice doesn’t remove the arsenic[0], cooking it with a lot of water like pasta does that. You might still want to wash the rice to remove other contaminants, depending on the rice you use.

[0] https://www.youtube.com/watch?v=B3CHsbNkr3c&pp=ygUEUmljZQ%3D...

There are about 6000 spoken languages around the world with an extreme variety in how they produce meaning. How could you make sweeping statements about all of them?

We made that change around 2017. Mozilla Developer Network is somewhat ambiguous. In surveys and user interviews people were confused about the name. Web developers thought it might be a resource specifically for Mozilla developers, which to be fair was the focus in the earlier days. The web platform documentation was just one part of many Mozilla related things documented on MDN for some time. In 2017 though the web platform documentation had grown to make up 95% of MDN's traffic and it had become clear that it was not primarily a resource for Mozilla developers anymore, the name change to "MDN Web Docs" was intended to reflect that change in focus.

Looking at browser usage for the last two major versions is misleading. That would only be true in a parallel release of a web platform feature in every browser, but that's basically never the case, and it's not the same for every feature. A feature like subgrid was launched years ago in Firefox, last year in Safari and will be launched later this year in Chromium. So, by the time it's in Baseline, it will be in two versions back for Chromium browsers, but 20+ versions back for Firefox and over a year old in Safari.

The issue with Safari is that it's tied to the operating system on iOS. That's an issue with minor releases, but even more so with major releases, where you can't get Safari 16 for iOS 15. That naturally means slower uptake compared to Chrome or Firefox which will update the browser in the background seamlessly.

I'm hoping that we'll be able to identify better usage data and a better understanding of developer expectations to refine this definition.

The core browser set is not defined in exact versions of browsers, since many browsers release every 4-6 weeks. The two most recent major versions refers to the number before the first point. So, for Chrome it would be 113 and 112, for Safari it would be 15.x and 16.x.

But the crucial point is, it's not the same for every feature. A feature like subgrid was launched years ago in Firefox, last year in Safari and will be launched later this year in Chromium. So, by the time it's in Baseline, it will be in two versions back for Chromium browsers, but 20+ versions back for Firefox and over a year old in Safari.

Maybe showing the version numbers on the widget per feature might be useful.

Wow, is that really necessary? It almost hurts physically to read that strong of a statement directed at another person.

You aren't even really disagreeing with the OP. You could have said: "You're right about the 99% of non professional use cases (sharing on social media and the occasional small print), but not the 1% case of big prints.

Thanks for the feedback! So, one thing we are doing differently this time around is updating the site incrementally instead of a big bang redesign. In the case of the article pages that means limited changes in the first phase to get them to conform to the new brand identity. The number of characters per line is an issue though. As stated in the blog post, we'll address the article page layout in the next phase. Article pages are where MDN users spend most of their time, we want to make sure we get those right, so we are setting aside time to focus on just them.

But Mozilla claims that it's exactly the old add-on system that keeps Firefox from being more secure. What if they were just as secure as Chrome after giving up on the old add-on system? Wouldn't it make more sense for them to compete without the disadvantage of being the less secure browser?

Can you say why you would drop Firefox for Chromium?

I was chatting with my Uber driver last week and he said he preferred Uber, because they guarantee $1500 a week provided you accept a certain amount of rides. This is in SF.

AFAIK they don't. There is a cap on licensing for H264. Cisco is already hitting that limit with their commercial offerings, so they can essentially offer OpenH264 at zero (licensing) cost.

> There is a lot to be said for having choice. Just because the dominant browser today is OSS (Chrome) doesn't mean Mozilla should declare victory and pack its bags with Firefox.

Just since this is repeated so often: Chrome is not and never has been open source software in any shape or form. Chromium is OSS, but has only a tiny fraction of Chrome's market share and AFAIK nobody really knows what the differences between those two are (outside of the obvious: Flash player, pdf reader, etc.). Btw, Firefox is still the only major browser that's OSS, neither Safari nor Edge/IE are open source.

This isn't academic nitpicking either. Mozilla had to build a PDF reader from scratch (pdf.js), it couldn't just reuse what Chrome was using to display pdfs, since it wasn't open source. However everyone can now use pdf.js for the same task.