The value is that it lets you comfortably watch stuff with other people.
502 karma · joined December 14, 2020
You're shipping commercial software with CL so I think you're about as hardcore as it gets :)
> I have modified the LW editor to be more "Mac-like" which I guess makes me less hardcore.
If you mean in terms of keybindings, I did the same when I did a trial recently even though I usually use Emacs for working with lisps. I think it's nice to keybindings that match most text editing programs, and I think the benefits of Emacs-y structural editing are a little overstated (in my opinion). Was just curious to hear how folks using LW do their work.
Sublime Text 4 Update FAQ, May 2021
https://forum.sublimetext.com/t/sublime-text-4-update-faq/58...
In his documentation he mentions that he made the plugin in part because he did not want Paredit mandated by a plugin. I was curious to see what kind of structural editing he used instead, so I tuned into one of his streams. Turns out he just writes raw lisp in sublime text, and he's fast as hell at it too.
Since then I've been trying out using Sublime for Clojure development and falling back on Intellij when I need anything more than basic inline/REBL debugging, and I'm very happy with it so far.
Anxiety also causes you to perceive normal bodily sensations, that you otherwise filtered out, with heightened sensitivity.
"With health anxiety there is the misinterpretation of discomfort and normal bodily sensations as dangerous. The body is very noisy. Healthy human bodies produce all sorts of physical symptoms that might be uncomfortable, unexpected, and unwanted, but not dangerous." https://adaa.org/learn-from-us/from-the-experts/blog-posts/c...
NIH estimates that 31.1% of U.S. adults will experience an anxiety disorder at some point in their lives. https://www.nimh.nih.gov/health/statistics/any-anxiety-disor....
I would encourage you to discuss with a licensed medical professional about which you are more likely to be experiencing.
Just because someone open sources something does not imply they owe the world a change in their status, focus and effort, e.g. from inventor to community manager.
As a user of something open source you are not thereby entitled to anything at all. You are not entitled to contribute. You are not entitled to features. You are not entitled to the attention of others. You are not entitled to having value attached to your complaints. You are not entitled to this explanation.
If you have expectations (of others) that aren't being met, those expectations are your own responsibility. You are responsible for your own needs. If you want things, make them.
Open source is a licensing and delivery mechanism, period. It means you get the source for software and the right to use and modify it. All social impositions associated with it, including the idea of 'community-driven-development' are part of a recently-invented mythology with little basis in how things actually work, a mythology that embodies, cult-like, both a lack of support for diversity in the ways things can work and a pervasive sense of communal entitlement."
https://gist.github.com/richhickey/1563cddea1002958f96e7ba95...
But the way that I actually got competent enough to do anything interesting with it was to learn Common Lisp, because they are similar in that learning to solve problems in Common Lisp lets you do the same in Elisp. I learned Common Lisp by reading Practical Common Lisp by Peter Seibel and writing small programs.
I would really recommend spending a little time learning both dialects because it's easy to learn "just enough" elisp to configure your setup but not enough to appreciate what you can do with it.
After I learned enough Common Lisp to build a few small projects, I realized how powerful it is to write small, bespoke functions for odd text editing jobs. You can write and save functions that do something very specific but powerful to any project you're working on, regardless of the language or tooling used, because everything uses text. I'm so glad I learned it.
They are all logical, but will unfortunately add to the burden of new learners who read books and guides that contain obsolete references. I know a lot of the material I learned with will be confusing when examples start spitting out compile errors. I didn't see if there are efforts to account for this with some custom error messages that notify you why the obsolete code no longer works and suggests how to fix it, but I think that would be helpful.
Edit: It looks like that concern was already raised and addressed, glad to see it.
I would say it's been significantly harder to achieve the same functionality in CL than Clojure, but there are major perks to the ecosystem. I was surprised by how much I've valued conditions and restarts, type inference from SBCL, stack traces, and tooling in general.
Clojure OTOH feels like it takes much less effort to get up and running, feels more intuitive to write, and has far better documentation.
I'm probably going to continue writing my project in both languages in parallel because I love learning and I spend my time poorly. I want to stick with Clojure given that it sees more use these days, but it's hard not to prefer CL once you invest the time in learning its capabilities.
As a final note, was Practical Common Lisp challenging for anyone else? I've read many glowing recommendations of the book, but at times it feels DENSE, and it took a fair amount of staring at the intermediate stages of the projects to understand what was going on.
"VR fuzzy" gave me 28,100,000 results just now on google, so.. maybe not that strange or abnormal.