tomnipotent

> I've seen way more Nvidia specific issues in the mpv bug tracker than AMD

Could that maybe be because Nvidia now has almost an order of magnitude more customers? I think they closed 2024 with 90% market share.

Most of the Linux Nvidia driver bugs seem to be related to the DRM/KMS layer, not the shared code. That's still a pretty big surface area.

I would posit that they're a single component for most consumers and buyers, and that a small majority will upgrade any single one of these three components in the lifespan of their computer. A quick check of r/buildapc reinforces this to be the case, as most posts are either full-system builds or peripheral upgrades (GPU, SSD).

My guess is that Framework had a unique opportunity with the AMD Ryzen AI and decided to capitalize on it to serve a fast-and-growing home market for this class of hardware, and the soldered LPDDR was a compromise considering the requirements of the CPU. If I had to choose between them offering this product with that restriction, or "sticking to their core values" and waiting for an alternative solution then I'm going to learn to live with the restriction. If the traffic queue wasn't just marketing BS, I assume many other people are also willing to live with it.

I want Framework to be a long-term successful company and that means making good use of their cash, and this gives them a safer opportunity to test a new product category. Maybe the result of this decision is an expansion of the category to include more modular options, at which point everyone wins.

Numbers are incredibly common in many products - pretty much most computer parts (3080, 4090, z270, 13900k). Should probably always include them in ranking, but not necessarily filtering. Consider "PlayStation 5 games" should prioritize PS5 games, but many PS4 games may also be eligible. What it should not prioritize are $5 PlayStation 1 games.

Many of these challenges are obviated through "advanced" UI with separate fields for things like min/max price, though that's not available in text-only mediums.

Not OP, but at a minimum I'd expect range searches to work.

This particular search pattern could either be a open-ended range search "all products 80-infinity" or it could be a keyword search "80+" as in "PSU 80+ Gold".

I'm also noticing that many results have mixed-bag prices, while I was expecting something closer to being ranked by the price delta. For example "psu" returns 5 different $155 products, but "psu 300" returns a $2000 RTX 4090 along with 4 $155 PSU's. I don't know if it's a coincidence that the RTX has a stock of "304" or if you're applying the ranking method to fields outside of price.

What does "having no RAM" have to do with it"

The question is how much different is a motherboard with soldered CPU vs. CPU and memory soldered. You seem to be of the opinion that it's a completely different product category, I'm of the opinion they're more the same than different. I don't remember the last time I didn't upgrade all three components at once.

I remember using MemTurbo in the Windows 2000 era, though now I know it was mostly smoke and mirrors. My biggest gripe these days is too many "hardware accelerated" apps eating away VRAM, which is less of a problem with Windows (better over-commit) but which causes me a few crashes a month on KDE.

> Do I get to commit all my project management IDE/editor specific files too

Yes, if those files apply to all team members using the same tool absolutely check them in. What's the problem? It reads to me like maybe you don't know what these files are actually used for and why a team benefits from sharing them.

This is literally the same product they've been selling with just one more component soldered on (memory). I think it's a bit of a stretch to call it a "pivot".

I know very few people that do anything other than upgrade their GPU or SSD during the entire lifespan of their computer. Maybe when I was younger I'd upgrade the RAM after saving up, but am fortunate enough now to be able to buy what I want up front.

This product is for me.

A few years ago I tried to repurpose a desktop with a bad motherboard, but it was impossible to find a replacement for the 7-year-old CPU. eBay prices were more than the original MSRP, and at that point it was cheaper to buy new parts for the oldest still-selling generation.

I'm already replacing everything except the SSD and GPU with every upgrade anyway, now it will just be the SSD but I can keep the case.

Have you considered looking into a personal freight forwarder? I used these a few times while traveling through Europe.

It's very common for shared project-specific setting files to be stored in ".vscode" that are used by all developers on the project, including launch/task configurations. VSCode settings are hierarchical and composable (non-scalar keys are merged).

Totally doable, of course. But I'll need fewer ClickHouse servers for the same amount of data, and I'll get more utilization out of them with faster query times. High selectivity combined with colocated row data means that hybrid storage formats will need to read more I/O, use more memory, and churn through more buffer for the same queries.

Not at all too sales-y.

I'm all for keeping as much as possible in your initial Postgres deployment as possible. If your team isn't having to work around things and things "just work" it's a wonderful conjunction of requirements and opportunity. It's incredible how much you can get out of a single instance, really remarkable. I'd also add it's still worth it even if there is a little pain.

But I've found that once I cross about 8-12 terabytes of data I need to specialize, and that a pure columnar solution like ClickHouse really begins to shine even compared to hybrid solutions given the amortized cost of most analytic workloads. This difference quickly adds up and I think at that scale really makes a difference to the developer experience that a switch is worth the consideration. Otherwise stick to Postgres and save your org some money and more importantly sanity.

You reach a point when you have enough queries doing enough work that the extra I/O and memory required by PAX/hybrid becomes noticeably more costly than pure columnar, at least for the workloads that I have experience with.

ClickHouse is now in my toolbox right alongside Postgres with things to deploy that I can trust to get the job done.

BioWare acquired the license in 1995, before the acquisition. Wizard's role was to collect the royalty check. I believe they were otherwise at work on D&D 3rd Edition. Outside of the debt load it looks like the three games more or less recouped the acquisition cost in the first five years.

I probably owned 50 Dragonlance books by the time I graduated high school in 1999. Didn't get my first PC until 1994, but my search for Champions of Krynn led me down the classic CRPG rabbit hole so I had a chance to enjoy the classics before the "new" generation appeared with Diablo, Fallout, and Baldur's Gate.

