That’s a very uncharitable interpretation of what they wrote, and goes outside of how what they wrote is supposed to be interpreted.
The researchers are not claiming that cognitive ability changes would definitely take longer than 21 days to appear, they’re suggesting that that is the next thing to test.
Computer vision based SLAM definitely has use cases and you can definitely make money applying it at the right companies to the right set of problems. Building a whole career around a single technique, any technique, probably is probably not gonna work. You need to be broader than that.
I’ve worked on plenty of problems where all you need is to find what pixels are a specific color. While I’m sure a NN could be setup for that, why make things harder than they have to be?
I’ve found C# pleasant to write in, and I get a bad feeling every time I deal with npm. On the other hand the library support for React is just so much better so I put up with it.
EDIT: I’m not a web dev, the web is just the most consistent UI platform for supporting mobile and some desktop we have now so that definitely influences my opinion.
I looked before I started using Let’s Encrypt for some internal stuff and there really isn’t a way to use name constraints in a practical way with modern web browsers at this point. If you’re not using a browser, things get a lot easier, but for browsers you sort of got to suck up that you can’t really avoid the “big” internet.
To pick on the game of Go as an example, the insight from the Bitter Lesson is the best method to use for Go is probably going to be the most broad method that abuses the magic of brute force the most, compared to a method that really encodes the best existing strategies of Go.
I think what OP is referring to and what I’ve observed is that in some fields you have to have a certain amount of expertise to just understand the rules of the game, and there are a lot of applications where someone approaching a problem with the goal of applying ML can’t quite get over the hump of understanding all the rules.
You could get a C++ job. One of the issues with C++ is most people using it for anything useful only need to know some particular subset, only actually know that subset, and then get bit when the subset they know changes.
Forgejo currently is only applying branding changes and currently plans on being a soft fork. I think it’s existence is a good thing for the ecosystem (if Gitea the Company did something wonky, there will be an organized group already doing releases ready to go), but I’m not sure there is a huge benefit in running it, at this juncture.
“ Wow is the web a weird application delivery mechanism where people are writing applications and then essentially compiling them down to binaries using WebAssembly, but weirdly shoehorning it into a hypertext framework”
I thought this was an interesting quote from the article that relates back to something I’ve been thinking about as I’ve started to look at writing apps that run any where and realized that forces you into writing a web app, but web apps kind of suck because at the end of the day you’re really writing a website not an app…
I wonder if you could at this point reinvent the browser so it was specialized for web apps not sites, and what that would even look like.
This. Google’s policy is kind of dumb (I write a lot of stuff for fun that no one wants the ownership of… The primary value is I learned something that I can use later on something important),but pretty much any experimental thing some one at Google works on will wind up there even on their free time.
Podman implemented Dockers REST API as part of either the Podman 3 or 4 release (whichever one is in Debian stable), and I’ve been able to use docker-compose with it since then.
Podman has fairly good support for k8s deployment configurations, which I’ve used as well, if you’re a k8s shop, but I understand there are a lot of places that have standardized on compose for development.
I’m pro open source and run gitea at home, but looking at their issue list and pull requests it doesn’t really come off as a mature open source project that I’d want to run my company from, when down time at the wrong time can get really expensive.
You’re “backend” isn’t JavaScript.