Marijn Haverbeke is a user on You can follow them or interact with them if you have an account anywhere in the fediverse. If you don't, you can sign up here.

Marijn Haverbeke

Half of the HN comments on any Web-based thing, no matter how awesome, are guaranteed to be 'eww it's JavaScript'. Hell yes it's JavaScript, and it's still winning.

Automating the release process of ProseMirror was time well spent. Releasing often and with accurate release notes is much easier when the notes are in commit messages and the actual process that generates tags, commits, and changelogs is a script.

I still do have to run a command—not comfortable with having every bit of garbage I push to github immediately becoming a release, and I do like to combine a day's work into a single release without the complexity of a dev branch.

love to write code against a spec that's not kept in sync with the implementation

This toot was brought to you by me watching the a11ycasts videos, which have _great_ accessibility information but a terrible google polymer bias (and some rather bad code)

I don't feel any of the tech being added to the web under the name 'web components' is very helpful, and I'm worried that we're adding more complexity to an already overcomplex system to accommodate a dead end.

If you publish stuff on npm, don't upgrade to npm 5.7.1—it creates tarballs with all timestamps set to 0 (1970), which breaks some users' workflows (zip won't pack such files, for example).

The 3rd edition of Eloquent JavaScript is now the definitive edition!

Editing my book is making it apparent that I'm a terrible comma-abuser. And almost every use of scare quotes ends up being edited out or replaced by emphasis, so I'm not sure why I keep introducing those.

Seems that in this brave new package lock world people are often accidentally stuck on old versions of dependencies. I keep getting bug reports about an issue in a dependency that has been fixed for months.

I know a proper workflow can avoid this, or greenkeeper or what have you. But the tools make it really easy to do wrong.

It's me, the nerd who forgets crucial personal details about people and then has trouble carrying a conversation with them because I don't want to ask again.

Characterizing RxJs-style (event stream) programming as pure functional (which their docs do a lot) seems inaccurate. Every bigger 'reactive' app I've seen is a tangle of imperative streams with the same data coherence problems that jQuery-style code would have.

I'm sure you _can_ use them to implement a clean design, but the same goes for jQuery

My ability to learn shell scripting, TeX, or Perl is seriously hampered by the way I go "how did anyone think this a good idea?" for half the concepts, and then dropping it.

See also emacs lisp, vimscript

When I learned C++ is was still young and gullible enough to assume all the complexity and programmer-hostility had good reasons. I'd have more trouble with that today.

Let's see what's going to take me longer—writing this book, or getting the pdf to look right.

One thing I got from trying to render multi-script text with LaTeX is an appreciation for how well browsers handle Unicode. There's a _lot_ of things you can get wrong (and LaTeX, by default, gets every single one of them wrong)

I'm starting to suspect the gmail team doesn't even test with Firefox anymore. Editor regressions keep piling up, don't seem to get fixed.

When I feel bad about my projects having some bugs open I look at the Chrome or Gecko bug tracker and I feel so much better

Removing more mentions of linked lists from EJS. And then turning in my Lisper badge.

The new Eloquent JavaScript edition has a cover (by! See More illustrations to come soon.