Are those features client or protocol specific? My Lemmy client, connect, let's me block instances and has search for posts, communities, users, comments, etc.
Funny thing about ai is there isn't really a moat. Once an idea is out there it's easy to catch up, so don't be surprised to see the big players ahead now get caught up by competitors very quickly.
I think a lot of academic oop adds inheritance for the heck of it. Like they're more interested in creating a tree of life for programming than they are in creating a maintainable understandable program.
The super famous ones do but for every one of them there are thousands of poorly paid ones. What the studios are doing would remove the possibility of even becoming well paid in the future. These strikes are about helping the people not at the top, and about protecting their upward mobility.
I don't think any body for example would brush their teeth completely sub consciously, but when it becomes a habit I'd say it becomes the default choice rather than something you need to remember to go out of your way to do.
Wait, why? The reason the first father named him sue was because he abandoned him, so is the other version saying that they're also going to abandon them?
It depends on the project. A server used by thousand of users and companies? Super secure. A random library with barely any usage or engagement? I wouldn't trust it without reading the source first.
We did a full rewrite of our site years ago going from backbone to react and TS. We just did it page by page, clean sweep on each page, all new work done on a fresh slate with the old code base being abandoned page by page but otherwise left alone until all the pages were migrated at which point we could just completely drop the old code base. We're so much more productive now and happy working on the code base. Refactors are much easier than before as well.
I've worked on massive jQuery code bases before and they turn into worthless spaghetti code in no time at all. Dynamically altering html with no source of truth is the worst pattern you could have on a frontend. I have a ton of respect for what the jQuery library introduced but it was never a framework and was used in a terrible patchwork way. I wouldn't even bother trying to save any of it. Clean split and keep that codebase tightly quarantined behind lock and key and don't let it even touch the new code base. The spaghetti code it creates is like a virus.
I've always said JavaScript was an elegant language with a horrible implementation. Now that we have typescript and modern ecmascript standards I feel vindicated.
The prototype system is a bit confusing despite being simple, but it's very powerful despite being simple, which I think balances it out. Also using modern classes abstracts the more confusing bits and you very very rarely need to actually understand the underlying mechanics if ever anymore. Plus you rarely even need classes either with the first class functions.
Parallelism could really improve. Don't think I'd want to mess with shared memory, but I'd like to be able to pass actual in memory objects instead of having to serialize everything first. Maybe a child process sandbox that can be filled and relinquished once or something like that?
He specifically called out Ashkenazi Jews and Chinese. Cultures that cares a lot about health and community and most the Asian countries already masked way before COVID.
Text is basically free to host, especially text that you can index on a primary key like an account id. The only reason to do this is to reduce dev maintenance costs, but they're not achieving that by cutting back on the storage time
Is there a sci Fi world where that ancient civilization is just the current modern day?