Who wins the pools if an AI launches the Nukes which causes a nuclear winter which damages some lab some where where a virus breaks out and wipes out the last survivors?
That beaker does not look half full to me. Many like 1/3rd full, or at least somewhere between that and half full.
So someone that is not involved in rust at all and does not seem to like the language thinks it will get a GC at some point? That is not a very credible source for such a statement. Rust is very unlikely to see an official GC anytime soon if ever. There are zero signs it will ever get one. There was a lot of serious talk about it before 1.0 days - but never made it into the language. Similar to green threads which was a feature of the language pre 1.0 days but dropped before the 1.0 release. Rust really wants to have a no required runtime and leans heavy on the zero-cost abstractions for things. Which a GC would impose on the language.
And other browsers can be configured to do the same. Though that is not ublock origin doing anything with the cookies and these settings can be enabled wtihout ublock (though you likely want ublock if you are enabling them).
That is and big if though. Yeah you, me and half the people here might leave over this, but we block ads already and so are not highly valued to YouTube or a lot of the creators and are only a small drop in the ocean of viewers.
YouTube is betting on more people turning off ad blockers then those that leave. And i am glad to see that it might be having a small effect on more people actually discovering ad blockers instead. Which I bet is something YouTube did not expect to see.
I’m still forgetting things I learned 3 or even 4 times like how to do a for each loop.
I have been programming for decades now and still have to look up how an if statement works in bash - or other similar things, especially when switching between languages. It takes 5 seconds to look up and remember so I would not bother worrying about it. Far better to know when you need to use an if or for loop and quickly look up the syntax then to know the syntax but not when to use it.
I see tutorials say to make a tic tac toe game or a calculator or to contribute to open source code. Which is good I suppose but all of it feels too advanced and I get lost on how to begin.
Break problems down into simpler problems, then break those down into simpler problems until you have a trivial problem you can solve. Then build up from there. Like take a tic tac toe game - lots of things to consider that can all be dealt with in isolation. Like rendering the game to the screen, that is one problem you can start with, and can be broken down even further to maybe how to draw a grid to the screen, which again can be broken down to how to draw a box or line.
You might even want to look at the book " Think Like a Programmer: An Introduction to Creative Problem Solving by V. Anton Spraul" which goes into this way of thinking in more detail.
At thins point I am starting to think they are more pro-suffering
No it is not ment to be empty. You will need to reinstall it to fix that.
pacnew files are created when the package has changed it, but so have you. So you would replace it only if you don't care about the changes you have locally. Otherwise you likely want to diff them and manually merge in any new changes to the config. Generally speaking most should not make your system unbootable, but I would look more closely at any core system files and see what the changes are rather then just blindly accepting them. Even if you do that for less critical packages.
I think the big contention comes with touchpads. They are half way between a mouse and a touch screen. Traditionally they acted like mice, you two finger down to scroll down like on a mouse wheel - but you have no wheel so are directly touching the surface. Much more like a touchscreen.
So to me traditional feels natural to me on a actual mouse, but on a trackpad natural feels more natural. I really hate that on the Mac you can only set all mouse life devices one way and not be able to have actual mice behave different to trackpads like I can on Linux systems.
Some things are very easy to do in loosly typed languages - just as letting a function take a string or int, and then parsing that string into an int if a string was passed in. In a loosly typed language you can just call something like if typeof(input) but in a strongly typed language you often need a lot more boiler plate and extra wrapper types to say the function can only take an int or string - for instance in rust you might need to wrap them in a enum first or some how create a trait and implement that for each types.
This is quite a bit of extra upfront cost some of the time that really rubs people that are used to loosly typed languages the wrong way. So they think it is slow to work with types. But what they never seem to count is the countless hours you save knowing that when you read a value from something and pass it to a function that wants only an int, that the value is an int and you dont end up getting 2 + "2" = "22" and other suprising bugs in your program. Which results in less time debugging and writing tests for weird cases the compiler does not allow.
But all that extra time if often not counted as that is dissociated from the original problem at hand. And they are already used to this cost - people often notice a new cost, but don't notice a possibly bigger saving else where.
nous
0 post score0 comment score
Also worth pointing out: