Our twins are four months old today, and holidays are approaching, and I thought it would be a good idea to give a little something to someone who could use it. This coming Sunday, I'll buy the "Be a Coder" bundle (https://www.humblebundle.com/books/be-a-coder-books) to someone who needs, and wants it.

If you'd like to have it, or know someone who would, and you (or them) can't buy it, contact me. Either via DM, or e-mail at [email protected].

Boosting this toot for better coverage is most appreciated!

I know everyone's ready to rake Mozilla over the coals for that Mr Robot stunt, but keep in mind that they build their own browser engine, which is very expensive: http://robert.ocallahan.org/2017/12/maintaining-independent-browser-is.html

So you can switch to qutebrowser/WaterFox/etc., but keep in mind that they're just downstream from the people who actually build the browser engine. Mozilla is fighting on a totally different level than those other browsers.

Funny thing happened today. I went to an electronics shop to find some mounts for the #Keyboardio. I was looking through the available ones, trying to imagine how I'd use them to achieve my desired setup, when a helpful member of the staff came up to me and asked if they can help, what kind of camera I have, what I'm looking for in a stand, and so on.

He looked a bit surprised when I told him it's not for a camera, but for my ergonomic keyboard. But that's not the funny part...

Question: When building a #WebApp / #SPA, and using a #js framework. Which one do you use, and (more importantly) why do you use a framework?

I am investigating what it is exactly that a framework offers over plan #javascript.

The reason for this research? A framework (, , , whatever) comes with a big vendor lock-in, and it's really easy to make an app that is not accessible.
I want to find an alternative (I have yet to investigate WebComponents as I only skimmed it).