I just started a plain typescript project, and was too lazy for a docker setup so I just installed Node with apt and went on my way.
I installed Typescript, that went fine, but when trying to use it it gave a vague error.
Quick search fixed it, but... I'm amazed by the cause: Typescript didn't support the version of Node I had installed, which sure.. That's okay. But why didn't NPM tell me this? NPM does not have node version constraints?!?
@lukasrotermund@jaapio For me I've hit that trap when I've tried to 'composer update' an entire large project at once. Now I start with my least important dependencies first then work my way up to the framework itself.
@syntaxseed yes that's my strategy as well, I rarely use composer update. I use composer require to bump versions because that will give me the latest possible version.
@captainepoch There's a big difference between supporting v3 and phasing out v2. Firefox already supports Manifest v3.
Mozilla's implementation is not restricting adblockers in the way Chrome does.
Criticizing Firefox here is also something I just don't understand. The only thing it will do is making Chrome users doubt and not move away. It's time to move to protect the web.
Some of you know, I'm learning to control a windmill.
Have some pictures of the brake of a windmill.
Pulling the rope slightly and then letting go of it slowly will drop the beam, which will move the beam so the circular beam around the rotating wheel gets tightened.
@thomastospace usually you hire someone who is going to perform the pentests. In that case, you just wait for a report and address the issues they will point out.
If you're the author of the pentested application, it makes no sense to be also the one who will do the pentesting. The best results are when someone else makes those.
@thomastospace I'm really new to this, but I'm using both Onshape and TinkerCAD. Onshape is nice for precision and how my brain thinks by default. TinkerCAD is fun for experimentation and playing. Some serious design, too.