* The core idea sounds interesting. Make it the first paragraph, not paragraph seven.

* Spend more words describing what makes Oak different.

* "I built a version control system in my free-time called Jam". You probably didn't name your free time. "I built a version control system, called Jam, in my free time."

https://functionalprogrammingstrategies.com/

I'm currently writing up what is the last major chapter, which introduces capability-passing as an architecture, and builds a simple TUI framework using it. Fun stuff!

I'm a few months away from launching the book, but the early feedback is very positive. I find writing enjoyable but also, damn, do I need to get this book finished. :-)

That said, I'm the kind of person to invest time in my editor and I appreciate this post.

People holding your attitude is one thing that keeps people away from Emacs. Very few people want to get into the weeds of customizing their editor. They want to do whatever it is they are interested in and the editor is tool to get it done. Doom Emacs, and other approachable "distributions" are the way to make the power of Emacs accessible.

But really this is something you should search up yourself to follow your particular interests + constraints.

I've worked with people from Ada. Some were slackers, but the people I worked with directly were great. They were still studying, so not very experienced but keen to learn and improve. Very applied / practical focus, which has advantages and drawbacks.

I think there are others. For other kinds of engineering I don't know, but I'm sure the search engines do.

Comments URL: https://news.ycombinator.com/item?id=48493125

Points: 2

# Comments: 0

The guy's whole website is also worth clicking around. A huge amount of effort.

Birds have higher neural density than mammals (https://www.pnas.org/doi/10.1073/pnas.1517131113) so can pack a lot into their tiny heads. I do wonder what they'd have to say, if given the chance.

[1]: https://github.com/creativescala/gooey

(Don't tell me here. Make your docs better, so everyone benefits!)

The JVM is an odd place where it requires too much heap to compete with the AOT compiled languages, but its startup time is too slow compared to interpreted languages. I think these enhancements are essential to keep the platform relevant.

The great thing about TUIs is that a simple text component is a universal widget. If the user can display text and capture events they can implement any interface components they want in terms of that.

That said, whatever the framework provides pushes users in a particular direction. The core of the things I'm thinking of (some links below) is providing easily accessible context for the user right at the point where they are working. This can be completions at the cursor, or a quick key to pop up a command palette. Fuzzy search is standard.

Here are some examples:

* Corfu: https://github.com/minad/corfu

* Vertico: https://github.com/minad/vertico

* which-key: https://github.com/justbur/emacs-which-key

* LazyVim: https://www.lazyvim.org/

I've included links that have screenshots showing how they work. The list is biased to Emacs, because I'm an Emacs user (Doom Emacs in particular) and so more familiar with that ecosystem.

Hope that helps!

My framework is demonstrating the capability-passing approach to effects, which is the underlying architecture in most modern JS frameworks, Jetpack Compose, and "immediate mode" toolkits (though the authors are not necessarily aware of capability-passing as a concept). If you've read recent posts on "algebraic effects" or "effect handlers" it's in the same space. It makes for a quite pleasant user experience. I'm enjoying the work uniting theory and practice; one of the benefits of writing the book is I can justify these excursions.

[1]: https://functionalprogrammingstrategies.com/