Reading this article and discovering how Ramp team use Modal for sandboxed dev environment just saved us weeks of custom infra development and potentially months of headache, thanks you !
> From the developer standpoint, it's very nice to use, I just throw documents at it and it saves them. If I want an extra field, I just add it. If I want an index on something, also just add it. No big complicated schema migrations.
This sentence summarize all the issues developers working with Mongo will have: multiple version of documents living in the same DB and unpredictable structure
Best thing MongoDB have it's definitely their marketing (making everyone think it's amazing to invest hundreds of millions to deliver an "OK" tier database) and their customer support
Eh, not really. I've done both at considerable scale, and I don't hit these problems. Perhaps you need better developers? For sure, having your database enforce guardrails on what $thing should look like means your code can be lower quality, but you should pick the right tool for the job. For scenarios where I have one 'thing' that's not very relational, it works well. If your application dies because your $thing expects some field which isn't there, that's a you problem not a storage problem.
You joke. I still use an old winamp 2.81 on my windows machine.
About 15 years ago I came across some plugin dll files that added flac support.
The only issue I ever run into is some non ascii characters in ID3 tags make that file unplayable. But winamp is perfectly capable of editing them.
It's even pretty good in the high dpi monitors because Ctrl-D enables "Double size" mode on the main window and equaliser. And the playlist window has customisable font sizes.
After schema-less MongoDB, the nightmare of debugging microservices and over-engineered GraphQL, half-baked vector databases have become the new trends you want to avoid.
