tasogare

Ce nom de domaine de camé... Ça en dit long sur l'état de délabrement intellectuel du pays.

No we don't. Sci-hub is doing the job fine. Also just like music and tv, the fragmentation of the market would require on the have multiple subscriptions at the same time.

> the belief that the ordinary smile emoji U+14642

For those who wonder and had to search, it's U+1F642.

I did that once: had a Unicode related bug somewhere in a code that fit nicely 2 A4 pages so I printed them and debug when have lunch with a friend. I was able to think a quick solution that involved few changes, probably not what I would have been go for if using a computer. One of my most debugging experience so far. Also I fixed another bug (or more likely something not in the requirements at the time) and still use that portion of code today.

I know quite a bunch of software engineers which are fine with what are basically beta version of vaccines. Go figure.

> 2006 era JS was more than sufficient to build out highly maintainable 100k+ LOC codebases

Typescript wouldn't have been created if this was the case.

I hate when automatic translation is creeping into software or websites without a way to stop it. In particular since a few month youtube decided it was ok to list video on its home page with translated titles. As I browse videos in 3/4 languages, it became hard to know what language a video will be it. I did some change on language preferences in my account but it didn't really solve the problem.

> I guess maybe Korean (Hangul is phonetic, no?).

Wrong, Korean writing is morpho-phonologic and has complex rules for transforming letters to actual pronunciation. And those rules applies at three different level (whatever position in the syllable, across syllable boundaries or not, or just within syllable).

You are confusing language and its written representation. Sure languages change, that doesn't mean its writing system shouldn't be standardized, as there is a lot of benefits (efficiency) when it's the case. There isn't much discussion about language usage anyway save for a few points.

> So these are entirely problems with private actors

The CROUS, which manage the dorm in my example, are a public actor.

The article speaks of 40,000 cases in just one Indian state vs one case in France. It's really not comparable. That being said the French administration is particularly infuriating and being locked out of everything because "opening bank account requires a proof of residence" coupled to "you need a check (thus bank account) to get your university dormitory room" can definitely happens. And while honest citizens are easily screwed it doesn't even remotely stop fraud which is massive, with a billion of euros scammed out of the wealthfare every year (https://www.google.fr/amp/s/lexpansion.lexpress.fr/actualite...)

I agree about the not wanting to die but "Not wanting to kill someone is something like a universal." is clearly wrong in a lot of cultures. And ignoring this fact is precisely what lead to some recent military disasters as well as bloodshed within Europe.

Because SQL looks and is more simple: plain English words that are easily recognized, with basic queries (select from) that can be taught in less than an hour and then build on it. Now let's look at SPARQL: everything screams at technicality. Curly braces (I'm not sure a non-programmer even know how to type this). Then the variable name prefixed by ?. Then the need to understand what is an URI and how and why prefixes are declared, not to mention the sheer fact of using URI instead of a simple names such as one found for database columns. But even that isn't enough knowledge to start writing the simpliest query. One also need to be taught about RDF triples.

So no, every query languages are not born the same. SPARQL is overly technical and requires a lot of knowledge to do even the simpliest things.

> no entity reconciliation

On the other hand there are still duplicates. I queried Wikidata once and every date result was duplicated because they existed in a slightly different format (7-7-2000 vs 07-07-2000; both were declared as xsd:date). Very "semantic" and powerful data model indeed. In fact the technology should be renamed stringly typed web, because this is what it really is.

Yep. Not only this but in the sample "wd:Q9682" is a lie. wd is a namespace shortcut which is expended to an URI, and the prefix to URI mapping has to be defined as part of the query, otherwise it won't work. Notice how the sample use two of those prefixes (wd and wdt): data is segregated in different namespace that one have to search for and remember each time they want to make a query. And I mean remembering the prefix value, ie a partial URI, not the little cute prefix like wd that semweb sample always use.

Exactly like governments are moving goalposts with their measures: one lockdown... second one... wait no, a third one is necessary; herd immunity will be reached at 70% vaccination + infected, ah no actually only vaccinated count and it's 90%... did I say 99%? No, it will be 100%!

