|
It is also true that the number of choices for Worldle are much less than the number for Wordle. There are only 190+ countries in the world, and this means that even if they cover all the "registered countries", then they will have to repeat after 190+ days. So, perhaps they want to include the smallest of the small countries in their game.
|
|
|
|
|
agree
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Wordle 462 4/6
🟨🟩⬛⬛🟩
⬛🟩🟩🟩🟩
⬛🟩🟩🟩🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 462 2/6*
⬜🟨🟩⬜🟨
🟩🟩🟩🟩🟩
Happiness will never come to those who fail to appreciate what they already have. -Anon
|
|
|
|
|
Wordle 462 4/6
🟨⬜⬜⬜🟩
⬜⬜🟨🟩⬜
⬜🟩🟩🟩🟩
🟩🟩🟩🟩🟩
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
Wordle 462 6/6
🟨⬜⬜🟨⬜
🟨🟩🟨⬜⬜
⬜🟩🟩⬜🟩
⬜🟩🟩⬜🟩
⬜🟩🟩🟩🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 462 3/6
⬛🟨🟩⬛🟨
⬛🟩🟩🟩🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 462 3/6
⬛🟩🟩⬛🟩
🟨🟩🟩⬛🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 462 5/6
🟨🟩⬜⬜🟩
⬜🟩🟩⬜🟩
🟨🟩🟩⬜🟩
⬜🟩🟩🟩🟩
🟩🟩🟩🟩🟩
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Wordle 462 3/6
⬜🟩🟩⬜🟩
⬜🟩🟩⬜🟩
🟩🟩🟩🟩🟩
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
Wordle 462 4/6*
⬜🟩⬜⬜🟩
🟨🟩⬜⬜🟩
⬜🟩⬜🟩🟩
🟩🟩🟩🟩🟩
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Quote: The industry should treat C and C++ languages as "deprecated," says Azure CTO Mark Russinovich ZDNET article[^]
|
|
|
|
|
"'Tis better to remain silent..." etc.
|
|
|
|
|
|
I'm a bit surprised at these mild reactions!
Coming from anyone else I would just have frowned upon this, but I tend to believe Mark Russinovich as he really is a C/C++ veteran, or better: a legend.
|
|
|
|
|
RickZeeland wrote: Mark Russinovich as he really is a C/C++ veteran, or better: a legend. He writes great Sci-Fi books too.
It's all about about software security.
Languages like Rust and Swift are attempting to address that.
|
|
|
|
|
I am an avid SF reader. What are some of his titles
|
|
|
|
|
Zero Day
Trojan Horse
Rogue Code
They're all on Amazon.
While I have all three books, I've only had the time to read the first one. While it's not the greatest thing ever, it's been generally praised for its technical accuracy - as in, not stretching things because the author actually understands the topic, unlike other authors. Which would be expected from a guy like Mark Russinovich.
|
|
|
|
|
|
For general business applications this is very definitely a true statement. I can still see real time systems using C/C++ (at least the non-object oriented parts) for performance.
|
|
|
|
|
The object-oriented parts really don't have that much overhead, and I would never give them up for "performance" when their use was appropriate. The main problem that I see with C++ is that C# now provides more infrastructure as the result of C++ standards focusing on pedantic horseshite instead of things that actually add value.
|
|
|
|
|
The Register has a nice quote from Stroustrup in their coverage of it[^]. It's obvious from it that he doesn't know who Russinovich is, though. You're right (below) that Russinovich knows C and C++. Some of his utilities are frighteningly tight code.
Quote: "It is not unusual for people – especially executives – to become enamored with new and shiny things that promise to make their lives easier," he told us.
TTFN - Kent
|
|
|
|
|
Stroustrup is fighting a loosing battle in defending C and C++. The bottom line is that both Microsoft and Google have reported 70% of their vulnerability patches are from memory related errors. C/C++ simply are not memory safe.
|
|
|
|
|
Don't blame the language; blame the developers. I definitely blame the errors I make on myself.
|
|
|
|
|
From a security standpoint, C and C++ have several fundamental flaws:
- Unmanaged heap, leads to several problems such as "use after free", "insufficient memory" when there's plenty of memory, and memory leaks where objects are orphaned in memory
- Null terminated strings, which are the single biggest source of buffer overruns.
- Implementation defined word size and in earlier versions, no specific pointer/address data type, leading to arithmetic errors and buffer overruns.
I've written complex software in both C and C++ so I know you can usually work around these flaws in modern C/C++ compilers, but the reality is you cannot prove most C/C++ programs to be correct from a standpoint of memory management or integer arithmetic.
|
|
|
|