The man is a genuine living legend.
Yawn. Wake me up when he finishes TAOCP and takes a brief diversion into creating TEX.
(sarcasm, obviously, but in the best possible taste... legends, both)
2678 publicly visible posts • joined 8 Nov 2007
Minor pedantry alert... the Japanese is "yurusenai"...
The English translation is close enough to "I can't forgive you", so that's cool. An alternative translation might be "intolerable!"
We've had the long-ish period from that guy from Sun (I think it was) saying that privacy is basically dead to the current time where breaches like this have especially become criminals stealing from other criminals. William Gibson nailed it... the future is here, but it's just not evenly distributed.
I wish I could give a cheery outlook and say that everything is going to be all right, but I'm sort of equivocal on that. At least I can offer some wisdom from Leonard Cohen: "There's a crack in everything... that's how the light gets in." ("light" is kind of cheery, no?)
Stay safe, be well, y'all.
It's not only that. If you want to be a "scofflaw" (as per the article) in Japan, you either strike out on your own (high risk, high reward, particularly attractive to western immigrants) or roll in with the existing local grey/black economy. (or do some other lower-level shit like promoting bitcoin or selling pornography). And if you're a non-western immigrant, you just keep your nose down and do your regular (healthcare, restaurant, combini, etc.) job so that you can eventually gain citizenship (and besides, you're not going to be able to change jobs without putting your visa at risk).
This foreign attempt at setting up a new grey economy is destined to fail.
THE UNIONS FOREVER! DE-FEND-ING OUR RIGHTS. POWER TO THE FACT-RIES! THE WORRRKERS UNITE!
"Down with the blackleg," surely? (I can't believe I had to apply the strike tag and all)
(Yes, "There is power in a factory, power in the land, power in the hands of a worker" but you are misquoting)
Unfortunately, not all apps implement shift-insert in the same way. I would love it if all apps pasted what you have just highlighted (ie, do the same as mouse middle click), but Firefox, for one, pastes the contents of the main copy/paste buffer.
At least shift-insert works the way I want in terminal programs. It's particularly handy for mouse-free copy and paste between an emacs buffer and a terminal. Still very useful if I have to use mouse to select text in other source apps.
I am rather curious as how the taishoku daiko perform their task. In person? Can imagine it would be excruciatingly formal.
Not only in terms of business etiquette, there's also a higher level of language formality to deal with. Sounds like a difficult job all right.
Apologies JP speakers if I have commited a "the hoi polloi" on "the taishoku daiko."
No, it's not a "the hoi polloi" error on your part ("hoi" literally translating to "the?"). Japanese has no definite or indefinite articles, so when translating from Japanese to English it's OK to add one or some other surrogate word ("these", "such") as appropriate.
No, what's "clunky" is that the OP:
* thought that some post was interesting
* (presumably) reached into his/her knowledge of Japanese and pulled out "omoshiroi"
* decided to post it using Japanese script (mostly .... that space between the words tells a different story, though; I call cut and paste)
* added a superfluous attempt at "being polite" (as they imagined they should) (that "desu")
Other low-effort interpretations are possible, but they mainly revolve around the OP not really knowing Japanese.
If something is genuinely interesting and you want to express it in Japanese, it's just 面白い (+ Japanese exclamation mark, which I'm not set up for at the moment). Same as "itai", "mazui", "umai", and so on. Tacking on unnecessary "politeness" defeats the purpose and actually sounds sarcastic.
The advice is sound. Given that memory corruption often allows RCE, it makes sense to use a language where memory corruption is simply not a concern.
But even rust grandfathers C/C++'s (what you might call) cargo cultism around order of execution (memory barriers and whatnot). The problem is that order of execution is a non-trivial (unsafe) problem where you're cribbing from C/C++, where your compiler can't check for non-compliance when it comes to translation of the standard, and the CPU can make up its own mind ...
But yeah, in general Rust is a whole lot better. Just not perfect.