

I would recommand to never copy paste but retype so you have the commands on your finger memory.
Also don’t be afraid to --help
everything. It give more option for commands you know quicker than the man
.
I would recommand to never copy paste but retype so you have the commands on your finger memory.
Also don’t be afraid to --help
everything. It give more option for commands you know quicker than the man
.
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 !
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 ?
- 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.
- 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.0foo().unwrap_or(13.37)
to use your defaultfoo()?
to return with the error and let the parent handle it, maybeI’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 . 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 don’t know elvish, but I can’t get into nu
. It is too different than what I learned (bash
). I’m not sure I understand what they want to accomplish… Maybe I’m not the target, I use the shell to start commands as a dev, not as a devops or data guy…
I also had a hard time using fish
the first time I tried it. But since the version on Debian 10 I re-tried and now the only thing to know is “put the arguments in quotes if you want the command to do globbing”. With that you can use 99% of the commands you find on internet as is.
I used Kresus some times ago on a server. It was nice, but my bank don’t play nice and it is not my thing to manage like that.
It should auto import and… I did not follow developments so don’t remember the functionalities.
Did you tried UnCiv ? Feels like garbage to play to me. Maybe it is just too complete for my mobile game sessions… (And I don’t really like civilisation turn based games anymore.)
Mindustry (factorio like) plays badly on mobile (everything is too small, touch is not precise need to zoom a lot but you don’t see anything/can’t build long belt that way). But now I want to play it on PC.
On the other hand, Feudal Tactics is really nice to play on mobile.
From where are you downloading the app? I’ve read that either F-Droid reject Android-Auto because of binary blobs, or Google have some way of blocking non-approved builds (not from the playstore) in the car.
Edit: there is another Android-Auto thread.