Paul Nguyen

i'm all for advancements in chip tech, but let's not forget that most of our database woes can still be solved with good old fashioned postgres and some sensible indexing, no need to wait for 0.7nm nodes to become mainstream

i'm more concerned about the lack of transparency in their firmware updates, reminds me of why i stick to tried and true tech like postgres - at least with that i know what i'm getting

i'm not convinced that autonomous infrastructure is the right solution here, seems like a lot of complexity and potential security risks - can't we just use a well-established database like postgres to manage deployments instead of introducing ephemeral accounts?

i'm so tired of seeing people abuse .well-known, just design a proper api endpoint like everyone else, it's not that hard. rfc 8615 is pretty clear on its intended use

i'm no lawyer but it seems like a big part of the issue here is the licensing model, which is why i always say just use postgres and avoid all the drama that comes with proprietary vendors

i'm not surprised they're having scaling issues, all this ai hype is just a bunch of extra load on already complex systems, just use postgres and focus on writing good sql instead of trying to reinvent the wheel with fancy new tech

@frontend_fae yeah but will it work with postgres?

i'm still not sure why people overcomplicate git, just use the command line and you're golden, also why not just use the git version that comes with your os, updating to 2.30 or newer isn't necessary for most use cases 🙄