I'm just a Chinese student from the West so take it as just my two cents but I don't think it will evolve to phonetic syllabaries. Chinese has a lot of homophones so it's useful while reading to have an extra semantic meaning. They also say that once you're used to it, you read faster but at my level I can't confirm it. So with modern input devices you're basically simplifying the hard part of the characters, which is writing, and keeping the reading part where they're better than pure phonetic systems.
I'm a happy owner of an original VF2. However, people buying this board should be aware that the StarFive JH7110 is not compatible with the RVA23 spec, which Ubuntu said it was the bare minimum for now on and might create some software incompatibilities in the future.
There's nothing that's compatible with RVA23 except qemu, and very few boards which are even partially compatible. Ubuntu's decision is a dumb one. This should run Fedora or Debian just fine.
> Ubuntu's decision is a dumb one. This should run Fedora or Debian just fine.
You either pull the future forward, or drag the past. Because of the small market, they decided to forgo generating legacy concerns before they even started seeing mainstream adoption.
I like the decision (they are choosing a better foundation) but I can see the merits either way.
I don’t think it’s dumb - hasty and premature perhaps. Manufacturers have been shipping boards with flaky RVV support, a years old kernel and undocumented blobs on in house baked OS and calling it a day.
Feels like a step towards strong arming them into shipping products that can be supported easier/not being left to rot in a drawer.
For release 26.04 next year, it makes more sense because that is a Long Term Support release and a lot of new hardware from then on will be RVA23-compliant.
They recommend 24.04.3 LTS for current hardware. Maybe they just don't want (then) old hardware to be stuck on a non-LTS release.
A person might suggest that it would be more user friendly to support hardware that people own. There's a parallel to years ago, when Ubuntu was a lot like Debian but it was willing to ship non-free firmware by default because that was the hardware that people actually had, which is part of why it was praised as noob friendly.
I don't think it's dumb. There are very strong hints that we can expect SpacemiT K3 RVA23 boards from possibly multiple vendors by perhaps the end of the year and certainly not long after that.
Leaving RVA23 support until 28.04 LTS would be FAR too long.
It would be nice to see both RVA20 and RVA23 supported in the same OS but the problem is that it's not actually practical to do runtime selection of alternative functions or libraries for all extensions in RVA23. It is possible and sensible for things such as V, perhaps, but extensions such as Zba and Zbb (not in RVA20, but supported by VisionFive 2) and Zicond, Zimop, Zcmop, Zcb have instructions which want to be sprinkled all through just about every function.
You'd have to either deny your main program code the use of all those extensions, or else completely duplicate every program binary.
Not an American, but a Spaniard and I noticed that because we have many common Latin words between English and Spanish, some people from Spain prefer to use the Latinate versions of the words when speaking in English, even if they do not feel the same. But it's easier for us to remember.
In Spanish, we consider Ñ to be a different letter, with its key in keyboards and under a different chapter in dictionaries. Of course you could say that it's just an N with a ~. But that tilde is not defined for any other letter. Why did they do it? In medieval Spanish it was common to write two Ns in many words, with a different sound. For example: "anno", which is now: "año" (year). Two Ns was very similar to M so the tilde was added to remark that it was two Ns, not one M. Later, they just wrote one N with the tilde.
Exactly and ä is never just a, ö never just o and ü never just u. Words like "Uber" just feel wrong from a German perspective.
Also, ß is ss and since words don't start with Ss there is no need for an uppercase ß. When whole words are capitalized ß turns into SS.
Of course there is a little edge case where capitalization isn't reversible. For example, is the capitalized version of the name
MASSMANN to be converted to Maßmann or Massmann?
That is in my opinion the only reason the uppercase ß was added to Unicode. To resolve this ambiguity. It has no place in proper German typography.
Worse, in Spanish it used to be that 'll' and 'ch' were until recently digraphs considered separate letters, which meant that they would sort as such too. That is incredibly annoying to implement.
Technically the ij is a digraph and sometimes a ligature. Although computer keyboards have never really supported that but some mechanical keyboards for typewriters used to. Most modern Dutch people would simply be typing an I and a J and wouldn't necessarily know that they need to also capitalize the J at the beginning of a sentence (Ij would be incorrect). Not a lot of words start with that but some place names do.
The Dutch keyboard layout is effectively US international. There are no special characters that that keyboard supports; including all the accents/modifiers we inherited from French, German, etc. Spelling without those is now correct.
This is something that has evolved over the last decades. In the eighties, people would memorize the character codes to produce letters with those. I remember having a card with the right key combinations for word perfect. This is not a thing anymore. People just skip it and the grammar and spelling rules were actually modified to not require these anymore in most situations.
Funnily enough, the Y, is not commonly used in Dutch and usually referred to as the Greek IJ but pronounced the same way.
For me the Unix/Linux compose key and compose key sequences is where it's at. It's much nicer than the US international keyboard input method, though if I were constantly typing in a language that requires [lots of] accents/diacritics I might have to switch.
And, while its not the case any more, but illustrates how arbitrary the "new letter" vs. "new sound for old letter or combination" is "ll" also was considered its own letter for ~250 years.
It's not mutually exclusive but getting into the right posture is key. Otherwise you're just fighting against it constantly. That's why most doctors advise for change of habits as the first thing to look for. This is sometimes difficult as we want to keep doing the same things but changing keyboards ergonomics is a thing you can try. In fact my doctor was the one to suggest that for me.
Most keyboards have not spent a single thought on ergonomics, unlike chairs where it is common. There's not a lot of real research in this area and there are contradicting theories (some physicians even say that creating muscle in certain areas like the neck is not worth in the long term). Microsoft ergonomic keyboards have some studies behind and many people report success on split and column staggered keyboards.
In addition to the other comment, which I agree as I've heard the same, for the most part Spain and Portugal have been operating as if the Iberian Peninsula was an island. The Pyrenees are a big barrier, and in Franco's era the country was very isolated.
The same happens with the electricity grid, even though it is connected to France, it has very small capacity.
I like Kotlin and I use it at $dayjob but I'm not doing Android development, just backend. I'm at a big company and most new code is Kotlin, many colleagues like it too.
Most people think Kotlin = Android, but it would be interesting to know the exact proportion of Android vs the rest of Kotlin developers. Even frameworks like Spring Boot officially support Kotlin, so I think there's a significant user base, maybe too silent.
I use Niri at home and PaperWM at work but I use most apps maximized. The thing that I like is that I can move between windows in a WASD like shortcut, more convenient that doing Alt-Tab. However vertical split is also very easy to do in Niri and it's sometimes very convenient.
As a reminder, LaLiga got caught spying their users with their app using the microphone and the geolocation to detect illegal emissions in bars. They got fined, applying the GDPR, with 250k euros. [0]
However, the last court order, removed the fine as they interpreted the AEPD (Spanish data protection agency, and the ones that fined LaLiga) did not showed any guidelines about this kind of stuff so it couldn't be fined retroactively. And that showing a "Mic in use" warning every time the app was using the microphone, as AEPD wanted, was "excessive". [1]
reply