Meanwhile in Japan: people living freely their lives with no lockdowns, no forced vaccination, no vaccine pass. Another model is possible but the Western governments are addicted to their power trip.

No, seperation is a very reasonable position. Some US-based developers and companies tend to forget that not only their ideology is not fully supported within their own country but more importantly that the rest of the world, even if not vocal about, often disagree. There are a lot of different cultures, values and opinions around the world (you know, the actual diversity) and inevitably one political opinion good for virtue signaling points in the US will rub people elsewhere in the wrong way. Pushing it too hard will also produce opposite result by polarizing people more. Some people/culture won't change anyway (cough cough 800 millions USD for promoting women rights in Afghanistan). So stop your cultural imperialism and let the professional stuff separated from your myopic politics.

> YAML

Can't we let this format die? It's both hard for human to format correctly, and for library creator to make a compliant parser.

> The point is that it does seem like this Delta variant breaks through regularly and it does seem (again, purely anecdotal) like it's v infectious. Of course the thing to emphasise is that, whilst it might break through, the vaccine still stops serious illness to a high degree.

If numbers from IHU Méditerranée are to be believed, the Indian variant is about 6 times less dangerous than the English one. Way more infectious and less dangerous, the latter part helped mutating it to the former. And that's the numbers without taking vaccination into account.

I wish medias would relay the information fully instead of spreading fear by only telling about the more infectious part. If indeed less dangerous this is a very good news that this strain is spreading more.

Nothing beats it for data exchange? You must be joking, because if it were remotely true RDF would be in wide use, which is totally not. Except a few niche domains like bioinformatics, it is not used. No killer application use it as a data format, no popular data format is based on it either. Actually I can think of a single data format based on RDF, and the only open-data I know which use it have been converted to it and was simplier to use in their original format.

And for the model: property graph. But yeah, enjoy your Stockholm syndrome with your model where reification is required to annotate an edge. Also even your nickname is an aknowledgment of RDF failure: named graphs (n-quads) were created because RDF triples aren't good enough for modeling data.

The thing I like the best with dotnet (core) is how great is the cross platform support (for console and web applications). I use macOS most of the time, to build Linux containers and this works perfectly. I recently found a bug in the SDK... which impacts Windows only. Other OS than Windows are really supported.

UWP was doomed to fail from day 1 because of how it was tight to UI framework and distribution model. Having a separate, incompatible implementation of the .net framework was another big smell.

Install the SDK. Open a terminal, create a folder and run "dotnet new console" inside it. "dotnet run" (prints Hello world) then start playing around by adding code to Program.cs.

Those already was only one machines or two, if at all. Also a big issue with arcade games is it's quite expensive (100 to 300 yens per game), especially in comparison to buying occasions.

RDF has to be the best and saddest example of sunk cost fallacy. Instead of redirecting their efforts to a more general graph model which has actual hype and use by developers, its cultists are double downing on their abstruse technology stack, making it always more complicated while still not addressing any of its fundamental problems.

I'm living fine with a 3GB data plan (yes 3, not 30). It's only problematic if using tethering otherwise I have hard time understanding how people can consume more data just by browsing the web. Too much adult movies maybe?

My comment isn't unpolite in any way. On the other hand your patronizing comment is rude, so it would be good you start applying to yourself what you are preaching.

I wish people could stop spreading lies about writing systems; giving 3 false information in a single sentence is quite a feat. Of course cuneiform writing is a set of characters, a lot of which being encoded in Unicode starting at U+12000 codepoint. One character doesn't equate a syllable, some even are unpronunced (determiners), and the phonology of Sumerian make its a poor way for its writing system to transcribe English.

I'm using a logical FR layout on a physical Mac FR layout, the underlying layout for Japanese input is QWERTY while the pinyin for Traditional Chinese uses AZERTY... I'm tired of all these context switches and I wish there was an universal keyboard IME that allow me to type the languages I care about without having to switch between IME all the time. Same complains about mobile (iOS). I might build something one day because of how annoying it is (at least typing English is easy from FR keyboard so that's one less keyboard to use).

Thanks for giving me an idea: I'll name each of my project I don't want to be used in professional setting with outrageous names for Americans. Btw Coq will be soon free to use for another project.