zlacker

[return to "Why users cannot create Issues directly"]
1. Maxiou+Yb[view] [source] 2026-01-02 03:23:27
>>xpe+(OP)
For example, memory leak investigation is currently spread across discussions, x/twitter and discord https://x.com/mitchellh/status/2004938171038277708 https://x.com/alxfazio/status/2004841392645050601 https://github.com/ghostty-org/ghostty/discussions/10114 https://github.com/ghostty-org/ghostty/discussions/9962

but has not graduated to issue worthy status

◧◩
2. quantu+Jc[view] [source] 2026-01-02 03:33:09
>>Maxiou+Yb
That's a shame to hear. I had to give up on Ghostty because of its memory leak issue. Granted, it was on an 8GB system, but that should be enough to run a terminal without memory exhaustion a few times a week. Foot has been rock solid, even though it lacks some of Ghostty's niceties.
◧◩◪
3. favfla+Uf[view] [source] 2026-01-02 04:09:27
>>quantu+Jc
btw, is it me or is there any justification for anyone including a developer to run more than 8GB of RAM for a laptop? I don't see functionality as having changed in the last 15 years.

For me, only Rust compilation necessitates more RAM. But, I assume devs just do RAM heavy dev work on a server over ssh.

◧◩◪◨
4. pdpi+Nh[view] [source] 2026-01-02 04:29:17
>>favfla+Uf
There's all the usual "$APPLICATION is a memory hog" complaints, for one.

In the SWE world, dev servers are a luxury that you don't get in most companies, and most people use their laptops as workstations. Depending on your workflow, you might well have a bunch of VMs/containers running.

Even outside of SWE world, people have plenty of use for more than 8GiB of RAM. Large Photoshop documents with loads of layers, a DAW with a bazillion plugins and samples, anything involving 4k video are all workloads that would struggle running on such a small RAM allowance.

◧◩◪◨⬒
5. gizmo6+3j[view] [source] 2026-01-02 04:43:39
>>pdpi+Nh
This depends on industry. Around here, working locally on laptop is a luxury, and most devs are required to treat their laptop like a thin client.

Of course, being developer laptops, they all come with 16 gigs of RAM. In contrast, the remote VMs where we do all of the actual work are limited to 4GiB unless we get manager and IT approval for more.

◧◩◪◨⬒⬓
6. sumant+2C[view] [source] 2026-01-02 08:34:07
>>gizmo6+3j
Interesting. I required all my devs to use local VMs for development. We've saved a fair bit on cloud costs.
◧◩◪◨⬒⬓⬔
7. wongar+pX[view] [source] 2026-01-02 12:07:59
>>sumant+2C
> We've saved a fair bit on cloud costs

our company just went with the "server in the basement" approach, with every employee having a user account (no VM or docker separation, just normal file permissions). Sure, sounds like the 80s, but it works rearly well. Remote access with wireguard, uptime similar or better than cloud, sharing the same beefy CPUs works well and gives good utilization. Running jobs that need hundreds of GB of RAM isn't an issue as long as you respect other's needs too dont hog the RAM all day. And in amortized costs per employee its dirt cheap. I only wish we had more GPUs.

[go to top]