For my language I've been using a US layout with a similar alteration for years as well on Windows and Linux: AltGr+C = Č, and AltGr+V = Ć (the second one is much less common, basically only used for writing names). Similar for Š, Ž and Đ, I stopped bothering with stuff like á because I need them maybe once every couple of years.
My point being: wow, I've never thought about standardizing the layout, what a marvelous thought. Not for the general public perhaps, but for some programmers it would be a godsend. The whole terminal is basically non-ergonomic on other layouts. Stuff like ./ is right together on the US layout. Similar for coding. I preach to my fellow developers and they see my point but most won't go outside of what's provided by the OS for some reason.
I don't know enough about other European languages from my "region" to make a more general standard (though I suspect it wouldn't be as simple as creating a single "eastern" one, I doubt e.g. Hungarian and Polish have so much in common) but it's a good idea, something that could be collaborated on.
Well, no. I mean something I can stick in my actual code to ensure it matches the spec, be it through validation, strongly typed interfaces, unit tests or some other mechanism.
Also, while a nice API document is a godsend (and sadly often missing in practice), a way to generate the consuming side of the API (again via various mechanisms) is also a very useful thing.
Re-reading the page, perhaps I got it wrong and it works the other way around? Voiden uses e.g. OpenAPI files and verifies it's still compliant with them? That would work, although it's a bit of a double effort.. still, useful in many cases.
That is unfortunate, EU could well present itself as an example of how things can be done right. Unfortunately incompetence and/or indifference, plus lack of IT talent willing to work for the public sector is also a thing in politics. It's an opportunity lost for sure.
Functional cookies are fine. Even analytics is fine if you're using your own (though said own analytics must also company with GDPR personal data retention rules).
What is not fine is giving away your users' personal data to pay for your analytics bill.
That's not true. You can use those cookies, you just need to explain them somewhere on the site. No opt in required.
I talked with our then national information law official (funny fact, same person is currently president of our country), rule of thumb is if you're not using your users' personal data to pay for other people's services (e.g Google analytics) or putting actual personal data in them, you're generally fine without the banner.
Further, if you're a small shop or individual acting in good faith and somehow still violated the law, they will issue a warning first so you can fix the issue. Only the blatant violations by people who should've known better will get a fine instantly (that is the practice here, anyway, I assumed that was the agreement between EU information officers)
My wife worked in one of the national standardization organizations. She was urgently called into her boss' office: "Please be on this meeting with me, I think they will try to bribe me if I'm alone". It only happened once while my wife worked there and it was right before the vote where Microsoft tried to fast track their office format.
Here in Ljubljana too. I wasn't even fully aware of them, doing something else, but somehow it made me check my phone and there was the news bulletin, only a couple of minutes old.
If readability was the only criteria perhaps YAML deserves to win. For some data XML is more readable, its complexity is the bigger problem.
People went all in with things like XSLT and namespaces, Java became the "language that transforms XML into stack traces" for no good reason and complex XML monstrosities were considered normal so when something simple came along it was a much needed breath of fresh air (we were even prepared to overlook its lack of comments). If it wasn't JSON it would have been something else, I'm sure.
YAML seems easier to read, but for me it's much harder to actually read properly since so many things are ambiguous. JSON is very explicit - you always know the data type you're looking at. YAML has a bunch of special cases that you have to remember, and these frequently lead to bugs.
The best example are boolean values. With JSON, you have `true` or `false`. With YAML you have all of these: y|Y|yes|Yes|YES|n|N|no|No|NO|true|True|TRUE|false|False|FALSE|on|On|ON|off|Off|OFF
We are trained from a very young age, as a rule, to see the comma. The semicolon, not so much. Semicolons are unusual: they are not part of story telling; they are from a forgotten grammar which is hardly used.
Pooh had wandered into the Hundred Acre Wood, and was standing in front of what had once been Owl's House. It didn't look at all like a house now; it looked like a tree which had been blown down; and as soon as a house looks like that, it is time you tried to find another one.
What do you mean, not part of story telling? There are 64 semicolons in The House at Pooh Corner; and by the way, nearly all of them are followed by conjunctions.
I get the argument, but I can't imagine a double-blind study of children or adults of any age that would find they see a semicolon versus a comma at a different rate. If anything, the reverse argument works; the semicolon is more obvious because it's so unusual.
My point being: wow, I've never thought about standardizing the layout, what a marvelous thought. Not for the general public perhaps, but for some programmers it would be a godsend. The whole terminal is basically non-ergonomic on other layouts. Stuff like ./ is right together on the US layout. Similar for coding. I preach to my fellow developers and they see my point but most won't go outside of what's provided by the OS for some reason.
I don't know enough about other European languages from my "region" to make a more general standard (though I suspect it wouldn't be as simple as creating a single "eastern" one, I doubt e.g. Hungarian and Polish have so much in common) but it's a good idea, something that could be collaborated on.
reply