Computers have ruled the planet for longer than the Greeks ever did. The history lesson is appreciated, but we’re living in the future, now, and the future is digital.
Computers have ruled the planet for longer than the Greeks ever did. The history lesson is appreciated, but we’re living in the future, now, and the future is digital.
K/M/G/T/P = decimal prefixes. K is 1000. M is 1,000,000. etc.
Ki/Mi/Gi/Ti/Pi = binary prefixes. Ki is 2¹⁰ (1024), Mi is 2²⁰ (1,048,576), etc.
It’s a disambiguation of the previous system where we would use KB to interchangeably mean 1000 or 1024 depending on context.
The American way would probably be still using the units you listed but still meaning 1024, just to be confusing.
American here. This is actually the proper way. KB is 1024 bytes. MB is 1024 KB. The terms were invented and used like that for decades.
Moving to ‘proper metric’ where KB is 1000 bytes was a scam invented by storage manufacturers to pretend to have bigger hard drives.
And then inventing the KiB prefixes was a soft-bellied capitulation by Europeans to those storage manufacturers.
Real hackers still use Kilo/Mega/Giga/Tera prefixes while still thinking in powers of 2. If we accept XiB, we admit that the scummy storage vendors have won.
Note: I’ll also accept that I’m an idiot American and therefore my opinion is stupid and invalid, but I stand by it.
I also looked at Excalidraw, which while being web app, runs reasonably well on Android. But some of the functions either don’t work at all or I’m doing something wrong. I was able to import a photo and trace it, but couldn’t find a way to export just the trace outline.
After you trace the photo, can’t you delete the photo from the canvas and just save as SVG? Won’t it save just the trace if that’s all there is?
My phone doesn’t have a 3.5mm headphone jack.
I need to make it a priority to give logseq a try. I moved from Joplin to obsidian.md a couple years ago, because i realized an open data format (plaintext markdown files) was more important to me than an open source app (because I can still easily query and manipulate my data with open source CLI tools). I think at this point if I can replicate about 75% of my obsidian workflow in logseq, I’ll make the jump and adapt my workflows to logseq’s strengths and capabiities.
I’m a capable troubleshooter. I’ll take 5 minutes of troubleshooting once or twice a year to save a cumulative few hours opening an app store to manually check for and install updates. I’m glad they’re giving options to both of us!
This is the way. I started on Obsidian, and Logseq is painful in comparison. It’s a good product, but I got accustomed to too many nice conveniences over the past couple of years.