drdnl

joined 1 year ago
[–] drdnl@programming.dev 4 points 3 months ago

Same, had to scroll too far to see another nixos user

[–] drdnl@programming.dev 9 points 4 months ago (1 children)

Scissor for sure

[–] drdnl@programming.dev 4 points 8 months ago

I've been using one full time for about five years now without issue. Even kind of like having to move around a little

[–] drdnl@programming.dev 2 points 8 months ago* (last edited 8 months ago)

I'd like to be able to say it'll work, I've been gaming on Linux for years and just finished Doom Eternal at 5120x1440 at 120fps

But I have the previous generation top end cpu and gpu, 16 core something and a 5900xt iirc, so we can't quite compare

One thing I did notice though is that your cpu seems weirdly overloaded? Or at least, the windows values are very different from the Linux ones? Are you dual booting? Or did you maybe reset something in the bios whilst switching?

Just wondering if you might be looking in the wrong place

Is that cpu one of those with an embedded gpu? That you're maybe running the wrong hardware?

Nm, looked it up, it's a mobile cpu, no idea unfortunately

[–] drdnl@programming.dev 1 points 10 months ago (1 children)

I have had a couple T14s without issue, did you remember to change the suspend mode in the bios to Linux?

[–] drdnl@programming.dev 3 points 1 year ago

Although a bit long, I do like this almost impossible to ignore example of self documenting code :)

[–] drdnl@programming.dev 5 points 1 year ago (9 children)

A header might be useful, although there's likely better ways to (not) document what each sql statement does.

But inline documentation? I'd suggest trying to work around that. Here's an explanation as to why: https://youtu.be/Bf7vDBBOBUA

If possible, and as much as possible, things should simply make enough sense to be self documenting. With only the high level concepts actually documented. Everything else is at risk to be outdated or worse, confuse

[–] drdnl@programming.dev 3 points 1 year ago (1 children)

Pretty happy with nixos these days, after the initial (crazy) learning curve. But I really like the creative simplicity of this idea

[–] drdnl@programming.dev 5 points 1 year ago

No sure about 64gb, but for performance/watt and reliable Linux I can really recommend the Amd p16s and t16(s?) machines from Lenovo. Have about seven in the office and they are excellent.

I too, as someone in devops, am wondering what you need that much memory for. Do you simply really like VMs? :)

Also, have you considered doing the really heavy stuff remotely? Whenever I need desktop type power (16 physical cores and 128gb memory) I simply wake the desktop, ssh into it and do it there.

[–] drdnl@programming.dev 1 points 1 year ago (1 children)

I had an extreme, as nice as it was it kind of sucked on Linux due to all the dual gpu weirdness (working hdmi or battery longevity, pick one)

Has this changed recently? Because it used to be due to the wiring of hdmi though the external gpu

[–] drdnl@programming.dev 5 points 1 year ago (1 children)

I thought it had to do with the fact that most themes on Linux consist of a large collection of dotfiles, dots, rice. But that might just be me

[–] drdnl@programming.dev 1 points 1 year ago (1 children)

Tbh, these days WSL2 might be slightly better than macOS at being Linux. As it is Linux (in a very transparent vm) instead of posix or *nix

But for most dev work all three are good options. I've noticed that once you start deploying against stuff like kubernetes or, less so, doing docker stuff you run into limitations on Mac and wsl2. Just random weirdness, especially with new the m1 chips and say cockroachdb. At that point there's no substitute for the real thing :)

view more: next ›