Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Don Y <blockedofcourse@foo.invalid>
Newsgroups: sci.electronics.design
Subject: Re: All VM-based development
Date: Wed, 15 Jan 2025 18:27:57 -0700
Organization: A noiseless patient Spider
Lines: 30
Message-ID: <vm9nb4$36r20$1@dont-email.me>
References: <vlq25f$3l4rh$2@dont-email.me> <vlq961$3q2a6$1@dont-email.me>
 <vlqkln$3tbjk$4@dont-email.me> <vlqlhv$3tegj$1@dont-email.me>
 <vlqnla$3tq6t$1@dont-email.me> <vm9c7c$34v1g$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 16 Jan 2025 02:28:05 +0100 (CET)
Injection-Info: dont-email.me; posting-host="5c4476b3bab58763ec60fbd13d6fd507";
	logging-data="3370048"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+TY76V9fllZy0oowEzyAZ7"
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.2.2
Cancel-Lock: sha1:yJ0O8E48WC6IPkecuGgVD9KjXTI=
Content-Language: en-US
In-Reply-To: <vm9c7c$34v1g$1@dont-email.me>
Bytes: 2710

On 1/15/2025 3:18 PM, Klaus Kragelund wrote:
> I looked into it a month ago since I got a new PC. My intention was to use it 
> for the programs that could be updated often (compilers, maybe Altium/Orcad)

I *tend* not to update, often.  But, have to preserve <whatever> versions
of <whichever> tools I happened to have used for a particular project.

> Seems any VM and container takes significant resources (both CPU load, but more 
> important memory). So I did not go through with it.

My smallest box has 96G of RAM.  Most are 144G or more (192G, 256G).

For interactive applications, I suspect the performance hit falls
into the noise as the applications tend to spend much of their time
waiting on the user for input/direction.

For BATCH applications, I don't sit and twiddle my thumbs "waiting";
there is always some other thing that could use my attention.  People
who insist on having faster hardware to minimize thumb-twiddling-time
just need to rethink HOW they work.

What I am more concerned with is apps that may have taken measures
to protect against virtualization.  Or, peripheral devices that
"misbehave".  Or, apps that want to talk directly to the hardware
and may have implicit timing dependencies in those interfaces.

If I have to resort to different environments for different virtualizations,
that would be an acceptable compromise  (the goal here is to get rid
of hardware).