1,974 karma · joined January 3, 2021
Have a decade's worth of business analysis & consulting experience.
My industrial experience ranges from steel mill automation, power station and electrical distribution networks down to smart homes.
My business IT experience includes insurance, FMCG, supply chain and manufacturing.
I have a recent PhD in software engineering and have taught postgrad software engineering courses.
Available under contract to create engineered IT solutions for your business.
Email: gian@cyberfonic.com
Didn't work too well last time. Will be amazingly effective this time </snark>
You just need to recognize that not everybody aspires to be competent with lower-levels of hardware and software that Apple makes that much more difficult. Most Apple users are content to use apps written by others and that is as far as their interest goes.
An analogy is the car market. Most people don't care how the car works, etc. They just want to get to places. If you only need to drive to the shops and do minimal errands, you don't even need a truck - a sedan will do just fine. Same with computers, lots of different market segments with distinct needs and expectations.
Microsoft, as its name implies, started out and cuturally was always a software company. By the time Microsoft started dabbling in hardware it was seen as a competitor by the many software licencees. Microsoft could never control the hardware side of their platform like Apple has.
The other factor is that Apple ditched the proprietary OS and went down the Unix/BSD and derivatives path. MacOS is effectively a FreeBSD derivative overlaid with a custom desktop.
Without a quasi-portable OS at the core, there is no way that Apple could have made the switches from Motorola 68000 to PowerPC to Intel to ARM.
Windows, on the other hand, is running NT which is basically a port of DEC VMS. Didn't work out well for DEC/Compaq/HP.
As I see it, WASM is used to augment the JS/WebAPI ecosystem. For example, when you need to do heavy bit manipulation, complex numerical processing. The round-trip JS->WASM->JS is an overhead. So the WASM modules should perform a substantial amount of processing to offset that inefficiency.
I frequently find that V8 optimisations yield sufficient performance without needing to delve into WASM.
IMHO if you want to write WebApps in Rust, you're holding it wrong.
For example, for architectural 3D modeling software, the operating the software is being the architect who visualises, designs and refines the building's design.
Deep domain knowledge and expertise is essential. Until you actually work at the coal face in a given industry you don't know the complexity nor the opportunities for improvements. Talking to the workers is good, but you never get the complete picture.
From a business point of view an independent operation would require a very large investment. To recoup at least part of that requires advertising and affiliate revenue which in turn creates perverse incentives.
I very much believe that comprehensive domain knowledge and technical proficiency are both essential. Actual code production can be mostly delegated. If AI produces better quality code than the contractors available to you, then it is the preferable option.
IMHO a small team of experienced engineers using AI is the optimal choice.
Vibe-coded startups without competent technical oversight is tech-debt on steroids.
However, we have to acknowledge that if you consider Android as being Linux based and all the servers in the cloud, then Linux has already supplanted Windows.
My process is very simple. I just write from top to bottom. Of course, the first pass is rough. But the focus is on capturing the material in approximately the logical sequence. For really complex and lengthy materials, I might write an outline with mostly headings and snippets as they come to me.
For emails and other time critical writing, I go back to the top and edit / re-write. I don't need nor use AI for this. Then send. Rarely do I use a third pass.
For reports and papers, I tend to put the first pass aside for a day or more. When I return to it, I edit viciously and re-write. Depending on the importance of the writing, I might repeat this process 2 or 3 more times.
In any earth sciences based work, there would be requirements for either data sciences or AI related processing, improvements, etc. Those are the sorts of areas that you might want to peddle your SWE skills as delivering.
These days, I just delete and move on if the "article" doesn't deliver interesting and meaningful content within the first half page or so.
I started out with Deno and when I discovered Bun, I pivoted. Personally I don't need the NodeJS/NPM compatability. Wish there was a Bun-lite which was freed of the backward compatability.
Of course, the big AI companies blithely ignore moral and legal issues.
I do doubt that you could actually discern 16M colors. But even many thousands is entertaining.
Instead of downloading various open-source utilities and finding none does exactly what you require, you can have AI build a bespoke program, just for your specific needs.
If you are a government procurement manager, you certainly would want to know where the biggest kickbacks come from.
IMHO rechargeable models are not worth the extra cost. With a typical 5 year replacement cycle the batteries will no longer hold the early levels of charge. 312 batteries are cheap and easy to carry spares.
Then I read Alan Kay: "When I invented OOP I didn't mean C++". So I explored Smalltalk, loved the environment, hated that deploying apps is a pain.
Tried Go, because Google ...
Now mostly JS because it's everywhere and Python for the batteries.
The silver tongued sales persons who wine and dine the decision makers continue to make out like bandits selling snake oil.
BUT why not get a startup going and address the opportunity?
Amazon, eBay, PayPal, Uber, AirBnB, etc likewise saw problems as being opportunities in disguise.
For example, there is a housing crisis. Not enough trades persons, building supplies, capital to solve that problem.
The unemployment statistics aren't detailed enough to show IBM, MS, Facebook, Amazon, etc laying off tens of thousands of employees a year, each. Last I read, over 500,000 staff have been laid off in the past couple of years.
"Why do you think you need to share your code?"
"What benefit(s) do you expect to gain from sharing your code?"