Permissive licenses permit a broader range of use compared to “copyleft” licenses.

“copyleft” here just being a cute way of being the opposite of copyright - instead of disallowing others from what they can do with “copyrighted” code, “copyleft” requires that they (upon request) share modifications to your code.

Permissive takes away this requirement to share your modifications. “copyleft” is considered more free and open source (FOSS), permissive is more business friendly.

Which part sounds off to you? This looks like a very reasonable paper hoping to distill traditional medicine into viable research paths, and does it using a pretty interesting model of compounds and effects.

If all you see is jibber jabber, maybe you should just default to trusting the experts on this one? Like, it’s not in an obscure journal - it’s a highly regarded peer reviewed journal. The authors aren’t random, they’re researchers at some of the best universities in the world (Nanjing University ranks #7 on the Nature Index).

The abstract is about as plain-speaking as it gets in the world of cutting edge research. You can probably look up the handful of domain-specific terminology and have a good grasp at what the research is about.

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.

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.

Thanks for sharing! Really interesting history in this article. It’s scary to think what a world would look like if Sun didn’t sue Microsoft into oblivion and put an end to this strategy.

We could be living in a world where Windows is the dominant desktop OS instead of our beloved Solaris.

To be serious, though, being sued/forced to settle isn’t an indicator that the strategy hasn’t worked. In fact, as is evident by the continued doubling down on the strategy by Microsoft and the unfettered execution of this strategy with Chrome, it’s clear that the value far outweighs the cost of the occasional settlement. The only real deterrent is antitrust regulation and that has been just about entirely defanged. These concerns are especially pertinent for something like Lemmy where there’s no central entity to soak the legal fees to go to court.

A few animal-inspired names that I think have a nice ring to them

• Dodopedia (extinct like Mastadons, similar vowel rhythm to “wiki”)
• Hippopedia
• Komodopedia