aartaka

Yeah, and I think it was there for longer than on Pixels.

That’s a lot of work, and I don’t expect all readers to open more than one page on my blog. But yeah, great that it sparked some debate.

That I can relate to, and that’s how some of my blog posts get born. Like this one.

You’re right with your analysis, but I still find this device ironic in addition to what you said.

Still, it’s sad we’re in this timeline.

Huh, draggability is a good argument, actually.

I know this is a bad answer, but. Web is a multi-stakeholder environment. Publishers and shitty content farms are stakeholders too. So they find a use for selection toggling in their dirty business and push for it.

But in case of text selection toggling, it has likely appeared because of the need to make interactive elements non-inadvertently-selectable. Because complex UIs.

Yeah, all these extra steps for something that should've been native in the first place. Ugh.

Life goals.

Not portable across different flavors of Android, but yeah, it’s a solution too.

Made it for y’all, it’s cool you noticed!

Accessibility though...

Hell yeah, I did that!

Totally agreed. I’m often compulsively highlighting things too, and I often get caught in clickable areas. We need proper text content, not this.

It was never supposed to be read by a sane mortal.

Actually, I figured file inclusion: https://codeberg.org/aartaka/pages/commit/a7204e7cb1d389d8e7...

Only required recursively calling ed with a pre-baked script :D

Same experience, that's why I've decided on something more down-to-the-earth and imperative.

I think Unix hackers would get horrified by how wrong and non do-one-thing-well my setup is. ed(1) was never intended to be an SSG, after all.

I'm aware of edbrowse and am trying to use it more!

And my scripts are fully POSIX-compliant, running on GNU, slewsys, and OpenBSD ed(1), so the standard is pretty reasonable.

But well, it's actually the most readable and meaningful language... to APL programmers.

This is a good style indeed, and I'm using it a lot in JavaScript, but you have to admit that it's never as consistent as that—there are basic functions mixed into it, and some lambdas, and whatever.

That's one way to think of it.

Humans read code. I'd like to become a machine someday, but alas, I still am human and I need to read mine/others' code. Lisp code too.

Well, it's all based on my experience. In two Lisp companies I worked in, colleagues complained or even were trying to fix how I indent things. So it's not just some anxiety whatever, it's experience that needs explanation and justification.

I'm aware of arrow-macros/diamond wands, and am using them myself. But I often have to write dependency-less libraries for moderately complicated algos, and that's where indentation style is the only thing I can rely on.

That's a point too!

I literally program in Lisp for five years now, and I ain't going anywhere.

That is

I'm a Lisper myself, lol.

Why 35%? I can't seem to align with you on the math here.