(webdev Tory) @worldsendless@qoto.org

For Clojure as a 1st language it depends upon where you want to go. But here are great trail-heads:

- the best talks, most of which don't actually involve code: https://techyaks.com/clojure-all-tytop.html

- @yogthos list of beginner resources: https://gist.github.com/yogthos/be323be0361c589570a6da4ccc85f58f

- But most of all, the community: clojurians.slack.com, clojureverse.org, clojurians.zulipchat.com. That last one includes an awesome aggregator of all of them.

Illustrating that os is struggling VS capitalism

https://techcrunch.com/2024/12/15/open-source-companies-that-go-proprietary-a-timeline/

programming today: I thought I'd start with something little. Just get the latest General Conference talks in plain-text, as I've done for years.

Error: Syntax.
Error: my language version is too much older than some dependencies. Upgrade needed.
Error: my coding evironment is 30-version too old. Upgrade needed.
Error: my Java was too old, so upgraded.
Error: my system was missing a crucial tool (Pandoc. last time using this tool was on a different computer). Installed it, which also updated 22 system packages, including my printer stuff.
Status: my original web scraper is working beatifully. Fingers crossed that nothing else broke from the accidental updates...

#Clojure #java #pandoc #programming

I want a usbc hub with two HDMI connections to be seen as two different displays, not as one oversize display. I have one old hub that manages this,but have had $ expense and frustration finding anything else with the same behavior. Insights please?

I spent 30 hours and a sick day debugging an issue I thought was my xorg setup when, in fact, it was a cruel #guix command combined with a bad version of the #LinuxKernel

#CSS media queries are worth the time and effort to remove. Modern responsiveness doesn't require specific pixel values. Why did no one's code sense start tingling a warning that Media Queries were never a good idea? #ResponsiveDesign #DRY

Why does my #emacs crash every couple hours of work? I can be doing whatever, even writing non-code. I can be in Gnome or in EXWM. Today it's occurred after about 2 hours of work, and then again 2.5 hours later. It doesn't seem to matter my window-load or my CPU load; I just hear my fans start whirring, my CPU usage goes way up, and I either freeze or even my cursor becomes sluggish. This didn't happen very often a month ago, back on emacs 28.2. What could be causing it now? Maybe #GarbageCollection?

One of the issues with the #REPL (and #emacs which is just a great big text-oriented repl) is that it is additive in nature; it usually takes major effort or a restart to REMOVE things once they've been added (thinking on plugins which modify app state). #Clojure

#guix gc is already a wonder for freeink up space. `guix gc --delete-generations` just freed over 50GB. Now will my exwm stop loading emacs 28.2 when at a prompt I get 29?

My #guix gc freed about 14gb. How about that? #GarbageCollection

Today I learned about #gnuOctave, apparently as an OS alternative to #MatLab. Full disclosure: I've never actually used matlab. Does anyone have experience with Octave? Was it good?

https://wiki.octave.org/Differences_between_Octave_and_Matlab

ah, the pains of being a power user. "Is it stable? How often do you restart?"

Well, it's not usually the software's fault. At least, not under normal usage.

Firefox just worked up my browser and froze my machine. I switched to a terminal and ran `pkill firefox`. Now I am keeping a close eye on my `about:processes` tab.

My life is so much better after I removed #emacs #UndoTree. Things that I just wrote off as failing before, and as freezing my process, just WORK now. For example, it turns out that "elfeed update" causes big buffer changes and that undotree was freezing the thread trying to track those changes. Same story with Telega startup. I had really suspected that my HD was failing; it didn't occur to me that I was getting sabotaged by a global buffer-monitoring plugin.

#emacs I was experiencing freezes of sometimes up to 30 seconds about 3/4 of the the time when I used my muscle memory to hit "undo", which I do as part of my regular "kill-line undo" combo. Something must have changed recently because I started to have show-stopping freezes of my emacs thread when I tried a routine "undo." I finally managed to squeeze a `toggle-debug-on-quit` and, with a bit of patience, got a C-g in during the freeze. The culprit in the resulting stack trace was my global undo-tree mode, which in combination with my other settings must have started failing. I turned it off by removing the line in my init.el and also running `global-undo-tree-mode` to toggle the mode and… far, no more funny freezes on undo. There are occasions when the undo tree is great and useful, but not at the cost of sometimes completely being a show stopper.

The fact that #emacs out-of-the-box includes "undo-in-region" is not only super cool, but also extremely useful. I just copied a bunch of stuff, changed it into org headings, updated the title, then realized that the stuff had multiple lines, so I undid just the heading part and removed the linebreaks before going back to headings -- without undoing the title change.

Will "Live Tweeting" a big event cause issues on a #mastodon instance? I know that cross-posting back in the day between Twitter and Mastodon seemed not good

Today I am reminded that the difference between lazy "a la" and correct "à la" is called a "grave accent," not the pinyin 4th tone. We are doing french-english, not chinese-latin characters! #unicode In #emacs that's "LATIN SMALL LETTER A GRAVE"