I'd always prefer paying for certainty than design a solution built on a lottery.
133 karma · joined November 12, 2021
I'd always prefer paying for certainty than design a solution built on a lottery.
For an honest bandwidth offer, I'd much sooner consider Fly.io rather than Cloudflare. At least with Fly their true pricing is transparent
edit: speaking of transparency, https://imgur.com/HnlWFUe
Instant hire!
And how would you describe HR?
If you can stomach the perf tradeoffs, compiling to WASM is much easier than this
I'd prefer it if these things opened in Firefox, but I can just as easily see how from an engineering perspective they want this mechanism and are willing to defend it. From that perspective, Firefox is intentionally fucking around with OS internals in a way that could create costs for their support org.
(edit: please don't shoot the messenger. I'm an affected user too)
Stepping back a bit, YAML is good enough, and this problem has been incrementally bikeshedded since at least the 1970s, it is time to move on. Human-convenient interfaces (like YAML, bash, perl) are fundamentally messy because we are messy. They're prone to opinion and style, as if replacing some part or other will make the high level problem (that's us) go away. Fretting over perfection in UI is an utterly pointless waste of time.
I don't know what NestedText is and find it very difficulty to care, there are far more important problems in life to be concerned with than yet another incremental retake on serialization. I find it hard to consider contributions like this to be helpful or represent progress in any way.