Yes. I talked about screenshots because the first message said:

I can't see any screenshots from the article, all require a bluesky account. At least on twitter you could see images without login before the takeover.

For "text source only" I'm with you quotes are enough.

And if images are post anywhere, always provide an alt text, plz everyone !

I don't say "remove the source", I say "the source can disappear, the way back machine have already been attacked, just do your own copy of the source and make it available".

I know screenshots can be faked, but if your news source does it it is not reliable. Drop it immediately.

Source can be destroyed. An alternative screenshoot backup/proof is good measure. Especially in web its better to not depend on an outside server.

Like if they close (or some billionaire buy them and requires an account for everything), your content becomes worthless.

XR?

I'm with the others: fd default syntax is easier to remember.

And for the interactive search I'm using skim. With it I cd to the dir I want and Alt t to trigger fuzzy finding. There are also bindings to search for dir or in the history. The neat part is that results are inserted as is in the command line, no need to xargs or copy them. It also make the history look like I always know where the files I want are when in reality they are just fuzzy-found

First time I hear about checked exceptions. How do you use them ? Are you forced to handle them explicitly ? Is the handling checked at compile time ?

3. Is a modern language with a good build system (It's like night and day compared to CMake)

Meson exists ... as do others.

But they are not the default option. And your new job may not use them.

4. And I just like how the language works (errors as values etc.)

Fair enough; though why? What's wrong with exceptions?

Exceptions is a non standard exit point. And by "non standard" I'm not talking about the language but about its surprise appearance not specified in the prototype. Calling double foo(); you don't know if you should try/catch it, against which exceptions, is it an internal function that may throw 10 level deep ?

By contrast fn foo() -> Result<f64, Error> in rRst tell you the function may fail. You can inspect the error type if you want to handle it. But the true power of Result in Rust (and Option) is that you have a lot of ergonomic ways to handle the bad case and you are forced to plan for it so you cannot use a bad value thinking it's good:

• foo().unwrap() panic in case of error (see also expect)
• foo().unwrap_or_default() to ignore the error and continue the happy path with 0.0
• foo().unwrap_or(13.37) to use your default
• foo()? to return with the error and let the parent handle it, maybe

I'm using helix with arrows. On a standard layout its not so great, but on my main keyboard I have a layer with arrow keys near hjkl. So I can use that on all software even on my BÉPO (DVORAC like) layout.

From the article's own summary.

False Load Output Prediction and Speculative Load Address Prediction allow for data leaks without malware infection

But I guess "IA summary" did its best ¯(ツ)/¯

Why should I use a sudo alternative?

-g is not documented, what does it do?

Note: this made me discover topless (SFW) and its Caveat section.

From your example, I have a hard time inferring what is it doing.

--single-branch

neither strictly nor strictly typed.

I think one of them should be "strongly", but I understood your point.

Thinking back, I don't have the doc easily accessible (on phone), but I think the C API state the type you want to read. Like get_int(smt, VALUE_INDEX, …), so at least in the C API, most of this should not be visible. Maybe only the SELECT 1 = '1' part (or others comparaison fully done in the SQL string)?

But they silently converted the string '1' into the number 1. So now in my same code, I want to select back my stringy '1' that I putted in the type affined INTEGER column.

And you are telling me its normal that I don't get it back ? Or maybe I'm misunderstanding something?

Most of the time the fix is: put quotes around your strings (especially when they may contains globing patterns). Sometimes its using newer syntax available in bash but not on the snippet.

I only have to "quotes" strings that contains globs. The rest mostly work or use the newer/recommanded way to do things for posix shells.

But I must admit, I only use it interactively. For scripts I #!/bin/{,ba}sh. I will use something else once it won some/most the distro preinstalls (either nu, elvish, fish, but for now it's sadly python).

Thanks to valve/proton, the biggest issue for playing on linux nowadays is the kernel level anti-cheat they force on some competitive games.

Other than that most of the games just work, especially if they were made in a common engine (godot, unity, ue, …)

The only AAA I play are Nintendo ones (and RTS/MOBA since its a niche genre and you need a community for PvP). Since quite some times already. But I only look out for indies, I love getting new experiences and gameplay.

And even when the gameplay is not new, the attention to details (gameplay wise) is at 1000% only on indies (Celeste, Hollow knight, Factorio, …)

I think some peoples developped an allergy to projects being (re-)written in rust. Not sure why.