Programmer currently into streaming and cloud stuff. Formerly working on video games (PC, Console and latterly backend), Fintech, Banks, Leisure and, most recently, Marketing technology. Rust, Scala, Neovim and Emacs.
The very first paragraph about macros taking a while is wrong. They are really useful and once in your muscle memory a near instantly accessible solution to small tedious tasks.
This is true in Neovim and Emacs.
I also don't use these editors for identity. That is also dumb. I use them because it's fun and they are invisible tools once mastered.
These kinds of internet dramas get so much more attention here and elsewhere than technical discussion it makes me wonder if Andrew Kelley is a marketing genius.
Same thing happens in Ice Cube's "Are We There Yet" where the characters are driving from Portland to Vancouver but the whole movie is filmed in Vancouver and surrounding area.
The main difference in my proposal is separating git completely from asset management and replacing it with a flexible, scalable system built for that purpose
I see Git as a tool aimed at experts that spend time to learn the tool. Asking non technical people to use it is a mistake. You can build guard railed apps on top of it for them, but probably it's the wrong tool.
One of the reasons I left the game industry, or at least one the benefits of leaving was to not have to use Perforce any longer. Albeit a necessary evil, hopefully lore is better.
I always wondered if a combination of a database to index assets and asset versions with the data being in S3 style storage would be better for game assets; code can be in Git.
Then your workflows are easy to build on top of that.
Both Emacs and Neovim reward rtfm and working up from a vanilla configuration to your own custom one.
The distribution style packages for these editors make the user skip all that initial learning and discovery. It leads to people writing plugins and packages that simply replicate what was already possible. I have written plenty of elisp myself only to find out I was rewriting builtin functionality.
I'd also say that both editors are fully discoverable but you have to first learn how to use the various help available. Emacs is a bit ahead here with its help options, letting you search for functions, variables, info and man pages, apropos (fuzzy search) and more.
In short start vanilla and explore; this kind of blog really helps with that.
They already have a very codependent relationship because of their revenue share over putting Google search up front in iPhones so I doubt either party would put that at risk.
May be of interest: A Critique of Modern SQL And A Proposal Towards A Simple and
Expressive Query Language.
It is a critique of modern SQL and a suggestion for "SaneQL":
"SaneQL features a straightforward and consistent syntax, which improves its learnability and ease of implementation. Additionally, it provides extensibility, with the added ability to define new operators that integrate
seamlessly with the existing built-in ones. Unlike most data frame
APIs and NoSQL query languages, SaneQL fully embraces the core
principles behind SQL, especially multiset semantics."
This is like the Adam Sandler movie where he says bomb on an airplane.
It's an overreaction, is it not?
A terrorist is not going to call their bomb's bluetooth trigger bomb. Even if they are, are you telling me we have no idea whether there is a bomb in luggage or not?