|
The Let It Crash philosophy is an approach to error handling that seeks preserve the integrity and reliability of a system by intentionally allowing certain faults to go unhandled. You mean all these years my programs have been crashing I've been following a philosophy?
|
|
|
|
|
Maybe Boeing should stop listening to Erlang programmers.
|
|
|
|
|
Syntax error: 'horizon' not found.
'CriticalSystems.exe' will be terminated. Please check the log for details.
"Five fruits and vegetables a day? What a joke!
Personally, after the third watermelon, I'm full."
|
|
|
|
|
Is this new?
Or is it, as I remember very clearly, exactly what we used to do, back in the days before we had all the advanced debugging tools that we have now?
Me, I prefer the advanced debugging tools.
You don't give up the successful gold mine because someone's found a vein of clay.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: Is this new? It's another form of "on error resume".
When my applications would go into an exception (meaning ANY exception), it would terminate, since from that point I could not guarantee that the data had not been corrupted. It would simply state and log the error, and exit.
Now imagine Windows doing the same. Wouldn't be very workable as an OS, if every exception were to cause Windows to shutdown without saving.
The area between those extremes is big and gray; but it is better than being extremely religious about it.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Can't believe you missed your chance to describe this article as:
"The code never bothered me anyway."
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Individual programs are harmful walled gardens - a stifling barrier to true expressiveness, productivity, freedom and consistency of computing experience. Those who do not fear COM are doomed to repeat it
|
|
|
|
|
He's quite right.
For a start, we should stop using Private functions, and make all variables global -- across the entire computer, not just per program.
The problem with pipe dreams is that you might fall asleep while having one, and set fire to the house.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Kent Sharkey wrote: Those who do not fear COM are doomed to repeat it
Olé, Olé, Olé
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
>Quote: A new kind of object-orientation
Which was the original concept of "objects" - that they would be autonomous and "smart", a vision that has failed utterly.
|
|
|
|
|
Marc Clifton wrote: Which was the original concept of "objects" True.
Now we have "frameworks" as a poor man's substitute.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Let him prove his big mouth with his own migration product, and make the connection-strings available, not only computer-wide, but accesible over the internet.
Wouldn't that spark a lot of creativity and innovation?
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
To help advance and improve access to FIDO authenticator implementations, we are excited, following other open-source projects like Solo and Somu, to announce the release of OpenSK, an open-source implementation for security keys written in Rust that supports both FIDO U2F and FIDO2 standards. *Dongle not included
|
|
|
|
|
Programs written in the language include one for fortune-telling from the I Ching In case you'll need to program any Chinese classics in the future
Journey to the West, perhaps.
|
|
|
|
|
OK, let's give this a try...
Ming wing jing ding ... or is it bing ?
It's no good. I'll have to get the missus to translate my code for me.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Come for the anime fansites, stay for the Spice Girls MIDIs "Sometimes, dead is better."
|
|
|
|
|
It's nice that he has a hobby, but maybe he should consider getting a life, too.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
How on Earth do you patch the software on a computer orbiting the Moon? Very carefully. Because you never know when you might need to build your own
|
|
|
|
|
Marvellous. Loved every minute of it.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Agreed! It's got me wanting to build a DSKY interface for a Raspberry Pi.
"When you are dead, you won't even know that you are dead. It's a pain only felt by others; same thing when you are stupid."
Ignorant - An individual without knowledge, but is willing to learn.
Stupid - An individual without knowledge and is incapable of learning.
Idiot - An individual without knowledge and allows social media to do the thinking for them.
modified 19-Nov-21 21:01pm.
|
|
|
|
|
Microsoft is continuing to try to clear up its muddled UWP messaging and strategy. Fewer ads on the horizon? Sad.
|
|
|
|
|
Yet, Microsoft still insists on UWP.
|
|
|
|
|
I've got no problems with the decision to make every program work everywhere, whether using native code, background VMs, or emulators.
It's deciding that every device should have the same UI that's the problem -- hugely compounded by the completely moronic decision to use a smartphone UI.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I have a big problem with it. Recently, I worked on an app where we could have saved money by running it on an Intel NUC running Windows IoT, only to discover that the latter requires UWP. This project would have been worthwhile ONLY if the cost of "porting" was minimal. (Even if we had the time & money, the performance of UWP is unacceptable.)
Microsoft continues to nuke themselves in the foot in the embedded space.
|
|
|
|
|
I'm sure that they thought of all that, but decided that they're smarter than you.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|