Zykino

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?

Collecting the traces can cost some performance, but that is a small price to pay for the advantages and could even be turned off in production builds.

They clearly intend this post for developers.

But yeah I want my stacktraces… in my IDE/debugger where I can see them and jump the stack. Most of the time I just need the head, where the breakpoint (or crash) is.

They also complain about rust where you can RUST_BACKTRACE=1 <program>. The default error tells you so !

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

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 ¯\_(ツ)_/¯

I'm on Linux and a prebuit PC would be a nice change. But at the same price or lower than Windaube, since I don't want a licence for them.

I will prefer to build myself rather than paying an extra k…

Apparently stow -t exist too.

1. You need a license
2. usage should just be help (avoid extra step)
3. connect does not exist (see add and cmd list)
4. You can git clone <REPO> <DEST FOLDER>, no need to cd
5. maybeCreateDir is not used each time, there are some mkdir
6. "changes" is not a helpfull commit message. Accept an optional argument string and {MESSAGE:=change}
7. Accept a different repo path
8. set -euxo pipefail at the start of the script if you want to exit at any error. Some sort of bash strict mode
9. shellcheck does not like iterating over ls's output

I'm too lazy to open issues/PR for all that, and I still need to learn stow. Hopfully this might help me ? (I don't really need help with git that this sçript look to abstract too much for me.)

Thanks. I think your message is not very clear at first (since I did not know about "nav mesh"). But reading Wikipedia is clear now. It also helped me find the official page (added the link in the post).

La faute à qui ? Qui aurait pu prévoir que le groupe présidentiel ne retrouverait pas la majorité au lendemain des européenes ?