CoolCold

Interesting, mind giving couple of examples? For myself I cannot say I have problems with focusing by using Windows OS - it's my daily driver over the years.

it's not receiving new features and basically hard to do real improvements which are very Linux tied, so provided as is I think.

Noway if I need systemd, I can try to run in on WSL1 and this won't change.

> Btrfs gets first tier support under the UEK.

> The UEK also includes all the drivers available in stock Linux that are removed in RHEL.

WSL2 usually runs on kernel from MS, not from one of the distros

* RHEL officially coming * new tar-based images - "Set the WSL distro name and install location with wsl --install options --name and --location (Now you can install straight to your other hard drives!)" * friendship with your Corp IT guys - Intune integration and Entra ID integration

no idea on Linux, but I've seen some benchmark reported up to crazy 28h long on Windows, and ~ 22h more like average across several models

I still run one distro on WSL1 - the fact it shares network with "main" Windows helps me to do simpler TCP proxying when needed. So you are not alone ;) While WSL1 is nothing bad, the most of things I do involving WSL happens in WSL2.

Not to say you are doing something wrong - whatever suite your needs. For me, WSL2 provide Linux tooling, i.e. systemd, which WSL1 just cannot by design. The very same way managing system as I do on servers.

When it's possible/makes sense, I do run gitlab-runner in my WSL2 for easier builds debugging, when setting up new projects for programmers - comparing to 250-300+ ms latency working on remote hosts, it's often much more productive.

Basically stable Linux without fighting with Linux-on-desktop-year-to-come.

I cannot imagine things of this sort in terminal would be useful for me, but interesting outlook for my bubble, thank you

> Probably not very detectable for Meta since it uses a wrapped webview

Interesting, my naive understanding is that push notifications won't work and battery life should be greatly affected, how do things work for you?

those are unsafe from different perspectives - AFAIR, io_uring just passed some/many filtering mechanics applied to other subsystems in kernel when say reading/writing files, so security frameworks could not be enforced. Something about auditd subsystem as well.

My take here - when working with stable system, changing OS once a several years (last one was when changing laptops basically, so 4+ years in my case), I don't care much on _single_ reboots. For those who tirelessly do distrohopping, things may look different of course.

for myself, I couldn't find good reasons to keep using WezTerm vs Windows Terminal - not saying WezTerm is not capable terminal, of course.

I was insulted as well - luckily just mental insult, assuming my age and the context of what's old and what's not :)

out of Slack and Mattermost, I'm not sure what I miss for work focused workflows - somehow Zulip writes in articles ( https://www.hostingadvice.com/blog/emerging-open-source-team... )it has threads, but both Slack and MM has it too.

Probably for "big community" things differ and make you like Zulip more? Or something else? I'm curious.

Mattermost works just fine being self-hosted and using push notifications

I agree with your view on this too (though I'm not fan of FreeBSD, quite opposite), OS doesn't seem relevant here much.

I do observe similar cases here and there, especially on "small" sized projects with Laravel/WPs - basically there is no one to say "hey guys, 20 years ago, the same type of load was working faster on my Dual Pentium 3 server with 512MB of RAM - what your code is really doing under the hood?"

interesting point, I think there is large chunk of truth in real life here.

stretching it a bit further, I can imagine things like "we've used the best clouds money can buy to run it fast, but task is soo complex, not every project can deal with such complexity, thus is current performance is at it's peak. Also, we used the best DX practices so all team members, while tired, do feel happy about projects progress".

> I have started using Alpine for servers - its small and fast.

I'm curious about "fast" here, as for "small" I don't care much - you mean benchmarks doing better on Alpine or fast in which terms?

FreeBSD is performing very well, kudos for such a small team delivering such great results!

Would be interesting to see ClearLinux compared too, especially on those tests where *BSD families are million miles ahead of Linux Kernel

we do use multiconnections when doing interviews - candidate solving test case on VM, interviewers are observing. Idea was not to confuse candidates by requiring screensharing during the interview, just see the particular ssh session.

> PostgreSQL can be protected against the OOM Killer in a more aggressive way with regard to Linux

Is it? What's "more aggressive" comparing to setting needed OOMScoreAdjust= in unit file, like "OOMScoreAdjust=-1000"

> Therefore, in order to protect the postmaster or any other PostgreSQL process, you need to manually use protect(1) as already shown. I am not sure if this is going to change in the future to allow the rc.d script to honor the oomprotect variable.

When/if FreeBSD one day will get good service manager, like systemd, I guess.

well, it's quite easy to evade - I've got new laptop recently and did RESET THIS PC couple of times, so my experience is less than 1 month old ;)

