The only thing keeping my secondary / gaming / file-server computer on Windows is Backblaze. The main obstacle to me switching from macOS to Linux is Office 365 (doesn't work on Wine).
If tech companies implemented real, e2e encryption for all user data, there would be a huge outcry, as the most notable effect would be lots of people losing access to their data irrevocably.
I'm all for criticizing tech companies but it's pointless to demand the impossible.
Just say "we are storing your keys on our servers so you won't lose them" and follow that with either "do you trust us" or even "we will share this key with law enforcement if compelled". Would be fine. Let people make these decisions.
Besides, bit ocker keys are really quite hard to lose.
is it just me or would "Microsoft refuses to comply with a legal search warrant" be an actual, surprising news story? like of course MSFT is going to hand over to authorities whatever they ask for if there's a warrant, imagine if they didn't (hint: not good for business. their customers are governments and large institutions, a reputation for "going rogue" would damage their brand quite a bit)
Only in certain fields. For most interactions divide by 10 is far easier than divide by 12, and you'd end up with far, far more "eyeballed" measurements.
I hope you're comfortable with changing literally every number in society to base 12. My house cost $42A765_12. My SSN is 399-AA-5866 and phone number is (289) 257-B84A. The distance to the moon is actually 50A693_12 feet. I used the additional symbols A and B as per usual notation, but it's okay if society agrees on some other symbols for the extra two digit values.
If you don't make the base of the number system agree with the base used for converting between units, then conversion becomes so much harder. For example, it's not immediately apparent that 204 inches is 17 feet, but it is immediately apparent that 204 cm is 2.04 m. Furthermore, when the base disagrees with conversion factors, you run into issues like variable-length fields - like, "2ft 9in", "2ft 10in" (notice the inches transitions from one digit to two digits).
Possibly yes. But every implementation of base-60 I've ever seen is actually implemented as alternating base-6 and base-10.
A true base-60 would have 60 unique symbols for the different digital values, much like how in our set of ten digits {0123456789}, none of the symbols have any rhyme or pattern with respect to the others.
Good luck memorizing the ~1800 entries of the base-60 multiplication table.
Base 12? That's a small number. Now base 13? 13's a big number. The biggest number, perhaps. That's what they're saying at least. Base 13, 13 colonies, now that's America.
This can make sense for currency, but units of weight and distance and so on are infinitely divisible. You can just have a third of a metre if you like. Or 333 mm if the inaccuracy is acceptable. And so on.
And it's not like 1 is some special value. If you start from a base of 120cm you get enough even divisions that you rarely run into the need for fractions
Unless everyone worked in base 12 numbers too, that'd be a mess. Part of the beauty of metric is how often calculations devolve to shifting the decimal point.
No, converting units is not a useful exercise. airplanes are measured in mm - even the full length is in mm not decameters or even hecameters (i had to look those prefixes up, spellcheck doesn't even know the word, but I think they are correct)
Vehicle drawings (maybe mechanical engineering in general) might be in millimetres, but a lot of civil engineering works in metres, so when designing some bit of infrastructure to fit certain kinds of vehicles, I do need to convert between the two, and the easier, the better.
You can actually count to 12 on your fingers using one hand. Use the thumb as a pointer, then for each of your other fingers you have three joints. So 3*4=12.
It's hard to actually count using more than 4 bits/hand though. The quickest methods that require the least dexterity are those that count the knuckles (which are actually used in some counting traditions, unlike binary finger-counting).
Ghostty is so great. Cross-platform but native on Mac and Linux. Core written in a cool random language, showing that you can have well-behaved Mac apps that aren’t just pure Swift / Objective C. Same great design no doubt helps here.
When users reattach to their session we render the terminal state and output from ghostty. Super cool and works really well. It’s basically tmux-lite in 1k LoC
I like that. I don’t want to use tmux (and I don’t when I’m working on my local machine), but I can’t escape it when SSHing. I could ssh to a ton of sessions, but then I 1. Have to remember their names 2. Can’t easily create a new pane (on the remote host) for some short task and 3. Need yet another solution for restoring my pane layout for when my client restarts.
Maybe I’ll try the session name thing, I just foresee it being annoying. Do you see your tool as a shpool replacement?
I totally understand your concerns for creating new terminals for short tasks. I generally lean towards `nvim` terminal buffers to solve that issue. Or I have a `term` session open that I can quickly go to for random terminal commands that don't belong to a project.
I also (coincidentally) just started using OP's coder, and that also sets up ssh config to use special wildcard hosts, and unfortunately 'hogs' the config (it threatens to trash any changes to the coder section).
Love this idea. Though, apparently zig isnt available in any version of Debian including sid, which is annoying. A multiyear packaging effort stalled out 8 months ago with zig 0.14, which is too old for zmx.
Will try this out on my arch system later this week though.
I like System 6: the most complete version of the “real” classic Mac OS before System 7 started to be more “modern.” Dead simple, not a lot of new abstractions and metaphors layered on.
reply