Just looking at it makes me wonder why you'd consider the thumb placement that strange (although all hands are different and all that). What was off about it for you?
dnzm
joined 2 years ago
I'm actually still on my first ergo, a Lily58 (my first mechanical was a "regular" 75%). I was a bit on the fence between this and the Corne, and I think I would've been fine going with the Corne; I barely used the numrow and currently it's not even mapped, and I'm experimenting with putting the things I had left on the outer columns on layers or combos.
But regret... no, of course not. It's been a great learning experience so far!
I'll certainly build more boards at some point, at least a Corne because, well, gotta build a Corne, but maybe some other things as well. Maybe a Charybdis or a Cygnus or something like that.
You gotta love the copy on the Warp site. As for why they're now launching it on Linux:
Despite this, Linux has relatively few terminal options compared to Mac and Windows
...relatively few? Really?
This sounds like it'd be exactly how I currently use Tumbleweed on my workstations: I don't update daily, but rather every once in a while. I appreciate the new versions of things, but being on the daily bleeding edge is more work than I care to put in.
I can also see this working quite nicely for those with nvidia hardware, where with TW you'd sometimes end up with a kernel too new for the drivers to get shoehorned in. A slightly easier-going pace would help there.
It also reminds me of Android, where you have roughly monthly updates (theoretically) and every now and then a bigger one.
Installing a software package through a distro's package manager sounds like a perfectly fine "Linux way" to me.
Of course, that filesystem exists today as btrfs.
Which, to be fair, isn't exactly the fasted FS around. I love me some btrfs, but not for the benchmarks.
Muscle memory needs some time, especially for symbol stuff. Don't hesitate to tweak your mappings, I've made some changes at some point which made things a whole lot more workable. I started with Miryoku which was completely unsuitable for the PHP work I was doing back then, to mention something, and moving the number cluster to the right hand rather than left did miracles for my day to day work as well.
I code with it, yeah. Just have those symbols wherever you want them (I never used those inner upper keys either, except for things that I don't mind lifting my hand for). Layers layers layers. Also home row mods.
For my next board, I'm probably going with a 6×3+3, I don't use the number row either. Keypad on a layer under the right hand is so much nicer...
Als ik de bedrijven in dat artikel zo aan het woord hoor over "krapte op de arbeidsmarkt" en "diversiteit", zegt de cynicus in mij "we nemen gewoon internationale studenten aan want die slikken blijkbaar nog dat we ze zo min mogelijk betalen". Er is m.i. sowieso een verschil tussen "het personeel is het Engels machtig zodat een klant in die taal te woord kan worden gestaan" en "het personeel spreekt alleen maar Engels". Dat tweede vind ik toch een mindere ontwikkeling, ondanks dat ik me persoonlijk prima in het Engels kan redden. Er zijn er genoeg (ook onder de 87,25 jaar) die dat niet kunnen.
That's correct. Btrfs will simply divide your disks in 1GB chunks, and when writing, always ensure that a bit of data is always stored in 2 chunks on two different disks. You can also do 1C3 or 1C4 if your data is truly that critical, which means data is always stored in 3 or 4 chunks (on different disks), respectively. Of course, that also requires at least they amount of drives.
This chunking is also the reason why the sizes of the drives don't have to match, as long as it's possible to divide it evenly you won't lose space as unused. Simply put, make sure your largest drive is not larger than your other drives combined and you should be fine.
In my case, data will always see one copy on the 4gb drive, and another on either of the 2gb drives.
As for the reason to switch: that's something I can get behind, although you could also just slap Proxmox on it an do all your experimenting in VMs; at least that keeps the server itself running as smoothly as possible, while not limiting you in your learning experiences.
As for btrfs: it most certainly does have RAID functionality. RAID5/6 is considered unstable (although I've heard/read from plenty of people who have great experiences with it, provided you don't run into the edge cases), but I'm sticking with RAID1 because I don't need to run the risk, and I'm not sure if waiting for a checksum calculation whenever something does go pear-shaped is going to do a whole lot of good for me.
Anyway, as for my setup: an HP Microserver (an oldie, a Gen8 with a Xeon switched in) running Leap, powering a few VMs, a collection of Docker containers, and a few "native" services (nginx, PHP, stuff like that). The root fs is a single SSD (btrfs SINGLE with some directories having a flag to disable COW), and there's a data pool of 3 spinning disks (2x2 and 1x4GB), 4GB effective, that contains "data". Most of it is setup with Ansible these days, hence no real use for YaST on that machine for me.
Keyboards is no beter. Like you said, the fluff makes the hobby.