Thank you!

Sounds like something I should find project to play around with Swiftwave

If it's not a secret, what kind of activity requires having "many dozen" of key files - I currently have 3 of ssh keys and already thinking I'm doing things wrong, especially if more than 1 of them used for Github/Gitlab auths on different accounts - makes things quite messy for me.

Mind describing the case in bit more of details? I find that I can learn on interesting approaches, especially in cases where I cannot see direct benefits/use case - i.e. here I'm not sure why and even how I'd want docker-compose to be synced - I feel there is a hidden gem in your idea!

Thank you in advance!

I tend to agree with you - using in "default" setup with mod_php and mpm_prefork is known to be far from optimal (still fine for blog about you and your cat).

With reverse proxy in front of such setup is - much better in terms of performance. For shared hosting - yet again, may be not optimal if one needs to support multiple system users.

Thank you for clarification - makes a lot of sense what they state in that docs

> Why you shouldn't use mod_php with the prefork mpm anymore

>

> mod_php is loaded into every httpd process all the time. Even when httpd is serving static/non php content, that memory is in use.

> mod_php is not thread safe and forces you to stick with the prefork mpm (multi process, no threads), which is the slowest possible configuration

I probably very biased here - I silently imply it's a Nginx in front of Apache in 99.9% cases - so serving static files and long-living connections is not a problem with mpm_prefork [for setups and system administration around me].

Mind highlight differences/advantages over Dokku?

> An open source PAAS alternative to Heroku. > Dokku helps you build and manage the lifecycle of applications from building to scaling.

Good luck with your project!

I think that OP really meant that in his/her mental model of things, answers already known and battle tested for numerous cases [by using Nginx] - making HA with keepalived? Check. Making logging to be buffered to save iops? Check. Implementing ratelimits and custom logic? Check.

Keepalived is not really bound to Nginx by any means and should perfectly fine work with Caddy too.

Mind sharing bit more on this?

> because deploying Python/Diango is a mess (at least without docker)

I'm playing around with FastUI (disclosure - I'm not a programmer at all), so I'm in "day 0" position and would like to hear more on "day 1" side of things. Coming from Ansible side - it's easy peasy, just install things with pipenv and later `pipenv run ...`

> Unlike Laravel and Symfony, WordPress doesn't support the worker mode of FrankenPHP (yet?), so there are not many benefits in terms of performance (except the ability to preload assets using 103 Early Hints, which can reduce the latency of a page load by 30%).

This part is clear for me, but thank you for mentioning HTTP 103 too. I will not state for sure, but in my blurry memory, FPHP (FrankenPHP) was _slower_ than Apache+mod_php in that tests. But again, I won't say for sure, I just remember I was totally impressed as was expecting otherwise - much likely some subtle differences in setup on my side. If/when I have more precise info - I may ping you.

> That being said, FrankenPHP makes it easy to enable HTTP cache with WordPress and simplifies the deployment story. There is a dedicated project for WordPress and FrankenPHP, that comes with a built-in HTTP cache tailored for WordPress (using the Souin Go library): https://github.com/StephenMiracle/frankenwp

Thank you, have not seen that yet - may get idea or two from it. At glance, they just do naive `BYPASS_PATH_PREFIX` handling and that's all.

Beyond tests, I of course do prefer Nginx over Caddy and "simplifies the deployment story" doesn't resonate with my needs much yet - one of that things may change of course.