aartaka

4 ms·

31.
by aartaka 1y ago
Yeah, and I think it was there for longer than on Pixels.
32.
by aartaka 1y ago
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.
33.
by aartaka 1y ago
That I can relate to, and that’s how some of my blog posts get born. Like this one.
34.
by aartaka 1y ago
You’re right with your analysis, but I still find this device ironic in addition to what you said.
35.
by aartaka 1y ago
Still, it’s sad we’re in this timeline.
36.
by aartaka 1y ago
Huh, draggability is a good argument, actually.
37.
by aartaka 1y ago
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 selec
38.
by aartaka 1y ago
Yeah, all these extra steps for something that should've been native in the first place. Ugh.
39.
by aartaka 1y ago
Life goals.
40.
by aartaka 1y ago
Not portable across different flavors of Android, but yeah, it’s a solution too.
41.
by aartaka 1y ago
Made it for y’all, it’s cool you noticed!
42.
by aartaka 1y ago
Accessibility though...
43.
by aartaka 1y ago
Hell yeah, I did that!
44.
by aartaka 1y ago
Totally agreed. I’m often compulsively highlighting things too, and I often get caught in clickable areas. We need proper text content, not this.
45.
by aartaka 1y ago
It was never supposed to be read by a sane mortal.
46.
by aartaka 1y ago
Actually, I figured file inclusion: https://codeberg.org/aartaka/pages/commit/a7204e7cb1d389d8e7... Only required recursively calling ed with a pre-baked script :D
47.
by aartaka 1y ago
Same experience, that's why I've decided on something more down-to-the-earth and imperative.
48.
by aartaka 1y ago
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.
49.
by aartaka 1y ago
I'm aware of edbrowse and am trying to use it more!
50.
by aartaka 1y ago
And my scripts are fully POSIX-compliant, running on GNU, slewsys, and OpenBSD ed(1), so the standard is pretty reasonable.
51.
by aartaka 2y ago
But well, it's actually the most readable and meaningful language... to APL programmers.
52.
by aartaka 2y ago
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.
53.
by aartaka 2y ago
That's one way to think of it.
54.
by aartaka 2y ago
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.
55.
by aartaka 2y ago
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 an
56.
by aartaka 2y ago
That's a point too!
57.
by aartaka 2y ago
I literally program in Lisp for five years now, and I ain't going anywhere.
58.
by aartaka 2y ago
That is
59.
by aartaka 2y ago
I'm a Lisper myself, lol.
60.
by aartaka 2y ago
Why 35%? I can't seem to align with you on the math here.

More ›