av8avenger

You're right here, they won't be able to charge you automatically via the credit card, but you're still legally obligated to pay for the subscription since you have agreed to the terms of service during sign up. Depending on the action that they would take, you could easily end up paying a higher amount than the original subscription price if they put additional charges on you...

The provided i18n library is really good, but it lacks tooling around it (like proper extraction of keys, meanings, descriptions, etc..).

Unit testing works flawlessly out of the box with Karma and live reloading, E2E needs a bit of setup, especially if you want to go with Cypress instead of Protractor.

For most use cases its ready to use and for everything else there will almost always be some articles on how to achieve it (i.e. E2E with Cypress).

This was actually my first thought even before continuing reading what they do.

I think they‘ll hear from lawyers sooner than later, if this gathers more attention…

Something that is currently being used (sort of widely) is X509 OCSP. As the Cert gets signed, the CA also embeds an OCSP URL which clients can later use on the fly to determine if a cert is revoked.

In case of a leaked private key where the actual PKI wasn't breached, they still have authority over the CA itself and can therefore determine which certs are valid and which are fake.

This retains validity of the known issued certificates, but invalidates fraudulently issued certificates. The downside is that its an optional check and that every client needs an online connection in order to validate the cert.

Anyway, the COVID certificates don't seem to be actual X.509 certificates and are rather just a signed message, so this isn't something that could be utilized right now.

I didn't include all devs. Of course a "normal" developer doesn't make this much. As a lead developer you earn a lot of money here.

I know a couple of senior (non lead) developers who earn this much.

Lol sure. If you get this kind of responsibility anywhere in western Europe in a professional setting, you are getting paid definitely somewhere in that salary region.

The effective amount will of course differ greatly between the countries, but please don't forget that the expenses vary as well. (15k a month in Switzerland isn't as much as 15k a month in Germany)

Totally agree with you. I use my MBP mostly on native resolution if my screen gets really crowded and on the other hand it's nice when you're doing creative work and can switch to a downscaled image with so much more "smoothness" and details. I like the specs of this Pangolin notebook, but as soon as i saw 1080p i was gone.

Are there actually any devs out there that are really offended and feel excluded or worse than others because the default git branch is called master?

I work in a fairly small company, but if i think of all the things we'd have to change in our infrastructure to exclude all of those offending words (like Black- and White-Lists), we'd probably be busy for a couple of weeks.

Personally i do not care about the change in the default name of the main / master branch in git.

But i totally agree with you on the point that we should be able to differentiate such terms from their meaning in another context. I see how this can offend people but honestly the only thing we'll ever be able to do is change the labels on such things. We're assuming so many of those words to be a defacto standard in IT that they won't die anytime soon.

Switzerland's down too. It works if you access it without session though.