wscott

The dedicated user isn't really required; it just expects that /home/linuxbrew/.linuxbrew exists. That can just be a symlink to your home directory. But yes, creating that symlink requires root on most systems. Brew itself doesn't require root or that pathname; you can put packages anywhere, but then many will have to be built from scratch since the pre-built packages don't work. And you need bubblewrap installed (which requires root) to use the sandbox, but again that is optional.

All that said, when you are running without a sandbox installing to a nonstandard location, not everything works consistently. I run this mode all the time. But it has been getting better.

You can hear the engineer in that second question. They hear a wild statistic pulled out of someone's ass and ask what is that sticking to the side?

That is normal on his blog. He is a brand that he has developed over many years, and he is constantly promoting that brand.

Yes, he has done a lot of good work in the past, but he has put as much effort into self-promotion and landed a series of interesting and well-paying gigs.

I can't blame him for that. It just makes me tired to watch.

The funny part is that the Tesla doesn't have a basic dumb cruise control. It only has "traffic-aware" cruise control which uses the cameras and doesn't use the new FSD code so it has lots of glitches and phantom braking and decides for itself what speed to use. My wife just wants to set the speed and have the car go that speed.

This kind of work is really valuable and much needed. There is also often a surprising amount of friction to making contributions to open source projects. This article did a good job and highlighting some of those difficulties and friction. But improvements to the official documentation is so much better than standalone blog posts to explain confusing concepts.

So, thank you Julia & Marie for persevering and making a solid contribution.

Dataview can generate all of the data from Bases (and a whole lot more), but Bases is a lot easier to use as you can build queries in the GUI and the data comes out in nicely formatted table where you can edit the fields directly in the table rather than needing to load each data item one by one to make changes.

And still after using and making changes in the GUI the query is stored in a nicely formatted and editable YAML file.

Very small town in the midwest. The US is a big place and this is just one possible look.

The important thing to understand about why AVX512 is a big deal is not the width. AVX512 adds new instructions and new instruction encodings. They doubled the number of registers (16->32), and added mask registers that allow you to remove special cases at the end of loops when the array is not a multiple of the vector width. And there is piles for new permutation operations and integer operations that allow it to be useful in more cases.

The part Intel struggles with is that in many places if they had the 256-bit max width but all the new operations then they could build a machine that is faster than the 512-bit version. (assuming the same code was written for both vector widths) The reason is the ALUs could be faster and you could have more of them.

I was pleased to read such positive contagious excitement and someone who can still see the wonder of the American west. And excitement of trying new experiences.