• 0 Posts
  • 47 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle




  • You think electric cars are some sort of solution? They are part of the problem, not the solution. Making things worse but not quite as quickly is not making things better.

    Truth is we could never stop it without radical global abolition of high energy activities. That’s impossible given the short term gains of breaking ranks and the unpopularity of that level of denial. We didn’t have to destroy ourselves as quickly, but the path was set when we had the industrial revolution.


  • Hmm, I’m not taking about hacking defaults, I’m talking about hacking functionality. I’m talking about making capabilities that didn’t exist, all seamlessly part of my typical integrated text manipulation environment (that’s way broader than editing)

    The unique power of emacs is it doesn’t have typical boundaries, so integrated personal unique functionality is possible. May well be a huge downfall, security wise - it rides a lot on security through obscurity.

    Frankly it’s taken me decades to properly appreciate how my computer experience can be so fungible. Most computer systems don’t allow it.


  • Lazy about tooling? The biggest point people make is that IDEs tend to work out of the box while the likes of vim or emacs need configuration and have an initially steep learning curve.

    Well, as in this discussion, some people sometimes also tend to raise a lot of features as if only IDEs have them, but that’s frequently just ignorance.


  • Hackability not on your list? It’s the ability to extend and adapt it to my particular needs that, above many other things, means I am too deep into Emacs to even imagine leaving.

    Plugins are a very weak substitute that cannot provide that utility, and I notice Helix doesn’t even offer plugins. That sword does have the horrendous opposite edge of almost total lack of security, so perhaps I’ll regret that one day. There are so many ways I value Emacs that isn’t matched by any other text environment that none of the others are even on my radar as possible replacements.

    Out-of-the-box experience is very weak on Emacs, but I’m decades past that being a concern to me directly, though it does inhibit newcomer uptake.

    Other than that, for me it ticks your boxes while barely scratching the surface of its merits. At least its speed and latency is not something I notice any meaningful benefit when working with something that people praise, like vim. Come to that most of the time like now, typing into a browser text box, I’m not even bothered by latency, and that’s way worse than Emacs.

    It’s biggest failing to me is working remotely when there’s significant network latency, where VSCode is clearly superior, but I have neither the time, nor probably the ability, to fix it.






  • sping@lemmy.sdf.orgtoOpen Source@lemmy.mlMeshtastic
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    2 months ago

    Meshtastic is fully dominant in user numbers, but is fundamentally broken by design for what most people actually want to use it for, which is a distributed zero infrastructure communication network. As soon as numbers rise it is crushed by the weight of its own administrative traffic. Also, it’s way too easy to set nodes up as ROUTER nodes, which crushes the mesh and swallows traffic ironically.



  • I remember it as just beer and cider, with the addition of blackcurrant making it a Purple Nasty, and all sorts of tales of how they allegedly reacted to make a vicious drink more than the sun of the parts that I am sure was fiction.

    And for Americans, this means alcoholic ciders, since they also call raw apple juice cider, and most Americans have no idea what a blackcurrant is (a delicious intense berry that was illegal to cultivate in the US for a lot of the recent past).





  • sping@lemmy.sdf.orgtoLinux@lemmy.mlAny window manager suggestion
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    2
    ·
    7 months ago

    I know about window managers and how using them will reduce the memory usage by system a lot because they are less bloated etc.

    Ehhhh… I think it’s more “not using a curated general-purpose DE”, rather than “using a WM”. All graphical systems include a WM, and a DE in some senses is more of a concept or category than a concrete thing. The choice is whether it’s one you cobble a DE together yourself, or use a pre-configured, curated one.

    Many people use stand-alone WMs and then create their own DE, but quite a few of us put the WM of our choice within existing DE because we want the WM but have no interest in re-inventing all those DE wheels (and/or have >4Gb memory so the “bloat” is not an issue). In my case it’s i3 on Gnome via gnome-flashback.

    Curated DEs do tend to use more resources - typically mostly memory - partly because they tend to be comprehensive for diverse users. Rolling your own minimal DE for your personal needs can often be lighter weight. If you have a very constrained system then it can be beneficial, though that circumstance is more and more unusual these days when 8Gb of memory is often considered “minimal”.

    The main reasons for making your own DE is to do things exactly the way you want, at the expense of having to do it. Beware though, there will be various helpful features of DEs you may not realize you appreciate until you have realize you don’t have them. E.g. what happens when you plug in a USB drive? Nothing, by default - a DE usually manages that. SSHing into servers a lot - a credentials agent is nice - better add one of those…

    A lot of rolling your own DE is months or years of “oh yeah, that is a useful thing to have; I need to find tools and configure them to do that”. Conversely, dropping your WM of choice into another DE is often a case of “huh, that happens automagically; nice!”.