I agree. I make adjustments depending on which parts of the page I'm on and what I'm writing. This is a nice project but I'm not sure id want to use it for anything.

I believe that this is already done to several models. One that I've come across are the JOSIEfied models from Gökdeniz Gülmez. I downloaded one or two and tried them on a local ollama setup. It does generate potentially dangerous output. Turning on thinking for the QWEN series shows how it arrives at it's conclusions and it's quite disturbing.

However, after a few rounds of conversation, it gets into loops and just repeats things over and over again. The main JOSIE models worked the best of all and was still useful even after abliteration.

- Lisp Free x Emacs like

- Lightweight x Electron

Contradictions. Writing ones own editor is a bit of a rite of passage though. So, on that front, Congratulations!

I understand the irony! It certainly sounds like a contradiction.

As I've discussed in other threads, my goal was to extract the physical UX and muscle memory of Emacs and bring it into a modern, zero-config environment. It might be a "dry water" approach, but it's what works best for my daily workflow.

Regardless of the contradictions, the experience of building my own editor has been truly exciting. Thank you for the comment and the encouragement!

dry water powder. just add water

Indeed. I don't remember all the details of the flow but the aesthetics of the diagram are still stuck in my head.

True. Damaged parents are often the kinds of people who are taken advantage of by sex offenders. I think it requires a social fix of some kind.

However damaged someone is they have a duty of care to their children. There's someone else with a blame in the story but to excuse this is very wrong.

Completely agree. It shouldn't be treated as an excuse but it's silly to ignore this as a HUGE risk factor. Probably should be considered when making policies etc.

I've never used Arch but I can really get the vibe here. Wikis (especially toopical ones) are social media of sorts. There was a strong community around the #emacs IRC channel and emacswiki.org back in the day. About a 100 people who knew each other quite well. And an Emacs bot that could read from the wiki (pre-modern RAG I suppose) and answer questions.

I think with arch wiki it is even more than that. Before I switched to arch back then, you would consult the arch wiki for an unrelated distro, because it was (is) that good. Even the aur repository helps you alot, by checking the raw scripts, how to compile stuff. I can't make a good example but it feeled like reading vi specific wiki that helped you with plugin development for emacs.

AUR is particularly useful because Arch has really simple build scripts. They are bash with some particular function names that you need to define (like "build" and "check") and a few bits of package metadata in variables. Pretty intelligible even if you don't know the format beforehand.

Contrast that with Debian build scripts which I never managed to figure out. It's dozens of layers of helpers for "common cases" with lots of Makefile magic. Completely inscrutable if you aren't already a Debian package maintainer. Very compact though.

Arch wiki is something special. It is astounding how diverse and detailed (and yet concise) it is.

I can relate to this. Early social media were forum sites, boards, irc, mailing lists and things like that.

Tangentially related. The idea that scientific research operates in a vacuum uninfluenced by real world considerations in its relentless search for truth is a notion that a lot of scientism advocates put out.

I've always found the idea laughable and this is a good example of that.

I remember a panel once at a PyCon where we were discussing, I think, the anaconda distribution in the context of packaging and a respected data scientist (whose talks have always been hugely popular) made the point that he doesn't like Pandas because it's not excel. The latter was his go to tool for most of his exploratory work. If the data were too big, he'd sample it and things like that but his work finally was in Excel.

Quick Python/bash to cleanup data is fine too I suppose and with LLMs, it's easier than ever to write the quick throwaway script.

I took a bio statistic class. The tools were Excel/ R or Stata.

I think most people used R. Free and great graphing. Though the interactivity of Excel is great for what ifs. I never got R till I took that class. Though RStudio makes R seem like scriptable excel.

R/Python are fast enough for most things though a lot of genomic stuff (Blast alignments etc..) are in compiled languages.

Whenever I had to use anaconda it was slow as molasses. Was that ever fixed?

This has been fixed for ages. The dep solver was changed to Libmamba a few years ago.

What tasks were slow?

I've been using Thinkpads exclusively from 2005 or so. My first was a T40 I got from work. Then I got a T42 of my own. I used it heavily till the fan gave out. After that, I got an X200 which I used for a long time. The keyboard got damaged because of a spill. I replaced it but somehow, the motherboard got shorted out and it died. I then bought a second hand X240 (roughly 2013) and used it as my primary machines. Replaced the battery (twice), fan, hand rest. And it's still running. My kids use it to play some simple games. My main machine right now is an X1 carbon (which I'm not really happy with compared to the others but it's okay for now).

I used a Macbook for about 2.5 years in between. Didn't like it (hardware was decent. Software was terrible). I also bought a Dell latitude (which was okay and is being used now as headless machine at my workplace for tinkering).

But my primary machine is a Thinkpad and I don't expect to see that changing in the near future.

> (hardware was decent. Software was terrible)

I'd be interested to hear which software was terrible on mac and what was the better alternative on your side of the fence?

I think it was mostly familiarity. I'd been using Linux on thinkpads for so long that I had a few config files which for the tools I used. Mine was a very text heavy command line workflow. Mostly driven by the keyboard. Almost no mouse usage (except the occasional GUI program to draw). Tiling window managers. I was also very used to package repositories which worked smoothly (Debian/Ubuntu). Brew etc. wasn't that smooth.

I suppose I could have learnt how to use it and become efficient but even the possible gains seemed very poor and I didn't think it was worth the investment. I used the smallest subset of features I needed to get my work done and that was enough.

Not original poster, but in my experience Excel on the Mac is a God-awful piece of software. It's like Excel-lite, and that just doesn't work for what I need. ymmv of course, depending on what you need.