I fell victim to this one on authentic “retro” N64 hardware, which has a hard plastic analog stick. Got an enormous blister right on the palm of my hand trying to win this tug of war. Of course, my young brain was able to hyperfocus on the game and completely tuned out any sense of pain in my hand. It was quite gruesome when I finally beat it and realized my hand was torn to shreds. I was at my neighbors place and I remember how shocked their mom was. She applied some cream that I think was meant for severe burns.

Nintendo would later run a campaign where they’d send you fingerless gloves for free to try to do some damage control on all the negative press when reports started popping up.

To some people, yes. To others, no. You’re replying to specific people who seem to be against the idea, and I’m guessing for them it detracts significantly from the experience.

At the end of the day all of the concepts we have in fantasy are derivative in some regard, so the line will vary just like it will vary for people that want to do total homebrew vs following a book.

My group dabbled with AI when it was at its peak buzz, and if I’m honest, my head cannon sort of ignores those bits. They don’t carry the same authenticity that I came to expect from my group. It detracts from my experience because I play ttrpgs primarily to learn about my friends and how they’ve interpreted a shared world, not to hear algorithmically mid fanfic. I’m also not crazy about following a book. With a book, at least I know someone willfully released the work into the world and is getting appropriately compensated.

These are not the same. Here are some of the ways someone may be fine with reusing existing material while being against AI:

• Someone may value thoughtful and coherent world building, while feeling like the AI generated amalgamation dilutes the cohesiveness of the material.
• Someone can be for public sharing of ideas, while simultaneously against AI companies disregarding licenses attached to those ideas to build AI products.
• Someone can value the personality and individual perspective that a content author or DM injects into material and feel that AI-generated material lacks this character.

Don’t reduce the use of AI down to the reuse of material. It also averages out material into some sort of lowest common denominator - sacrificing exactly the things that many niche fandoms value: personality and imagination.

I’d bet that they symlinked /ubuntu to the server’s home root - probably for continuity with some previous file structure. It sure looks silly, but I’m sure the reasons for doing it were pretty reasonable.

For those that look at this and still think the solution might just be more money, first recognize that Google donates only to keep Firefox as a viable competitor to avoid anti-trust legislation.

If we raised half a million dollars, we haven’t saved anyone any money except Google - they’d simply donate only 100k next year so Firefox remains competitive, but not successful.

I don’t disagree with the sentiment of the post, but we also have to realize that we’d only be improving things after the first ~600k.

I don’t know anything about being an electrician - commercial or otherwise, so I’m curious to hear your side.

When all those people go to working remote, it’s not like they’re no longer in need of electricity. Presumably their home demand is higher and we might even see people adding new office spaces to adapt their home. Maybe the public grid needs to change to support it? Won’t this mean that there will just be a different type of demand for electricians?

Are there reasons this would be less attractive to electricians? Pay, job security, or something else?

For anyone who’s curious, this is the state of discussing this feature: https://github.com/helix-editor/helix/discussions/8572

I’m not an authority on the helix ethos, but I’ve contributed a bit and hung around long enough to have a good read on their stance on most topics. The project is still young and managing the growing pains of getting a lot of traction relatively early. I think the devs value keeping the maintenance footprint small to keep the project sustainable.

The philosophy of helix’s design is to be a more convenient kakoune, not necessarily a vim. vim is much more widely known, so that analogy springs up more often, but this idea of using piping out to an external command for most operations comes from kakoune.

For features that would introduce significant maintenance overhead, may jeopardize the performance of a more common workflow or where the design goals are still maturing, the team tends to push such suggestions toward being developed as plugins when that system is added. I get the impression that they see the value of this workflow, but would prefer to see it battle tested as a plugin first.