1,053 karma · joined November 30, 2014
To me it looks like the author is grasping for straws when saying "well, a server rack is just like a mainframe, so the mainframe is not dying!".
To me it's the opposite: yes, a server rack is just like a mainframe. That's why the mainframe is dying - a bunch of servers can do the same work much more cheaply.
Well, no... You get fined if you make improvements AND use your already big position to bury competition that may compete with your improvement.
Google could've just marketed their option along the competitors but no, they had to get rid of the competitors results in search too, and that's the issue
But I like to imagine the Web frontend made in Go, compiled to WASM. Would be a fun project, for sure.
To me it sounds like people trying to justify that what they do has some higher value than what it really does.
And as always, no one discusses the danger of creating even more plastic waste by not using refillables, or using the pouches being sold by this company.
It's an unreasonable request with ordinary code, even more with ML where very few ones have access to the necessary hardware, and where in practice, it is not deterministic.
That's why we've got HTTPS an DoT/DoH so widespread these days
From my experience: besides both Win32 and VB being from the same entity (Microsoft), which helps a lot, what we had basically were VB bindings for the underlying Win32 library.
This Rio project seems more analogous to a library that tries to do an abstraction on top of Win32, like wxWidgets or Java's AWT. They work but the end results always seem a bit "off".
And unlike Win32, web technologies are moving targets and any assumptions one makes may be wrong some browser updates down the line... and there's where the nightmare comes
For example, I've been bitten before by Dell due to plundervolt updates that removed the undervolting capability under the umbrella of "security fixes".
The feeling is the same as being sure that something, like an algorithm, is able to do what you expect. Then you sit down, trying to write a proof for it and end up finding the flaw in it. By making the thought process explicit you can uncover so much.
I've lost count of how many times we had a problem, I went and read the proper documentation and said what had to be done, only to be ignored because upper mgmt didn't like the solution, so they called "support" only to be told the exact same thing.
So much for a project that claims to be apolitical
There are numerous libraries and launchers on github; my favorite is [1].
CPU limits are only for Windows 8 or greater though, so for people still on Windows 7 or earlier, then okay, this post is relevant for them.
The problem is dropping automation BECAUSE it fails.
They aren't able to rely on the automation because it's faulty - and as consequence error rate increases.