That'll just lead to a dick-swinging contest if your resident Java guru already said 4gb is enough. It's futile. There are many ways to reduce the memory consumption of your desktop machine. Start with those.
Ask HN: Our lead architect says 4GB is enough for a developer machine
31–35 of 35 posts
Re: Ask HN: Our lead architect says 4GB is enough for a developer machine
#32Earlier quoted context omitted.
Point?
Trying to understand why OP talks about VDI clients (basically dumb terminals), but then complains that they don't have enough RAM to run apps locally.
Re: Ask HN: Our lead architect says 4GB is enough for a developer machine
#33Earlier quoted context omitted.
Trying to understand why OP talks about VDI clients (basically dumb terminals), but then complains that they don't have enough RAM to run apps locally.
Good question. I misread the op the first time. So yeah whats the advantage of stuffing more on the thin client. Unless he is also using the thin client to run stuff he cant run remotely.
What's the term for the instance I connect to? I guess I should have just called it the VM. My VM only has 4GB of RAM and one core and I'm supposed to write and test (deploy) decent sized applications on it.
Re: Ask HN: Our lead architect says 4GB is enough for a developer machine
#34Earlier quoted context omitted.
Good question. I misread the op the first time. So yeah whats the advantage of stuffing more on the thin client. Unless he is also using the thin client to run stuff he cant run remotely.
Just a terminology mistake on my part. I don't know what to call the virtualized OS I'm remoting into. We just refer to it as VDI, but that's more general. What's the term for the instance I connect to? I guess I should have just called it the VM. My VM only has 4GB of RAM and one core and I'm supposed to write and test (deploy) decent sized applications on it.