0x3444ac53

Yeah TUIs are great. I'm shit at making GUIs but I was able to slap together a relatively simple TUI for some tooling at work, without any AI. Cheaper, faster, cross platform, less intensive. Most TUI frameworks nowadays have mouse support as well etc. So what if it looks just a little dated?

So, I've had a pretty shit time with Microsoft products over the last ten years, but it wasn't quite as bad 5-7 years ago. Our disagreement on that might be that I'm only in my late 20s, so if you're older than I am, or had newer consoles than I had around that time, I might be a little more tolerant of jank.

But according to the other replies, it seems Microsoft has been purging QA for years now.

Yeah based on your comment and the others, it seems he did an initial purge in 2014.

QA doesn't get enough love :(

Thank you for the correction! I think I was conflating the two (having heard about the one from 2014, and then also hearing about the more recent rounds, and not recognizing they were different)

I've edited my comment to correct this. Cheers!

Oh thanks for the correction/supplemental information. The gutting you're referring to might be the huge lay offs that I'm thinking of. Possibly conflating the recent AI driven layoffs with those from 12 years ago.

The bad part is that Microsoft (generally) used to have some of the best QA in the industry, and that was somewhat extended to Xbox. But they laid off their QA team a year or two ago because "AI will change everything!"

Yeah at the time it was bad. Now, it's a pretty nice codebase

Bedrock does have better performance but it is also hella buggy and unstable.

In Microsoft's defense at the time the java code base had a ton of technical debt and overtime they've essentially done a full rewrite of everything.

That said, I'm convinced that 90% of the reason that the current mess exists is because Microsoft was convinced that most users would be migrating from Java to bedrock. And they probably would have (modding and other things aside), had the Microsoft team not decided to "fix" many aspects of redstone.

Since then there's been the constant issue of parity between the two versions, which will likely never be achieved. And 90% of the time it's because the Microsoft developers working on bedrock edition decide they know better than mojang does, so they can implement a feature in a different way, or just implement a new feature entirely.

Ugh it's a mess, and I've spent way too long thinking about it.

Thank you for the recommendation! I opened it out of curiosity and I'm already a chapter deep :)

Correct.

I've never been more thoroughly convinced that I would like ruby more than from this article. I'm currently stuck reaching for python a lot of the time (absolutely love it tbc), but maybe it's worth changing things up and trying to give ruby a shot.

It was one of the first programming languages I was introduced to at 16 or so, but an older person that I looked up to told me it would get me stuck in "hobby coder land". He was wrong in so many ways, but even if he was right, I wanna have fun in my hobby code :)

Hi, out of curiosity is there a way to persistently set the `--native-tls` flag? UV always fails without it because of Zscalar configurations at my day job.

Also, is there any plan to add support for specifying that a compatible python version for a specific architecture? One of the packages I maintain at work has to use 32 bit python, and I always have to pass the `--python /path/to/32bit`

For what it's worth, anytime I have written a macro it's usually not because it's needed, but just because I think it'll be fun :)