51–60 of 166 posts
Earlier quoted context omitted.
because you don't know the number of images before running the code so no number to do the mod part
Why wouldn't you know that? It's a set of preloaded stock photos, it's always gonna be the same number.
Why they made it that complex? A simple rand/mod based on first character of username should be sufficient?
It's somewhat odd that filesystems don't have a call to tell you how many files are in a folder.
Earlier quoted context omitted.
That's a matter of taste, but for many it was the Windows they used first and/or spend the most time on and there's a lot of love for that reason alone. I never used XP all that much, but I always changed the theme to the Windows 2000 look. I really didn't like the default, it looked unprofessional and clunky in my eyes. Upon release XP was also pretty universally mocked as a Fisher Price-like UI. To me Windows 95/NT…
win2k was peak for me. lean, functional, just a pinch of glitter here and there (short fade-ins). it was on par with the amazing stability brought by nt5 kernel. i kinda miss xp at a cultural level since it was a bit the end of that computing culture cycle (after that apple started to dominate and ubuiquitous computing influenced desktop ui)
When did Apple dominate? I'm not trying to hate on Apple here, but there's this weird belief that Apple have had a lead in personal computer OS market share at some point in the last few decades, and it isn't really true since about 1984.
You can argue that they should dominate, but that doesn't seem to have happened.
Earlier quoted context omitted.
because you don't know the number of images before running the code so no number to do the mod part
Why wouldn't you know that? It's a set of preloaded stock photos, it's always gonna be the same number.
Why they made it that complex? A simple rand/mod based on first character of username should be sufficient?
It's somewhat odd that filesystems don't have a call to tell you how many files are in a folder.
It's somewhat odd that filesystems don't have a call to tell you how many files are in a folder.
On top of that, how often is it necessary to efficiently know the number of files in a directory while at the same time not caring about the files enough to list or display them? This algorithm is a special case where you could use the count of using a bit simpler code that ultimately would have the same file system API calls (since you cannot tell the FS to give you file #37 from that directory, so you'd have to use FindNextFile 37 times anyway, just like the sampling algorithm).