Part 2 is, perhaps suprisingly, a follow-up to libinput and lua-plugins (Part 1) . The moon has circled us a few times since that last...| who-t.blogspot.com
‘Search & Replace’ popup windows are bad user interface design.| MOND←TECH MAGAZINE
This is a topic of intermediate complexity in SLOs. If you are coming to this cold, we recommend you read a few other pieces about SLOs first, then this will make a fair bit more sense to you. SLOs, as you may know, have a dual nature: they have both| RelyAbility Blog
I have noticed a trend recently of library authors abandoning their CHANGELOG.md files, in favour of Github Releases.For a library author, the choice is unde...| bessey.dev
Neovim 0.10 was the longest release cycle since the heady days of the 0.5 release. There are a ton of new features in this release (as well as some breaking changes), so be sure to check the full release notes. You can view the release notes directly in Nvim with :h news. The news file includes information on new features, deprecations, and breaking changes. I especially urge plugin authors to read this file carefully.| gpanders.com
Previously: security engineer at Square, co-author of HackLang, put the 's' in https at Facebook. Maker of CTFs.| www.quaxio.com
Understanding Cost Models| justinjaffray.com
The final part of the article about pattern matching in Ruby, putting it in a broader context of the industry state, possible future usages, and a general effect on the language design.| zverok.space
Or, finally biting the bullet to redesigning my developerly and writerly experience, from the ground up, with Emacs.| www.evalapply.org
Ah, Semantic Versioning. The concept sounds simple enough, but it's been the source of untold lost hours of confusion and disagreements. I'd like to offer up a small change in perspective that I hope will help settle such issues once and for all.| vincenttunru.com
Bound version constraints (upper caps) are starting to show up in the Python ecosystem. This is causing real world problems with libraries following this recommendation, and is likely to continue to get worse; this practice does not scale to large numbers of libraries or large numbers of users. In this discussion I would like to explain why always providing an upper limit causes far more harm than good even for true SemVer libraries, why libraries that pin upper limits require more frequent u...| ISciNumPy.dev
The widely used Python package cryptography changed their build system to use Rust for low-level code, which caused an emotional GitHub thread. Enthusiasts of 32-bit hardware from the 1990s aside, a vocal faction stipulated adherence to Semantic Versioning from the maintainers, claiming it would’ve prevented all grief. I will show you not only why this is wrong but also how relying on Semantic Versioning hurts you – the user.| Hynek Schlawack