It's one thing to try to steer basic, non-technical users toward an MS account by default. Fine; I may not like that, but I get it. But at this point, anyone left who's still using these methods to create a local account is likely to be a technical user who's deliberately and intentionally wanting a stay on local account for whatever their own reasons.
I suspect that's a rather small group, which leaves me puzzled: (1) is the juice really worth the squeeze, and (2) is it really worth being so hostile to your power users?
Not quite. The smallest Qwen3 A3B quants are ~12gb and use more like ~14gb depending on your context settings. You'll thrash the SSD pretty hard swapping it on a 16gb machine.
A good first exercise for new hires! (And I say that as having been both a new hire who's updated the documentation after trying to execute it, and as someone who's guided a new hire when the documentation proved inadequate.)
Best Buy has been a big one for me when I need things like USB sticks or SD cards. (Bad enough with the occasional duds from the reputable sources without mixing in counterfeits on top of that.)
Price matching on most of their stuff and their budget line of cabling is actually quite competitive. When I have to do buildouts sometimes we need to buy a lot of Ethernet cable and their pricing is not terrible in a pinch.
Once bought an entire store out of patch cables, ha.
I've often wished that formatters had some threshold for similarity between adjacent lines. If some X% of the characters on the line match the character right above, then it might be tabular and it could do something to maintain the tabular layout.
Bonus points for it's able to do something like diff the adjacent lines to detect table-like layouts and figure out if something nudged a field or two out of alignment and then insert spaces to fix the table layout.
I believe some formatters have an option where you can specify a "do not reformat" block (or override formatting settings) via specific comments. As an exception, I'm okay with that. Most code (but I'm thinking business applications, not kernel drivers) benefits from default code formatting rules though.
And sometimes, if the code doesn't look good after automatic formatting, the code itself needs to be fixed. I'm specifically thinking about e.g. long or nested ternary statements; as soon as the auto formatter spreads it over multiple lines, you should probably refactor it.
I'm used to things like `// clang-format off` and on pairs to bracket such blocks, and adding empty trailing `//` comments to prevent re-flowing, and I use them when I must.
This was more about lamenting the need for such things. Clang-format can already somewhat tabularize code by aligning equals signs in consecutive cases. I was just wishing it had an option to detect and align other kinds of code to make or keep it more table like. (Destroying table-like structuring being the main places I tend to disagree with its formatting.)
reply