533 karma · joined February 8, 2013
But I do wonder if the timing is completely coincidental.
npm being "badly broken by design" is one opinion. But the fact is that almost all modern language tooling is moving in the direction of becoming more npm-like or has been created from the beginning with heavy npm inspiration. See for instance Rust's Cargo, Dart's Pub, Go's modules, Python's virtual env, Esy for Ocaml, and more. Developers love being able to easily manage and add dependencies, and this problem is only going to grow for Linux distributions across language ecosystems.
What I don't understand is why the casing around the board itself is so well designed and good looking. To me it looks like a "finished" self-contained device on its own. But if you use it together with, say, 2 3.5" HDDs you'll surely need some enclosure around the enclosure. At that point an "ugly" Raspberry PI-style board would have been just as good.
Granted, OP makes good use of the board enclosure, but needs to DIY a case in order to do so.
> btrfs has had some issues in the past, especially with the RAID5/6 setup
I'm pretty sure that btrfs still has major issues with RAID 5 & 6, and that these RAID modes are not recommended to be used in anger.
> For data use cases like this, USB 3 can be reasonably comparable to Thunderbolt 3, and that connection is generally faster than the media.
External HDD enclosures can often contain 4 drives. During a resliver all of these could be heavily accessed. I'm not sure how the single USB 3 connection fares in this scenario. In a normal desktop you'd have four separate SATA connections, and even then resilvering a large RAID setup can take quite some time.
In some ways it seems very attractive as you can just get a low-power SoC (like a Raspberry Pi or a NUC) and hook it up to the external drives.
But there also seems to be many potential pitfalls. Like, how slow will a resilver be over the USB? Might it be unusable/dangerously slow? How reliable is the USB connection? Does it perform to spec or might it cause weird issues? Can you get SMART info over the USB connection? Other issues?
> Syntactic uniformity also means there is a lot less room for syntax bikeshedding. Really the only thing you can bikeshed is the naming convention for identifiers, and how S-expressions should be indented.
This might be true in theory, but in practice I find to be effectively false. Lisp makes is very easy to add your own macros that implement DSLs with custom "syntax". Common Lisp for instance has bunch of these build in, for instance for iterating over lists. While this is technically not syntax in the traditional sense that the parser is aware of it, it has the same characteristics for a user. You need to learn the "syntax" that the macros implement and _that_ syntax you can certainly bikeshed about.
The fact that this completely standard binding has been broken in a crucial macOS app for 5 months basically tells me that Apple does not care about the "Emacs-style" shortcuts in macOS.
Recall that Apple bought Beats to acquire the music streaming platform that Beats was developing with the purpose of turning it into Apple Music. To me this always seemed like a bit of a weird move since Apple could obviously build their own music streaming service without acquiring a company to do so. My guess is that someone at Apple who's more of a business person than a product person wanted Apple to have a Spotify competitor ASAP and saw the acquisition of Beats as a quick way to get there (with means that a business person can carry out: acquisitions). The acquisition happened, Beat's tech was turned into Apple Music (probably with time to market as the key metric that management cared about), Apple Music was released. Then the business person was happy, called it a day, and moved on.
Had Apple put their own focus and top talent into Apple Music the way they did with iTunes and iTunes Store back when iPod was their main cash cow, then I think Apple Music would have been very different. But alas, "music streaming" is probably just a check mark in someones list of services that Apple should have, and it's already checked so the job is done :)
That being said, your statements about macOS sounds like they are coming from someone who's never used it and are making a fairly uninformed straw-man opinions about it. For instance, the statement "Apple products are dumbed down even more with every release" is just demonstrably false. Apple products gets more features with every release. For instance, the last macOS release got Shortcuts, Focus Modes, and Universal Control. All of which are power user features.
So as long as one avoids all the inconsistencies then one gets consistent shortcuts? ;) Only using Qt apps on Linux is very hard. A lot of good apps are GTK or Electron. On macOS there is no GTK & Qt divide and Electron apps are very good at implementing macOS shortcuts. Hence you get more consistent bindings.
Also, many bindings are absent even in Qt app. For instance, on macOS you have Emacs-style bindings in every app (Ctrl+a, Ctrl+p, Ctrl+k, etc.). Those are very useful. You can get them on Linux (at leasts in GTK apps) but it's very hacky and it conflicts with a bunch of stuff, whereas they fit right in on macOS. Cmd+Shift+/ to search all menus is also super useful and I don't think you can do that on KDE.
> And those behaviors can be "even" configured globally! (That's something to mention specially of course when talking to Mac users as such an advanced feature like "configurability" is notoriously missing in the Apple universe).
If you don't think macOS can be configured then you are mistaken. It can't be configured to the extend that KDE can that is true (some of us consider that to be a feature). But a lot is still possible. As an example, kindaVim adds vim-style keybindings to every app which is kinda cool.
What am I missing?
Atom was made to be infinitely customizable by using web technology. You can dynamically change everything you want with custom HTML, CSS, and JavaScript. Nothing is off limits. Want to shrink the size of the tabs? Just throw in some CSS, everything is changeable.
Code on the other hand runs plug-ins in a separate isolated thread where they are left to communicate with the editor through an extension API. Every customization "hook" that a plugin has access to needs to be explicitly added in that extension API. The things that the devs didn't think (or want) to add are simply impossible. Want to shrink the size of the tabs? Tough luck (except for unsupported hacks).
Code is awesome, but I think Atom should get more credit for what it tried to do. It is arguably the most customizable text editor ever.
1: Source, Gabriel Weinberg's book Traction.
He mentions KDE in the blog post:
> The feedback I get is that I should move to QT/KDE, but I think that theming has had the same issues for way longer already and I do really like the Gnome HIG.