FizzyOrange

To be honest I suspect they wanted to do this before, but the power mods wouldn't allow it. I definitely remember the staff posting a proposal to allow second chances for closed questions, and it was downvoted to hell by the mods. They presumably got scared because they were getting a lot of free labour from the mods (even if it probably wasn't exactly the kind they wanted).

Now StackOverflow is dead the mods have no power, so they are free to make changes.

The company is going forward with it because the "active community" killed their site and now they have no choice.

If they had done it before AI became a viable alternative they might still have some users.

I would say it maybe makes sense to do that for team based projects so your TODOs don't impact other people finding new warnings in their code.

For solo projects I don't think that makes any sense.

Deno is great. The best way to write web site and static sites IMO. I really hope they survive.

recent addition of opinion based questions, as well as the upcoming removal of close votes

lol they had at least a decade to do this, and they're finally doing this after they're well and truly dead. Fuck them.

Not the great rebuttal you think it is... AI isn't really about writing code that I couldn't write. Unless you're a beginner it is absolutely not at that level yet. It's about saving time.

Which it definitely can do. Especially for one-off tasks. For vibe coding projects my experience has been mixed. AI seems pretty good for getting things going, especially in areas you aren't familiar with (e.g. I wrote a simple Chrome extension with it; never written a Chrome extension before). But after a certain point they seem to get stuck in a muddle and you basically have to stop using AI, fix all the code it wrote badly and continue yourself.

But overall it can still be significantly faster than being prideful and doing it all by hand.

Yes if you don't get a real GUI you'll end up using this poor-man's imitation a lot.

I found this one recently which is really good:

https://github.com/sourcegit-scm/sourcegit

Much better than most of the standalone Git GUIs, even the commercial ones.

However I don't actually use it, because I use VSCode and there's a great extensions called Git Graph that integrates nicely into it. It is abandoned unfortunately but it still works fine so I still use it.

Here's my rating of all the Git GUIs I've tried (that I remember):

• SourceTree: works ok but just so incredibly slow.
• GitKraken, SmartGit, Tower, Sublime Merge: Commercial and I don't like the UX of any of these.
• Git Extensions: This one is actually really good. Terrible name though. Also kind of Windows-only.
• GitX: This is also really good but unfortunately it's one of those pieces of software that has forked into dozens of half maintained versions that you'll need to spend hours in phpBB forums figuring out which one to use (like TomatoUSB). Also Mac only.

I never tried Magit because TUIs are dumb.

Also don't listen to anyone that says "just use the CLI". It's okay once you've learnt how git works, but even then you're still going to want a way to view the commit graph. Learning Git without a GUI is needlessly masochistic. Once you have learnt it you can start mixing it up with the CLI.

He also thought that Rust integrates poorly into project with a deep C++ OOP hierarchy. That is probably still true as well.

Is there any language that can do that? As far as I know there isn't. You can use SWIG or whatever but it's just as awful as any Rust/C++ interop. There's Carbon, but that's a work in progress.

IMO if you need integration with a deep C++ OOP hierarchy your options are a) give up and just use C++, or b) pain, no matter what language you target.

The connection column indicates the connection used. USB FS stands for the usb full speed protocol, which allows up to 1000Hz polling, a feature commonly advertised by high-end keyboards. USB is the usb low speed protocol, which is the protocol most keyboards use.

USB Low Speed allows 1kHz polling too. I don't think you gain anything at all from High Speed. Keyboards probably only use it incidentally because the chip they are using happens to support it anyway.

Huh I was under the impression that you could limit it to specific applications and dbus would tell kwallet the path of the application making the request (which could be done at least vaguely securely). But upon further investigation it just uses the "appid" that the app reports which it can apparently set to anything it wants. It's difficult to find information about this stuff though. D-bus is not very well documented at all.

Interesting how do you do that exactly?

I was thinking you can just start the app that has permission to read the wallet, attach a debugger and then inject code to dump the wallet. It's definitely more complicated than reading a plain text file but not fundamentally less possible.

But really if you have that level of access it's game over anyway and you just MitM sudo and get root access, or use one of the many local privilege escalation vulnerabilities and get root immediately.