|
Wordle 625 3/6*
⬜⬜⬜⬜🟨
⬜🟩🟩🟩🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 625 4/6
⬜⬜🟨⬜🟩
⬜🟩⬜⬜🟩
⬜🟩🟩⬜🟩
🟩🟩🟩🟩🟩
hard one
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Wordle 625 4/6
⬛⬛⬛🟨⬛
⬛🟨🟨⬛🟩
🟨🟩🟨⬛🟩
🟩🟩🟩🟩🟩
Get me coffee and no one gets hurt!
|
|
|
|
|
Wordle 625 5/6
⬛⬛⬛⬛⬛
🟩⬛⬛🟨⬛
🟩🟩🟩⬛⬛
🟩🟩🟩⬛🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
ESP Display S3 Parallel with Touch running htcw_gfx[^]
See that bee? That bee is victory.
That's an SVG graphic with an embedded CSS stylesheet, running on a $1.80 processor wired to a touch display.
This is vector rendering sitting on top of a skeletal w3 parsing framework on an IoT device.
That bee file is xml with an embedded CSS stylesheet. Not converted to some IoT friendly format first. Nada. Just loaded as is. Could have been streamed from the web even.
This is fantastic.
Most of this sits on top of my embedded markup pull parser.
Gosh at this rate, my w3 parsing framework will make these devices browser ready after banging on it for another year or two.
To err is human. Fortune favors the monsters.
|
|
|
|
|
Yeah.. All this tech..
And still the US can't build machines that simply count votes.
Bastard Programmer from Hell
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Should they allow nasal fitment?
|
|
|
|
|
All of the hand recounts confirmed the automated tallies within a very negligible percent. Please stop spreading lies.
|
|
|
|
|
David O'Neil wrote: Please stop spreading lies
???
What lies?
Bastard Programmer from Hell
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Sorry Eddy. Not correct.
US Machines are reliable and accurate.
People are not always so.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Nobel Prize is in the bag.
|
|
|
|
|
When I first saw the tag line I read the BeeGees...blah blah
Yeah I'm brain dead working on the follow up ARM article...Timers.
|
|
|
|
|
Mike Hankey wrote: eah I'm brain dead working on the follow up ARM article...Timers. In the meantime I am playing with the SysTick of the poor cousin of your chip (STM32C0).
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
It's odd to me that there doesn't seem to be much information about SysTick timer, especially the registers and how to program.
I don't discuss SysTick or Watchdog timers in my article, thought I'd save that for another article.
|
|
|
|
|
I have just gone through four QA questions, each of which is an error caused by a null reference. And yet none of the posters seems to have any idea a) how to diagnose and fix it, or b) even what the error means. Do those of you who still work in teams find this is a common problem with younger team members?
modified 5-Mar-23 8:12am.
|
|
|
|
|
Perhaps because they are so spoiled that they have never in there life encountered "nothing" and have no empathy for the poor code where they would otherwise put in a null check or try/catch to help it succeed.
Prolly not. But kids today.
|
|
|
|
|
Well, after all it is the Billion Dollar Mistake[^], as Tony Hoare himself put it
Recently I had to go through a large code base where the authors went crazy using Non-nullable pointers[^] almost everywhere. What can I say, seems a complicated problem for many people
Mircea
|
|
|
|
|
Mircea Neacsu wrote: Tony Hoare himself put it
But I'm unsure if he doesn't really believe it himself; nulls are still a very good idea, but dangerous in the wrong hands. But so are chain saws, and hair spray, big deal.
|
|
|
|
|
The song "Absolute beginners" by David Bowie springs to mind
|
|
|
|
|
Well, in a world where we have programming languages that have concepts like "truthy" and "falsey", what can you expect?
|
|
|
|
|
Marc Clifton wrote: in a world where we have programming languages that have concepts like "truthy" and "falsey", what can you expect?
In that Universe, I expect Qubits.
Just putting a Quantum spin on things.
|
|
|
|
|
Not sure... there's nothing to understand
|
|
|
|
|
I read somewhere, years ago, that zero/nothing is one of the most difficult concepts for the human brain to understand. I think it was suggested that that was why there is no zero in Roman numerals.
|
|
|
|
|
It isn't. I have one apple in my hand. How much do you have in yours?
Even prehistoric hunters came back with "zero".
There's no 0 in Roman Numerals because it would not make sense to count nothing. A farmer that owes no taxes gets ignored, they counted what was owed. "Zero" would have no use there; even if that is the return of your hunting trip, 0 is not recorded. Writing is too precious to record zero's.
Bastard Programmer from Hell
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
In Norwegian, the name of numeric zero is 'null'. So Norwegian kids 'sort of' have an excuse for confusing the two.
But they are quite different. Zero is a distinct, well defined numeric value that you may treat 100% like any other numeric value.
'null' is nothing, not a numeric value, but a void. Emptiness. An abyss. Not at a valid numeric value. Some programming languages use the term 'void'; it is really much more descriptive.
I feel like digging up my old Robert Heinlein collection to re-read the short story—And He Built a Crooked House[^]. The story tells about a crazy architect (in California, obviously ) who designs a house which is a 3-dimensional projection of a 4-dimensional cube, a tesseract. The night before the house owners move in, there is an earthquake that makes the house fold up as a true tesseract, in 4 dimensions, not just as a 3-dim projection.
I believe that Heinlein has taken liberties in his description of how a real tesseract would appear. But his description of the view out one window, of a total emptiness, not even black, gave me shivers when I first read it, many years ago. It is a beautiful literary description of the concept of a 'null'. I think that I didn't fully understand the concept of null, void, myself until I read the Heinlein story.
|
|
|
|