melissalobos

I liked this part:

> To use an analogy, if SICP were about automobiles, it would be for the person who wants to know how cars work, how they are built, and how one might design fuel-efficient, safe, reliable vehicles for the 21st century. The people who hate SICP are the ones who just want to know how to drive their car on the highway, just like everyone else.

That kind of summed up my experience with SICP for learning scheme. It won't really tell you how to get things done, but it does help you figure out how scheme works. Which for me at the time when I read it was exactly what I needed.

> So, how onerous is package management in Slackware if there is no dependency checking?

I can't say that I have used Slackware ever, so I don't know. But I have used a Linux distro where every package was statically linked by default. In that case they didn't use any dependency management since every package was just a tarball of some fully statically linked executables or libraries. The only real dependency was the Linux kernel.

In the end Electron may be slow and bloated, but it is easy to distribute and you can make it look exactly how you want. People often say they want apps to look "native", but really most people I have met don't really care that Spotify doesn't use native Windows widgets.

Also, I liked the idea on this site of responding to twitter comments by posting them whole on the site and writing the response below. It feels more like it is an older style mailing list that way.

This seems like it is the second time we have had to learn about the importance of maintain large open source infrastructure projects like this. log4j and openSSL before it, show that these projects aren't just the responsibility of the maintainers, but all of their users as well. We really need more money being paid by larger users like Google directly to the maintainers.