Small nuance, but the term ワープロ馬鹿 actually is unrelated to software like MS Word, and refers to the at one point ubiquitous ワープロ (Word Pro) dedicated hardware device that many Japanese people owned in the 80s/90s to write letters. Read more here: https://en.wikipedia.org/wiki/Word_processor#Japanese_word_p...
Interestingly the English Wikipedia page above only mentions Japanese word processor devices in a small section, but the Japanese version of that page is almost entirely dedicated to these hardware devices: https://ja.wikipedia.org/wiki/%E3%83%AF%E3%83%BC%E3%83%89%E3...
I was lucky enough to live with a Japanese family in the early 90s and used one to learn how to type Japanese but also write letters home in my own language. I guess you had to live through this age to understand the difference of how Word Pro is used and the hardware association it has in Japanese.
The other weird thing about that term is that it's somewhat uncommon to see 馬鹿 actually written out in kanji, as those characters mean horse and deer with no direct association with 'idiot' (the proposed etymology is a reference to Chinese history and/or a Sanskrit loanword). I guess in a way the kanji form is a word processor autocomplete tell.
A Toshiba Rupo word processor (found in both links) is safely stored in the backyard shed, together with some floppies and documentation. That'll be my winter project next year.
Treating rent-seeking as a sin is common theme across many religions, including - at least historically - Judaism (within the community) and Christianity. Indeed, for several centuries in Europe, usury would get you excommunicated.
> Last thing I'll say is, you know your API is good when "S3 compatable API" is a selling point of your competitors.
Counter-point: You know that you're the dominant player. See: .psd, .pdf, .xslx. Not particularly good file types, yet widely supported by competitor products.
Photoshop, PDF and Excel are all products that were truly much better than their competitors at the time of their introduction.
Every file format accumulates cruft over thirty years, especially when you have hundreds of millions of users and you have to expand the product for use cases the original developers never imagined. But that doesn’t mean the success wasn’t justified.
Most people use libraries to read and write the files, and judge them pretty much entirely by popularity.
A very popular file format pretty much defines the semantics and feature set for that category in everyone's mind, and if you build around those features, then you can probably expect good compatibility.
Nobody thinks about the actual on disk data layout, they think about standardization and semantics.
I rather like PDF, although it doesn't seem to be well suited for 500MB scans of old books and the like, they really seem to bog down on older mobile devices.
Does anyone happen to know if ChatGPT's voice feature uses audio compression similar to Opus? Especially the "heavy 30 percent receiver-side packet loss" example sounds a LOT like the experience I have sometimes.
Was going to post the exact same here. Economics major. Making this comparison shows lack of insight into what a central bank actually does, or the power it yields.
Tried both for quite some time, Obsidian has better community plugin support, better sync (paid) and stores plain text files instead of using a DB. Most importantly the mobile app (at least for iOS) of Obsidian is 1:1 with the desktop app.
Switched from Joplin to Obsidian and haven't looked back. Both apps are great initiatives though!
Does it reflect notebooks/folder structure also in the filesystem? That's exactly what I need from a PKM tool: that not only the files but also the structure of the notebooks is reflected in the filesystem so I can have interoperability. This way I can decide to work with Obsidian, EagleFiler, Notebooks.app or DEVONthink while also having the possiblity of using the regular Finder to work with my files.
