Nice project!

Did you know that instead of buying new motor controllers, you can re-use the hoverboard motor controller? Awesome people have made open source firmware you can flash to it: https://github.com/EFeru/hoverboard-firmware-hack-FOC. With this firmware you can make the motors go way faster, up to 40km/h with a 12S battery.

We are also building a kart with hoverboard motors, with a custom welded steel frame. Vibrations are a real issue with the standard solid rubber wheels, hopefully I can find the same air tires you used!

Our website is in Dutch, but you can watch the videos: https://projects.raphson.nl/projects/kart/

Even with all the drama Firefox is still an excellent browser, definitely better for privacy and uBlock than Chrome.

uBlock origin is so much better than just DNS-level blocking can ever be

AdGuard also has a browser extension for blocking inline ads. The combo of AdGuard extension + DNS blocking is good enough that I haven't missed uBlock Origin

It is much more effort than sending a data request to a cloud provider, and it can't be done without you knowing.

But I can install it on any Linux system from the base repository

If all your targets are .PHONY, you might as well just as bash (or your favourite shell) directly.

Make targets look suspiciously like functions (or procedures), but they actually aren't.

I don't typically use .PHONY as my targets aren't the same name as files and performance isn't an issue.

Here is an example of a "complex" Makefile I use to help manage Helm deployments (https://github.com/peterwwillis/devops-infrastructure/blob/m...). It uses canned recipes, functions (for loops), default targets, it includes targets and variables from other Makefiles, conditionally crafts argument lists, and more. (It's intended to be a "default" Makefile that is overridden by an additional Makefile.inc file)

I could absolutely rewrite that in a shell script, but I would need to add a ton of additional code to match the existing functionality. Lines of code (and complexity) correlates to bugs, so fewer lines of code = less bugs, so it's easier to maintain, even considering the Make-specific knowledge required.

They say "use the best tool for the job". As far as I've found, for a job like that, Make fits the best. If some day somebody completely re-writes all the functionality of Make in a less-obnoxious way, I'll use that.

> I don't typically use .PHONY as my targets aren't the same name as files and performance isn't an issue.

They are still phony at heart in this case, even if you don't declare them .PHONY.

Make really wants to produce files; if your targets don't produce the files they are named for you are going to run into trouble (or have to be rather careful to avoid the sharp edges).

> They say "use the best tool for the job". As far as I've found, for a job like that, Make fits the best. If some day somebody completely re-writes all the functionality of Make in a less-obnoxious way, I'll use that.

You could try eg Shake (https://shakebuild.com/), but it requires some Haskell.

One of the benefits of just -- it isn't a build system, it's a command runner.

Good facilities for arguments, builtins like absolute locations -- there are a ton of benefits (see the README).

this is a good service for those who cannot use yt-dlp on the command line. However I am turned off by the AI generated images, they are very odd and have nothing to do with the website. Also some of the text reads like AI marketing speak

It's a "security nightmare" because clients can make holes in your firewall. If you're fine with that, then it's okay.

I think Chris's wiki counts as well: https://utcc.utoronto.ca/~cks/space/blog/

It opens a directory picker, which then says for some directories that you can't use them and must create a more specific directory.