It was an eleven day war and the casualty was their future. Eich was the last time that Mozilla hired a CEO from the ranks of its own engineers. Eich would not have prevented the economic external challenges faced, but Eich and other such engineer-leaders would have prevented the unforced errors Mozilla is known for today. Every CEO after that was business, not engineer. This placed the company onto the same runway of mediocrity and collapse that we see Boeing crashing planes into with some regularity.
the poor countries use WhatsApp mostly due the fact that sms was costly.
so you're tryna to monetize against businesses serving poorer users. yes - they maybe more in number but margins are razor thin.
the richer countries where margins are higher - sms, email, etc are cheaper & permission less. so eventually most providers most settling on email & sms/rcs.
It's not "richer countries", unless none exist in Europe or Asia. SMS has only kept its primacy for text communication in North America. Also note the RoW has never had to pay to receive SMS.
But NB even where messaging apps are defacto norms, most of the confirmation and verification for businesses remains via SMS.
Europe is in a weird middle-ground where WhatsApp is still dominant for person-to-person messaging. Not only was SMS costly back when WhatsApp emerged, users are also split 50/50 between Apple and Android, and SMS between them wasn't nearly as good as Whatsapp for the longest time. But WhatsApp Business is not a big thing. Of course that's vastly overgeneralizing, local differences exist, Europe is a big continent. But I mostly see SMS for transactional messages, and platforms like Instagram DMs for actual two-way communication
Interestingly enough, Instagram has none of this weird pricing stuff on their messaging API, despite being run by the same overlords
Fair points, the geography/margin angle is real. Two bits of nuance:
In a lot of those "poorer" markets WhatsApp isn't cheap-SMS, it's the actual commerce channel. People browse, ask and pay through it (India, Brazil, Indonesia, MENA), so even on thin per-message margins the volume and conversion are way higher than email/SMS ever hit there.
In richer markets it's still dominant for messaging across most of Europe and LatAm, RCS is still fragmented (Apple only just added it, carrier support is uneven), and email open rates are a fraction of WhatsApp's. So I'd push back a bit on "everyone settles on email/SMS."
that xkcd is always funny - but there's a white lie in it e.g on motorcycles in areas where you are allowed to ride median. there's instances of drivers actively tryin' to kill you by swerving onto the median when they see you comin'.
Numerous times now, using Tesla FSD, I've found the car seemingly drifting from the center of the lane, only to have motorcycles buzz by at high speed on the opposite side. It's very polite toward motorcyclists.
I started riding in AZ, which does not allow splitting.
I now live in CA, which does.
The actual justification for it is valid, but mostly outdated:
Older and less powerful motorcycles often have air-cooled engines, and if you sit idling in them in e.g. a traffic jam, they will absolutely overheat and die (at best).
Newer and more powerful bikes are liquid-cooled, and do not have this issue (though the driver overheating is another very real issue).
My personal take is that most riders who use bikes to commute are too reckless, and lane split at speed rather than doing so more safely.
25 mph or below, in fully-stopped traffic, is relatively safe. Ditto for <=35 in a 10-20 mph flow. Each of those gives you a relative stopping distance of about 50 feet, which is 3 or fewer car lengths, which is easy to account for.
60 in a 25mph flow OTOH isn't lane splitting, it's just weaving through traffic recklessly, hoping to God that no one in the next 20 cars lengths merges or drifts at all.
The good rule that most of Europe uses is that motorcycles can "lane filter" (i.e. go in between lanes but only for cars that are basically stopped and only at low speed). Going between lanes is suicidal at high speed, but if cars are <5mph and the motorcycle is ~10mph it's actually safer for the motorcycle because it removes the chance of them being rear-ended. (It also makes motorcycles faster than cars which is helpful for discouraging cars in cities)
Officially allowed in France, Belgium, the Netherlands and UK, from what I can tell. Interesting though, I'd have assumed it's permitted nowhere in the EU.
It's actually safer-ish. First: terms. Filtering is good, involves moving slowly through stopped traffic between the cars, usually under 20mph differential.
Splitting is less good, that involves weaving between cars at speed and is actually dangerous.
Some of the worst accidents are rear endings where drivers (not paying attention) just run you over while stopped in traffic.
This is offset by accidents where people do the stuff you're worried about but when it's practiced correctly that's not as big of a risk and generally leads to less catastrophic accidents than rear endings.
It's also just kinda dumb to force a class of vehicle that can get out of traffic jams to instead sit in them
once mongo rewrote their engine - it's performant, scales & easy to run. seems a lot of devs got burnt by the early issues don't consider it all together.
its probably the easiest database to run at scale. run & forget. you just have to do a little more work on the data modeling part before you write your application i.e consider your query patterns.
since then it has been downhill since.
reply