angelsl

What do you mean "embedded in the core"?

All drivers are in-tree.

Sounds like arrogance... on the part of the interviewer.

You can really do photography on Linux nowadays though. Darktable and rawtherapee are shaping up nicely.

Oh no, Make 3.80...

Why not build a more recent version? This thing is 15 years old!

FreeBSD decided to just remove the Pale Moon branding.

Ugh. Another site that hijacks scrolling. Why?

It may be worth lodging a complaint with whatever authority your country may have against that doctor that dismissed the bullseye rash.

So now we need to invent something else to organise source code repositories?

The "improved" aka "less annoying" UAC that we have by default now is as good as no UAC [1].

[1]: https://blogs.msdn.microsoft.com/oldnewthing/20160816-00/?p=...

Your double space was collapsed by the browser.

Err, what? You can't get root access or escape a chroot from being able to read arbitrary memory.

Microcode updates are distributed as OS updates.

Says whom?

You mean enable KPTI.

No one's mentioned it yet, so I guess I'll be the one.

I can't tolerate that many misspelt words and grammatical errors...

You've totally missed the analogy. See pfranz's comment.

What?

He's just saying it's not that hard to determine the location of a chirping sound.

Not whether it's funny or not.

This is a Firefox issue, although uMatrix works fine on Windows for me.

Firefox limits the size of popups to 800x600 CSS pixels, which in theory should account for high DPI (are you using a high DPI display?).

Not sure what is going on here. What is your display resolution, zoom, and font size?

>> No iterator invalidation from iterators you get from it

> How are you guaranteeing this? C++ doesn't, so what is going on behind the scenes to make this work in Rust?

Rust's lifetimes.

This, exactly. What's so hard about one more command? If you really want a "save all" , just `git commit -a`.

This doesn't really have anything to do with *nix, but rather the customer being an idiot.

There are probably assumptions/invariants built into how rustc generates LLVM IR that you will have to guarantee are met if borrowck is disabled.

Do you really want that?

They are moving everyone else off so they themselves can move off XUL.

The point is that we fell for all of that.

You can get your own (or group's) chat ID with @get_id_bot, if you don't want to just get it yourself via `getUpdates`.

> Also, even if it were true, storing the actual passwords means that you have a single point of failure - if the password storage is compromised the whole thing is compromised.

How is your system different? If I get ahold of your master key, your entire thing is compromised.

> we only have limited resources

I understand, but I'm still disappointed. You all only needed to come to a decision on how you wanted to proceed with supporting the newer libraries required and I would have taken it from there. I'm not sure if you guys have even now come to a decision on that.

And it took a month before someone mentioned they would prefer if the KDBX 4 functionality was separated (and I do agree that it should be).

You could probably merge a similarly-sized patch into the kernel in less time...

That would be me.

I wrote the patch against the original KeePassX which seems to be no longer maintained (?). One of the KeePassXC guys asked me to rebase it over so I did. Then we (they) spent a week or two debating on how to support libargon2 and the newer libgcrypt required for ChaCha20, coming to no resolution, and I just lost any motivation to push for them to merge my patch.

They also disagreed with the way I implemented KDBX 4 (by adding conditionals to the KDBX reader/writer instead of just creating a whole new class — I did this because KeePass did it this way). I agree that it should be separated, but at that point I already gave up on getting them to accept my patch.

The PR is [here](https://github.com/keepassxreboot/keepassxc/pull/399), you can read it, I know I sound rather impatient here. The other PR on updating their Docker to get newer libraries (libargon2 and libgcrypt) is [here](https://github.com/keepassxreboot/keepassxc/pull/419).

I honestly thought someone else would take it up after I gave up to get it in by 2.2 (it's not even a very big patch), but.. I guess not.

Someone with more experience/patience/persistence, please, you can take the patch and rebase it and clean it up to what they want. You'll also need to wait for them to figure out how they want to use the libraries required with their packaging system.

No KDBX 4 support unfortunately.

Since when did writing a driver become the kernel maintainers' problem?

I don't think the AMDGPU driver not being mainlined really affects Linux. On the other hand, AMD will really benefit from it.