• 0 Posts
  • 158 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2024

help-circle

  • Dolphin (well, whatever the KDE’s indexer is called) uses xattrs under the hood for tagging, so it will be compatible with other software (including {get,set}fattr).

    The index has to be up-to-date, but then that would be true with any tag-based filesystem, it’s just happening on a different layer (and arguably a layer which is more suitable for this - not sure it’d be a good idea to enforce synchronous indexing during xattr writes).

    The most significant user-facing obstacle is lack of software which supports this system, but I guess that shows that there’s not much desire for it in reality.









  • Abstraction, when used well, is actually a tool that produces more simple code in the long run. It separates different concerns into different pieces of code, makes code readable by extracting common logic and giving it a recognizable name, and reduces boilerplate.

    That said, OOP-style inheritance-based abstractions, while useful in some cases, quite often lead people down the complete opposite path - mushing together unrelated logic and then making call sites difficult to understand with a lot of hidden state that has to be kept in mind.


  • So yeah, there’s no exact answer to “what happens to Linux after Torvalds”, it’s more of “who gets to add more maintainers to torvalds/linux.git if nobody merges things in there for 72 hours”. I suppose Linus is confident that the system of distributed maintainers is robust enough to survive his & gregkh’s incapacitation, and the only remaining point of failure is access to the central repo itself. I think he is underestimating the governance upheaval that would happen if he was to disappear, so I hope that he puts some more details about his views on future project governance in writing.





  • There are some good ideas in there (the main one IMO is structured objects as the main form of IPC, instead of text), but the execution is really bad after XP and maybe 7. They stuck to a lot of legacy garbage in the name of “compatibility”, but in the end it’s an inconsistent mess of dozens of frameworks, and yet many old programs run worse than they do in WINE on Linux. Now with the advent of vibecoding the core components, it’s pretty much over unless they literally start over from an old checkout.






  • Ground is always there just for safety. It is supposed to be connected to any metal bits on the outside of any device, so that if a live wire touches the outside it just shorts and some fuse blows or circuit breaker trips, rather than providing an unpleasant surprise to anyone who touches it.

    Most modern electronics is “double-insulated”, meaning there are at least two layers of reinforced insulating material between any mains-carrying conductors and the user. This is deemed to be safe enough so that those devices don’t need to be grounded, and if the case is plastic then they will almost never be. So if you’re only connecting plastic-cased electronics to the socket, a ground would be superfluous in almost all cases. There might be some exceptions, like power supplies connecting one of the low-voltage pins to ground, but it is quite rare to see.