I haven’t booted up an editor in a long time but I’ve written lots of software recently (mostly with codex).

Interesting times…

Can’t wait for the sequel:

Bodega Rats of New York

The progress on computer use / OS world is nuts.

14.9% a year and a half ago and now 72.5%

forgot how much fun this game is. really takes me back

I’m a big fan of Django and Go as well but the only thing in the Go ecosystem that I’ve found that comes close is beego: https://github.com/beego/beego

But it still needs to mature quite a bit before I’d be comfortable saying it’s anywhere near Django or Rails

There’s also https://www.goravel.dev/

I found Pagoda required me to juggle too many things that were only loosely coupled together.

GoBuffalo was great but as soon as I started using, it got archived :’)

Now I default to beego. It isn’t as batteries included as a rails or django app, but there’s enough there that I don’t have to write as much boilerplate as with only the stdlib.

The best thing I’ve found is beego: https://github.com/beego/beego

Not affiliated in any way, but to me it’s better than most of the alternatives

This is the most thorough resource I’ve found: https://www.scratchapixel.com/

Though admittedly it is a bit chaotically organized.

That one combined with the ray tracing in 1 weekend series is a good start.

ScratchPixel's articles are some of the best mathmatical breakdowns of rendering I've seen all these years, along with perfect diagrams, charts, and formula noations. Defiitely worth its weight in gold if you approach topics from a logics/proof standpoint.

But man, I feel I was waiting for that path tracing article for 8 years now? It's not even on their recent roadmap. Treat the unreleased sections as wishlists instead of a "upcoming" section.

>Though admittedly it is a bit chaotically organized.

looks like they completely revamped the website (and their roadmap seemed focused on revamping existing articles over making new ones). The beginners section now seems to make enough sense if you were following a college raytracing course. The other sporadic articles are pushed farther down to prevent confusion.

I like this too. I even found a mistake and the authors were open to correcting it which is always a good sign

agreed. It's interesting that Go has a lot of the ground work set up (built-in prod server, etc.) but no framework has really taken off. And the dev productivity when compared to something like Django is painfully slow...

The most succinct and intuitive explanation I’ve found on PID is this one: https://www.youtube.com/watch?v=4Y7zG48uHRo

Just watched, and yes this is a very good explanation. My intro to PID controllers was when writing AI vehicle steering for video games. I wasn’t taught about PID controllers in my CS degrees, so I started naively with what I would later learn is a P controller, and then got really surprised when lowering the gain turned into larger error. Like trying to smooth out the steering makes the problem worse, it was surprising to me. I told a very smart guy near me what I’d learned and he was like, “Oh yeah, you just need a PID controller”.

I used to design PID process controllers in industry. In watching this vid I realized one reason that designing a self-driving car is so difficult. Toward the end, in the process control diagram, he has [Vehicle] as the controlled process. This reminds me of the old math joke about "assume a spherical cow". The difficulty with a self-driving car is that it isn't just the vehicle that has to be controlled but [Vehicle + Current Road] so the controlled process is not just difficult to model but that it is changing all the time and sometimes rapidly.