While I appreciated Meta's early open weight models - large benefit for society, I am in agreement with Yann LeCun recently. Two things can be done: judicious use of LLMs, especially energy efficient models and infrastructure, and research into new architectures and technology.
This article struck a personal chord with me: I bought a new MacBook a week ago and installed minimal software on it, specifically I did not install VSCode and I don’t miss it.
I use Emacs exclusively on my new laptop. I have about 40 years experience with Emacs and except for a treemacs automations, I am using my regular setup.
VSCode is a great project but I just didn’t feel “happy” while I was using it. I feel happy using Emacs and I only use very minimal LLM integrations with Emacs, preferring to separately running gemini-cli occasionally, or using a variety of LLMs (especially strong local models) with one-shot prompting.
Likewise, I feel happy when using Emacs in a way that other editors do not. Emacs was made for a different era of development, with different views on what productive programming looked like. Rider, VSCode, and etc are all post-NetBeans editors and it shows. Editing text buffers isn't the focus so much as refactoring projects is; and agentic AI development slots easily into that refactoring process. With Emacs, it _feels_ purposeful, manual, and dare I say it, artisanal.
Also started using emacs (doom) a couple of months ago, after realizing that jetbrains and vscode are going to be AI-shittified, and there is no turning back.
At this point, I would recommend to every coder worth his salt to just jump to vim/neovim or emacs, these editors will be around for the next 1000 years and you wont need to fight against some BS features and you wont need to switch ever egain.
The 1-2 month learning curve is worth it!
I was a long time Emacs user, spent way too much of my life in ~/.emacs.d/init.el. I don't use it for anything other than magit any more. I just tried it again, first by upgrading my packages in package.el. Of course, everything is still locked up when I `package-menu-execute` to upgrade packages. I guess in a thousand years it will still be mostly single-threaded, with almost every action locking up the UI thread.
I’ve fallen in love with emacs again now that I can have an LLM tune up my config. I love emacs, I don’t love lisp. Maybe LLMs are helping me with that, too.
But I so happy with my config now. Simplified and modern.
Believe me I have tried. And already have made my config. Took me weeks, and is still no closer to getting to be up to par with what I get with helix out of the box.
It also is just super slow on windows unfortunately.
I'm also a long time emacs user (>15 years) but got tired of the endless config fiddling, with some packages breaking over emacs versions, other packages which were cool at the time slowly getting stale and need to switch to yet another similar incarnation of the same idea.
And most of all having to recover the config every time I use a new computer or just connect to a new VM.
I'm building an alternative, and I haven't opened emacs for a month now
I‘ve been happily using Doom Emacs on Linux as VSCode replacement. When I switched to macOS, I found the experience to be rather slow with significant input lag, though. (And yes, I did use native compilation.) Has something changed in that regard, or did you just accept it?
I had the same issues. I mainly use Doom on my linux machine, but on mac it is distractingly slow. d12frosted/homebrew-emacs-plus seemed to reduce the lag, but I've had other issues with it, so have gone back to vim.
Many Emacs functions are sluggish on my work Mac, but I found out that this is because the Cisco endpoint security software stops and checks every binary that runs, every single Goddamn time, which means that things which shell out, like M-x compile and anything in magit, are noticeably slower.
I bought a new basic laptop last year, with enough RAM, and little do you know, the VS Code did not feel faster on the new device. So last week, when I noticed that Zed for Windows is "stable" now, I've uninstalled VSC.
VS Code is still the better tool (imho) but I can't stand it.
I've been Emacsing for 30+ years at this point, but I'm frustrated at its performance in the 21st century.
By which I mean both startup time (yes, I know real Emacs people never leave the editor. I'm Not That Guy) but its single-threadedness leading to painful blocking pauses when using eglot + rust-analyzer, etc.
Q: While I agree strongly with the philosophy of this article, and twice I have set up static site generators for blogs hanging underneath my top level personal domain markwatson.com, each time I cause I could only blog when sitting at my computer, not when I was using an iPad or iPhone (I limit my daily time at a computer to just a few writing and coding sprints, otherwise I literally put my laptop away - out of sight out of mind).
Does anyone know of any mobile friendly static site generators?
I think I have about 3000 blog articles between Substack and Blogspot.
If you set up the static site generator as a CI/CD action in you favorite git provider, can work with both hosted GitHub, GitLab, etc. or self hosted Forgejo [1], you have both version control for your blog as well as an automatic way of publishing.
Sure, the UX is not that great as with a dedicated interface like substack, but building a Hugo site is really just editing markdown files anyway, most mobile git enabled editors should be able to do that.
You could use Substack/Blogspot/Mastodon themselves as your "static site generator".
POSSE (the concept linked here) is overrepresented in relation to revealed preference. PESOS (publish elsewhere, syndicate on site) is more compatible with how most people (including nerds) actually use the Internet; for all the talk about static site generators and "owning" your own "digital garden" >9/10 people would fall somewhere on the embarrassing part of the curve from the "Blogging vs. Blog Setups" comic. <https://rakhim.org/honestly-undefined/19/>
If you migrated to a fediverse instance with longer post length limits, you could use that to actually blog/post while mobile, and meanwhile you have a script on your homepage that "lazily" syncs those posts to your static site—
When anyone visits your homepage, they see your site as it was when you last built it.
When you visit your own homepage, it automatically fetches your social media feed, patches the previous input to the SSG with the new content, and then uses the APIs of whatever you're using to host your site for rolling out the new posts.
You can write your posts in Markdown, use Obsidian to sync them across devices, and render the pages in Quarto. This might not let you publish from mobile, but you can at least write them anywhere you want.
Very nice, thank you. The tests directory is good for testing, and I suggest adding an examples directory with a few very short and complete simple examples.
I think the author is better off self publishing, based on my personal experience:
I wrote ten tech books for big publishers (McGraw-Hill, J. Wiley, Springer Verlag, etc.) and I was so happy being a published author. However, about twenty hears ago I moved to self-publishing, finally ending up using Leanpub. I am much happier only writing self-published eBooks now because I can update my old books as needed. I still write new books from scratch (just started a book that is basically a rant against over-spend of SOTA LLMs called ‘Winning Big with Small AI’) but hardly a week goes by without an update to an older book.
Writing is great, and even better when not attatched to a conventional publisher.
Austin: if you are here, good luck, and enjoy writing!
I use a Creative Commons share alike license and my eBooks can be read free online. Occasionally some readers purchase my eBooks, and I use sales as a signal for what readers enjoy and that is a guide for deciding where to put my energy. I only allocate three hours a day to writing and sales also guide what books I update.
I used to keep statistics: about 1 in 60 people who read online buy a book, except for my Common Lisp book that had a 1 in 20 purchase ratio. As you might imagine, I put more effort into the Common Lisp book.
For 30 years writing tech books was an economic driver for my career as a computer scientist. Now that I am retired I still write because I enjoy writing and interacting with my readers.
I had to switch from Duck Duck Go browser to Safari, then the Book Recommendation app worked for me. For what its worth, the recommendations were good, evidenced by my having already read half the recommended books. The vibe promots to create this app were incredibly simple.
reply