• 1 Post
  • 577 Comments
Joined 2 years ago
cake
Cake day: June 9th, 2023

help-circle

  • Unfortunately, there are only 3 companies developing browsers right now: Google, Apple and Mozilla.

    Apple’s browsers are only available on Apple platforms. In fact, if you’re on iOS you have no choice, you have to use Safari. Even browsers labelled as “Chrome” or “Firefox” are actually Safari under the hood on iOS. But, on any non Apple platform, you can’t use Safari.

    Google is an ad company, so they don’t want to allow ad blockers on their browser. So, it’s a matter of time before every kind of ad blocking is disabled for Chrome users.

    Firefox is almost entirely funded by Google, so there’s a limit as to what they can do without the funding getting cut off. They seem to be trying to find a way forward without Google, but the result, if anything is as bad as Google if not worse:

    “investing in privacy-respecting advertising to grow new revenue in the near term; developing trustworthy, open source AI to ensure technical and product relevance in the mid term;”

    https://blog.mozilla.org/en/mozilla/mozilla-leadership-growth-planning-updates/

    All these other browser people like are basically reskinned versions of Chrome or Firefox. They have a handful of people working on them. To actually develop a modern browser you need a big team. A modern browser basically has to be an OS capable of running everything from a 3d game engine, to a word processor, to a full featured debugger.

    It looks like it’s only a matter of time before there will be 0 browsers capable of blocking ads, because the only two companies that make multi-platform browsers depend on ads for their revenue, and both of them will have enormous expenses because they’re obsessed with stupid projects like AI.





  • Yeah, I love that one.

    “Try” is too hopeful. “fuck_around” makes it clear that you know what you’re doing is dangerous but you’re going to do it anyhow. I know that in some languages wrapping a lot of code in exception blocks is the norm, but I don’t like that. I think it should be something you only use rarely, and when you do it’s because you know you’re doing something that’s not safe in some way.

    “Catch” has never satisfied me. I mean, I know what it does, but it doesn’t seem to relate to “try”. Really, if “try” doesn’t succeed, the corresponding block should be “fail”. But, then you’d have the confusion of a block named “fail”, which isn’t ideal. But “find_out” pairs perfectly with “fuck_around” and makes it clear that if you got there it’s because something went wrong.

    I also like “yeet”. Partly it’s fun for comedic value. But, it’s also good because “throw” feels like a casual game of catch in the park. “Yeet” feels more like it’s out of control, if you hit a “throw” your code isn’t carefully handing off its state, it’s hitting the eject button and hoping for the best. You hope there’s an exception handler higher up the stack that will do the right thing, but it also might just bubble all the way up to the top and spit out a nasty exception for the user.







  • I’ve heard that in Germany it’s “Golf von Mexiko (Golf von Amerika)”. That’s really annoying. I can vaguely understand it having the parenthesized name in English. Say in 3 years some kid in England is doing a report about something in the US and the Gulf of America comes up. Maybe you’d want the kid to be able to find it on the map. But, maybe it’s fine if the kid has to look it up somewhere else, realize that’s the stupid name, then search for Gulf of Amerikkka.

    But, it doesn’t make any sense to do that for other languages. Just like we don’t get Finland (Suomi) when searching for Finland, Finns shouldn’t get something like Meksikonlahti (Gulf of America). They aren’t going to be exposed to / hearing the Finnish translation of the English name, so it’s not helpful in any way to have that parenthesized version.


  • What’s dumb about this is that in their jurisdiction (Mexico) it is actually the “Gulf of Mexico” in Google Maps, they don’t get the “Gulf of America” name. In the US it’s labelled as “Gulf of America” without mentioning “Gulf of Mexico” which you could argue Google has to do because it (theoretically) follows national laws everywhere it operates.

    That’s why Korean users don’t see the Sea of Japan to their east, they see the East Sea. That’s why in some locations the Persian Gulf is referred to as the Arabian Gulf instead. It’s also why inside India the borders you see for Kashmir don’t match the borders you see for Kashmir if you’re in Pakistan. The rest of the world sees a third version of that area with areas marked as disputed.

    What’s really annoying is that every other country in the world is exposed to this “Gulf of America” silliness, even countries where people don’t speak English. I can understand (just barely) having “(Gulf of America)” under “Gulf of Mexico” in English-speaking countries because if someone is hearing news from a US source and they refer to the Gulf of America, it might be useful to know what they’re talking about. It’s in the news now, but in 3 years say you’re a high-school kid trying to do a geography report and can’t find the feature on the map, that could be annoying.

    But, this parenthesis rule apparently even extends to Germany, where it’s “Golf von Mexiko (Golf von Amerika)”. There’s no reason to include a name that doesn’t exist in your language on your version of the maps app. If I, as an English-maps user look at Germany, I don’t get Munich (Munchen). I don’t get Florence (Firenze), I don’t get India (Bhārat). There’s a long-standing tradition that maps show things in the name that’s local to the map user. Sometimes, over time, a name gets changed to be closer to the way it’s said in the local language, so Peking became Beijing.

    Also, google addressed this in a blog post from 2008, almost literally describing this situation:

    “How Google determines the names for bodies of water in Google Earth … if a ruler announced that henceforth the Pacific Ocean would be named after her mother, we would not add that placemark unless and until the name came into common usage”

    Other than the ruler not being female, the body of water being a different one, and “America” not being Donald Trump’s mother, this is the exact situation.

    Edit: I guess technically Donald Trump is female.


  • the concept of file folders and directories, essential to previous generations’ understanding of computers, is gibberish to many modern students.

    This is so weird to me. Aren’t people at all curious? Like, I would never try to fix a car’s engine, but I have a basic understanding of how one works. I wouldn’t install a toilet, but I know about J-traps. I wouldn’t write my own 3D engine, but I know the basics of how they work.

    Files and folder is such a fundamental and basic thing. Where’s the basic curiosity?



  • Just once I’d like to see a movie mock this “asteroid field” trope. Instead of arriving in this area with huge boulders everywhere that you had to juke and swerve around, have them arrive in the asteroid field and see… nothing. Maybe one rock way off in the distance. Maybe have the ship get hit by a grain of sand.

    Captain: I told you to take us to the Main Asteroid Belt!

    Navigator: I did, that’s where we are!

    Captain: But, I thought…

    Navigator: How long have you been a spaceship captain? Did you think it was some kind of quarry? Asteroid belts are mostly empty space!




  • Launching 25 this late would have been a disaster anyhow. 25 would have cannibalized sales from 26, but it might not have sold well to begin with because people want to buy FM for the current season, not for the season that just ended.

    What would be really good is if they got their act together enough to launch FM 26 early, like pre-launch before the transfer window closes, and launch a patch with the new squads as soon as the transfer window is done. It has always been a bit annoying that they launch in November, when the season has been underway for months.