3,152 karma · joined December 2, 2014
https://www.justus.ws
> Our second generation R1 vehicles feature an entirely new electrical architecture and compute platform developed in-house by our hardware and software team. This significant update to our onboard computing system makes our vehicles more robust, less costly to produce and easier to service — all while improving the experience for our customers. Our new system also dramatically improves scalability for deployment in future vehicles.
> Core to the new system is a substantial reduction in the number of electronic control units (ECUs) used to control the vehicle, down from 17 different ECUs in our first generation to just seven ECUs in our second generation. This massive simplification has been achieved by shifting to a zonal architecture and by significantly increasing the computational capabilities of each of our ECUs. While infotainment, autonomy, vehicle access, drive units and our battery management system each have their own ECU, every other vehicle function is controlled by just three ECUs.
> Shifting to a zonal system enabled us to remove over 1.6 miles (2.6km) of wiring from each vehicle, shedding 44 lbs (20kg) of weight. This reduction in wiring, along with the elimination of 10 ECUs, greatly reduces production costs. Fewer components needing to be installed during assembly also improves manufacturing efficiency, allowing us to build vehicles more quickly and with better quality. With less components onboard, vehicles are easier to service and require us to stock fewer parts, improving serviceability.
Mac: https://www.backblaze.com/computer-backup/docs/configure-exc...
Windows: https://www.backblaze.com/computer-backup/docs/configure-exc...
wget https://www.ioccc.org/2001/Makefile
wget https://www.ioccc.org/2001/herrmann2.c
wget https://www.ioccc.org/2001/herrmann2.cup
wget https://www.ioccc.org/2001/herrmann2.hint
wget https://www.ioccc.org/2001/herrmann2.ioccc
cat herrmann2.hint #instructions
make herrmann2
./herrmann2 < herrmann2.ioccc
My mind is boggled. I get the basics of how autostereograms work, but the fact that it works so well with ASCII text is mindblowing.Edit: If you're lazy, I made a quick Gist that does the above, so you can just do
curl https://gist.githubusercontent.com/justusthane/a8c27c72350793ac452b86cc665a268b/raw/72aa6bf37689ea0cbbb70fa70fbd758c3a1fde3a | bash
(Obligatory "It's not safe to pipe internet stuff into a Shell" disclaimer)Backups are a specific point in time.
It's pretty impressive. I read it back in June when this came out, but the basic gist of it is that everything that _can_ be done on device _is_ done on device, and everything else is run in a _provably_ secure and private cloud environment.
Edit: The title is “TikTok feed for your clips” so I guess in a literal sense it is describing itself as “TikTok for X”, but I think that’s kind of like saying that something is “Uber for ridesharing”. Yeah, that’s just Uber.
Seems like an ideal use for a very simple DIY static-site generator. Write it in Bash or Perl and it will be future-proofed forever.
An analogy: a bunch of indigenous people are kicked off their island, and coffee is grown there by the people who evicted them. You buy the coffee, and the people who have the rightful claim to the land don't receive any of the profits.
To add insult to injury, the coffee is named after the island it's grown on, and that's mostly why it's popular - because it's a really good name for coffee (maybe it's called Java Island).
That's basically what the .io domain is.
More seriously, I did actually live just an hour south of there briefly. Northern Ontario is a big place.