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

help-circle
  • In North America, 2-6-4T types were very uncommon, mostly used for commuter passenger service. Not sure if any were preserved; I know of only a 4-6-4T on display in Montreal. This made them very exotic to this colonial.

    They’re also an ideal size for models-- big enough for all the motion and complex design features, small enough to traverse 50cm radius curves. :)



  • I wonder if it might be an unreproducible moment in history.

    I suspect the Cambrian explosion of X11 window managers came from two things:

    • Propriatery and former-propriatery systems with unique look and feel (see, for example, Open Look/olvwm) There was also a tendency to copy any style you could (WindowMaker copied NeXTStep, IceWM mocked OS/2, and when those cute QNX demo discs came out, within days there were lookalike themes). It feels like the last major outside inspirations, MacOS and Win1,1 are converging on almost intrrchangeable insipidness.

    • The 1990s/2000s customization era. Machines were finally powerful enough to do mildly nifty things, but still attainable by hobbyists gluing together pixmaps and this bred stuff like Enlightnment E16 or Afterstep

    Do these forces still exist in 2024? It seems like Unix Porn today is a bunch of neokvetch windows without even a titlebar to provide a personal statement.


  • I think I’d be a lot more excited about Wayland if I felt like I can get a compositor that matches my tastes.

    I want to iconify things to the desktop, not relying on a taskbar-alike. Nothing seems to offer that. Hell, the taskbar is often a third party program.

    I want to double-click to shade. Labwc just added this, a feature that X11 window managers have been offering since the 90s.

    I want an aesthetic that’s got real depth and skeumorphism, rather that flat and featureless. Maybe something offers that, but there are plenty of X11 choices that have beveled buttons out of the box.

    The charm of Unix systems used to be flexibility, buy Wayland seems to be an extinction-level event for traditional window management. Nothing fills the gap of FVWM or WindowMaker. But gosh, I can get 92 flavours of tiling compositor and windows that ripple when dragged.










  • But even that’s a relatively high bar. Wl-roots is self-described as “60000 lines of code you don’t have to write yourself”, and any arbitrary compositor may not use it or may not be up-to-date with it. In X11, you don’t need 60,000 lines of code to be functional. Hell, the example Window Manager that was printed as a couple of chapters in the old X11R5 reference books works well enough especially considering its size.

    I feel like I missed the historic genesis of this particular quagmire. Knowing that a composer was essential, you’d expect developers would want to make very robust core functionality-- a super-rich libweston or something like wl-roots, so that “real” compositors would just be paper-thin extensions that answered the opinionated parts. Did early Wayland design get bogged down on embedded-style use cases where such features were seen as too expensive (compare: no built-in printf in C), or was it a deliberate territory grab by early compositor developers, trying to turn it into a place they could to gain competitive advantage?


  • What has kept me away from Wayland is the tendency to be dependent on the compositor for so much.

    I use my preferred X11 window manager for largely aesthetic reasons, but by and large, I can swap it out and the rest of the software doesn’t give a damn. At most, you might have to tweak a RC file to fix missing custom assumptions (i. e. disabling decorations on full-screenified Proton games)

    It seems like on Wayland, there’s a lot more of a “if you aren’t using GNOME or KDE, the odds something meaningful breaks are much higher.” Aside from the perceived bulk of these environments, they’re highly opinionated-- I suspect it would be a major production number to hammer them into a shape that looked like FVWM or WindowMaker, even if you only wanted to match a single theme’s aesthetics (as opposed to, say, FVWM’s dynamic configurability).


  • HakFoo@lemmy.sdf.orgtoLinux@lemmy.mlSystemD
    link
    fedilink
    arrow-up
    13
    arrow-down
    1
    ·
    10 months ago

    What worries me about the “systemd does everything as a tightly integrated package” is the too-big-to-fail aspect. I’d be worried that we’re seeing a lot of configurations that can’t be pulled apart piecemeal-- for example, if you need a feature not available in systemd, or you need to deactivate a systemd component due to an unfixed vulnerability. It feels like there’s value in supporting a non-systemd init in the same way there’s value for individual packages to support an architecture beyond x86-64-- you get some extra checks that you aren’t making assumptions that only work for a specific happy path.




  • Seems like a good balance-- big enough to not devolve into territory battles, small enough to look full in the end.

    The fun thing is seeing what content is missing-- it seems like some fandoms never really migrated to the Fediverse. For me, a lack of Genshin stands out; anything this big usually gets a Fallen Qiqi out of principle.