I wonder if they’d be willing to sell it to the right group of folks. I’d love to have a community owned read it later service. Otherwise, we’re all on a never ending treadmill from one service to the next.
Same here. I get a massive amount of value out of writing things down at home and at work. I get comparably little value out of linking things together — beyond direct references at least. I think this may be a difference in how different people think and recall information.
However, the SDKs are very tightly integrated with the runtime in each language, and we use gRPC on the workers which will make it more difficult to call the APIs directly.
This is unfortunately not emphasized with many breakout boards. It pays off to skim errata sections at the start of a project. All hardware has errata, and it ranges from incorrect details and minor malfunctions all the way through to broken peripherals and all manner of critical malfunctions.
To be clear, this isn't a problem with the breakout board. The issue is inside the microcontroller itself, which, iiuc, is why there is such a long lead time on fixing it.
While I agree that reading the errata absolutely should be on the "mandatory TODO before you start" list for any project (esp with new/unfamiliar hardware), one should be equally aware that manufacturers aren't always transparent about the defects in their products, sometimes failing to note that entire subsystems, frankly, don't work.
There are industrial knitting machines, but they’re orders of magnitude more expensive, heavier, and tied to closed software ecosystems. They’re extremely capable, but they’re also far outside the hobbyist realm. The only real evolution on these old hobbyist machines is the Kniterate at $16k and 600lbs.
