money might not be relevant to them
Hilarious.
money might not be relevant to them
Hilarious.
I doubt it. The cited precedent of .yu didn’t have a ton of big international commercial interest, but .io does.
They will absolutely find a rationale to change what io means when ISO retires io. The “laws” will be tweaked, ignored, or loopholed around.
It’s not the story in general, it’s the “but always a man” that’s objectionable.
If it weren’t for that “but always a man”, there would be no issue. Celebrating “but always a man” is the issue driving objections here.
That’s one hell of a strawman to invent and ascribe to folks who have no whiff of implying minorities shouldn’t receive representation.
No, they see further than that. Sometimes their restricted stock takes a whole year to be released!
Problem is for a company like Amazon, even if the brain drain will result in obviously inferior customer experience, it could take years before that happens and for it to be recognized and for the business results suffer for it. In the meantime, bigger margins and restricted stock matures and they can get their money now.
Particularly with business clients, like AWS customers, it will take a huge amount of obvious screwups before those clients are willing to undertake the active effort of leaving.
Also a sea of people looking to put in a respectable time at a recognizable employer to dress up their resume.
It’s real and it can suck.
Any time someone has one of the ‘big names’ on their resume, they get to skip the line and call the shots. Problem is in many of these cases, they got fired from those big companies for very blatantly obvious reasons once you work with them. They will tank their new projects, and executives will just say “this can’t be right, Google is such a success” yeah, because they fired that guy…
My relatively poor experience with Prime I attribute to deliberate bad choices rather than lack of workers. It probably doesn’t help to be sure, but even with the most awesome staff, I think Prime was going to suck no matter what. The whole economy is particularly “screw the customers over, get us money now, no need to attract or retain customers now”
You are going to give them ideas…
Ironically, reinstall the whole system, make sure to add some CrowdStrike, SolarWinds, and Ivanti for security and management though…
All well and good when ssh activity is anchored in a human doing interactive stuff, but not as helpful when there’s a lot of headless automation that has to get from point a to point b.
Problem they had was that ssh doesn’t really have any way to enforce details of how the client key manifests and behaves. They could ship out the authentication devices after the security team trusted the public key, but that was more than they would have been willing to deal with.
Rotating the passphrase in the key wouldn’t do any good anyway. If an attacker got a hold of your encrypted key to start guessing the passphrase, that instance of the key will never know that another copy has a passphrase change.
Meanwhile, my company has systems insisting on expiring ssh keys after 90 days…
This article is an example where statistical confidence doesn’t help. The model has lots of data so it likely has high confidence, but it didn’t have any understanding of the nature of the relation in the data.
I recently did an application where we indicated the confidence of the output of the model. For some scenarios, the high confidence output had even more mistakes than the low confidence output
As I said, I’ve dealt with logging where the variable length text was kept as plain text, with external metadata/index as binary. You have best of both worlds here. Plus it’s easier to have very predictable entry alignment, as the messy variable data is kept outside the binary file, and the binary file can have more fixed record sizes. You may have some duplicate data (e.g. the text file has a text version of a timestamp duplicated with the metadata binary timestamp), but overall not too bad.
I still have weird glitches where applications don’t seem to update on screen (chrome and firefox, both natively doing wayland).
Lack of any solution for programmatic geometry interaction. This one has been afflicted with ‘perfect is enemy of good’, as the X way of allowing manual coordinates be specified is seen as potentially too limiting (reconciling geometry with scaling, non-traditional displays), so they do nothing instead of proposing an alternative.
The different security choices also curtail functionality. Great, better security for input, uh oh, less flexibility in input solutions. The ‘share your screen’ was a mess for a long time (and might be for some others still). Good the share your screen has a better security model, but frustrating when it happened.
Inconsistent experience between Wayland implementations. Since Wayland is a reference rather than a singular server, Plasma, Gnome, and others can act a little different. Like one supporting server side decorations and another being so philosophically opposed to the concept that they refuse to cater to it. While a compositing window manager effectively owned much of the hard work even in X, the X behavior between compositors were fairly consistent.
I’ve been using Plasma as a Wayland compositor after many failed attempts, and it still has papercuts.
Thing is that they could have preserved the textual nature and had some sort of external metadata to facilitate the ‘fanciness’. I have worked in other logging systems that did that, with the ability to consume the plaintext logs in an ‘old fashioned’ way but a utility being able to do all the nice filtering, search, and special event marking that journalctl provides without compromising the existence of the plain text.
Uh… Sounds like it’s not really system’s fault, your setup is just terrible.
I don’t know his specific issue, but the general behavior of systemd going completely nuts when something is a bit ‘off’ in some fashion that is supremely confusing. Sure, there’s a ‘mistake’, but good luck figuring out what that mistake is. It’s just systemd code tends to be awfully picky in obscure ways.
Then when someone comes along with a change to tolerate or at least provide a more informative error when some “mistake” has been made is frequently met with “no, there’s no sane world where a user should be in that position, so we aren’t going to help them out of that” or “that application does not comply with standard X”, where X is some standard the application developer would have no reason to know exists, and is just something the systemd guys latched onto.
See the magical privilege escalation where a user beginning with a number got auto-privileges, and Pottering fought fixing it because “usernames should never begin with a number anyway”.
Because money means influence. Whether it’s the nation to benefit or the myriad of US tech companies that want it to stay, or other international interests, it’s way too much potential influence and I suspect cannot be ignored for some strict adherence to rules that no one really would care to defend.