Atom Editor was, and still is, an amazing piece of technology. It was the first practical example of web technologies running locally, applied to a really hard problem: text editors. It it was, and still is, darn good at handling code. — The impossibility to maintain Atom

Apparently, the formers developers of Atom (whose status remains unclear at the time of this writing) are now developing a new text editor, Zed. Note that there’s also Lapce in the radar.

Hot off the kitchen

Building a Full Stack Application with Flask and HTMx.

Note that “semantic understanding” is mostly unrelated to the traditional interpretation of “IDE” as Integrated Development Environment. I personally don’t feel that the “Integrated” bit is all that important. I commit&push from the command line using Julia scripts, rebase in magit, and do code reviews in a browser. If anything, there’s an ample room for improvement for the integration bits. For me, I in “IDE” stands for “intelligent”, smart. — Why an IDE?

Implementing cosine in C from scratch. #clang

Like many here, I turned off commenting years ago. My motivation had less to do with spam. (I’m on WordPress and it does a pretty good job with that.) It had more to do with the conversations moving from my site to the social web. Folks wanted to talk about stuff where they already were, rather than centralizing that conversation on individual blogs. — Ask HN: Are blog comments a thing of the past?

  Soft Cell, Kitchen Sink Drama.

Statistical Learning with Sparsity: The Lasso and Generalizations.

Some developers won’t use an editor without a debugger, or linting, or Git built-in. For me, these aren’t hard requirements but are bonuses. Indeed, most good editors have these, or plugins that enable them. How useful they’re all depends on the language and platform you’re developing for. — Why Neovim is the best code editor / IDE for developers