|
Software in 2022 is overwhelmingly built with little to no consequence and is made up of other components which are overwhelmingly developed by unpaid volunteers on an AS-IS basis that are being financially neglected. A rant. With bonus squirrel burgers
|
|
|
|
|
Well, except maybe writers
|
|
|
|
|
Joe Woodbury wrote: Well, except maybe writers
And alternative "therapies."
|
|
|
|
|
|
Most of the other professions listed there involve significant risk to health or life if the practitioner gets it wrong. This is true of some software projects, but not at all to others.
People had been building for millenia before practice was standardised and regulated. Engineering had a few hundred years. Software has been around for around 70 years in total its still a very new area. I'm not convinced we yet know what good practice really is, and premature regulation could impede establishing that.
However, where the results of mistakes can involve significant harm, we should probably be moving towards some form of regulation.
In the UK, government contracts have requirements of the methodology for development, and they seem to have got it utterly wrong, as government IT projects are notorious for being late, buggy and expensive. So much so that I will no longer accept work in these fields.
Incorrect regulation can be more harmful than none.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
Quote: Software practitioners should be licensed Stopped right there. People who say this have no understanding of unintended consequences and how things get politicized and corrupted. The writer is ignorant and, as is proper to the ignorant, should shut up.
|
|
|
|
|
Greg Utas wrote: ...as is proper to the ignorant, should shut up As has been seen over the last few years, ignorance knows no 'proper.' You could say they are 'ignorant' of the term.
|
|
|
|
|
Sharing your phone with a friend, family member, or another individual—or even leaving it briefly on a nearby surface—could expose your privacy in the form of an incoming call, email, reminder, or app notification. This brings new meaning to, "you're holding it wrong"
|
|
|
|
|
On a large scale it isn’t as awesome as you think define: big
|
|
|
|
|
Quote: define: big More than 5 lines?
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
|
I think I could write articles like this too - I came to this conclusion way before reaching halfway through the Python tutorial.
GCS d--(d-) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
Used in conjunction with the new vcpkg artifact capabilities you can quickly bootstrap an embedded development machine and get started. I'd put something here, but my brain is currently embedded in stone
|
|
|
|
|
The addition of tabs to File Explorer in Windows 11 allows for multiple folders to be open in one window. Can we get drawers next to complete the metaphor?
|
|
|
|
|
why not adult beverages instead of drawers?!
|
|
|
|
|
That would be a nice feature in Windows. It would certainly reduce my complaints.
TTFN - Kent
|
|
|
|
|
Why? The entire idea of GUIs is to have multiple windows open. In the case of File Explorer a single window will make it far more opaque when copying and moving files.
More importantly, why the F is Microsoft dead set on mimicking Apple's interface? Monochromatic, boring, and completely separated from good UI practices on larger screens.
|
|
|
|
|
Today we’re excited to announce our support and collaboration on a new Stage 0 proposal to bring optional and erasable type syntax to JavaScript. It's a type!
And I'm sure no one will mention the "Embrace, Extend, Extinguish" memo.
|
|
|
|
|
So if JavaScript, the champion of duck-typed languages, embraces type checking, I wonder if the insanity of other duck-typed languages will finally begin their slow demise. Or adopt the type!
|
|
|
|
|
Meanwhile, strong-typed languages will start adopting weak-typed features until everything is wiped away with the new languages
|
|
|
|
|
Kaladin wrote: Meanwhile, strong-typed languages will start adopting weak-typed features until everything is wiped away with the new languages
Yeah, you make a good point.
|
|
|
|
|
Kaladin wrote: Meanwhile, strong-typed languages will start adopting weak-typed features until everything is wiped away with the new languages
Meanwhile in C#...
dynamic has entered the chat.
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
|
|
|
|
|
I'm not sure I'd call JS the "champion" of duck typed languages. Certainly the most widely used. Also probably the worst implementation of it.
Having used Smalltalk, better implementations were available decades before the abomination that is JavaScript.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
How about we say javascript is the most ducked up duck type language.
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
|
|
|
|
|
It's not GitHub versus Gitlab. They're both based around the Git distributed version control system, but they have very different development approaches. I'm assuming the 'Hu' vs. "La"?
|
|
|
|