For me, both sites work fine on mobile. The first one makes a strawman argument by deliberately writing bad CSS and then pointing at it to say that CSS is bad.
Not only idiots. They bank on laziness. One time you enable something by mistake then you might not spend the time to find the well hidden option to disable it.
Which reminds me, anyone know the precise location where one would disable Google's Gemini on their account?
And they would be correct. Less than 5% of users change defaults. That's why features get shoved in, on by default because if they didn't, very few would ever enable them. Not defending the practice, I hate it, but that's why they do it.
But it's a reality that English is the primary (if not sole) focus, for historical reasons and as the global lingua franca. English is taught (poorly, from what I hear) in schools, played on train announcements, is the only Western language available on ticket machines, and is the assumed language of non-Asian visitors to the country. I was even on a couple of domestic flights a few days ago and the captain / FAs made announcements in English. It is not "arbitrary" at all.
Do you think Japanese people actually read and write in kunrei-shiki? No, they write using their own letters.
Romanization is an approximation that exists primarily for two purposes: 1. to express Japanese terms in other languages and 2. to enable typing Japanese on a computer. It’s silly to enforce kunrei-shiki, a system rarely used in practice, in the name of "accuracy" based on arbitrary criteria. Romanized spellings will never be accurate for obvious reasons.
Given the purpose of romanization, it’s more practical to choose a system that allows non-Japanese speakers to pronounce words more closely aligned with the correct pronunciation.
What I’m complaining about is that the romanization is based specifically on English, arbitrarily chosen from all languages that natively use the Latin alphabet. For example, what’s transcribed as “shi” is only “aligned with the correct pronunciation” for English speakers. In other languages it would be more accurately transcribed as “ši”, “szi“, “chi”, “schi” or even “si”.
If French didn't use the Roman alphabet natively, you might have a point.
At some point you might as well use Roman characters the way the Cherokee alphabet does - which is to say, uses some of the shapes without paying attention to what sounds they made in English.
And the way English generally uses the Roman alphabet (obviously excluding the zillions of irregularities) isn't that far off from how most European languages use the Roman alphabet.
I'd expect that Spanish, German and French speakers would benefit just as much as English speakers from these changes.
> And the way English generally uses the Roman alphabet (obviously excluding the zillions of irregularities) isn't that far off from how most European languages use the Roman alphabet.
Its not far off from the union of how all other European languages use the Roman alphabet, would be closer to accurate.
Sure, but the point is this isn't really making romanized Japanese more English-like. It's making it more similar to how just about every other language already uses the Roman alphabet. This isn't an Anglo-centric thing, it's just good common sense - unless your goal is to make it harder to pronounce your language properly, which seems like an obvious own-goal.
About 30% of people worldwide use a language that's not written in Roman alphabet.
Additionally, being written in Roman alphabet doesn't neccessarily mean it's clear how to pronounce it. Hungarians calls their country "Magyarország", but unless you know Hungarian, you will be surprised with how it's pronounced. Same as "Chenonceaux", "Tekirdağ" or "Crkvina".
Those are especially pathological cases, and not especially relevant to this discussion, as the romanization rules are explicitly designed to be consistent.
We're not talking about words like worcestershire. I'm talking about words like "bat" "monkey" "chimichanga". Those that follow the rules. There can't possibly be irregular spellings using the romanizations we're talking about!
> It's making it more similar to how just about every other language already uses the Roman alphabet.
There is no way "every other language already uses the Roman alphabet."
Many languages are internally consistent in how they use it, but those that are aren't consistent with each other. And then there is English, which does pretty much everything any other language which uses the Roman alphabet does somewhere, and probably a few that none of the other extant languages normally using that alphabet do with it, on top.
It's not entitlement, it's the entire purpose of OSS. You are free to modify, distribute, and profit from other people's code. If you can't do any of these things, then the project is NOT OSS. Simple as that.
Entitlement is when you expect that OSS contributors must provide you with a warranty or a certain feature you need for your business activity. They are not.
The page summarises the license as “Basically… the MIT do-whatever-you-want license”. The MIT license is of course one of the most popular permissive open source licenses.
This is an incredibly misleading comparison. The subsequent clause is a complete contradiction, not a subtle clarification.
The descriptor is correct. The source is available to you, free of charge, and you can do anything with it as long as you extend the same rights to your users.
Yes, I agree that "source available" is an accurate description. Unlike "Open Source" licenses, which have no restrictions, "O'saasy" does not allow you to do "anything" you want. Adding a clause like "but you can't compete with us" makes it incompatible with OSS licenses.
I am fine with licensing your code as you wish, but I will always oppose attempts to redefine the widely understood and established meaning of "open source" that has been in place for over 30 years. You don't get to change its definition.
The “established” meaning has in fact been deliberately created by megacarporations like Microsoft so they can exploit free labor by volunteers to make money without lifting a finger. Look at who is sponsoring the OSI.
Having all your code go through a multi-step process that spits out 30 different files makes it impossible to know what’s really happening, which I’m uncomfortable with.
reply