Tag: monoculture

Posted on
by

A yellow-faced bumblebee above an orange poppy, a clump of orange pollen stuck to its legs.

This is kind of hilarious.

Conservation groups asked California to protect four species of native bumblebees. The agriculture industry objected on the grounds that the state’s endangered species law doesn’t cover insects. But the state fish and game code, in trying to cover all its bases defining marine life, defines a fish as “a wild fish, mollusk, crustacean, invertebrate, amphibian, or part, spawn, or ovum of any of those animals.”

So technically, bumblebees, being invertebrates, are eligible for protection as fish.

The state supreme court ruled in favor, because that’s technically what the law says. The judge pointed out that the legislature “is in a position to make whatever statutory amendments it may regard as necessary or useful” to resolve any ambiguities…and specifically stated that the ruling does not mean that the court actually believe bumblebees are fish!

Photo of a Yellow-Faced Bumblebee I saw at the South Coast Botanic Gardens a while back. It’s not one of the four species being petitioned for protection. But I wanted to use one of my own photos for illustration, rather than use the one from the newspaper. Though it’s amusing that of the four endangered species they went with a photo of — I kid you not — Bombus crotchii, a.k.a. Crotch’s Bumblebee. Named after George Robert Crotch.

Expanded from a post on Wandering.shop.

Also: Darwinian Honeybees

On a more serious note, hobbyist beekeepers are starting to use a strategy called Darwinian beekeeping to fend off colony collapse disorder.

Essentially you try to mimic how honeybees would live in the wild instead of trying to pack in as many monocultured hives as you can. Build smaller hives and spread them out, so if one gets infested the parasites or diseases don’t spread as easily to the next. Capture a wild swarm of honeybees, which, unlike mail-order bees bred to maximize honey production, have evolved defenses against the invasive mites that have been attacking developing bees. Keep the hives away from plants you’re going to be using pesticides on.

The causes of CCD are still unclear, but there seem to be multiple factors that contribute to it — and these strategies mitigate several of them. And a lower honey yield in exchange for colonies that survive longer seems like it would be worth the trade-off.

Posted on
by

I never thought I’d see Microsoft throw in the towel on their browser engine. Or that, by the time it happened, I’d see that as a bad thing.

But it’s true: like Opera did a few years ago, Microsoft is dropping not only the old Internet Explorer engine, but the newer Edge engine, and will be building Edge on Chromium going forward. That means Edge, Chrome, Opera and Safari are all built on the same codebase. (Chromium split from Apple’s WebKit a while back, but they still have a lot in common.)

Monoculture is still a problem, no matter who runs it. We’re already at the point where webdevs are treating Chrome like the defacto standard, the way they did IE6 back in the day.

Firefox is going to be even more important in the future, ensuring that the web continues to be built on interoperable standards instead of one stakeholder’s goals.

Mozilla is a non-profit organization, and like many, they’re running a year-end donation drive. Now is a good time to contribute to their mission to keep the internet and the web open. (I’ve already made my annual donation to them.)

I think I may want to finally shut down or retool that old Alternative Browser Alliance site I ran during the Second Browser War. The last time I made a significant update to it, Chrome was the new upstart.

Posted on
by

Opera IconIt still feels like an April Fool’s joke, but Opera is in fact switching to WebKit and discontinuing their own engine, Presto.

I can sort of understand. They can stop worrying about the long-running headaches of browser-sniffing websites that assume Opera can’t do things that it can. They can focus their efforts on the features they want to add or enhance, instead of maintaining their own separate codebase.

But here’s the thing: Throughout its history, Opera has served as a check against monoculture, against a single engine dominating the web too thoroughly. And now, it’s embracing the engine that dominates the fast-growing mobile web.

Remember the bad old days when people just wrote for Internet Explorer, and there was basically no innovation in web browser capabilities? It took Firefox’s success to turn the tide, but Opera was there, needling the industry with things like the “Bork edition” which turned the tables on browser-sniffing websites. Opera was a constant reminder that no, the web isn’t just Internet Explorer and Firefox, or just Internet Explorer and Webkit, or just two flavors of WebKit. That it was worth building technologies to leverage cross-browser web standards instead of picking the current 800-pound gorilla and feeding it even more.

There’s a real value in having different engines approaching the web in different ways, because it prevents stagnation. And there’s real value in having different engines use different code, even when implementing the same capabilities, because that means when a security flaw is found in one browser, it doesn’t apply to all of them. I go into this in a lot more detail in the old, but IMO still relevant article, Why do we need alternative web browsers?

The problem, of course, is that as much as I appreciate that role for Opera, it’s never really been their goal. Opera’s purpose is to sell web browser-related services. In the past, an open web was necessary to do that. Now, they’re throwing in their lot with the front-runner instead.

That leaves Mozilla, whose mission actually is to promote an open web, to go it alone. Apple and Microsoft certainly don’t care. And Google only really cares to the extent that their services are available as widely as possible. And when you get onto mobile, all three prioritize getting you into their particular silo.

Webkit browsers are a dime a dozen. The only ones that really matter are Chrome and Safari, and Safari is a lot more important on iOS. Opera will soon be just like Dolphin, Rockmelt and others that I have to rack my brains to remember. Maybe it’ll be enough for the company to survive, but it won’t be enough to keep them relevant.

ยปAll pages site-wide with this tag