It is an old trick https://apple.fandom.com/wiki/RAM_Doubler

RAM Doubler was a third-party application in the days when a top-of-the-line Mac had 128MB of RAM, with a 40Mhz processor. The level 2 cache was 256 bytes.

That's not in the same universe as hardware compression on a 6-core, 64-bit ARM processor with cores that can run at 4GHz.

That is why it is an old trick

Sure, but there’s a difference between a hack and an intentional architectural decision.

Weird .. I easily run 40 docker containers on an 8GB MacBook just fine!

(Just posting this to show that you have to be very specific when talking about these kind of things. Yeah maybe you need 32GB because you run some large deployment 3 times. Others mayb be totally fine with less if they just develop a basic Python web app. Who knows. The devil is in the details. Omitting them makes the discussion ambiguous and just difficult.)

It is easier and less intrusive to implement good RBAC on your database.

All you need is a JAVA_CODING_GUIDELINES.md with some hints about what kind of Java code you like the agent to write.

All you need is [to encode all of the lessons you’ve learned about style and best practices over your entire career into a single markdown file].

Sorry, couldn’t help myself.

File the bugs if you want to see things improved.

It is an extremely bad idea to send your encrypted signing certificates and password thereof to a third party like this.

This service is most likely malicious and should be shut down.

I want to upvote this 100x

Do not underestimate the power of a single server to host you app. Sure it won't work in _all_ situations but omg you can get so much out of a single $30/month VPS .. we've been indoctrinated that everything needs to be on hyperclouds and mega scale. But that brings so much cost and complexity that most applciations don't need.

> you can get so much out of a single $30/month VPS

I agree with this 100%, but only wanted to note, that not all VPSes are equal. Having worked in shared hosting business in the past, I can tell from experience that performance can vary greatly depending on hosting provider and how much they have over provisioned their virtualization platform, since VPS is nothing more than a VM running on someones else's hardware and that someone can put 4 VMs on single CPU core - all fighting for same CPU time, so it's depends on certain luck what will your VM get and what neighbors are doing - idling of being hacked and mining crypto. So if requirements are serious, look out for dedicated core VPS hosting and stay away from too good to be true cheap VMs deals. Also relevant monitoring metric is CPU steal time - its percentage of time a virtual CPU waits for a physical CPU from the hypervisor while it is busy serving another VM - that is strong indication you are being ripped off CPU.

100%. And super easy to scale up to a certain point. Alternatives have it's place though (PaaS is excellent for 100% product focus in limited timeframe, cloud/orchestration when you have scale, Kamal in Rails world is a neat middleground for some extra robustness).

Sure, but you need the knowledge to set it up. And that is what I do :)

The RFC MUST SHOULD discussion is funny ...

Considering that Google Workspace is a major player and a place where your customer are, do you want your customers to succesfully use your product?

If the answer is no then yes go ahead and debate the RFC.

If you care about your customers and your product working broadly with a diverse set of mail services then please spend 15 minutes to write a patch to add a Message-ID header?

FWIW Mac Minis have not increased in price because of "RAM Prices". Same models cost exactly the same as a year ago. Maybe it will change in the future, maybe not. Who knows. But right now Apple seems to have secure a good stash of RAM to use and avoid price changes.