72 karma · joined December 21, 2022
Modern C compilers/runtimes also have bounds checking (although I've never used it) like java if you want to use it.
Sure there's some improvement but it's not nearly as extreme as it's made out to be.
Some languages like Rust and Haskell do a little better by having the compiler keep track of most of them (if you use it right) but the consequence of misunderstanding them here is accidentally coding yourself into a corner which is extremely unpleasant.
There are other things people like to talk about like automatic memory management and package management and again I'm not convinced these really improve much. The pain of allocating memory in C means people often find ways to avoid doing it altogether which results in much more predictable behavior. Same with pulling in third party libraries. It's rare using more than a couple is actually beneficial but when the package manager is there the temptation is way too much for most people and the result is both unpleasant and very vulnerable to supply chain attacks.
I'm still not convinced any of this is the improvement people think it is.
I don't know what to tell you if you're going to assume the other side isn't arguing in good faith although I feel the same way about most of the anti-crypto people here.
Its ability to generate what are essentially highly specialized tutorials that match exactly your use cases is also a really big deal.
Overall it's really extended what I'm capable of doing. Not because I couldn't do the things before but because I can skip over the boring part in the beginning and save my emotional energy for the part that actually matters.
>do I basically have to describe an algorithm in English or can I go up to a higher level and talk about features and what the software ought to do?
It understands any "well known" algorithm, api, paradigm or pattern that was written about before 2022. Even pretty obscure stuff. One thing I tried was copy and pasting some of my code into it and having it generate unit tests.
The whole thing felt like a parody of itself.
1) People who shouldn't have been using crypto at all because they can't handle it.
2) People deliberately misusing other people's money who did actually know better.
I think a large amount of the stolen funds fall into the second category.
This is something you can't do with securities and it's why I'm not convinced regulators really need to be as closely involved.
IMO the problem with kiwi farms isn't that they're far Right. A far Left forum should (and probably would) face the same consequences if it behaved the same way; it's being abusive. Spammers get kicked off the internet for the same reason. Don't abuse the network and you'll be allowed to say pretty much whatever you want.
If you're not willing to spend the hour total of research required to use crypto safely then don't use it.
This is a limitation with Android and not a fundamental network/OS limitation. As long as your protocol allows for long enough keep alive latency you can periodically wake up for a short period and allow apps to service their connections (which is what I'd imagine this does anyway just with a singular app.) This works on Linux if you don't have the extra Android crap getting in the way.
It's kind of a bummer to see bad OS architecture feed into over-complicated protocol/application design.
EDIT: I guess I wasn't clear here. In my experiments I had the background wake up service wake the device up once and applications had just that singular window for all of them to service their connections. The problem with Android is instead applications either keep the phone from suspending entirely or (apparently) have some API allowing them to register their own periodic wake up that isn't shared.
EDIT2: I also want to be clear that this isn't a criticism of NTFY. The developers behind it deserve congratulations for solving a serious problem with FOSS Android apps. My complaint is that the poor architecture and unescisary inflexibility of Android made this such a complex problem in the first place.