The twit obviously didn't read more than the headline.
Probably hadn't read more than the headline of anything actually.
556 karma · joined March 5, 2018
The twit obviously didn't read more than the headline.
Probably hadn't read more than the headline of anything actually.
My cats regularly imagine a future in which I'm going towards the fridge to provide them with food......
...when the reality is I'm going elsewhere and just going to trip over them.
...built entirely to circumvent sanctions and fight "Die Swart Gevaar/Rooi Gevaar"... ("Black Danger" / "Red (Communist) Danger")
When the changes came they continued on without missing a beat except their number one problem now was to convince someone to continue paying them to carry on making munitions.
We're producing and exporting and importing just fine thank you.
Borders are closed to casual visitors, not goods.
Yup, that can (and just has) create opportunities for the virus to enter.
But that is a risk that can and is being managed.
Instead of overseas visitors spending in NZ and rich NZ'ers spending their tourist dollars overseas .... the richer NZ'ers are spending locally.
Turns out not as different as the doomsayers predicted.
https://writings.stephenwolfram.com/2020/04/finally-we-may-h...
Do you have an evil twin that doesn't have bruxism?
Hmmmm. Biltong.
I'm drooling.
The code melts and changes for awhile... and then congeals into unchanging rock again.
"Nah! It was your turn you big bully!"
Bon Appetit.
He said their policy was to invest in a 100 startups in the hope that one would go viral.
The sooner the other 99 died and stopped bleeding the happier they were.
Go big or die soon was their policy.
If the 1 went viral, they'd make back all and way more than they lost on the 99.
The fact that 99 founders were broke and broken didn't bother them at all.
Don't collect it if you don't need it. Destroy it as soon as possible if you do.
And the grand parents and obese parents are vulnerable as all merry hell.
Today it looks like an icon of British Imperialist jingoism.
Ahh, but which way does the relationship go..?
Unsurprisingly if I'm dying of something really serious and lying in bed sick as a dog.....
...I lose muscle mass.
That article could say absolutely anything for all I can see....
WTF?! The data says nothing like what the headline says!
Yes, the projection goes down sharply... but the best estimator of tomorrow is yesterday, and the last few years of data are saying nothing like what the projection is showing!
For some phantasmagorical stubborn up yours world, various nations continue to hunt them. Sea shepherds have been fighting that sort of crassness.
eg. There was a major linux conference at the local university.... Full of cutting edge real world OS / HW stuff.
The CS department didn't bother to attend.
Counterpoint.
Your users won't read the documentation. Get used to it.
Odds on your developers won't either.
Take care when you do read the documentation, it's probably out of date and / or wrong.
Every truly successful device will be used for purposes you didn't dream of when you first created it.
ISR's are random events that preempt your scheduler.
Deferred Service Routines run in the same thread as your scheduler.
It's excruciatingly hard to write (correct) code that can be interrupted and have it's internals monkeyed with at any clock cycle.
Thus the ISR/DSR handoff is a way of sequencing events into a manner the scheduler can handle sanely.
Most ISR's are written to be preemptible, it ack the interrupt and enable interrupts. Thus the chance of losing an event is very small.
The larger your isr the more you're into the realm of "excruciatingly hard to write (correct) code".
Your scheduler may be very simple... eg. only one thread as you described above, but my point applies.