I feel the same, but then I remind myself of how I used to feel about dark matter (I really disliked it). Having an arena where no scientific question is out of bounds is great.
I just use emacs for programming, not note taking or email reading or the other things people love it for. Strengths: magit, wgrep, vterm, buffer management, plugins & packaging. Weaknesses, irritations, embarrassments: yaml-mode, responsiveness, overlays & mini-buffers.
My usage of emacs is so vim-like that I’ve tried switching a few times. Vim is definitely faster, and overlays and cursor placement is much simpler and more intuitive. But there were still feature gaps and configuration issues that prevented full adoption.
Sane & interesting enough to have been disproven, by Boaz Barak iirc. Maybe not surprising since simulated annealing never achieved the results of gradient descent + backprop.
I reluctantly agree. It’s like ebikes — yes it’s great that I don’t have to pedal up hill, but on the other hand the cyclists that did it the hard way deserved the praise and glory for their achievement while weak and distracted ebikers definitely do not.
holding my nose reading this. if scientific progress killed god, it seems unlikely that meaning would emerge from more ramblings of the same kind that gave rise to him in the first place. we have learned to disbelieve in miracles and to be skeptical of novelty, that change is excruciatingly slow and its cause is failure, pain and death. nature and the feelings that nature has given us should be our philosophical guide posts.
This is great, and I need it and will use it, but what I need even more is some kind of integration with org mode (or just note taking generally). I found out the hard way that github/copilot deletes conversations after 30 days! So much for building a knowledge base with an AI assistant! I really need something a bit like Goog's `notebookllm` for capturing research, except I'd like to control it locally.
This video is one of about 60 recorded in a year long series of lectures that were delivered at Caltech early on in the project. They are archived by Pau Amaro Seoane at this address https://astro-gr.org/online-course-gravitational-waves/
you create an output arrow table and populate it with rows. but w/r/t the original idea, arrow data always comes with a schema and is efficient and compact, so it makes it easier to share data between different programs.
The key point of the article is "your data is trapped inside your program", i.e. data models can't generally be shared between programs. One thing that has improved my life has been using apache arrow as a way to decrease the friction of sharing data between different executables. With arrow (and it's file based compressed cousin parquet), the idea is that once data is produced it never needs to be deserialized again as you would with json or avro.
As a longtime emacs user, this perfectly summarizes what is most awful about it! It makes me cringe when people wag their fingers to correct the "misperception" that emacs is merely a great text editor and IDE, but rather a programmable elisp application platform. In reality, vanilla emacs with only a little bit of configuration (and as with any other editor, substantially more tinkering with installation and configuration of supporting binaries), provides a really great programming environment for almost any type of application.