Tekhne

Have you used fish? The built-in fuzzy matching works pretty well for me. Wondering if there’s any reason to add atuin in. Sync seems like a negative to me more than a positive.

This is a fantastic write-up, thanks for sharing!

I use Jenkins for work, unfortunately, so I have plenty of experience

FYI, Jenkins has an endpoint to validate the pipeline without running it, and there’s a VSCode extension to do this without leaving the editor: https://www.jenkins.io/blog/2018/11/07/Validate-Jenkinsfile/

FYI you can (sorta) redirect searches from the start menu: https://www.windowscentral.com/how-let-google-handle-cortana-web-search-results-windows-10

Mine all go to DDG in FF

I feel the same way. Designing good, opinionated APIs is HARD, but it also provides the best experience for both the author and the consumer.

• Prettier is the undisputed king of JS formatters because it has no options by design. You set and forget.
• One of the reasons iOS is so successful is because they lock down their APIs and put strict standards on apps, making it hard to write something that doesn’t at least look good and slot into the OS well.

Among other examples.

In a world where your IDE and maybe also compiler should warn you about using unicode literals in source code, that’s not much of a concern.

VSCode (and I’m sure other modern IDEs, but haven’t tested) will call out if you’re using a Unicode char that could be confused with a source code symbol (e.g. i and ℹ️, which renders in some fonts as a styled lowercase i without color). I’m sure it does the same on the long equals sign.

Any compiler will complain (usually these days with a decent error message) if someone somehow accidentally inserts an invalid Unicode character instead of typing ==.

Actually I’m guessing this is a localization failure

I’d like to point out, the value add of Rust isn’t speed, it’s safety in a low-level language. C is also just as fast, it’s just that Rust guarantees safety in a wide class of potential catastrophic bugs with little to no runtime overhead, by using the design of the language and compiler.

What do you hate about macOS? From my perspective, it beats out Windows in ease of use, performance, likelihood not to break, and being *NIX; and it beats out Linux by having things working out of the box without needing to spend a decade tinkering just to get things almost working right.

I use Windows for gaming (and work, unfortunately), Mac for general computing and programming, and Linux for servers and vms.

To my understanding, you can’t really use WebAssembly for the frontend - it doesn’t support manipulating the DOM, so you still need to offload a lot of the work to JS. It’s an uncontested language when it comes to web frontend.

No one here has yet complained about Cocoapods and Carthage? I’m traumatized. Thank God for SwiftPM

Are you thinking of this? Great saga: https://imgur.io/gallery/dTv6b

No, practically speaking the domain name should have no effect on access time. DNS has so many layers of caching that as long as SOMEONE has accessed the website nearby (including you), the domain lookup will be local and therefore fast.

Anyway, DNS lookup times, even slow ones, are still not going to be noticable to the end use originally.