unscaled

57 ms·

421.
by unscaled 6y ago
RxJava or Reactive Streams won't solve the issue of ceremony needed for dealing with async I/O. You're correct that it only makes it worse. The real advantage the reactive model offers is a more powerful abstraction for data
422.
by unscaled 6y ago
It's funny enough that the REP family of instructions has existed at least since the original 8086/8088. It's very much a relic of the CISC heritage of the x86 ISA, and it was probably meant to make writing assembly code easi
423.
by unscaled 6y ago
Kanji dictionaries are usually not sorted by reading. These are the dictionaries you will be using for looking up unknown or obscure kanji, not for looking up words (which may be composed of multiple kanji - or no kanji at all!). Since it
424.
by unscaled 6y ago
The SKIP method is indeed a modern invention. It was invented by Jack Halpern and used in his Kanji dictionaries which were published by Kodansha and Kenkyusha - I guess this is where the 'single publisher' idea is coming from. Th
425.
by unscaled 7y ago
No, that doesn't solve the problem at all! AES-GCM was not designed to be used with random nonces - otherwise the nonce space would need to be larger than 96 bits. It was only designed to be safe with a unique counter nonce. That doe
426.
by unscaled 7y ago
I've never seen any claims by authors behind JWT claiming the purpose of JWT is limited constrained delegation, and I highly doubt that is the case. The fact that RFC specifies a subject claim (for the authenticated principal), but not
427.
by unscaled 7y ago
You're absolutely right, but there's one pretty critical point I want to make: > Good TLS and salt + strong hash solve the simple cases of DB theft and network MITM... It doesn't even solve this that. If you're explic
428.
by unscaled 7y ago
So the C philosophy is to provide a bad standard string library that is not thread-safe and makes it impossible to write programs without remote code execution vulnerabilities, rather than have a better library with exactly the same functio
429.
by unscaled 7y ago
If we looked at the past though, the Han Chinese did rebel many times, both agains conquering (e.g. the Yuan and Qing) and native dynasties and these rebellions were often successful. When you think about it, even the current CCP regime sta
430.
by unscaled 7y ago
Their first customers were microcomputer enthusiasts and both Steves were members of the Homebrew Computer club, and Woz built Apple I with continuous feedback from the club meetings. I would argue that it's moving to the Apple II (wer
431.
by unscaled 7y ago
Communism was a roadblock, but China's relative decline (which really just means stagnation) started back during the Qing dynasty in the 19th century.
432.
by unscaled 7y ago
To be fair, throughout most of history, as long as China was under unified rule, it was almost consistently had the largest GDP in the world for any political entity, usually amounting to 25% share of the global GDP. Compared to their histo
433.
by unscaled 7y ago
I think what they did not realize is that once a universal encoding won the battle of standards, it would have to be all-inclusive. Operating systems and platforms like Java settled on Unicode so they won't have to deal with a myriad o
434.
by unscaled 7y ago
Han Unification is something that should have been more nuanced, and I'll be quite surprised of it at least a few linguists didn't give a nuanced answer and have been ignored. 1. Let's start with a simple character (indeed th
435.
by unscaled 7y ago
I keep hearing this myth about how Java pre-5 used to be a pristine language, until it was touched by annotations and generics - and I doubt it, because I was there. Before annotations, Java libraries were basically using gigantic XML files
436.
by unscaled 7y ago
> Books? I have a lot but I'm not buying a lot of physical books these days. Video collections? How many DVDs have you bought in the past year? This is observation is unfortunately woefully irrelevant to Tokyo. CDs, DVDs and Blu-Ray
437.
by unscaled 7y ago
No, this is not what I'm saying. Nobody is asking you to store passwords in cookies. JWT is just a badly designed standard which like many other badly designed standards (XMLDsig, older versions of TLS) can be used safely if you choose
438.
by unscaled 7y ago
I don't think the NIST curves are backdoored, but they obviously have some serious theoretical and practical issues. [1] As far as I know, neither of these issues is relevant to their usage with ECDSA (although invalid curve attacks sh
439.
by unscaled 7y ago
If you are going to use JWT besides its failings, you should use it safely. But not all advice in this piece is equally strong. 1. RS256 vs ES256 - you shouldn't use either. RS256 not just an old standard on the way out. With safe keys
440.
by unscaled 7y ago
Yes, but so is SHA-384 and that is not relevant for the TLS context.
441.
by unscaled 7y ago
Java-the-language was designed to be anti-clever, but a decade later, most code written in it ended up being the epitome of hyper-cleverness. Lack of abstractions (a.k.a "cleverness") on the language level, pushed developers to ab
442.
by unscaled 7y ago
It's also the largest airline in Africa and it has been growing rapidly. Definitely a customer you'd want to keep satisfied.
443.
by unscaled 7y ago
How do you deal with IdP/AS mix-up? The BCP recommends either sending back client_id and iss (but that draft[1] is long expired, and nobody seems to support that implementation), or asking the client to provider a separate exact-match
444.
by unscaled 7y ago
The difference is probably between "can be made to run in a container" (which is true for almost every app) and "designed from day 1 to be containerized" - which is obviously not true for solutions like Keycloak. That be
445.
by unscaled 7y ago
This is more or less one of the only part that is respected in full. I've got to say, I've seen providers without proper discovery, I've seen providers with strange hybrid flows and I'm pretty sure most providers don&#
446.
by unscaled 7y ago
OpenID Connect predates the final JOSE RFCs, but not the drafts. It was not published by IETF, so it allowed itself to refer to internet drafts describing JWT before being released. The JOSE RFCs and Open ID Connect were basically authored
447.
by unscaled 7y ago
The writer is Japanese, so he might be basing this on personal experience. This is not a good list to sway Apple with, even if they had experience with Japan. The first 3 are not tech companies. Tokyu in particular is a huge conglomerate an
448.
by unscaled 7y ago
Only partially correct. I think the earliest drafts of OpenID Connect were completely agnostic of JWT, and so is OAuth 2.0, but the final Open ID Connect Core spec is tightly coupled to the JWT standard in multiple places. The first and mos
449.
by unscaled 7y ago
The "Go is performant" gospel seems to be coming from people who came from Python and JavaScript to Go. I don't think Go prioritizes performance more than most other popular statically-typed language Java[1], Haskell or Swift
450.
by unscaled 7y ago
I guess that's why Go is a subset :) Although to be fair to Go, I don't think ALGOL 68 had a (slightly broken) implementation of CSP and HTTP/2.0 support in the standard library.

More ›