Andrew Marcuse

When I saw [Every UUID](https://everyuuid.com/), I immediately thought about how this could work for other datasets.

I originally wrote [RSS.Style](https://www.rss.style/) using XSLT, but Google, as the malevolent friend of the open web, is deprecating XSLT ([flamewar on Hacker News](https://news.ycombinator.com/item?

I used the [Tabulator](https://tabulator.info/) JavaScript library for a recent project at work, and was blown away by how flexible and easy to use it is.

I recently started work at a company([Fiserv](https://www.fiserv.com/)) that has quarterly Hack Weeks where you can work on anything you want.

While working on [RSS Style](https://www.rss.style/), I discovered that a lot of RSS/Atom feeds in the wild are (cough) sub-optimal.

I am thinking of using [Material UI](https://mui.com/material-ui/) for a future project and wanted to try it out in an actual project, so I built a sitemap viewer that reads a `sitemap.xml` file (and any linked files) and displays them in an outline.

As part of [RegexPlanet](https://www.regexplanet.com/), I have implemented the same basic functionality (a straightforward [JSON API](https://github.com/regexplanet/regexplanet-next/blob/main/CONTRIBUTING.md#backend-api)) with multiple technologies.

This is a review of available logo APIs.

One of the things that (IMHO) is hindering RSS/Atom is poor discoverability.

Are you losing track of all the repos you have?

I saw a snippet in the Bun docs that [benchmarked a minimal Node.js webserver](https://bun.sh/docs/api/http#benchmarks), and thought it would be interesting to see how it would work with something a little bigger than "Hello World".

I know it is a little late to be joining the party, but I am starting a blog.