Personally I want as little code in between my hardware source of random numbers and my running application. That's why we made the random number instructions in Intel CPUs, rather than devices needing a device driver.
@@davidjohnston4240 just pull a random number from the temp sensor and compare to the Johnson noise 🤣 Sorry...still mad that my wife made me bust my sandy bridge cpu...
I think this generator is absolutely not recommended to use normally. Random device is a "real" random number generator, which means that does not follow a certain algorithm, but rather takes some variables from the system that are actually random and gives a number back. However, it can be terribly slow (the term people use is "running out of entropy", which causes the system to wait for some time until more is somehow created) and I do not think the quality of the numbers is guaranteed. Instead use it only for the seed of an actual pseudo random number generator, like std::mt19937, which is incredibly fast and the numbers are good for a ridiculous amount of time. An example would be: std::random_device rd; std::mt19937 generator(rd()); std::uniform_real_distribution dist(0.0, 1.0); std::cout
@@TheBuilder mt19937 is not cryptographically secure. Do not use it for any secure purpose like generating keys or DH or RSA. mt19937 is also not very good compared to state of the art non cryptographic, uniform generators like PGCs.
@@davidjohnston4240 on an x86 CPU AES is pretty darn fast, have not tested how it compares to the mersenne twister, but you can use that as a secure PRNG
@@StefanoTrevisani You can use the AES instructions in an RNG construction, like CTR-DRBG and it will usually be faster in a single thread than RdRand and always faster than RdSeed. With multiple threads, the AES instructions are always faster, because the is one lump of AES hardware for each core so it scales linearly while there is only one entropy source serving all the cores. However the AES instructions do not bring any entropy to the party. You need hardware specifically designed to do that and RdSeed is the instruction for that. There are libraries (E.G. in nginx) that seed from RdSeed and run parallel SW PRNGs using the AES instructions to get the fastest possible random number supply for SSL per-packet nonces.
@@davidjohnston4240 oh right the rdrand instruction. I don't know why but I bursted down laughing when I first found out about it. I was like "mmm x86 has a lot of cool instructions, like AVX permutations and so on, let's see if there's something for RNG" and of course there was 😂 I was like "wow assembly nowadays is the highest lever language, it has routines for RNG, for AES, for SHA, basically everything you would need an external library or to implement yourself is already available in there 😂"
Back when I used to do C++ for uni projects, I had implemented two very simple texture generation algorithms for an OpenGL game we were making (I only worked on the algorithm side of things). Working with the random library was a delight. It's one of the very few things in C++ that don't have any major hidden pitfalls (for my personal usecases). Coding in C++ feels really empowering when the batteries-included-ness of the stdlib kicks in. I'm trying to migrate to Rust these days and it feels kinda bittersweet to leave C++ behind.
this is way better than my solution, which was to make a deck of cards and then use 1+rand(time(0))%2 to basically get a coin flip, if its 1 it goes i cut it from the list and put it in the front if its 2 it gets cut from the list and put at the end, then i run that 200 times and get what seems to be random
I am in C++ for 30 years and I think the C rand() function is just fine for some uses. Yes, it is "bad" in terms of true randomness, but it can be still useful from time to time for simple things, where puristic randomness is not needed.
Thank you! Subscribed. Hope you one day do a vid on a random in a range but with a bias towards a value and maybe a way to control the strength of that bias
Thanks for the video. I am also getting the same number everytime, even using the exact same code shown in 3:25. The srand is deleted by this point, by which I understand that there is no need to update/change the seed. Thanks for your answer.
very informative video btw but quick question, how to set range of random numbers that are generated in an output lets say my random generator displayed a generated numbers of 78934561 but i want to set a range of only 4 numbers which is 7893. what line of code should i input?
@@TheBuilder nullptr uniform distribution vector iota. PS i like to understand everything in my code and its hard when youre a bigginer to know what "nullptr" means
Im getting some error that std::ranges has not been declared even though i did the #include thing correctly. Also, just started today, why arent we using std namespace here? isn't it always more convenient to do that?
you should be passing NULL into srand. nullptr is a C++ value of nullptr_t type. Sure, they're virtually always going to equate to the same zero rvalue, but the definitions could be changed and then you'd break functionality. So while it may seem correct or convenient to pass nullptr into C functions from C++, you should abide by the defined interface.
Ok Help!!! Newbie here! Used the Uniform distribution for random generated number in a function, but I need that number for a "Nested For Loop"; for 1 to the (generated number). Getting a error code of no conversion possible to make the randomize number into a integer. How do I get the " dist(rd)" (generated number) converted to a number for use in a "for loop"??
@@TheBuilder in the title you tell to stop using rand, and in the video you give alternatives to it, but you didn't explain why should we use these alternatives instead of rand in the first place
@@o0jjc951 I did, though it is irrelevant because this result happens because this guy didn't do it even properly you need to add "srand(time(NULL));" at the beginning to make the seed of your random generator be dependent of the current time so you get different results everytime but mere seconds later, he did add it later on and it did work, so where's the problem with the rand function? you are the one who didn't watch a minute of the video bro And what does he say next? "the problem is that ti's too simple and not flexible enough" just WHAT?? It's too simple?? And not flexible enough?? It's a random number generator bro, what flexibility do you need???
hmmm... I think you didn't understood that there are different RNG needed. There are a lot of programms that highly need always the same random numbers. So setting a seed is not a bug, setting a seed is a feature for them. First of all you need to think about what RNG do you need. Always the same? Always differnt? cryptographically secure? Does it need to pass special test? Do you need them fast? How many so you need? ... Depending on your answers you need to use different random number generators.
generally its too simple for most tasks. you can read this reply, its fairly complete stackoverflow.com/questions/52869166/why-is-the-use-of-rand-considered-bad
@@TheBuilder I read it. As you can see there are many pro and cons for rand() in that stackoverflow articel. In your video you selected only one argument, but that argument is depeding on your coding task. So you selected a "wrong" argument. In my opinion there is only one (strong) argument against rand(): rand() is an unspecified algorithm (So every operating system/compiler implemented it's own version. So you don't know what you get! (So in fact this is nearly the opposite of what you demonstrate in your video)
@@TheBuilder Yes, it is not recommended, but in your video your argumentation is totaly wrong. If beginners watch your video, then they will totally missunderstand why it is not recommended. In fact you explain the opposite in your video. rand is not recommended, because users expect always the same random numbers, but as soon as there is a new compiler or and other operation system they migth get other numbers.
@@coe9900 for linux/unix systems, just read from /dev/urandom or /dev/random. For Windows, use CryptGenRandom. Just don't use time() for random seed as it's predictable
How many libraries do you need to make a random number generator?
C++: YES!
Personally I want as little code in between my hardware source of random numbers and my running application. That's why we made the random number instructions in Intel CPUs, rather than devices needing a device driver.
@@davidjohnston4240 just pull a random number from the temp sensor and compare to the Johnson noise 🤣
Sorry...still mad that my wife made me bust my sandy bridge cpu...
Bro, you can't go out of your way and tell people to stop using some function that everyone uses if you're using light mode
ye lol
W
Yes he can. Enjoy being an individual with weak beta eyes. While us Chads program using light theme with our eyes capable of handling the intensity.
grow up
dark mode is for discord losers that never go outside, thus weak eyes.
light mode is for codeblocks chads that love nature.
I think this generator is absolutely not recommended to use normally. Random device is a "real" random number generator, which means that does not follow a certain algorithm, but rather takes some variables from the system that are actually random and gives a number back. However, it can be terribly slow (the term people use is "running out of entropy", which causes the system to wait for some time until more is somehow created) and I do not think the quality of the numbers is guaranteed.
Instead use it only for the seed of an actual pseudo random number generator, like std::mt19937, which is incredibly fast and the numbers are good for a ridiculous amount of time. An example would be:
std::random_device rd;
std::mt19937 generator(rd());
std::uniform_real_distribution dist(0.0, 1.0);
std::cout
Good tip
@@TheBuilder mt19937 is not cryptographically secure. Do not use it for any secure purpose like generating keys or DH or RSA. mt19937 is also not very good compared to state of the art non cryptographic, uniform generators like PGCs.
@@davidjohnston4240 on an x86 CPU AES is pretty darn fast, have not tested how it compares to the mersenne twister, but you can use that as a secure PRNG
@@StefanoTrevisani You can use the AES instructions in an RNG construction, like CTR-DRBG and it will usually be faster in a single thread than RdRand and always faster than RdSeed. With multiple threads, the AES instructions are always faster, because the is one lump of AES hardware for each core so it scales linearly while there is only one entropy source serving all the cores. However the AES instructions do not bring any entropy to the party. You need hardware specifically designed to do that and RdSeed is the instruction for that. There are libraries (E.G. in nginx) that seed from RdSeed and run parallel SW PRNGs using the AES instructions to get the fastest possible random number supply for SSL per-packet nonces.
@@davidjohnston4240 oh right the rdrand instruction. I don't know why but I bursted down laughing when I first found out about it. I was like "mmm x86 has a lot of cool instructions, like AVX permutations and so on, let's see if there's something for RNG" and of course there was 😂 I was like "wow assembly nowadays is the highest lever language, it has routines for RNG, for AES, for SHA, basically everything you would need an external library or to implement yourself is already available in there 😂"
Looking at the output of your program, I can confirm that 1:41 was filmed exactly on Thursday, September 1st 2022 at 10:06:48 PM GMT.
Back when I used to do C++ for uni projects, I had implemented two very simple texture generation algorithms for an OpenGL game we were making (I only worked on the algorithm side of things). Working with the random library was a delight. It's one of the very few things in C++ that don't have any major hidden pitfalls (for my personal usecases). Coding in C++ feels really empowering when the batteries-included-ness of the stdlib kicks in. I'm trying to migrate to Rust these days and it feels kinda bittersweet to leave C++ behind.
Btw, for users, who don't have access or can't use c++20 for some reason, use std::generate, for a random vector...
How about "it's way too bloated"? Bjarne Straussup had a good idea. Then committees got to it and ruined it.
Straight to the point and zero useless bullshit, nice.
Your C++ videos are amazing! They help me learn!
this is way better than my solution, which was to make a deck of cards and then use 1+rand(time(0))%2 to basically get a coin flip, if its 1 it goes i cut it from the list and put it in the front if its 2 it gets cut from the list and put at the end, then i run that 200 times and get what seems to be random
6:40 to use std::ranges::shuffle you need include not .
I am in C++ for 30 years and I think the C rand() function is just fine for some uses. Yes, it is "bad" in terms of true randomness, but it can be still useful from time to time for simple things, where puristic randomness is not needed.
Do you have any advice for new beginners in C++ like me? You have 30 years of experience
Thank you! Subscribed. Hope you one day do a vid on a random in a range but with a bias towards a value and maybe a way to control the strength of that bias
Thanks for the video.
I am also getting the same number everytime, even using the exact same code shown in 3:25. The srand is deleted by this point, by which I understand that there is no need to update/change the seed. Thanks for your answer.
just use the C++ random device
@@TheBuilder That's what I am using. The exact same code at 3:25.
@@alejandronieto576 post code
Ah, I wish I could use C++20, but the computing cluster I target my software to is stuck on GCC 8.3.0. std::ranges would be very helpful
How does the code compile at 1:27 without #include ? That header is necessary to use rand()
probably included by iostream. libraries can include other libraries
already included by the compiler
Yes libraries can include other libraries but we should not assume that.
One of
#include
#include
is right.
You said one should always use a random_device with a distribution, but why is that?
its a better alternative to using module and division to get a range. also its built in so why not use it?
very informative video btw but quick question, how to set range of random numbers that are generated in an output lets say my random generator displayed a generated numbers of 78934561 but i want to set a range of only 4 numbers which is 7893. what line of code should i input?
just change the limits in the distribution function. you can also try using "%" and "/" to get rid of the first or last x digits
btw why not use an array instead of a vector, jw since u are already declaring the size of the vector
Just personal preference. I use std::vector so much I forget std::array is a thing
@@TheBuilder oh lol :v
this makes alot of assumtion about the viewer knowledge.
like what?
@@TheBuilder
nullptr
uniform distribution
vector
iota.
PS i like to understand everything in my code and its hard when youre a bigginer to know what "nullptr" means
@@its4theer make a list of things you're having trouble with and try to understand them slowly over time
@@TheBuilder I will thanks ❤️
Im getting some error that std::ranges has not been declared even though i did the #include thing correctly. Also, just started today, why arent we using std namespace here? isn't it always more convenient to do that?
its not efficient to use it for whole programm running it just takes much gpu for it to work
you should be passing NULL into srand. nullptr is a C++ value of nullptr_t type. Sure, they're virtually always going to equate to the same zero rvalue, but the definitions could be changed and then you'd break functionality. So while it may seem correct or convenient to pass nullptr into C functions from C++, you should abide by the defined interface.
my iota 6:18 just doesnt work (im on c++ 22)
ok i found the solution u should add numeric library
Ok Help!!! Newbie here! Used the Uniform distribution for random generated number in a function, but I need that number for a "Nested For Loop"; for 1 to the (generated number). Getting a error code of no conversion possible to make the randomize number into a integer. How do I get the " dist(rd)" (generated number) converted to a number for use in a "for loop"??
clearly a conversion issue, I can't help if you don't post source...or ask chatgpt
What's to stop the code outputting a ridiculously high number in the quadrillions, for example?
With which example?
If you're talking about rand(), it is limited to the size of an integer
Thank you, I just started learning C++ and holy sht rand() and srand suck.
it always spits out the same number for me, even though i've made everything exactly like in the vid
Is there an algorithm that predicts the next odds of the aviator game?
im not sure what that is
Um, where is the part where you explain why these solutions are actually better than rand?
what is there to explain?
@@TheBuilder in the title you tell to stop using rand, and in the video you give alternatives to it, but you didn't explain why should we use these alternatives instead of rand in the first place
@@o0jjc951 I did, though it is irrelevant because this result happens because this guy didn't do it even properly
you need to add "srand(time(NULL));" at the beginning to make the seed of your random generator be dependent of the current time so you get different results everytime
but mere seconds later, he did add it later on and it did work, so where's the problem with the rand function? you are the one who didn't watch a minute of the video bro
And what does he say next? "the problem is that ti's too simple and not flexible enough" just WHAT??
It's too simple?? And not flexible enough?? It's a random number generator bro, what flexibility do you need???
Because it's just something he heard someone say and thought it sounded smart. Rand works fine for most things.
@@ernststravoblofeld srand will always be king one liner.
hmmm... I think you didn't understood that there are different RNG needed. There are a lot of programms that highly need always the same random numbers. So setting a seed is not a bug, setting a seed is a feature for them.
First of all you need to think about what RNG do you need. Always the same? Always differnt? cryptographically secure? Does it need to pass special test? Do you need them fast? How many so you need? ...
Depending on your answers you need to use different random number generators.
yes, but using rand in C++ isn't recommended
@@TheBuilder Who doesn't recommend it and why is it not recommended?
generally its too simple for most tasks. you can read this reply, its fairly complete stackoverflow.com/questions/52869166/why-is-the-use-of-rand-considered-bad
@@TheBuilder I read it. As you can see there are many pro and cons for rand() in that stackoverflow articel. In your video you selected only one argument, but that argument is depeding on your coding task. So you selected a "wrong" argument. In my opinion there is only one (strong) argument against rand(): rand() is an unspecified algorithm (So every operating system/compiler implemented it's own version. So you don't know what you get! (So in fact this is nearly the opposite of what you demonstrate in your video)
@@TheBuilder Yes, it is not recommended, but in your video your argumentation is totaly wrong. If beginners watch your video, then they will totally missunderstand why it is not recommended. In fact you explain the opposite in your video. rand is not recommended, because users expect always the same random numbers, but as soon as there is a new compiler or and other operation system they migth get other numbers.
1023 possible combinations of ten numbers should have ran in in a for loop 1023 with no duplicates
It keeps generating 1 when put in a function
I wish I could give this a double like 👍
Loved your comment..
for(float like; n < 10; n++)
Thanks for making the right video
any time ☺
The real issue is using time() as the random seed
So what to use?
@@coe9900 for linux/unix systems, just read from /dev/urandom or /dev/random. For Windows, use CryptGenRandom. Just don't use time() for random seed as it's predictable
... i was expecting a segment fault at the end...
I get the same number everytime I run the code why?
it's explained in the video. you'd need to set a seed that changes between runs
Does not work, I got the same number every run
Bro are you even a coder? Why you using light theme?
Oh no Light mode, It blinded me!!!
Your monitor is too bright
why dont you use using namespace std; so you dont have to write std:: all the time
If I do I'd get comments telling me it's bad practice
if (7+null) = true then
end if
}
set "notebook" = net (true)
Awful explanation.
glad you liked it
You should be using RDRAND or RDSEED