• 0 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle

  • There’s a lot of advantages that simply come with using a more popular distribution. For one, having a larger pool of package maintainers (and therefore more packages) is pretty important. Have you ever tried using NixOS as a daily driver? I did a few years ago. Very annoying having to create my own packages for so many different (and relatively common) things I wanted to use.





  • Every kind of hobby ultimately rests on some different kinds of reward mechanisms. Whether it’s the thrill of winning at a competition, the excitement of discovery, or the satisfaction of accomplishment, these sorts of positive emotions are what keep a hobby interesting and engaging for us. Collecting is no different, and this is where I believe the problems start.

    Collecting as a hobby gets its main motivator from acquiring rare stuff. While there is a learning component to it (learning about all the stuff that’s out there, the history, why some things are rare and others are not, and what fair market prices are for everything) and a sense of satisfaction and accomplishment (from gazing at a completed collection), the main drive that keeps people engaged is the excitement of unboxing and taking possession of new and rare item.

    Unfortunately, this is an extremely fleeting and hollow emotion. It can last as little as a few minutes and rarely lasts more than a few days. In the long run, I believe this is what leads people to lose interest in collecting: they simply run out of rare stuff to obtain and thus lose the excitement they once had. Some even get so frustrated and disillusioned by collecting that they go out of their way to destroy or sell off their collections, often experiencing an enormous sense of relief afterwards (but potentially also a sense of loss and regret).

    Contrast this with hobbies based around making or fixing stuff: making wine, brewing beer, gardening, cooking and baking, repairing old clocks or TVs or computers, restoring old cars, woodworking or blacksmithy or hobby machining, making jewellery or clothing, programming video games. These hobbies all differ from collecting because they’re focused on learning and personal growth. For example, there is a sense of satisfaction and accomplishment to pick a few jalapeño peppers off the plants you raised from seeds, but the ultimate driver is the thrill of learning how to better take care of plants so that next time they grow even bigger and healthier than before!

    Likewise with a repair hobby such as fixing old clocks: each one you come across (and there is some overlap with collecting here) has a unique history with a unique set of challenges to overcome if you are to get the thing repaired and running again good as new. But it differs from collecting in that the biggest satisfaction arrives at the end, when you complete the repair, rather than the beginning when you unbox the clock.

    Some of the other making/crafting/food hobbies also provide additional satisfaction when you’re able to give away or sell your creations to friends and family (or strangers at a farmer’s market or Etsy shop). Having another person be happy as a result of something you learned how to do is incredibly rewarding in ways that an obscure collection may not be. It can be quite a downer to have others fail to understand what’s so interesting about your collection and even painful if they tell you they think it’s a waste of time and money. Of course, ultimately this reward/consequence of a hobby depends greatly on your relationships to other people and how much you care (or not) what they think.







  • All the spatial persistence stuff was handled by the desktop database which was an invisible file that got stored on the disk. Hard drives and floppies each had their own so that if you shared a floppy with a friend the spatial properties of the floppy would travel with it. This also worked if you moved a hard drive from one system to another for the same reason.

    It also worked over AppleShare network file sharing. Where it didn’t work was if you had 2 different computers since there was no way to sync information between them. You essentially treated each computer as its own thing which is really more in keeping with the spirit of spatial design. After all, it would be really weird if 2 different drawers in different rooms in your house somehow always had identical contents which stayed in sync.


  • Q for all those with suggestions: do any of these attempt to replicate the Spatial Finder? No other system I’ve seen (contemporary to OS 9 or since then) seems to have got this element correct (or even attempted to do so).

    It’s such a key part of the OS 9 (and earlier) experience. Double click a folder and it opens where you expect it to, in the shape you left it, with the icons laid out as you left them. It’s a method of working that gives you great familiarity and confidence.

    If anyone’s worked in a kitchen or workshop for a long time and developed a deep memory for the layout and the location of every tool, material, and control, then they’ll know what I’m talking about. You can move around and work incredibly efficiently, relying greatly on muscle memory.

    Since the demise of OS 9, the only way to retain this level of operation has been to rely heavily on the keyboard. Since almost everything on the screen is transient and unreliably positioned (non-spatial), only the keyboard is persistent enough to allow us to work at the speed of thought and rely on muscle memory. It’s been so long now that I think people forget (or never knew) that the contents of the screen could also be persistent and spatial this way.


  • It would only be a temporary fix. Robert Nozick gives the example of the famous basketball player as a critique of John Rawls’ veil of ignorance argument.

    Suppose everyone had equal wealth but we remained different individuals with our own personalities, abilities, etc. For simplicity, assume everyone has $100 each and there are a million people in total. Now suppose one person is actually a legendary basketball player (Nozick uses Wilt Chamberlain as an example) and he decides to play basketball in the NBA to entertain everyone else. But he doesn’t do it for free, he charges each person $1 for a ticket to see him play.

    If everyone pays to see him play basketball, he becomes a millionaire while everyone else becomes $1 poorer. In effect, the balance of total equality has been broken.

    How do you solve this problem? You might say that he’s not allowed to charge $1 for people to see him play basketball but then what you’re really saying is that everyone is not allowed to spend their $1 to see a basketball game. So it’s actually not possible to preserve the state of total equality without taking away people’s economic freedom (that is, the freedom to decide how to spend their $100).

    Thus you either gradually revert to inequality or you make all money worthless by taking away people’s choices on what to spend (and so you might as well just have a ration system instead).


  • I mean the Gimp in particular. My point is that if we could suddenly wish the Gimp into non-existence (a counterfactual) then we could get a do-over. But because the Gimp actually exists it occupies a niche that could go to something better. Instead of banding together to create a better tool, people just grumble a bit and then use the Gimp (or hand over their wallet to Adobe).


  • I think my biggest issue with the Gimp is that it simply exists. If it didn’t exist there’d be a huge hole in the free software space and people would get together to build software to fill it. But of course there’s no guarantee that would actually produce something better.

    Maybe the real problem with the Gimp is that it’s built to scratch an itch for its own developers who are used to its bizarre UIs and workflows. For all the people I’ve seen complaining about the Gimp over the years, none have stepped up to create an alternative. I think this is likely due to the intersection between visual arts people and software engineers being extremely small (and likely most working for Adobe already).



  • The issue is that you don’t want to give some random untrusted process root access. You, the user, have root access as long as you’re capable of running processes as root, but that doesn’t mean you should.

    There could be tons of apps on the iOS App Store or Google Play Store that are completely benign under the existing security model but do nefarious things when run as root. No one knows that for sure because they aren’t tested under root by Apple or Google.

    The problem with root is that it’s giving the process the keys to the Ferrari. That’s long since been decided to be a bad security model. Far better to have the process request permission to access particular resources and you grant them on a case by case basis.