Comment by KronisLV

I kinda like the idea, decreasing the friction of doing things yourself to near 0.

I recently migrated from my YOURLS install to just having an Apache2 config with some scripts to append to it: https://blog.kronis.dev/blog/sometimes-dropbox-is-just-ftp-b...

Sometimes you don't need "serious" bullshit like Spring Boot either but something more minimalist is more than enough. Though I think it can only work well when you have enough usable primitives, e.g. I've written software in Go that has minimal dependencies and it only worked so well thanks to both the language being relatively simple AND also having a really strong standard library.

The moment when someone tries to write a web server from scratch in a collaborative environment (e.g. project at work with deadlines), I'm peacing the fuck out of there. And in my experience, trying to make design systems or frameworks from scratch leads to a pretty bad mess, because people miss all sorts of inherent complexity until it comes around to bite them later.

I guess what I'm saying is that there's quite the difference between what you do for your own projects, vs what is most likely to lead to long term success in a group setting, especially in 1-2 pizza teams - evaluate the benefits vs risks when considering using vs building.

I'm also a bit blind to this when it comes to certain things, look at this funny video: https://www.youtube.com/watch?v=40SnEd1RWUU I would still prefer to use self-hostable software so I know more of the stack and have control and possibly some cost savings vs someone who'd just fork over a bunch of cash to a SaaS / PaaS vendor.