Assuming this is true (others have already addressed a few of the many reasons it might not be), wouldn't that imply that practically all existing tests are already flawed? If you want to grade on time, every exam should be graded with a formula taking both the time and the correctness into account. A binary "fast enough" vs "not fast enough" is about as useful as a pass/fail class grade.
The exams that felt like the fairest reflections of my own knowledge were proctored in-person, closed book, and time unlimited. Of course, being time unlimited works better for quantitative/engineering exams. I haven't put much thought into more qualitative/liberal arts type exams.
Not sure how often they update these pages, but Thunderbird is still listed as beta on matrix.org clients page [0], and I remember trying it out some time back and it was indeed very beta (maybe not even beta). It didn't feel like it was getting much maintenance so I stopped using it. I think it's fair to expect bugs in beta releases.
> I’m also tired of this mentality that nobody is allowed to talk about the problems with the product
I think there's a pretty big difference between constructive criticism vs statements like "The development team seems to not care". To me, it seems pretty clear that the team absolutely cares, but they are also a small and very underfunded team, and things take time. Assuming the worst intentions of a team is the problem and is disappointing to see here.
> I’ve given Matrix/Element an honest try many times because some of the OSS projects I’m involved with use it, but month after month it’s the most troublesome of all of the apps in this space that I use, and it’s not even close.
I don't doubt that, but it does not resonate with me. There have been a few hiccups over the years, eg the database corruption earlier this year (unrelated to the protocol or synapse) resulting in stuck invites, but overall I've had quite a good experience. Far less problems than Teams, and even slack has had issues (mainly, notifications not happening) that I have somehow avoided with Element, although I am aware others have had issues in this area. There are even some things I do with matrix that are simply not possible/practical with the others to begin with.
It worked for me on GrapheneOS for quite a while, but a couple months ago things started breaking and I no longer have it enabled. There's an absolute behemoth of a thread discussing the issue, and unfortunately it's still active which I assume means I'm not safe to enable it again yet. If you want some light reading to help put yourself to sleep: https://discuss.grapheneos.org/d/1353-using-rcs-with-google-...
I've heard good things about "LLVM Techniques, Tips, and Best Practices" [0] but haven't gotten around to reading it myself yet. Packt does not always have the best reputation but it was recommended to me by someone I know and the reviews are also solid, so mentioning in case it's at all helpful.
> I don't think run0 uses the same configuration syntax as sudo, so it's a no-go from the start.
This is ubuntu, purportedly targeting ease of use, good defaults, and new Linux users. How many Linux newbies are running with custom sudo configurations? By definition, basically none, and of those who do, it's only for passwordless sudo, which I assume can be trivially recreated in run0. For advanced or enterprise users, it is not difficult to install sudo manually or port their configuration over to run0.
> This resistance, IMHO, is moot anyways since the sudo maintainer himself is in support of sudo-rs and actually helped the project in a consultancy capacity (as opposed to directly contributing code).
I'm not categorically against sudo-rs, but use the tool for the job. If all you need is a simple way to get root privilege, sudo is overkill.
> I'm not sure LP is a high-quality source. He has reputation that makes me want to listen to everyone else but him.
Based off his reputation, I would agree, but after reading a lot of his own words via blog posts, comments in github issues, etc, I wonder how he gained that reputation. He has solid reasoning behind many of his ideas even if you disagree with them, and his comments seem pretty respectful and focused on the technical aspects. Maybe things were different in the past, or maybe some segments of the community just never forgave him for the early buggy systemd implementations, or maybe I just happened to only read things he wrote when he wasn't having a bad day, who knows.
Yes, if you ignore all the bugs resulting from features that almost nobody uses.
> along with the rest of the systemd abominations
Not too interested in engaging systemd debates. I have enjoyed using systems with and without systemd, and while I understand the arguments against feature creep, I think you'd be throwing the banana out with the peel to overlook the idea behind run0.
For such a security sensitive piece of software like sudo, reducing complexity is one of the best ways to prevent logic bugs (which, as you mentioned in the sibling, is what the above bug was). If run0 can remove a bunch of unused features that are increasing complexity without any benefit, that's a win to me. Or if you don't like systemd, doas on OpenBSD is probably right up your alley with a similar(ish) philosophy.
> People start making sudo more secure by replacing it with sudo-rs
I would have much preferred if ubuntu went with run0 as the default instead of trying to rewrite sudo in rust. I like rust but the approach seems wrong from the beginning to me. The vast majority of sudo usecases are covered in run0 in a much simpler way, and many of the sudo bugs come from the complex configurations it supports (not to mention a poorly configured sudo, which is also a security hazard and quite easy to do). Let people who need sudo install and configure it for themselves, but make something simple the default, especially for a beginner distro like ubuntu.
Agree, Naver maps for navigating public transit in Seoul is excellent. Easier to figure out than public transit in any American city I've been to and I don't read or speak Korean. iirc it even tells the fastest routes/best carriage to be on to optimize transferring between lines.
I tend to like smaller phones as well, but even comparing the Pixel 9 Pro vs Pixel 9 Pro XL used markets, it seems really hard to find non-XL versions. I would totally believe that the XL is a far more popular model, unfortunately for the rest of us.
fwiw, installing GrapheneOS is by far the easiest phone OS install I've ever done. It's been a while but if there were any hiccups, they were too small to remember. My memory is just plug it into desktop with usb-c cable, go to grapheneos website in chromium (it uses web usb so no firefox), hit the install button, and wait a couple minutes.
And yes, it allows you to disable network permissions for apps, among many other nice things.
Sorry, I don't always see replies immediately. Yeah you can take a look at mine, it's somewhat customized so I'm not sure how useful it will be and I don't have time to add comments, but I've uploaded it to https://pastebin.com/zM2bYHD2
The big thing this might be missing from your perspective is I don't usually have multiple tmux (or wezterm) sessions going on simultaneously. Not sure if or how that influences the wezterm side of things.
Sure, but as long as the fallback for account recovery is sending a reset email or sms (both of which are similar or worse than yoloing textfiles on dropboxes), that's a very tough argument to make in good faith.
When I first tried to port my tmux config to wezterm it took about a day to learn about all the wezterm concepts, map them to their tmux equivalents, and reach an mvp. I tend to be on the slower side to pick things up though.
Locally - I far prefer wezterm now. The only issue for me was that getting persistent server side sessions seemed to come at the cost of some weird neovim gui refresh and latency issues which I'm not sure are fully solved yet, so I still use tmux for that. Looking at the issue tracker, maybe I should try again, seems that at least some refresh issues have been addressed since I last checked https://github.com/wezterm/wezterm/issues/4607
> Comparing sudo <bash script> to any Windows install is 30+ years out of date. sudo can access almost all memory, raw device access, and anywhere on disk.
They didn't say anything about sudo, so assuming global filesystem/memory/device/etc access is not really a fair comparison. Many installers that come as bash scripts don't require root. There are definitely times I examine installer scripts before running them, and sudo is a pretty big determining factor in how much examination an installer will get from me (other factors include the reputation of the project, past personal experience with it, whether I'm running it in a vm or container already, how I feel on the day, etc).
Not sure if there are true heterogeneous server CPUs or not, but with Intel Speed Select Technology (SST) you can mimic some similar features. SST allows you to set some cores to be higher base frequency, turbo frequency, etc, in return for other cores having corresponding lower frequencies. Naturally, the cores are not inherently different here, it's just distributing the power/thermal loads differently, so it's not a true heterogeneous system.
I don't think that is normal, at least I've never had any client take that long to load, and nobody I communicate with on matrix has ever mentioned that as being an issue either.
I think this is a pretty fair summary. I've been using matrix since before the patreon was started and it's gotten a whole lot better for sure, but there is still no single client that does everything. Element X is right out since it doesn't support spaces yet. SchildiChat next comes close for me, but it can't edit room topics, pinned messages can get a bit weird once you start editing them, and I have a few invites to some pretty nasty looking spam dms that I can't delete, so there are still some rough edges.
On the desktop side, if there were a client as good as SchildiChat maybe that would work, but last time I tried one of the Element desktop clients I wasn't even able to log in (it either crashed or hung, can't remember), and most of the time I'm fine with Fractal anyway. Fractal is actually a very nice client for what it does, it just has a limited feature set: missing spaces, copy/paste doesn't quite work like you'd expect, no search (I'm not sure there are any clients with fully functioning search for encrypted rooms), and my memory is that heic image previews weren't supported. I can fall back to nheko for some of the other things when needed.
As far as I know, there aren't any clients that support the new element call unless you enable the labs feature in element x.
All that said, I can't overstate how much I appreciate all the work the matrix devs do, and it is still fine for my daily use. Even if I sometimes disagree with Arathorn's conclusions about how ready matrix is, I have to appreciate the optimism and I imagine it is part of why he's been able to continue through all the negativity :) and it's not entirely wrong to say that matrix beats the competition - I'd say it easily beats teams and imessage (teams does not deserve to be mentioned in the same sentence as anything else), and it is mostly comparable with messenger and whatsapp. Slack probably has it slightly beat, and discord is leagues ahead of everything else.
Assuming this is true (others have already addressed a few of the many reasons it might not be), wouldn't that imply that practically all existing tests are already flawed? If you want to grade on time, every exam should be graded with a formula taking both the time and the correctness into account. A binary "fast enough" vs "not fast enough" is about as useful as a pass/fail class grade.
The exams that felt like the fairest reflections of my own knowledge were proctored in-person, closed book, and time unlimited. Of course, being time unlimited works better for quantitative/engineering exams. I haven't put much thought into more qualitative/liberal arts type exams.