^ This link worked yesterday when Ycombinator cited them. Now it doesn't work. Who at Microcad is scared right now? Or does this removal regard perhaps a more common situation -- such as their code wouldn't compile with microcad and so they had to pull it, rewrite it, and will publish Spirograph later?
Hey, microcad dev here. We are definitely not scared, just a bit overwhelmed by the amount of good and constructive feedback. The new link is here: https://microcad.xyz/spirograph/
Oh yes, it /is/ the f!@#ing hardware. The core FreeBSD developers have taken their sweet time to add support for WiFi on anything IoT running FreeBSD. In other words — FreeBSD's core developers usually will not listen to users asking for such things unless maximum pressure gets applied in every separate instance. Disclaimer: I'm not a FreeBSD user. Apart from the halfway decent distros which use FreeBSD as their core OS, the FreeBSD developers in charge of FreeBSD itself will not add a GUI installer for some old school reason that really, only they would know of. One issue coming directly from this constraint is that if you run BSD through a VM — either on Linux or Windows it is rather difficult if not impossible to get past 1024 x 768 resolution without going through some major hoops. FreeBSD does not do a thorough job supporting VirtualBox instances, generally speaking. BSD is meant more for the back-end "bare metal" servers.
Granted, mostly hobbyists are the ones who have Raspberry Pi's, and those devices have become more expensive since COVID.
It is really bizarre that the FreeBSD org has not written WiFi drivers for the Broadcom chipsets in RPi 3/4. They're still Ethernet-only in terms of networking. The FreeBSD dev community seems to be ignoring the RPI community. WiFi is pretty common these days. Is this happening because BSD is largely aimed at the industrial server market?
What's up with that, Microcad? This kind of reflects poorly on your overall ability to do things like host the actual code for microcad itself.