the Rust book
Do you mean this? https://doc.rust-lang.org/book/
I actually started with that, but somehow redirected to "Rust by Example" and realise they were different, probably because of the same domain name and theme.
Now I see, they did start with explaining ownership, which is one of the things I felt that i was missing, when I started moving forward in "Rust by Example". Thanks for putting me back on track.
Well, when I can just do $EDITOR file...
Those space construction startups know what they’re doing. They’re selling billionaires a bridge to nowhere; and it’s working.
Guess I should have gone CHA instead of INT.
I might have gotten some of that billionaire money to buy more RAM.
Any specific reason for the 2 separate engines?
What's the advantage?
All I can think of is that you might be running a much lower powered, single engine when not in 4WD mode.
A Gnoming wheel?
I'd say:
Except that that's hard to happen.
The very existence of an ultra-rich means that there was someone who managed to get extraordinarily high amounts of extra value from someone as compared to what they paid that 'one' for it and then did it over and over again, essentially leeching value out of the system, making it a -ive sum game for anyone inside it.
So when you take more than you give, you end up breaking the original meaning of money (that was "proof of work/goodwill") and when you do that enough, the worth of work gets warped and those who do similar work, end up indirectly losing more than what they give.
And for those who might not have noticed
There is 10 words in the prompt.
Might not be "willing", but just going, "oh it's fine. What's the worst that could happen".
Also, I failed to understand how Claude code generated another response after deleting the Claude credentials. Does it save the token in RAM?
I find it really hard to relate to people not liking Qt Documentation.
Specially if you use qtcreator, you get to simply F1 any Qt class and you are sent straight to the documentation specific to that thingy.
Then there are cases where on top of normally telling what a function does, the docs also give an idea about the performance considerations, other than just the space/time complexity.
Granted there are some gaps when doing more advanced things like sub-classing an item-delegate, but:
Of course, if you just want to download an older version of Qt, like 5.14 and use QML with it, you are in for a task.
Also, you are expected to understand C++ concepts before starting Qt, because that's not what its docs are intended to teach you.
P.S.: a lot of the phrases are intended for those who found the Qt Docs "awful"
+1 for being the kind of guy that goes to a Windows problem thread and suggests installing Linux (I have done that just for fun), but for Rust.
I am currently learning Rust in my freer time and found "Rust by Example" not as appealing.
For context, I learnt C when I was a kid, following "Programming with C - Schaum Series" and loved how it started by giving an idea of the memory representation for all data structures the way it is abstracted (or not so much) in C. Later in Uni, I hated "Let us C" (even though it seemed to do a similar thing at a glance) and "Let us C++" and just learnt the languages on the go as required by courses and projects (also simply used a C++ reference book instead of a course styled one).
Now I see "Rust by Example" and see some parts not having been explained in the beginning, for which I would have to open the link to a section, much further ahead (it probably is not a course styled thingy). I will end up learning it, given time, but is there some material available that has a similar approach to introducing programming with Rust as the Schaum Series one was for C?
Oh I get it now.
Also, for some reason setting
vias$EDITOR, it is not able to load the contents of the file, unlikevimthat does.