FranGro78

AMD did enter into an agreement to buy Taalas, which is speculated [1] will be used to augment their Helios offering.

1. https://www.youtube.com/watch?v=3MKRjt59hh4&pp=0gcJCRMMAYcqI...

Perhaps it would make you feel a little better to learn that RDP was created from Citrix’s ICA protocol during some cross licensing between the two companies.

I worked on using hardware acceleration to replace parts of the ICA client application’s raster functionality for “thin client” devices a lifetime ago.

I’ve also run into problems with tools that aren’t worktree aware so often that I’ve stopped using it.

I’ve been using jujutsu for about 6 months now, and the only time I’ve reached back for git was when I had to rebase and amend someone else’s branch to get it merged (when they weren’t available to do so themselves of course).

Switching between changes in jujutsu has been a pleasant experience for me thus far, although I’m not as good with it as I was with stacked-git to keep local only changes (things I’m hacking to match my workflow / local setup) out of change sets.

The way it displays diffs is also still something I am getting used to, and have made plenty of mistakes when pulling in changes from trunk. That’s probably more of a case of “old dog new tricks” than jujutsu.

Perhaps like myself, there are many people outside of the US who haven’t bothered with trying to claim?

My exposure was pretty small, definitely not enough to justify trying to figure out this whole process would work in my case.

So you’re saying that the more popular a game is, the more likely it is to be pirated?

Sounds like it has more like the desirability of the game driving piracy than the other way around.

If you find the “infrastructure from code” idea intriguing, then maybe take a look at https://www.winglang.io

It’s a new startup by an ex-engineer on the AWS CDK team.

That would be “Fleet” (https://www.jetbrains.com/fleet/)., which is still in early preview.

I tried it out 3 or 4 months ago, and I didn’t find it useful, nor familiar - kind of feels like a VSCode wannabe.

It was disappointing to see, as I am really tired of running multiple IDEs to work on mixed language projects.

Sounds like building something simple that aids in tracking “coverage” of reviewing ToSs could be useful to increase that the odds of spotting something untoward?

Iirc there was (is?) a site which gives a rating to the various license agreements of popular services and the like, so maybe it’s a solved problem?

Do you suppose the elastic block stores of the public cloud providers operate in a non polling manner?

The incredibly low level of latency and high levels of iops preclude having it be based on software interrupts, I think even in scenarios where sr-iov is available to the hyper visor.

Definitely not a concern for “most” folks, but I’ve seen sharding used to separate users into smaller pools which do not have shared fate wrt infra and deployments.

As an extra benefit these pools do not push the limits of vertical scaling to which makes them both easier and cheaper to test under high load conditions.

This is where Alexa has the edge, if you whisper to it, it whispers back (or at least responds at a low volume).

Trying to get it to answer random search type questions is a disappointment, ending mostly with quoting some page.

I wonder when the ChatGPT skills for it will land (assuming they haven’t already).

Progress in the technology landscape, which makes previously impossible ideas barely possible, sounds like just the thing wardley maps are good for.

Any suggestions for resources to get an understanding of the mathematics etc behind cryptography in general, and the ZK space?

I’ve been trying unsuccessfully to get buy in on config as code.

Instead we have property / yaml files, read into anaemic “classes” which do not perform validation themselves. Validation duties are also foisted onto other parts of the system.

Stacked onto that we sometimes have file name based convention for defining a hierarchy of configs, to save on repetition between environments.

That’s correct, the multi year project was known internally as MAWS - Move to AWS.

Same reason as every other time such a post has elicited such a “this is a PR stunt by GitHub” comment.