Today at work I was using 57 gigs of ram at one point and I think that's a new record for me

nostr:npub1srhg4hk63ew68kepu0znazgf9tdl089dkur5artp440htxqrc8zsqz8g90 nostr:npub1n783957maa2g7rpdyd5knx0whfggllws33clq9qg4dme3wauxrvq6q87ev I have been using it almost a year now and I am positively shocked how little it fucks up (watch it die now that I say that)

nostr:npub1n783957maa2g7rpdyd5knx0whfggllws33clq9qg4dme3wauxrvq6q87ev nostr:npub1srhg4hk63ew68kepu0znazgf9tdl089dkur5artp440htxqrc8zsqz8g90 since I got zsh working natively on windows I haven't really had a reason to mess with WSL anymore (thank god)

nostr:npub1n783957maa2g7rpdyd5knx0whfggllws33clq9qg4dme3wauxrvq6q87ev nostr:npub1srhg4hk63ew68kepu0znazgf9tdl089dkur5artp440htxqrc8zsqz8g90 I had to dig through so many WSL copypaste articles before I found a single thing talking about good native terminals. Absolutely infuriating.

The issue with WSL is it's so damn slow. It took 20 MINUTES to run git status on a repo of mine vs half a second on the native filesystem.

nostr:npub107wnkjl6crsjs73ukvfjwd89wpvtfcwqdpwnf4xmqfts2pam9deqk89n4a is this goonclown

nostr:npub1n783957maa2g7rpdyd5knx0whfggllws33clq9qg4dme3wauxrvq6q87ev nostr:npub1srhg4hk63ew68kepu0znazgf9tdl089dkur5artp440htxqrc8zsqz8g90 well it does handle it fine on windows terminal. But also sometimes when using vim cmder will "get stuck" and only the bottom line will update anymore and I have to save/exit or force quit and try and recover. I found a workaround but you have to disable scrolling entirely to fix it which is a dealbreaker. It breaks the same way on ssh but far more frequently.

nostr:npub1srhg4hk63ew68kepu0znazgf9tdl089dkur5artp440htxqrc8zsqz8g90 I MEAN KEEP IN MIND that you're not going to find a terminal that matches anything on Linux but windows terminal appears to be the least worst option after my sampling of the options.

Cmder is a close second but it shits itself and dies when trying to do SSH and sometimes in vim

nostr:npub1srhg4hk63ew68kepu0znazgf9tdl089dkur5artp440htxqrc8zsqz8g90 that's part of system sounds which you should disable anyway because that shit is absolutely everywhere and is hyper annoying, especially on 11/

nostr:npub107wnkjl6crsjs73ukvfjwd89wpvtfcwqdpwnf4xmqfts2pam9deqk89n4a clownworld taken to its logical conclusion

nostr:npub1srhg4hk63ew68kepu0znazgf9tdl089dkur5artp440htxqrc8zsqz8g90 well the settings menu is shit but I only had to interact with that once to set it up.

Everything else sounds like a general windows issue.

nostr:npub1pnpez7cn4h04pxg07dmmklzyz7u7fm0w2ddrw220qh785rq3m42ql452zw nostr:npub1tj5fw9d0cpzxe5mtrsnp4mtu2dq50hk05e93y33r0ea6kjd05swq9hl33p nostr:npub1zxxp06lma7hh358kc36fytf6psy3ra0v6r53epxrwssgnvm5plhs06u452 there's no way you can verify that yourself because it's closed source. Example: WhatsApp messages are moderated despite "being encrypted" (hint: that means they aren't)

nostr:npub1srhg4hk63ew68kepu0znazgf9tdl089dkur5artp440htxqrc8zsqz8g90 I would like to know what's wrong with it because every other console I've used on windows is much worse. Windows terminal is the only one that doesn't shit itself for me on some common use case.

The configuration is god awful though thats my biggest complaint

:blobcathairflip:

You can't tell me what to do

nostr:npub1w7x9m8xutlezyzmu7d78d8ygzk6sdpncfuuds8jsz2wnwk8f52dqkrpc4w nostr:npub1x2vc8gu0kj2slcujhkd2y684k32e2zhzn78d2quea4tajn9ql2pqqjar98 nostr:npub1pyy99xge0464jlmylqqgflk3y9a8gzfhemnz4ue55qp5qtxl57qsaljuws yeah but that's surely not open source, which is what he's telling me to use. Still good to know.

nostr:npub1pyy99xge0464jlmylqqgflk3y9a8gzfhemnz4ue55qp5qtxl57qsaljuws nostr:npub1x2vc8gu0kj2slcujhkd2y684k32e2zhzn78d2quea4tajn9ql2pqqjar98 it pains me because not even modern C and C++ programmers seem to actually know what makes good performance outside of the really obvious stuff like O time complexity

nostr:npub1pyy99xge0464jlmylqqgflk3y9a8gzfhemnz4ue55qp5qtxl57qsaljuws nostr:npub1x2vc8gu0kj2slcujhkd2y684k32e2zhzn78d2quea4tajn9ql2pqqjar98 performance profiling in code is a tool where you can map execution time to specific lines of code. There are very few tools I'm aware of that can do it competently. Visual Studio, as much as I hate it, is the only thing I know of that has that capability on windows.

nostr:npub1pyy99xge0464jlmylqqgflk3y9a8gzfhemnz4ue55qp5qtxl57qsaljuws nostr:npub1x2vc8gu0kj2slcujhkd2y684k32e2zhzn78d2quea4tajn9ql2pqqjar98 does it do sourcemaps from pdb to CPP files?

nostr:npub1x2vc8gu0kj2slcujhkd2y684k32e2zhzn78d2quea4tajn9ql2pqqjar98 okay I'll bite.

What is a free and open source performance diagnostic tool FOR WINDOWS that instruments CPU time and IO ops.

It must be FOR WINDOWS because this is for work.

I am expecting you to say "get a different job"

nostr:npub1pyy99xge0464jlmylqqgflk3y9a8gzfhemnz4ue55qp5qtxl57qsaljuws nostr:npub1f64hh0hxfp5yeswecth4mnjz78uxls5s48wjnnev9d5tfy7qgttspj5rsj yeah that's what I'm talking about with the hubs. They rarely if ever work correctly. Constant overheating and disconnecting. I've been through 5 different brands I think and everyone fucks them up. The plugin ones seem a bit better but those aren't very portable.