I made my own custom one in 241 lines of Python + 162 lines of templates of HTML and Atom.

It does not have some features most have like lazy compilation but is still plenty fast for me.

It has some features other usually have not, like per page summaries, explicit inclusion of pages into blogs, TweetThis blocks, and non-Javascript social media buttons.

The older parts of my website are still running on Ikiwiki but I really like the simplicity where I know and understand all the code.

I haven’t had ads on my blog in over a decade. I’ve been meaning to remove the Facebook Page/Twitter widgets too when I get around to my redesign, since I’m pretty much giving both companies free information with them.

Roughly thousands of manhours of manual testing all over the world. Requires a few months and millions of dollars. Details vary depending on the customer.

For the developers there is continuous integration testing for each pull request done via x86 simulation and on target device. Code reviews for each pull request. Sometimes manual full system testing by developers but mostly by a special integration team.

I’m working for an automotive supplier so our processes are probably not applicable to you. The contrast might be interesting though. ;)

Also, stop with the flat and “clean” design. If there’s something your users are supposed to click on, make it look like something you can click on. Make links that look like links, buttons that look like buttons, etc. Even lobsters fails at this, there’s a menu at the top of the page but it doesn’t look anything like a menu, it’s just a horizontal line of gray words.

The takeaway here is: your job is to find solutions to problems

Nope! It’s not. It’s to make the client happy, both long- & short-term. Here we go again, reaching for the Technical Hammer when we have a People Problem.

Kingdomino is a really great game. It has an amazing depth for the short play time (15 min for experienced players). It is easy to learn, so it is fun for casual players as well.

My english blog with mostly technical content: http://beza1e1.tuxen.de/blog_en.html

My german blog with less technical content: http://beza1e1.tuxen.de/blog_de.html

Less than one post per month lately.

As someone who never used Rust I want to ask: does the section about crates imply that all third-party libraries are recompiled every time you rebuild the project?

KeePass has clients that work the 3 operation systems in question, and I’ve had good luck using Syncthing to share the password file between computers, but the encryption of the database means that any good sync utility can work with it.

In the industry, you can optimize througput over latency because you produce the same thing over and over again. But in software development, you usually develop something new. If the software you need already exists, you just use it. You need an agile process because you develop something new, and you cannot plan everything ahead of time. Some issues are discovered along the road. Because of this, I don’t think the latency versus throughput trade-off is really relevant here.

Maybe Frankenstein would have been a better name for the distro?

It’s from 2014, so part 2 will probably never come.

The big question is if they actually need to be saved.

A year ago I would have said no. Feed readers may not be as popular as Facebook, Twitter, etc. but sites have feeds and I can use them.

For large parts this is still true. Luckily lots of sites build on Wordpress, Drupal, etc and they come with feeds out of the box. Sometimes the author may not even know he provides a feed for me.

However, lately I have the feeling this is in decline. It seems a wix.com (yet another diy website ui) blog does not provide a feed by default. Some wordpress blogs lack the auto-discovery HTML header for the feed. Signs that supporting RSS/Atom is not that important for content producers anymore.

RSS was a great concept (and appropriate for its time), but was designed by people who didn’t comprehend XML namespaces, instead forcing implementations (both generators and readers) to escape XML and/or HTML tags, which requires multiple passes for generating and parsing feeds - with an intermediate encoding/decoding step (Really Simple?). They purportedly addressed this in RSS 2.0, but if you have a look at their RSS 2.0 example, they still got it wrong, persisting a 1990’s understanding of the web. Although I still use it, I shake my head in disappointment every time I see RSS source. RSS 2.0 should really have been based on something that could be validated, such as XHTML.

At this point, it is probably way too late for a comeback, as:

1. Social media platforms like Twitter are commonly used as a substitute and have a large hegemony over content.
2. Browsers have given up on RSS in favor of their own peculiar readers.
3. Google, Microsoft, Yandex and whatever Yahoo is now are pushing for an entirely different system based on extracting information from HTML content via an ever-changing pseudo-ontology that lacks definitions and is inconsistently employed by every practitioner.

You could read the above points as things that RSS should be able to overcome. If RSS were indeed to make a comeback, I would hope that in a new “RSS 3.0” incarnation it would satisfy the following criteria:

1. Standard comes before implementation (e.g., utilize existing standards).
2. Validatable (e.g., employ XML namespaces and utilize an XSD for document validation).
3. Human readable (i.e., subset of XHTML or HTML, that can be consistently rendered as in any modern web browser)
4. Strict specification (use a well-defined structure with a minimal tag set that prevents multiple interpretations of the specification).

I’ll admit, I do not like JSON one bit because it is antithetical to several, if not all of the above criteria. However, since a JSON alternative is desired, I would recommend that it be directly based on an XML/HTML version that does satisfy the above criteria. Then a simple XSL (read “standardized”) spreadsheet could be employed to generate the equivalent JSON version, satisfying both worlds.

Maybe my 6yo and me finally get around to try the ~50 years old Lego train my dad already played with.

I also have to build a nice box for my Raspberry Pi RFID player, but inspiration is missing so far.

I have been thinking similar thoughts since I read this article.

Why would you use WebAssembly? There are various similar technologies. For example, the JVM certainly has a more mature ecosystem.

Some have compared WebAssembly to Java applets; in some ways, they’re very right, but in some ways, they’re very wrong. Eventually I’ll write a post about the wrong

I’m waiting for that post.

There is one aspect where Ed maybe has an actual advantage: It keeps you in write mode and discourages editing. I will consider using Ed for journalling where I currently use vim.

I can agree with the reliability of Java, but is there a good framework. Having used Java-Play and Python-Django I would say that Django comes with more add better integrated batteries. For a startup, development speed is probably more important. Later you can add microservices in Java if you like.

I’d really like to write more D. In my particular case, I couldn’t have a GC in play (self-imposed memory constraints), but there’s a lot about it that’s attractive to me. I don’t have any desire to choose Go over it - power of the language is considerably greater from my limited experience.

That said, Go does have a big package community behind it like Rust.

Nice article. How do you feel about the size of the language? One thing that keeps me off from looking at rust seriously is the feeling that it’s more of a C++ replacement (kitchen & sink) vs a C replacement.

The Option example feels a bit dropped off too early, you started by showing an example that fails and then jumped to a different code snippet to show nicer compiler error messages without ever going back and showing how the error path is handled with the Option type.

You should also add Ada to the list of your languages to explore, you will be surprised how many of the things you found nice or interesting were already done in the past (nice compiler errors, infinite loop semantics, very rich type system, high level language yet with full bare metal control).