miniblog.

← Back to all posts
Jun 10, 2017 at 11:50
Python is arguably a great PL for a long term project. I can't imagine there will ever be a Python 4 breaking backward compatibility.

Related Posts

Jul 9, 2026 at 19:44
1
It's really satisfying fixing crashes in rust-analyzer. You can start from a panic message and dig until you've got a tiny Rust program that triggers the problem. (It's usually an issue with incomplete source files breaking invariants.)
fix: Crash on code actions when an unresolved module is present · rust-lang/rust-analyzer@9d343e9
fix: Crash on code actions when an unresolved module is present · rust-lang/rust-analyzer@9d343e9
Previously rust-analyzer assumed that a module always had an item list, which isn't true for unresolved modules. Handle this situation gracefully instead of panicking, and add a test. AI disc...
Oct 9, 2024 at 15:07
I really like the MELPA model of packaging directly from git. It solves the problem of forgetting to release something -- just merge a PR and you're done. It also makes version number bumps much less important. You could go even further in a statically typed language and also figure out when breaking changes occur.
Oct 11, 2022 at 20:42
Superb discussion of Go semantics for `for` loop variables, the challenges of breaking changes, and the tradeoffs of static analysis:
redefining for loop variable semantics · golang go · Discussion #56010
redefining for loop variable semantics · golang go · Discussion #56010
Update 2023-06-06: Go 1.21 is expected to support GOEXPERIMENT=loopvar as a way of trying out these new semantics. See #57969 and https://go.dev/wiki/LoopvarExperiment. We have been looking at what...