Mine sure has it enabled. Been using RCS for years. Will lookup my brother’s, but I thought we were already past that phase
I tried to RCS with my brother today (iPhone user). I told him to set it up properly and… It didn’t work. SMS are still sent.
They won’t. They’ll just substitute them. The idea is trying to force every company do the same thing, as making people work locally makes them more dependent on their local company and less likely to jump to a better job.
Then you can lower salaries (not rise them) and destroy benefits. Also you can enforce dress codes to make it look like a dictatorship country like North Korea.
Is that American hand writing? It reminds me so much of James Hetfield’s, and basically no one writes like that in my country.
I’ll laugh so hard when “square-everything” is made cool again by Apple and millions of developer hours will be trashed.
The sad part will be that in another 5 years people will have to develop rounded corners from scratch again. Capitalism.
Arch Linux. All the software at their latest version (which is usually the best one), within a couple of commands, either from the huge official repos or the AUR.
One of the reasons surely is that it’s getting banned from government software 😅
In my experience (not in Android apps but in Arch Linux updates) parallel downloads are almost always waaay faster. Magnitudes faster. Using multiple cores? Is it the bottleneck actually enforced by the server? I don’t know, I just know it works.
And if they did it, it’s because it works on Android too.
¿Por qué solo tres?
3 years only
Or you can preinstall micro
like you preinstall everything else 😅
And all the shortcuts are SANE, not the weird thing of nano
In every post of this kind I am amazed at so many people using nano
instead of micro
which is SO MUCH BETTER while being the same thing at the same time.
I am a fan of Python’s or Rust’s official conventions.
For package names, tho, I don’t get why this-is-used over this_clearly_better_system, as I would expect a double click to select_the_whole_thing, whereas it does-not-happen-here.
It’s really so sad to see how marketing alone can shape the landscape even when they 🍎 are scamming their users so hard.
It is a project! All games are, 😅, just follow the instructions from the README. You’ll be solving Rust exercises on your preferred editor, and get some feedback from a terminal window. It’s great.
The thing is that, in C the API could be slightly different and you could get terrible crashes, for example because certain variables were freed at different times, etc.
In Rust that is literally impossible to happen unless you (very extremely rarely) need to do something unsafe, which is explicitly marked as such and will never surprise you with an unexpected crash.
Everything is so strongly typed that if it compiles… It will run without unexpected crashes. That’s the difference with C code, and that’s why Rust is said to be safe. Memory leaks, etc, are virtually impossible.
Everything is better in Rust. Faster, safer… And also the developer experience is amazing with cargo.
The problem here is not Rust, it’s the humans, it seems.
The dependencies are set manually, of course, and the dev was enforcing something too strict, it seems, and that is causing headaches.
But, as the debian dude has learned… Rust programs will 99.999 % work if they can be compiled.
I just wish every programmer completed the rustlings
game/tutorial. Doesn’t take that long.
I didn’t even fully complete it, and it made me a way better programmer, because it forces you to think RIGHT.
It may sound weird for people who haven’t experienced it, but it’s amazing when you get angry at the compiler and you realise… It is right, and you were doing something that could f*ck you up 2 months in the future.
And after a bit of practise, it starts wiring your brain differently, and now my Python code looks so much better and it’s way more safe just because of those days playing around in rustlings
.
So yeah, Rust is an amazing language for everything, but particularly for kernel development. Either Linux implements it, or it’ll probably die in 30 years and get replaced with a modern Rust kernel (Redox OS?).
What should I put in the
<command>
part?