lieks

When I was at school, I used to program on paper like this (due to not having a computer during class). It was accidentally a great exercise, that I think everyone should try. Because of it, I find myself writing mostly bug-free code on my first try these days (my bugs tend to happen on interactions between parts of a system I designed separately).

I haven't used s6 much, so I can't really comment on that, but Chimera tends to boot significantly faster on the same hardware, compared to Alpine with OpenRC, mostly because of dinit's parallel initialization.

As for system performance, mimalloc's effect isn't particularly noticeable in regular use. Or maybe I just don't stress the allocator often enough. There may be more daemons running by default, but they are also activated on demand if you aren't using them, so YMMV on that.

For desktop use, it feels like an early (but already quite usable) version of what a respectable systemd replacement would look like, and I think that's its greatest strength in practice.

I've switched to Chimera from Alpine a few months ago. It's much nicer for desktop use. The service supervision is great, and many things that require some setup on Alpine just work out of the box. The packaging system is nicer too, though it does have less stuff already packaged.

> Christianity considers any sexual activity other than heterosexual sex for procreation within marriage to be sinful,

Mostly true, except the "for procreation only" part. That's specific to Cathlicism.

Protestant doctrine tends to be "anything goes, so long as it's in marriage", with the implication that marriage is heterosexual.

> and female sexuality to be inherently corrupting because "it was Eve who tempted Adam in the Garden of Eden."

I don't know of any non-sectarian modern Christian group that think like this. I don't think it was even current thought at the time of the Reformation.

> The Christian dogma

You are, once again, talking about Catholicism. No other denomination calls their teaching "dogma", because only Catholicism claims to be infallible. And for that reason, any serious error in their dogma is nearly impossible to excuse without some serious mental gymnastics. Other denominations can go to the Bible and point to a passage showing some attitude was wrong, change their doctrine and move on. But not Catholicism.

I also heard these things in sociology class at school, but they are outdated and partially incorrect. And it's a very anachronistic interpretation of history.

> That isn't "sex positive" in any commonly understood sense of the term.

No indeed. Modern Christians aren't either. But that's not what the GP was referring to. What you got was women actually being consulted on who they should marry, getting basic human rights and so on. Which, at the time of the first century A.C., was rather revolutionary. A lot of these were weakened over time by Catholic (and also some Protestant) culture, but treating people like people is very much a big message in the Bible.

Another big message in the Bible is restraint, so of course Christianity can never be fully "sex positive" in the modern anything-goes sense of the term.

It works as a fork deterrent; forks can't easily prove they are still correct without the test suite, so if a company needs to tweak SQLite for any reason, they are better off paying for the tests so they know their tweaks won't break anything.

Because the whole goal is to not need any sort of "pointer discipline". The way he does it, you can store as many pointers to the arena as you want without keeping track of them, as long as they don't survive the deallocation of the arena.

One example would be having a big graph inside the arena. Pointers to other elements can just be plain pointers.

With "conventional RAII" you need to know if your pointer is the only pointer left to know whether to call the destructor. That requires some sort of pointer tracking.

They have already shown themselves to be both able and willing. Hopefully the backlash from this current decision will delay their plans long enough for GrapheneOS, Lineage and others to figure out how to work around it somehow, which is why I'm eagerly watching where this is going.

They didn't. They implemented the WebExtensions API for WebKit. It's not complete (e.g. Stylus doesn't work yet), but it's enough to run uBlock Origin.

You can install full uBlock Origin in the Orion browser, on iOS. It also has decent built-in ad blocking (though uBlock Origin is still better).

I had been thinking for a long time to switch to Android (GrapheneOS, probably) when my current iPhone 13 dies, but this whole thing with "sideloading" on Android is making me reconsider. If I can't have the freedom I want either way, might as well get longer support, polished animation and better default privacy (though I still need to opt-out of a bunch of stuff).

Common Lisp does have plenty of warts.

It was originally designed to be used by government software in the EU. AFAIK, it doesn't really get used for much else, but it fills a niche not covered by the GPL family, which is weak/non-viral copyleft (as the LGPL provides), plus handling SaaS in a reasonable way (as the AGPL provides).

Copyleft protects against proprietary forking, and also assures the community you can't close the source in the future. Weak/non-viral copyleft makes it so you can still link it to proprietary software, so you could sell integrations (non-LSP) or closed-source plugins.

LGPL and GPL licensed software can be provided over a network with proprietary changes. The AGPL and EUPL both close that hole. Every change to the modules covered by the EUPL must be open sourced, even in that case.

If your intention is to monetize the LSP itself, open source is probably not what you want. It's fundamental to open source that anyone can use it for any purpose, and also fork it. Permissive licenses like the MIT license allow relicensing to a proprietary license later (see Redis) but that causes problems with the community (see Redis), and is nearly guaranteed to cause a fork.

If you are already considering the AGPL, I'd like to suggest the EUPL. It also covers SaaS, is copyleft (forbids nonfree forks), but non-viral (can link to nonfree software), a lot easier to read, and also doesn't have the "bad name" some people attach to the GPL family.

I can't speak to how well it fits in your usecase. There are too many ways to do monetization, and I don't know which one you have in mind. But copyleft at least stops other entities from monetizing without sharing their contributions, so if you want to keep it open source, that's my recommendation.

As a Brazilian, I'm a bit torn on this issue. On the one hand, our social media regulations are terrible, are being approved without due process, and will certainly be used for (political) censorship. On the other hand, it's annoying that the US has to interfere, and concerning that they even can interfere in the first place.

It's a lot easier to get a large team of artists to follow the same artstyle when that artstyle is just "realism". Also, photoscans are convenient.