akvadrako

I had this symptom due to having an SSD without a RAM cache, which caused the latency of disk access to rise to seconds under heavy paging, effectively freezing the computer. Enabling the kyber IO scheduler, tuned for responsiveness over throughput, solved it for me.

You also cannot move most Ikea furniture without it falling apart, so taking it apart is actually the least damaging option. (Some of the higher end lines are okay)

This is a very common effect and I don't want to be defending LLMs here. But I've seen the same study with CLIs - people using them feel more productive but take longer than using GUIs.

What I want to say is that it's very situational and it's likely good to focus on the average. Using LLMs as docs are bad when good docs exist, but if you aren't sure if they do, it's a gamble. A much better approach would be to have somebody pre-create and edit the docs with an LLM for each service with bad docs.

Only when your situation isn't covered would it make sense to create new docs.

It's true the comments get it wrong. But their main point stands; they shouldn't use AWS.

It's also true that most companies which AWS does target shouldn't use it either, unless you have a good reason why ( like you need data centers in every continent or to quickly scale to 10+ thousands of cpus ).

It's not an Apple thing, though they may have adopted it first.

Basically every high end laptop comes with TB4 or 5 ports.

Most states default to registering you when you get a driver's license, but you can opt-out. Some are opt-in.

YAML is actually very complex, to the point that basically nobody implements the full YAML 1.2 spec from 2009 (https://matrix.yaml.info/), while 1.1 contains footguns like `country: fr` and `country: no` parsing issues.

Though I agree simple usage is good enough in practice, there are a lot of edge cases that can cause subtle bugs.

I had AppleCare when my keyboard failed. They blamed it on me because of an dent about 1mm wide I never noticed on the back corner.

So you just get screwed twice.

Lack of records isn't the issue. You authorize mailbox's servers to send on behalf of your domain. Then they let anyone with a mailbox account set the from to your domain.

I use mailbox for the past few years and I think it's the best option out there. But they have one major issue, which is that anyone can impersonate your domain:

https://userforum-en.mailbox.org/topic/anti-spoofing-for-cus...

Things like that existed in the category of accelerator cards. Xeon Phi (Knights) is one example, focused on core count. Some from HP have soldered on SSDs too. You also had blade servers which is more focused on that use case, though that's going out of style.

I don't think PCIe is really a good fit for general CPU tasks. You need big heatsinks and power and can't fit that much RAM on board.

Its easier to connect to existing sessions in your main browser.

I don't see how it's different. You could always describe what you want to a team lead or consultant and pay them to build it.

That's still the best way to turn a spec into a program and comes with all the downsides it entails.

I don't notice it at all, on my laptop or phone. Even when having one monitor 60 and one 120 next too it.

Only when looking at demo pages to show off high refresh rates can I tell.

Though what I do notice is replacing the mouse with a higher polling rate from 125Hz to 250Hz.

I don't know why you say that. I've measured Linux sleep power consumption for Lenovo and ASUS laptops over the past 10 years and S3 and si0x come pretty close.

I assume you are talking jean sizes, which might be related to inches in some historical sense, but now it's more abstract.

However dress pants, sports pants and everything that isn't pants is just as bad as for women.

Can't you avoid the OSD if you control it with DCC?

Seems they come with 200gbit ports so it takes 20 minutes to fill memory.

500 nits is not really good enough for laptop that you might use outside.

Luckily they are still improving and we now have Tandem OLED with about double that.

And if not mise, just a Makefile, shell scripts or custom docker images. Then you can run and develop them locally.

GitHub actions has some rough edges around caching, but all the packaging is totally unimportant and best avoided.

They are usually shaped to fit in exactly the space available to maximize capacity. Standard cell sizes wastes space.

Besides it's pretty easy to get custom battery pouches made.

Servers can support it but not browsers.

That doesn't match what I see. Shops don't issue an invoice until the product ships, well after payment.

Victoria metrics which has similar database design to clickhouse is good for metrics.

But it doesn't have a complete dashboard UI like Grafana.

I find it quite hard to follow PRs when there is a lot of rebasing. I don't really find separate non-time-based commits useful.

So I agree but unfortunately it's the norm and policy for some clients.

Git-absord by default doesn't squash the fixups though, it creates new ones with special tags for easy rebasing later.

That hasn't been true for at least 15 years. I was a k-root DNS operator then, and we ran several software stacks on each cluster in case one had a bug.

You can operate abroad with General in most countries.

This subthread is about a poster's claim above that every page would be in RAM if you have enough, "hot or not", not just the working set.

Only if you have more RAM than disk space, which is wasteful for many applications.

It doesn't matter but you can just go look.