This would be a great win for merging Literate Programming with documentation. You could show even a subset of a schema with some sample rows, and show developers what is at stake.
Sure wish that had been done with the field of dirty diapers I'm wading through a the office.
This is neat, but (and I say this as a 14+ year diehard Emacs fan and average-skill elisp hacker) this seems like a classic example of things in Emacs world being overly complicated.
I almost didn't comment because I hate to take a cool thing the author did and turn it into a negative, but I've been thinking a lot about this complexity lately because of a recent foray back into the Vim world.
I've been moderately Vim proficient for most of my career, and decided to give things another try now that Neovim and Lua-based configuration is so popular. I was astounded by how simple and straightforward it was to get an LSP + Treesitter + DAP + Telescope, etc setup working, and with a clean and relatively compact amount of code.
It just felt so uncomplicated, and everything just worked. No using temporary bridge packages for treesitter modes, while still needing to copy over your mode hooks and set parent keymaps. Fuzzy completion that is consistent and doesn't depend on which company backend is in use. DAP mode layouts that consistently work as well as e.g. VS Code (I still cannot get Python's Rich library progress bars to show up in dap-mode output on emacs).
I still prefer Emacs, but am glad I went around the block with Neovim. It's inspired me to start a ground up rewrite of my Emacs configuration in the quest for simplicity, so maybe there's hope for my config yet.
Nice. Love vim too, but letting go of org mode is too much of a negative to justify a switch.
I know I could use Emacs just for org mode, and vim for everything else, but that seems like even more overhead.
> It's inspired me to start a ground up rewrite of my Emacs configuration in the quest for simplicity, so maybe there's hope for my config yet.
Allow me to be the first to encourage you, for the satisfaction of it :) I too recently yak shaved my Emacs Gnu and wrote about it too, for utility of course, but also for joy. And, I wrote about it here:
Neovim's tree-sitter integration is so clean. I'd like to see Emacs develop a better api for injecting multiple parsers, like neovim's `#set!` queries. Currently, I've found multi-parser support to be pretty much unusable in Emacs.
Lately I've been writing blog posts for an Emacs audience who also uses Org. Org tables are part of Org Mode which is built on top of Emacs. If you're interested, you can learn more about it here. https://orgmode.org/features.html
I'm reading that page and it feels surreal all the things Org can do. I'm scrolling through amazing section after amazing section and starting to feel a little drunk. Too bad I don't use emacs!
(Aside: I love the neat and clean site design. The typeface is pleasing too. However, may I suggest serving it over https? Far too many ISPs are user-hostile and inject garbage into unencrypted traffic.)
Neat! I too use org as an SQL workbench. In fact, I am doing so as we speak, but with Postgres. However, some work with SQLite is nigh, and I will crib from your notes. Thanks for writing it up!
18 comments
[ 3.4 ms ] story [ 69.8 ms ] threadSure wish that had been done with the field of dirty diapers I'm wading through a the office.
I almost didn't comment because I hate to take a cool thing the author did and turn it into a negative, but I've been thinking a lot about this complexity lately because of a recent foray back into the Vim world.
I've been moderately Vim proficient for most of my career, and decided to give things another try now that Neovim and Lua-based configuration is so popular. I was astounded by how simple and straightforward it was to get an LSP + Treesitter + DAP + Telescope, etc setup working, and with a clean and relatively compact amount of code.
It just felt so uncomplicated, and everything just worked. No using temporary bridge packages for treesitter modes, while still needing to copy over your mode hooks and set parent keymaps. Fuzzy completion that is consistent and doesn't depend on which company backend is in use. DAP mode layouts that consistently work as well as e.g. VS Code (I still cannot get Python's Rich library progress bars to show up in dap-mode output on emacs).
I still prefer Emacs, but am glad I went around the block with Neovim. It's inspired me to start a ground up rewrite of my Emacs configuration in the quest for simplicity, so maybe there's hope for my config yet.
Ergo, use the best tool for the job.
I don’t foresee you leaving the eMacs world :)
but doom is pretty nice. the curation and integration is really helpful. Might be a nice middle way.
Allow me to be the first to encourage you, for the satisfaction of it :) I too recently yak shaved my Emacs Gnu and wrote about it too, for utility of course, but also for joy. And, I wrote about it here:
"Emerging from dotemacs bankruptcy the hard way"
https://www.evalapply.org/posts/emerging-from-dotemacs-bankr...
I've noticed everyone's life in orgmode is unique to them. Here is how I've come to use it: https://www.evalapply.org/posts/why-and-how-i-use-org-mode/
(Aside: I love the neat and clean site design. The typeface is pleasing too. However, may I suggest serving it over https? Far too many ISPs are user-hostile and inject garbage into unencrypted traffic.)