Karl Voit

Let me start by saying I like the goal and would like to see org mode accessible to everyone, but I do have some thoughts/reservations.

> For the little code I do write, I find having AI assistance (via CoPilot or Cody) to be tremendously helpful. So helpful, in fact, that I now tend to jump into VSCode for actual coding,

Aren't there both copilot and Cody plugins available in emacs?

edit, yes and the Cody one has first-party support:

Cody: https://github.com/sourcegraph/emacs-cody (first party)

copilot: https://github.com/copilot-emacs/copilot.el

> Use VSCode for everything. For me, this requires a full-featured org mode implementation. I currently feel stuck in Emacs just because of how great org mode is.

This seems much more difficult than creating plugins you need in emacs and with the downside that customization will be much worse in vscode, especially customization of behavior with things like hooks.

> Letting go of bug-for-bug compatibility with Emacs as a goal. Let's let the quirky behavior die off and move forward with a more cohesive program, even if it looks a little bit different.

If you don't have compatibility, then you aren't really implementing org-mode... you are starting fresh. Perhaps you should take inspiration from commonmark which is a spec for markdown?

Also, there is some existing work in making a spec for org-mode in orgdown:

https://karl-voit.at/2021/11/27/orgdown/

That's okay, but you'll likely annoy org-mode users and developers as…

Probably a better link would have been the one linked to in the post*:

https://karl-voit.at/cloud/

Which has these among a long list (retaining the reverse order from link above). NB I have just copied and pasted for convenience; neither removed text which refers to links nor added the actual links. You can click through yourself if you want to follow the links.

8<---

023-08: Again Microsoft, again Azure: "unauthorized access to cross-tenant applications and sensitive data (including but not limited to authentication secrets)". If you aren't tech-savvy: this is very bad. (Source)

A reoccuring pattern emerges more and more: Microsoft didn't fix the issue in months and as of 2023-08-03 it is still an open vulnerability in Azure, risking the data of all Azure customers.
related:

Microsoft comes under blistering criticism for “grossly irresponsible” security | Ars Technica

BrianKrebs: "The CEO of Tenable just ripped Microsoft a new on…" - Infosec Exchange

2023-07: Hackers stole a Microsoft Azure Active Directory certificate which gave them full access to basically all Microsoft cloud services including Outlook, Office, SharePoint, Teams, "Login with Microsoft", and so forth. (MS blog entry, Source, German source)

With the default logs, customers could not even detect intruders as you would need to pay extra to get access to those log files.

Microsoft did not communicate which services were affected and which not.
Any Microsoft cloud service was potentially…

I was very intrigued by the the comment that led me to the posted article:

> If you have worked with ZeroMQ, OpenAMQ, AMQP or Xitami, you have worked with code by Pieter Hintjens, a Belgian software developer.

> Out of a tragic personal situation, my attention was brought to a blog article of Pieter: A Protocol for Dying. This is quite an article to chew on. Pieter was diagnosed with a rare type of cancer with not much time left. He was very open with his disease and wrote quite a few articles about his situation. In 2016, he underwent voluntary euthanasia. If you are interested in learning from this situation, I recommend browsing through his blog.

> Here, I want to draw your attention to a different article by him: Confessions of a Necromancer. This is some sort of IT-related autobiography which begins in the old times of Microcomputer. Pieter wrote down his journey through many IT projects, companies and customers.

> It's a long article. Printed to a PDF file I read on my e-ink reader, it had 43 pages without the comments.

https://karl-voit.at/2022/01/23/Pieter-Hintjens-Necromancer/

Ah, Anil, but have you fought the plaintext syntax wars yet?

Jokes apart, regular, standardised, visually-suggestive syntax is a key reason I've stuck with org-mode despite its limited acceptance in the world at large.

The many flavours of markdown make it /less/ portable than org syntax, in my experience. As the post below says, "Pandoc lists six different Markdown flavors as output formats." This is not great for collaboration --- now we need some sort of middleware or advanced editor to help people work with more than one syntax format. Besides, mixing syntax in the same document is a boo-boo, because parsers only work at file-level, not semantic token level.

Owing to this, at times, I go as far as to /author in orgmode, but share in markdown/ (org-export), and slurp back and forth (tangle / detangle).

Cue:

Org Mode Syntax Is One of the Most Reasonable Markup Languages to Use for Text: https://karl-voit.at/2017/09/23/orgmode-as-markup-only/

I like Karl Voit's methodology. He goes more deep into Personal Information Management than anyone I've seen.

> For a couple of years, I taught PIM in a lecture at the St. Pölten University of Applied Sciences. My students are surprised, how inefficient they were doing even «common» things like handling email, managing files like photographs on your computer, or searching for information. It is so rewarding to see students realizing how much improvement is possible with some background-knowledge and a few hints here or there. Starting with 2021, that lecture started at Graz University of Technology.

> I hereby claim that I am able to save you at least twenty minutes of your computer time a day just by looking over your shoulder and suggesting more advanced tools, better methods, and efficient workflows.

https://karl-voit.at/tags/pim/

Sorry to take away your reason: https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Tool-Support.org

There are multiple solutions where you may use orgdown (syntax) from within vim although I bet vim implementations will never ever reach the same level as Org-mode (Elisp) does for Emacs.

As a vim + Emacs user for decades (both daily), I would really recommend to use vim for simple editing taks and Emacs for organizing your digital life: https://karl-voit.at/2020/01/20/start-using-orgmode/ and https://karl-voit.at/orgmode/

Many die-hard-vim users switched to Emacs and wrote that in their opinion, Emacs is the better vim because Emacs is able to provide everything that vim does (including vim key bindings, excluding vim-script) but not the other way round. I know that this is hard to swallow for most vim users.

YMMV HTH