This, and other projects like it, are NOT "from scratch". It doesn't include little things such as a motor; wires; other electronics; the metal frame.
Until "consumer" 3D fabrication can do more serious fab than random weak structural plastic components, it will remain as a hobby. The industrial machines able to sinter metal into strong parts or using carbon fiber - those have serious practical utility. I'd be much more interested in a low cost, high precision metal sintering 3D printer than a project such as this.
25,000 years ago, CO2 levels stood at 180 ppm - the lowest in 4.7 billion years of earth's history. About 30 ppm above the level at which RuBisCo stops effectively working, which would bring a halt to most photosynthesis on earth.
You can blindly accept dogma or you can think about the implications of that in light of fanatical calls to remove CO2 from the atmosphere - CO2 which has been steadily removed by long term geological processes, and which is now below the levels of over 99% of earth's history.
"We show (using relatively conservative assumptions!) that across 50 of the top public software companies currently utilizing cloud infrastructure, an estimated $100B of market value is being lost among them due to cloud impact on margins — relative to running the infrastructure themselves."
That completely overlooks the actual benefit and the reasons driving cloud adoption, which he states early on and then fails to integrate here. The real cost/benefit analysis would take into account the amount of time, money, and opportunity cost saved by using a cloud in development, a critical time that determines whether there'll actually be a profitable company eventually. Optimizing the cloud costs is certainly important, but being able to spin up highly integrated systems on demand offsets a huge amount of time and capital during development.
A takeaway might be that, e.g., AWS, should offer even larger discounts for large scale operations in order to retain mature customers.
I notice that "bugfix service" isn't checked under the open source column, only the enterprise one.
I always find it obnoxious and baffling that any company would delegate bug fixes to (current) paid customers. Either you're proud of your work and want to fix mistakes, or not. To blow off bug reports and bugs from anyone is a mistake.
Is making WASM able to operate almost completely independently of Javascript a design goal? In other words, be able to access and manipulate the DOM, CSS, browser functionality, and so on, without having to use Javascript.
It would be far more accurate to assume that the paper of Walter Duranty's record (https://en.wikipedia.org/wiki/Walter_Duranty) is routinely wrong than right. Their correct statements are the exception, not the rule.
Rather than following the data and logic, many twist themselves into pretzels trying to rationalize that it’s all natural. They’re doing Beijing’s propaganda work without even getting a paycheck.
Well, Amazon solved this problem - by censoring expression of developer dissatisfaction with the abomination. Way to solve a real problem plaguing your client base, Amazon.
"@amzn amzn locked as too heated and limited conversation to collaborators 3 hours ago
The remaining question is whether you have any control over it.