ucarion

19 ms·

151.
by ucarion 6y ago
From an API evolution standpoint, cursors are a no-brainer over explicit offsets: 1. Nothing stops you from having your cursors be implemented via a SQL offset under the hood. 2. You can have your cursors be base64 data, and embed a cursor
152.
by ucarion 6y ago
For what it's worth, there is a pretty solid conventional wisdom in this space. > - A simpler but much faster engine will beat a more complex engine any time because the advantage of another ply easily outweighs the advantage of som
153.
by ucarion 6y ago
Is it fair to categorize the pitch here as "a simpler AWS Cognito"?
154.
by ucarion 6y ago
SCIM is a pleasure to implement compared to SAML, no doubt. You might be able to get away with only supporting SCIM, the main thing you'd be missing is "just-in-time" user provisioning. But given that you'll probably nee
155.
by ucarion 6y ago
Depending on who your customers are, you might get away with only supporting OIDC. But not supporting SAML is going to be a problem as you move into the big enterprises. Many big companies run on SAML, and expect to auth with vendors over S
156.
by ucarion 6y ago
I push for docker-compose v2 over v3 at work for the same reason. Just to spell out explicitly what nikisweeting is hinting at: For local development use-cases, docker-compose v3 is just v2 minus all the features Docker Swarm doesn't s
157.
by ucarion 6y ago
Since you bring up Docker, this little behavior has always baffled me: $ docker image ls -h Flag shorthand -h has been deprecated, please use --help But: $ docker image -h ls Flag shorthand -h has been deprecated, ple
158.
by ucarion 6y ago
I fully agree with the rest of the article -- production is the only thing that matters, it's our _sine qua non_ -- but this section is too bold by far: > You’ll never prioritize work on non-prod like you will on prod, because custo
159.
by ucarion 6y ago
To that point, what are systems supposed to make of UTF-8 strings encoding codepoints in the surrogate pair range? Is that well-defined? In other words, to what extent are surrogate pairs a UTF-16 thing, rather than a Unicode thing that exi
160.
by ucarion 6y ago
One thing that's a bit unclear to me about properties, as described in this article, is how they should behave with respect to serialization. For instance, in C#, both System.Text.Json and Newtonsoft.Json will get and serialize all pro
161.
by ucarion 6y ago
Not saying this is automatically a problem, but you will lose money over this. When a build dependency is unavailable or broken, you cannot create production artifacts. You'll lose money over this because broken builds lead to incide
162.
by ucarion 6y ago
Unfortunately, this isn't quite true. At least if by Unix you mean POSIX, i.e. you include macOS in your considerations. 1. Sadly, short options are in fact more portable than long options if you're targeting POSIX. For instance,
163.
by ucarion 6y ago
This is pretty widely thrown around, but it should be noted that the central purpose of Haussmannization was public health and beautification: tearing down the slums, building proper infrastructure like sewers and aqueducts, and pretty park
164.
by ucarion 6y ago
As others here have mentioned, the British government maintains similar guidance: https://www.gov.uk/guidance/content-design/writing-for-gov-u... As does the US federal government: https://plainlanguage
165.
by ucarion 6y ago
Lest your comment suggest the author of this article isn't aware of this point, he has made this argument precisely: > Whereas China needed to control country-wide Internet access to achieve its censorship goals, Apple and Google
166.
by ucarion 6y ago
Another nice thing about env vars is that they don't appear in the process table, unlike argv. For many applications, that makes them a suitable place to inject secrets, and makes them convenient to inject via wrapper tools. For instan
167.
by ucarion 6y ago
Most cli parsers don't fully support the author's suggested model because it means you can't parse argv without knowing the flags in advance. For example, the author suggests that a cli parser should be able to understand the
168.
by ucarion 6y ago
For other readers: "Sorbet" refers to https://sorbet.org/ , Stripe's Ruby type checker.
169.
by ucarion 6y ago
You can also more easily generate schemas, or generate things from schemas, if they're in JSON. Sure, you can still do these things when schemas are a non-JSON format, but it increases the barrier of entry to writing tooling on top of
170.
by ucarion 6y ago
More legible formats: https://www.rfc-editor.org/rfc/rfc8799.html https://tools.ietf.org/html/rfc8799
171.
by ucarion 6y ago
This article has good discussion of this problem: https://blog.dyvil.org/syntax/2016/04/19/angle-bracket-gener...
172.
by ucarion 6y ago
You can pretty easily parse + verify JWTs in Bash using cut + base64 + openssl, although the precise invocations depend on which "alg"s you're using.
173.
by ucarion 6y ago
Putting secret information in a URI is explicitly called out as a bad idea in the very RFC you reference: > URI producers should not provide a URI that contains a username or password that is intended to be secret. URIs are frequently d
174.
by ucarion 6y ago
From the the article: > Germany had been in line with NHSX, but its government announced on Sunday it had switched tack to a "strongly decentralised approach". Today's Stratechery ( https://stratechery.com/2
175.
by ucarion 6y ago
To clarify for others: "anyhow" and "thiserror" are not placeholder names in that sentence. They refer to: https://github.com/dtolnay/anyhow https://github.com/dtolnay/thiserror
176.
by ucarion 6y ago
I'm not sure that's true. The more Florence debases the silver florin while Venice stays honest, the more I'm tempted to melt my old florins into Venetian silver ducats. I only get a better and better deal that way.
177.
by ucarion 7y ago
Good luck! Seems like previous discussions with the mailing list could have gone better, but PASETO seems like promising work!
178.
by ucarion 7y ago
What IETF WG are you working through?
179.
by ucarion 7y ago
The article mentions they use Bezier curves over the HSB colorspace. > I used Lyft’s amazing Colorbox to help normalize our colors. Instead of a naive linear scale at 10% increments, I used bezier curves—a vast improvement at the more ex
180.
by ucarion 7y ago
You can do this with the Auth0 APIs as well, no? By hitting the `/authorize` endpoint for saml-typed Auth0 connections? In that case Auth0 then acts as a SAML-to-OpenID Connect translation layer.

More ›