4 ms·
People are really going to be cranking out entire databases in a weekend that no one is going to use. Why even make the effort, if you can even call it that? It
by jhhh 2mo ago
People are really going to be cranking out entire databases in a weekend that no one is going to use. Why even make the effort, if you can even call it that? It would be one thing if the software was actually beneficial, as it would be undeniably useful and the fact that it took a weekend to make is of no importance. But databases are extremely complicated and require high levels of trust since they actually store important information. No one would care if you made a terrible AI-generated winamp clone that couldn't play music correctly. There's no consequence. But who would use and trust a database if the author didn't even understand it enough to make it? If you made this 5 years ago I would probably be interested and looking through some of the code. These days weekend projects aren't even worth a second thought.
- SamInTheShell 2mo agoI did. Distributed too and supports erasure coding. The reason is because nothing quite had the architecture or features I wanted in a deployment pattern that matched my use case. All major databases that are validated are complicated to operate. I built something that operates one way for a non business use. It’s great, doesn’t need to serve a million people, just about 5 or so. Doesn’t need to be the most optimized thing ever. I’m opting out of any corporate targeted code for personal use, anything not designed for user experience gets scrapped when I’m the user and I have Software on Demand as a Service.