The deal between TSR and Random House was interesting. Williams literally got to print money and get paid for whatever she delivered, but at the cost of building up a loan balance that would eventually come due. I know we make fun of MBA culture and bean counters but it takes a lot of discipline to run a company, and I wonder how the "blank check" influenced planning and production. Was it hubris that drove up an $12M loan? Was it poor communication from Random House to TSR about sales and forecasts?

It's also wild that if the TSR had lasted one more year it could have repaid its loan with the Baldur's Gate royalties and padded its war chest from the sequel and Neverwinter Nights. Business is a fickle beast.

Documentation on usage and limits from December 2024.

https://web.archive.org/web/20241213195423/https://docs.dock...

Here's the January 21st 2025 copy that includes the 10/HR limit.

https://web.archive.org/web/20250122190034/https://docs.dock...

The Pricing FAQ goes back further to December 12th 2024 and includes the 10/HR limit.

https://web.archive.org/web/20241212102929/https://www.docke...

I haven't gone through my emails, but I assume there was email communication somewhere along the way. It's safe to assume there's been a good 2-3 months of communication, though it may not have been as granular or targeted as some would have liked.

Business isn't static. Costs and operations are not static.

At one point Docker probably may have had an authentic intent for a free service, but costs along the way changed the reality of operations and long-term cash flow and success of the business required making changes. Maybe the cash saved from bandwidth is what makes the next project possible that helps them grow the bottom line.

Further what was once a positive value proposition 18 months ago can turn into a losing proposition today, and a company should be allowed to adapt to new circumstances and be allowed to make new decisions without being anchored and held back by historical decisions (unless under contract).

As fun as it is hold executives to unrealistic standards, they're not fortune-tellers that can predict the future and they're making the best possible decisions they can given the constraints they're under. And I don't begrudge them if those decisions are in their own best interest, such as is their responsibility.

I'll give Docker the benefit of the doubt that this wasn't a bait-and-switch, that they never excepted it to become so successful, and that costs outpaced their ability to monetize the success and were eating into cash reserves faster than plan. I think the current outcome isn't so bad, and that we're still getting a considerable amount of value for free. It's unfortunate that some people are only finding out now, and are now under pressure to address an issue they didn't sign up for.

Here's an announcement from September 2024.

https://www.docker.com/blog/november-2024-updated-plans-anno...

It's an interesting idea.

If code is ever updated by an LLM, does it benefit from using abstractions? After all they're really a tool for us lowly sapients to aid in breaking down complex problems. Maybe LLM's will create their own class of abstractions, diverse from our own but useful for their task.

> small companies and startups are great at interviewing

Small companies have the benefit of the pressure to fill a role to get work done, the lack of bureaucratic baggage to "protect" the company from bad hires, and generally don't have enough staff to suffer empire-building.

Somewhere along the line the question changes from "can this candidate do the job that other people in this office are already doing?" to "can this candidate do the job of this imaginary archetype I've invented with seemingly impossible qualities".

It's my understanding that weight lifting is superior to running for increasing bone density but that both together are superior to any one singular. Makes me think about a Mark Rippetoe article from several years back he helps an older woman (60? 80s?) eliminate her lower back pain with weight lifting and strength training exercises. Rippetoe isn't pefect, but he has a good-enough track record on this stuff.

I had a lateral fracture of my right humerus (arm snapped in half) and the only thing that made the pain go away was strength training. High-rep endurance exercises didn't help, hundreds of pushups a day didn't help, but after I switched to high-weight lift-to-fail the pain slowly disappeared.

I imagine most traffic to Wikipedia is through search, so I imagine such a fate is in the hands of search engines. If a community-driven alternative appeared, we'd have to rely on Google indexing this alternative and ranking it higher than the usurped domain.

> my contributions to a project had been sabotaged

I really wish people would stop throwing around the word "sabotaged". No one "sabotaged" anything. The opposition has been public from the beginning.

If I'm opposed to something, and someone asks my opinion about it in a private conversation, it is not "sabotage" to express my opinion. So far I haven't seen any evidence that those opposed to a mixed-language code base organized behind the scenes to hamper progress in anyway. Instead, their opposition has been public and in most cases instant.

Are people not allowed to be opposed to things anymore?

I fail to see anything in Sima's post that you linked that could be interpreted as toxic, rather than a perfectly normal human response. It's absolutely unreasonable to expect everyone to be perfect, always take the high road, or otherwise shrug off personal attacks.

Sima's responses can be excused. Even Hector's initial frustrations and his reactions to it can be excused. Hector's continued public reactions and escalations, however, are a different story and the reason folks are piling on him.

This seems like a perfectly reasonable response given Hector's prior comments. Pushing someones buttons until they explode and then pointing out they exploded isn't the indictment people think it is.

> that's a strategy decision that should not be up to any subsystem maintainer

So people are not allowed to hold positions and argue for them in public, or take actions that align with that position?

> I don't believe that was what the rust guys thought they'd be signing up for

It's not like there wasn't any existing precedence with C++, and many of the arguments I've read seem consistent with that history.

> That should not be a reason why to adopt a feature flag platform

It's one of the two big reasons. First is the ability to rollout features gradually and separate deployments from feature release, and second is the ability to turn new features off when something goes wrong. Even part of the motivation of A/B testing is de-risking.

I would put money on all of big tech and all public companies combined not employing more than 30% of professional programmers. At least in the US only 15% work at a large company (500+).

First extension I've used that perfectly autocompletes Go method receivers.

First tab completes just "func (t *Type)" so then I can type the first few characters of something I'm specifically looking for or wait for the first recommendation to kick in. I hope this isn't just a coincidence from the combination of model and settings...