330 karma · joined July 8, 2023
this actually makes a lot of sense lowkey, thanks :)
it's suspicious, but at the same time, iirc, nobody's been able to find a vulnerability in their encryption protocol :shrug
is it a honeypot? also did ovh change prices recently? I remember checking a couple years ago and it was more expensive vs hetzner
if you don't modify your library, app, OS, etc for 2 years, it's perceived as abandoned or obsolete, meaning even if you're achieved perfection in your product in terms of ui, you can't stay there, you must move forward and break it (i'm not talking about bugs or security vulnerabilities here, only the functionality itself)
prominent example is w/ microsoft word, where they kept adding an absurd number of features simply bc they felt like they had to, since ppl were paying for it, and this will KEEP HAPPENING TO EVERYONE so long as the software keeps moving at breakneck speed and backwards compatibility and stability are thrown out of the window...
like, you learn to work around this, mostly by just using raycast, but it's just unacceptable that they've spent BILLIONS on useless ai shit, while stuff THAT HAS WORKED CORRECTLY ALREADY IN THE PAST gets broken and goes unfixed for literal years
where? single header is just a way to package software, it has no relation to features, security or anything such...
C has macros, which is the ultimate form of hidden control flow, where a symbol can expand to any arbitrary code... also hidden allocations and functions that can error, which you could argue isn't traditionally understood as hidden control flow, but it's still nice to know when stuff is allocated and/or can create an error
you somehow managed to be perfectly unhelpful, condescending and insecure at the same time?
[1]https://www.uscis.gov/sites/default/files/document/reports/o...
i like how zig does this, and the creator of odin has a whole talk where he basically uses the same arguments as my original comment to reason why odin doesn't have a package manager
my mistake :)
like the entire point of my comment is that people have misguided criteria for evaluating build systems, and your comment seems to just affirm this?
the difficulty of including a dependency should be proportional to the risk you're taking on, meaning it shouldn't be as difficult as it in, say, C where every other library is continually reinventing the same 5 utilities, but also not as easy as it is with npm or cargo, because you get insane dependency clutter, and all the related issues like security, build times, etc
how good a build system isn't equivalent of how easy it is include a dependency, while modern languages should have a consistent build system, but having a centralised package repository that anyone freely pull to/from, and having those dependencies freely take on any number of other dependencies is a bad way to handle dependencies