> Eh, somewhat reductive thinking. Demand for renewables causes an increase in the build out of new renewables. Yea, it's not instant, but that's how markets work.
Funny how this line of thinking is indistinguishable from crypto.
> It is not when we can deploy massive amounts of renewables. Not only for AI, but for other industrial workloads that user power.
Funny how this line of thinking is indistinguishable from crypto. "Yes, we build a lot o power which is immediately consumed by us, but see how this is good? See? SEE?!"
> we'd be pushing out subsidies to build out renewables at 10x the rate we are now.
And these would be gobbled up by crypto and AI data centers, right?
These days every time a government as much as thinks of imponging on a supranational corporation's right to do whatever the hell it pleases you'll hear no end of cries ranging from "overregulation" to "tyranny".
So, it's not "trivially provable that Cyrillic is better suited to Slavic languages". But that "the symbols representtion we settled on in software has some difficulties disambiguatuong some, but not all cases of symbol use in a language, a problem that is not unique to Slavic languages, see Dutch IJ, Turkish ı/i, German ß etc."
Decoupling choice of script from "symbols representation" is a weird approach — this is how people type them out.
Yes, problems are not unique to Slavic languages, but at least for _some_ Slavic languages, Cyrillic has been taken to the most simplified form that is _accidentally_ easy to process on a computer too.
But yes, I was a bit too absolutist, I agree — as ever, everything is more nuanced, so perhaps not "trivially provable", but in "closer to full differentiation in graphical representation while being simple and unambiguous to process on a computer"?
> is trivially provable that Cyrillic script is better adapted even to languages which do not use it today, but have to resort to digraphs or glyphs with diacritics
Take a look at the Cyrillic section of Unicode to see your trivially provable claim being trivially disproven. You'll see all the same digraphs, glyphs, accents, graves etc. as used in Latin scripts.
It's also easy to see it easily disproven if you look at all the languages USSR forced cyrillic alphabet on.
To be fair, the parent post was clearly talking about Slavic languages, not "all the languages USSR forced cyrillic alphabet on", which were not Slavic and which required significant modifications to the alphabet.
Indeed: most notably, Croatian, Slovenian, Bosnian, Serbian and Montenegrin are all unambiguous with Cyrillic, but Latin script dominates, even in officially Cyrillic-first Serbia.
Again, it is seen as a political tool (pro-West or pro-Russia), when Cyrillic is technically better suited (there is certainly history as well, but that's very mixed up in the region).
Again, I am saying this as someone who has worked to implement things like full-text search, collation (lexical ordering/sorting) algorithms and tables, fonts and ligatures, functions like uppercase/titlecase/lowercase...
Eg. an already complex Unicode Collation Algorithm tables can never support exceptions with digraphs like "konjukcija" (nj is usually a digraph, but not here), etc.
The unique quirk with South Slavic languages is the linguistic work e.g. associated with Vuk Karadžić [1] which resulted in a cleaned up purely phonetic alphabet. This was done across the region and ended up getting plumbed through both alphabets, so e.g. the Croatians/Slovenes write in latin but with a handful of special characters for the unique sounds like "š" or the double-letter characters "dž" "lj", which also map 1-1 to stuff on the Serbian Cyrillic side.
It's the kind of legacy cleanup you love to see :-)
I invite you for a walk through Belgrade streets, maybe even with Google Street View. There will be Cyrillic in official signage, but ads and shop names will be predominately in Latin script. If there are some in Cyrillic, they are likely to be part of a newer "hipster" move to differentiate more for the tourists.
> None of those are digraphs or have diacritics, each is a single letter/character
Okay, you got me, these don't have diacritics, but other Slavic languages do. Unicode committee decided that some of these are separate letters (Ѓ, Й, Ё etc.) and some are not (Ў), but still doesn't make these "trivially provable to suit Slavic languages better".
> Nj (this "letter" is made up of two other letters)
Indeed it is. Invented in 1818. E.g. Russian uses two "нь" for the same thing.
My point is, even if I may confuse my linguistic terminology from time to time, is... How does all this make Cyrillic "trivially provable" to be better suited for Slavic languages than Latin script? It's all the same: invent new letters or new letter combinations, or slap a few diacritics on top. And when that is not enough, borrow from Latin. E.g., j in Serbian, ї in Ukrainian and й in Russian for the same sound.
Some of this was a top-down overhaul of the writing system in the 19th century. Before that it was an awful mess and people just "vibe-wrote" the weird Slavic sounds using latin how they saw fit; try reading some old writings from that era. Or read some modern Polish or Czech text :-D
So the original claim of "is trivially provable that Cyrillic script is better adapted even to languages which do not use it today" boils down to "in the 19th Century they cleaned up the writing system" (similarly, there was a top-down cleanup of Russian, with Bolsheviks removing ѣ,ѳ, і, ѵ and ъ version of yer)
Most of the extra glyphs are for non-Slavic (Turk languages of Central Asia and Siberia). You see the same (and worse) in Latin Unicode pages — just look at how many variations of vowels 'a', 'i', or 'e' you have, consonants like 'c', 'z', 's'…
Wait, what? Double-clicking will prompt for Face ID to open your default card for oayment, and from there you swipe down to see the stack — which I suppose is the screen you’re looking for.
But you cannot edit, add, or remove anything in this stack, and there's no way to go from it to the wallet. You have to close it, and open the actual wallet app which will show a slightly different view, and more items
> you can be unstuck (or I guess you would switch to Rust, Scala or F#)
Yup, I've seen too many of these engineers, trying to shoehorn a poorly thought-out half-working Haskell into every language they come in contact with :)
> If a third-party binding makes HTTP calls through concrete functions, we have no way to add tracing, no way to inject timeouts tuned to our SLOs, no way to simulate partner outages in testing, and no way to explain the 400ms gap in a trace
Given that tracing etc. is IO, are they just threading IO through the entirety of all their Haskell code?
Partly because Fox News would be much cheaper.
reply