I noticed it felt a little janky on my PC despite being "60 FPS"...then I noticed the "60 FPS" is hard-coded into the HTML.

IME this is how it used to be in many companies. You earn trust for a few years then petition to go remote. There was usually a lot of process involved (I remember having my request go up the chain to a VP for approval) but as long as you were a high performer and okay with a mild pay cut, it generally went through.

Then post-COVID many companies had trouble luring people back when being in-office was purely optional. That's when you started seeing the RTO mandates and the refusal to allow anyone to switch to remote regardless of performance.

If you're remote and there's an "upgrade" remote job, there's very little friction to switch beyond the usual onboarding. You don't have to find a local job for your spouse, sell your house, switch your kids' schools, etc. You just mail your old laptop in and wait for a new one to arrive. Maybe you have to get up early or work later to match the local time zone if you have many in-office coworkers.

And, if you work at a big company that pays well, it can also let you get off the hamster wheel early and "leave your job" for retirement by moving to a medium- or low cost of living area while continuing to get paid an outsized amount for the area.

Once we figured out what he was up to, I'd keep an eye on him so I could go pick him up and lay him inside on the cool tile next to his water bowl when he was done for the day.

But all MGS games are basically playable Kojima manifestos with sci-fi trappings. The actual minute-to-minute gameplay for them is really, really good so even if you don't dig the story they're worth playing.

The previous poster is right that MGS4 does clear a lot of this up. But MGS4 also slams more weirdness and callbacks to the previous games on top of it.

I've always heard this as the "Rule of three": https://en.wikipedia.org/wiki/Rule_of_three_(computer_progra...

I had near-zero experience with CNC and got a Cavera Air last year and it mostly "just works" from the hardware side. I just fixture stuff and run my gcode, zero issues with the hardware. The Z1 seems to be even more streamlined w/r/t things like chip evacuation.

But, my god, Makera's firmware/software is fucking garbage. Especially the CAM workbench.

The community firmware and controller software (https://github.com/Carvera-Community) is so much better and feature-filled that it's kind of sad. They also have a tool library and post-processor for the FreeCAD CAM workbench in that repo which will let you make a clean break from Makera's terrible software.

On the upside: Makera apparently won't invalidate your warranty for using the community firmware/controller software, which is nice.

"How do you tell the difference between a protestor with a camera and a protestor with a grenade?"

Do you see how the assumption of extreme (and very unlikely) danger is bad excuse for violating people's rights?

No more scouring junk yards for a particular heater core from wrecked cars or modding aquarium pumps.

That being said, I also never really understood the "add colorful lights to your PC" aspect of some builds.

I think it's more to have a big window with lots of RGB LEDs to show off on the internet.

Newer SFF cases from Ncase/Formd/Louqe are designed with perforations or mesh on every exterior surface to maximize air flow. They can support an air-cooled 5090 and an AIO or massive tower cooler for the CPU. Put a 1000W SFX PSU in there and I don't know if you'd really be wanting for anything spec-wise.

There's also solutions like Federal Syntech (https://www.federalpremium.com/handgun/syntech/) that doesn't get rid of the lead but fully encapsulates it to avoid the airborne lead problem.

LLM currently produce pretty mediocre code. A lot of that is a "garbage in, garbage out" issue but it's just the current state of things.

If the alternative is noob code or just not doing a task at all, then mediocre is great.

But 90% of the time I'm working in a familiar language/domain so I can grind out better code relatively quickly and do so in a way that's cohesive with nearby code in the codebase. The main use-case I have for AI in that case is writing the trivial unit tests for me.

So it's another "No Silver Bullet" technology where the problem it's fixing isn't the essential problem software engineers are facing.

There's an animated background element with shooting stars that seems to be updating per-pixel. The more pixels it draws, like for a high res screen, the slower the page seems to render. I deleted that element and it scrolled smoothly.

Bummer for the community but it seems like a reasonable position.

“Markets can remain irrational longer than you can remain solvent.”

TSLA's value has never been correlated to the fundamentals of the business. So it continuing to do so isn't super surprising.

As long as there's a steady supply of unsavvy investors/future bag-holders willing to buy, it'll keep climbing.

I think it's more "they are no longer piggybacking off our work for free".

I also think what they actually wanted was that plus "...and they paid us".

I don't know if it needs $400m but I wouldn't be surprised if it's $20m+ just to keep the browser secure.

Google paid out $12m last year in bug bounties and I assume they spend that much or more for in-house security researchers/developers (headcount is expensive) and periodic independent audits of the codebase.

Probably whales who can afford to rent one from Google Cloud.

Unfortunately, recalibration only "fixes" minor stick drift and, due to how the sticks wear, drift tends to go from "minor" to "major" really quickly.

The issue is that the stick will eventually report an increasingly unpredictable position. So it's not an issue of it predictably reporting (-1, -5) at rest, it's more like random values from -5 to 5 in both axes. This also affects the direction when actually pressing the stick so pushing the stick "north" may cause you to move N, NNW, _or_ NNE and unpredictably so.