Japan is a rather stubborn outlier, but even they still make an effort to learn. There's no getting around the fact that English is the language of science and commerce such that many people choose to learn it even if it's not their mother tongue. No need to get in a huff about it.
Of course English is the language for science and commerce, but that has nothing to do with it. Because you can't tell people "you can't speak your language here".
> you can't tell people "you can't speak your language here".
Yes you can, and that has been standard practice on the Internet since forever.
Things are much better now with Unicode etc., you will still run into problems with things like directionality and non-Latin scripts all the time.
If English is the default language and if English support is always the highest priority compared to every other language, that’s effectively the same as saying “you can’t speak your language here”.
And it works the other way around too. If you build something local and support only the languages used locally, you’re effectively saying to everyone else, “you can’t use your language here”.
> > you can't tell people "you can't speak your language here".
> Yes you can, and that has been standard practice on the Internet since forever.
Visst, klart du kan säga så, men andra kan lika väl strunta i det. Och tala om för dig att du beter dig som en översittare och ett arsel. Översittar-arslen har alltid funnits, det är inget nytt.
Well, you may have a hard time pronouncing the words, but that has nothing to do with understanding the language or with reading and writing in it. Spelling might actually be easier if you’re not distracted by inconsistencies compared to spoken language.
Also, “global” doesn’t have to mean “relevant and accessible to every single person in the world”. It could also be the opposite of “local”, for example, and describe the kind of content you can find, rather the kind of people.
Again it is not the point. English is not my native language and I have no problem in using it... but if I am replying to someone I know their own language and would like to use that (with just them) I shouldn't be forced not to do that.
yeah, I don't speak any other languages fluently but I also find that sentiment disgusting and reductive. use whatever language you want, wherever you want.
the navigation might benifit from the css scrollbar-gutter: stable.
it's kind of distracting how the content jumps a bit left and right when you navigate between for example about and news, because the scrollbar appears.
Learned a new thing, thanks. What about overflow: overlay? It can also solve the problem by being on top of layout and not part of it. Browsers still support it, although it is deprecated (never understood why).
It could. Right now, they've got about the same amount of support, so it wouldn't even matter much. (Though the caniuse stat is kind of misleading, since you wouldn't see the scrollbar on mobile anyways, and a large part of the non-support is coming from Safari on iOs)
I'm curious what was the approach to get enough users to actually use this, also noticed there's dark mode, but I don't see a setting for it. Guessing it's for registered users?
tangent: Why are there still a lot of sites not doing dark mode first. Discord did a great job of this.
I'm happy to see people exploring further now that we know a bit more about the effects of initial social networks, particularly their downsides from both personal and network level. We've barely made it off the beachhead IMO.
The same w/blogs which pretty much stopped evolving after Tumbler & Medium.
Good observations. Also I do think that many people still try to make blogs better. It just no one achieved success yet. But I remember seeing many products over the years reading.supply was cool. Microblog was cool. Maybe few others. They were/are cool, but a bit obscure
Yes, but it's based on the word's pronunciation starting with a vowel sound, not the word's spelling starting with a vowel letter. In the word "user", the 'u' is normally pronounced as 'yu', which starts with a consonant; therefore the correct phrase is "a user", not "an user". Contrary to ReactiveJelly's speculation, this is true in both American and British dialects. Perhaps there is some other dialect where it isn't.
It’s to do with the sound, not the letter. “User” is typically pronounced “yoozer”, with a leading consonant sound, so it’s “a user”.
There are all kinds of cases where this reveals interesting things about how someone pronounces things.
An American will speak of “an herb” because the h is still silent there (“an ’erb”), whereas an Australian (and most other English dialects) will speak of “a herb” because it’s no longer silent.
In the KJV, 1 Kings 10:29 gets two in one verse, speaking of “an horse for an hundred and fifty”, showing that in the English of the early 1600s, you had “an ’orse” and “an ’undred” by pronunciation, whereas all major dialects now sound the h. (For reading aloud, I personally say “a horse for a hundred and fifty”, having decided that a/an are the same word just with context-dependent spelling and pronunciation, like “the” has two context-dependent pronunciations (“thuh dog” versus “thee elephant”, likewise based on the next syllable’s sound), though they’re both spelled the same way.)
If a Rust developer writes “an &str”, they’re probably pronouncing it “an ampersand str” or “an and str”, but if they write “a &str”, they might be pronouncing it “a str slice” or “a reference to a str”.
> showing that in the English of the early 1600s, you had “an ’orse” and “an ’undred” by pronunciation, whereas all major dialects now sound the h.
I don't know what I'd call (or you're calling) 'major dialects' (just RP & GenAm?) but quite large geographic chunks of England would say "an 'orse for a 'undred", in the early 2000s.
(And 'a undred' is not a typo. I don't know why that's different, but 'an undred' just sounds wrong to me.)
I thought it was down to a few rather small regions left in the UK (and fading), but I’m not expert in their accents. I could well be wrong, and my word choice was injudicious.
I should also note that Indian English is also a bit patchy, their leading aitches are regularly silent due to it not being a common construct in their own languages; but they’re also less precise about a/an in general too.
As an American, I’m fascinated by your precise description of accents. We have plenty of our own, but we don’t categorize them that precisely. For example, I can usually distinguish between West Texas and North Carolina, but I probably couldn’t explain the difference.
I think they can be just as readily, not that I mean to tell you your own interests of course but if one is interested in accents/linguistics/usage etc. then the patterns are perhaps more noticeable.
I'm British, so I'm not that familiar with many American accents, certainly not your examples, but off the top of my head you do find elongated vowels, t->d, ay->i (short), rhotic r, nasalisation, 'vocal fry', 'baby voice', and ending every sentence or half sentence with rising intonation like it's a question?
Oh it's certainly fading. And I suppose I should have qualified that I meant the 'traditionally associated dialect & accent' of large geographic chunks - which isn't to say that the majority of the population there actually speaks it. But the accent of the guys propping up the bar of the locals' pub across large geographic chunks, I think. I'm no expert either.
But (because English is never simple) you also get people who will intentionally follow the rule based on a pronunciation they don't use, because "it's the rule".
Seems confusing on desktop, too. I suppose we are seeing the same thing. So some threads (or are they comments?) just end in an ellipsis. But there's also no way I can see the full thing...? Weird.
Putting nav down the left hand side of a narrow mobile view seems unfortunate. Should be sticky footer nav like a mobile app with sections easily reachable by thumb.
I must say that this looks amazing on my phone. Spacing, font, sidebar, and lack of header are chef’s kiss. I would however potentially add a dismissible welcome text as a header to describe what I’m looking at.
I suppose it's so the dev/mod can read what's written. Otherwise there could be tons of bad stuff that he might be liable for, and not be able to read to remove.
I don't know how to feel about this. While it seems like a great idea, looking at the front page I feel like looking at a door in a vandalized public toilet. Too much going on with barely any explanation, can't easily tell (at least at first) what is grouped with what, the sidebar (on mobile) being present at all times is a serious waste of space.
So they filter out any non-English text?
I also wonder what they mean with “untrustworthy” and how, specifically, this is and will remain different.
reply