YMMV, I think I only tried to sign up on 3 websites where it was not working. You can fallback to the original email address in those case.
The funniest part was that for one it work great for the signup part, but they used a third party tool for licences that broke because of my e-mail.
For another, only the js code was verifying the e-mail, and I could push it by removing the validation. When the owner had to validate my account, they got a message that the e-mail was incorrect when they tried to submit the form. They called me and had a great discussion about web apps security. We had a good time.
I would point out that it kind of prevents you from checking if your email is in a leak database as you need to test each aliases you used.
YMMV, I have 2 headsets I've never been able to make working reliably under windows 10 and 11. Cheap stuff, but they are are flawless under linux and with my phone on android.
Not to say there are no issue on Linux, but these days it's way better than 15 years ago.
Oled pc screens have a terrible reputation for text. Some more than others, but it seems it's better to stick to lcd if you happen to read or write a lot.
Interesting, my path is a bit like the opposite. I tend to avoid categories of tools that abstract too much the problem in a "magic" way for the same reason: you can't easily understand what's going on behind the scene, and you have to dive in each time you enter a corner case. If you can't control what it is doing on each step, then you can't be sure it will be doing what you expect and this can become a mental effort that outweight the tool benefits.
True; in the same vain, tools that have more implicit and declarative philosophy - React, Kubernetes, most ORMs, Spring Boot - are also harder to understand and reason about for the same cause - you have to know exactly how the given tool works (new abstraction, magic) to understand what might happen at runtime.
We replace verbosity - since these tools are usually way more expressive than the thing they abstract away - with a new abstraction layer that allows us to type much less stuff but at the same time introduces a completely new cognitive complexity layer.
As always; sometimes they give more than they take, sometimes not ;)
In case you weren't attempting to make a point through irony, GP appears to be using "F5" informally as shorthand for "instruct your IDE to attempt to build and run the code". Presumably, that kind of documentation wouldn't normally literally say "F5" there unless a specific IDE had already been prescribed. The point was simply that the user shouldn't be required to do anything manual to set up the code, when starting from scratch, except perhaps to authorize the automated setup procedure.
Exactly. And honestly- the screen is way way more than 1watt. According to RAPL power, a USB-PD power analyzer- changing the brightness on my 15" 4k OLED laptop screen can reduce power usage by 15-20W. The nature of OLED makes it hard to get a clear picture.
The funniest part was that for one it work great for the signup part, but they used a third party tool for licences that broke because of my e-mail. For another, only the js code was verifying the e-mail, and I could push it by removing the validation. When the owner had to validate my account, they got a message that the e-mail was incorrect when they tried to submit the form. They called me and had a great discussion about web apps security. We had a good time.
I would point out that it kind of prevents you from checking if your email is in a leak database as you need to test each aliases you used.