It prevents you from mutating via the reference that you obtain from `satisfies` without casting its type, yes (or rather more precisely, you can mutate it, but only to the one allowed value).
However, the object can still be mutated via other references to it. TypeScript is full of holes like this in the type system - the problem is that they are trying to bolt types and immutability onto a hot mess that is JS data model while preserving backwards compatibility.
I love my moonlander so much, I bought a second one for work. Both were secondhand, so the sticker shock wasn't quite so bad. Though, I did end up spending some of that savings on custom, coiled cables. A coworker, after seeing my setup, also ended buying two.
I agree with the author. It's a tool, and if your job requires a lot of computer use, it is worth it to invest in a tool that can not only help prevent RSI, but also make you much more productive.
I switched to a Colemak-dh layout at the same time, and it was a huge adjustment. I'm not sure it was really worth it yet. It is hard to catch up to 30+ years of QWERTY muscle memory, though. Key layout aside, the ortholinear arrangement has absolutely been worth it. It feels much more comfortable, especially with the tenting set up.
ZSA's layout editor and customer support also deserve a shoutout. Can't recommend it enough.
I don’t have a moonlander but I did get one of their ergodox keyboards after noticing an increase in pain myself. I tried using it in querty and my experience was unless you type with proper hand position and finger movements (and possibly not even then) querty on an orthinear was even more painful than on a regular keyboard. I tried colemak for a while but something about the layout didn’t feel comfortable still. I landed on using “middlemak” [1] which at least for me has been much more comfortable. It preserves a decent bit of qwerty placement to help with muscle memory, but I’ve also found that only using it on the ergodox keyboard and keeping qwerty on all of my “normal” keyboards has also helped the muscle memory a lot.
QWERTY with "proper" hand placement isn't too bad, but I've been typing like this since I was 4 years old and have never tried another layout, so I might just be missing out. Still, it took me more than a year to really get used to the Ergodox... I shudder to think how long a new layout would take to get used to!
I like my moonlander. Feels great and now that I'm used to ortholinear, I can't go back. The ZSA layout editor is awesome. I just wish it had more keys so that I could have an F row and dedicated keys for modifiers. Yes I can use the various features to get them and yes I know it'll be allegedly faster once I train myself. But I'm a busy middle aged man now. I float back and forth between Windows (home), Mac (work), and Linux (Steam deck) and having to keep all the keyboard shortcuts straight on top of having blank keycaps for modifiers makes my head hurt.
I briefly looked for labeled keycaps that let the light shine through but couldn't find any.
Where did you get your coiled cables? I bought one from Aliexpress. It took a month to arrive and then didn't work.
I use long press on the number keys for function keys (F11 and F12 on the inner columns) and I'm pretty happy with that setup.
I got my cables on etsy. There are tons of US-based makers who have large selections of colors, connectors, etc. I got my connectors cerakoted and they're really nice. It's pricey though.
I've bought bitcoin a few times using paypal, and while it says you can transfer it to any address, it would never actually let me complete the process. Support was utterly useless. Presumably it's some fraud risk sort of issue, but ultimately just cost me a few dollars in losses and fees to get my cash back.
Is Intel still working on it? Open-CAS bdev support was nearly removed from SPDK at a time when Intel still employed a SPDK development and QA team. Huawei stepped in to offer support to keep it alive, preventing its removal.
I’ve been under the impression that Intel got rid of pretty much all of their storage software employees.
I mean to ask a genuine, good faith question here, because I don't know much about Huawei's development team.
My head goes to the xz attack when I hear that Intel decided to stop supporting an open source tool, and a Chinese company known to sell backdoored equipment "steps in" to continue development, and it makes me suspicious & concerned.
This is to say nothing of the quality of the software they write or its functionality, they may be "good stewards" of it, but does it seem paranoid to be unsure of that arrangement?
What about cheaper, bigger displays? I want something that's ~16" but doesn't cost an arm and a leg, for displaying sheet music. Still haven't found anything that's suitable. Plenty of people I know use the 13" iPad Pro, but between the glare (stage lights can be intense) and the roughly-letter-paper size, I still prefer sheets of paper.
If you're happy with grayscale, biggest from Good-Display[1] offers 25" x 33". If you want bigger, you'll probably have to wait until Samsung's new 75" EMDX panel[2] becomes available for purchase.
I would love to switch over to Signal, but the video call quality pales in comparison to WhatsApp and FaceTime. Add to that issues with even sending pictures or videos on Android, and it's a really hard sell.
Lucky you! I pretty much can never send videos. I'm guessing it's something format / compression / transcoding related. Pictures are hit or miss; I think it's an infrastructure thing.
> Add to that issues with even sending pictures or videos on Android, and it's a really hard sell.
What issues? The only issue I've seen with Signal and media files, was on iOS, where users aren't able to download them (copy them outside the signal app).
Anecdotally, I've not had any issues on iOS (not that I'm needing to download media files often, but I have saved quite a few photos and the occasional video over the years and don't recall any failures).
Not that my experience invalidates that of people who have had problems, just sharing to say that the problems haven't been universal.
It's actually not more involved on iOS (unless you're unlucky and have problems with it not working - I've no idea if it's a tiny minority of people who have problems, or if I'm in a tiny minority of people for whom it works, or if it's somewhere in between). But for those of us who it does work for, it's just as simple as on Android.
You can hold down on the media, and after about a second it brings up a menu where one of the options is "Save", you tap this and it will be saved to your camera roll (ie open Photos app to see it). If it's a message with multiple photos/videos, you so the same thing and all of them will be downloaded at the same time.
Or instead of holding down to get the context menu, you can tap once to open full screen view of the media which has the iOS "share" button in the bottom left, which you can use if you either want to just save one thing from a message that had multiple photos/videos, or if instead of saving to the default place - it's the standard iOS share function, so you can choose from "save to photos" (ie a the default like above), or "save to files" (accessible from the iOS file manager or from other apps), or share directly to a different app (like an email client, or an FTP client if you have one installed, or to an app like DropBox, or any other app you have that supports the OS-wide share menu).
TLDR: The help page you linked to, the top part of that iOS section (that makes it seem complicated) is just explaining how to find an overview of all previously shared media for a contact/group, and then download from there, but you don't need to do that to download it if you're already looking at what you want to download in the main chat window. The bottom part on that page is my second option from above, which is basically identical to what you say about how to do it on Android - just 3 touches (press image, press 3 dots on Android or share icon on iOS, then press save image). But it's actually the more complicated way, with a 2 touch option available (hold down on image, then press "save" :)
(p.s. to any Signal devs reading this, if you'd like to offer a free backups subscription in return for me continuing to evangelise, or beta testing on my iPhone... feel free to reach out :P
And, although personally I'm more keen on the future feature or backing up either to iCloud or to my own server, may I make a suggestion that, if paying for you to backup media, I'd prefer to be able to pay for a "family" plan - as I've moved several family members onto Signal and would like to be able to gift them free backups rather than tell them all to start paying. I suspect I'm not the only person who would think an option to share storage with 5 or more family/friends would be worth paying a bit more than your current single-account price.)
Any recommendations from HN for a write-once (literally once), data storage format that's suitable for network storage?
sqlite docs recommend avoiding using it on network storage, though from what I can gather, it's less of an issue if you're truly only doing reads (meaning I could create it locally and then copy it to network storage). Apache Parquet seems promising, and it seems to support indexing now which is an important requirement.
SQLite works fine over read-only NFS, in my experience. Just only work on an immutable copy and restart your application if ever changing it. If your application is short lived and can only ever see an immutable copy on the path, then it is a great solution.
SQLite does work on NFS even in read-write scenario. Discovered by accident, but my statement still holds. The WAL mode is explicitly not supported over network filesystems, but I guess you don't expect it to :)
My experience has been the opposite... Lots of db lock and corruption issues. The FAQ doesn't call out WAL specifically, just says don't do it at all: https://www.sqlite.org/faq.html#q5
I've had multiple flaky issues with SQLite (e.g. non-HA Grafana) on Azure Files using NFS v4.1 leading to locked DBs. Perhaps some implementations work, I'm not gonna rely on it or advise others to do so.
Cheaper / smaller? I would say not likely. There is already an enormous amount of market pressure to make SRAM and DRAM smaller.
Device physics-wise, you could probably make SRAM faster by dropping the transistor threshold voltage. It would also make it harder / slower to write. The bigger downside is that it would have higher leakage power, but if it's a small portion of all the SRAM, it might be worth the tradeoff.
For DRAM, there isn't as much "device" involved because the storage element isn't transistor-based. You could probably make some design tradeoff in the sense amplifier to reduce read times by trading off write times, but I doubt it would make a significant change.
But much of the latency in cache is getting the signal to and from the cell, not the actual store threshold. And I can't see much difference in that unless you can actually eliminate gates (and so make it smaller, making it physically closer on average).
