News for hackers. Stuff that matters.
Re:Ligatures in programming fonts: hell no (2019) by h2odragon on Tuesday December 21, 2021 @10:01AM (#29637996)
Especially when programming, but also at most other times, I want a 1 to 1, unambiguous correspondence between the symbol I entered and the display on the screen.

Making my ":)" into an emoji is wrong. "Do what I meant" input magic bullshit is always going to be wrong about "what you meant" sometimes, and occludes the possibility of "I didn't know what I meant until I saw it" with its helpful corrections.

Have had this argument with fans of "autocomplete" systems, too. An analogy I like is a powered exoskeleton: if you had one you could run faster and jump higher and all these good things: but then when it breaks or you're not wearing it you've less native ability and no familiarity with the unassisted world, which makes you dependent on the tools.

Re:Ligatures in programming fonts: hell no (2019) by dharmaturtle on Tuesday December 21, 2021 @10:26AM (#29638242)
> [this] makes you dependent on the tools.

Socrates had a similar opinion w/r/t reading and writing:

> This discovery of yours will create forgetfulness in the learners’ souls, because they will not use their memories; they will trust to the external written characters and not remember of themselves.

I feel like you and Socrates are incorrect for similar reasons.

Humanity advances when it can hide complexity. Tools help with that. To argue against tooling because it makes you dependent on the tooling is like telling the construction worker to put away the jackhammer and pick up the pickaxe. Programmers are super productive (compared to other professions) because we can build tools that make us better programmers. The leverage recurses.

Re:Ligatures in programming fonts: hell no (2019) by msbarnett on Tuesday December 21, 2021 @12:26PM (#29639670)
> Humanity advances when it can hide complexity. Tools help with that. To argue against tooling because it makes you dependent on the tooling is like telling the construction worker to put away the jackhammer and pick up the pickaxe.

Calling replacing ">=" with a ligature for "≥" "hiding complexity" strikes me as more than a bit of a stretch. They're two different visual presentations of the same thing, neither more or less complex in-and-of-themselves.

The ligature has some external complexity, though, in that for certain things I have to remember that that's "really" 2 characters in the file, and backspacing directly in front of ≥ will net me > instead of deleting the entire thing.

So if anything, ligatures are introducing a small bit of complexity that otherwise isn't there. Any relation to Socrates' quote seems forced.

Re:Ligatures in programming fonts: hell no (2019) by lupire on Tuesday December 21, 2021 @09:00PM (#29644718)
Reading code is harder than writing. It's good to make writing harder so reading is easier.
Re:Ligatures in programming fonts: hell no (2019) by dharmaturtle on Tuesday December 21, 2021 @05:23PM (#29642840)
I had autocomplete more in mind.
Re:Ligatures in programming fonts: hell no (2019) by marginalia_nu on Tuesday December 21, 2021 @10:47AM (#29638477)
Socrates did actually have a point, though. This goes for all technology. Sure, it often makes us more capable in one way, but in many other ways, it reduces our capabilities.

Nobody today can memorize an epic like the Illiad today like people routinely would in Socrates' day. It a bit impressive if you can reproduce a 3 minute song text from memory. The Illiad often took days to recite.

Sure you can argue that tools (like writing) allow us to do more, to store more information, but the point is that they also cut us off from doing other things. Recitation from memory is available even when there is no paper.

This has gotten a lot worse recently, with tools like Wikipedia acting like external memory for a lot of people, granting them access to a lot of extremely superficial knowledge they don't actually possess themselves. It is certainly faster to look something up than to learn it, but a huge part of the benefit in actually knowing various things is to be able to connect what you are seeing now with something you know from beforehand, to generate a conclusion. That only works if you know the thing, you're not helped by theoretically being able to look it up.

The same with auto completion. Sure you can type faster, but it also means you, as a human, become less capable because you've never needed to hone the skills necessary to program without it. Programming without autocompletion is available in any text editor, even on paper.

Using tools is fine, but being completely reliant on them even to perform basic tasks is hobbling yourself. You turned yourself into an idiot in a powerarmor: Completely useless without your training wheels, unable to reason, unable to perform even simple menial tasks. I have a hard time seeing how that's made you, the human, more capable.

Re:Ligatures in programming fonts: hell no (2019) by guitarbill on Tuesday December 21, 2021 @11:32AM (#29638976)
> Nobody today can memorize an epic like the Illiad today like people routinely would in Socrates' day.

They can, and occasionally do. It tends to be people with a lot of spare time, or interested in memory techniques. And it probably helps if you know (ancient?) Greek, so it actually still rhymes. But it isn't super useful, so people generally don't.

If you paid people a living wage to recite the Iliad, you might get some more takers. We kinda do that, except it's actors in theatre plays or films. Sure, they don't take days to recite, but e.g. people put on several, different plays a year.

> It is certainly faster to look something up than to learn it

If it's faster to look it up, why bother learning it? Conversely, if someone had to look it up often, I bet it would be learned. Spaced repetition and all.

> The same with auto completion. Sure you can type faster, but it also means you, as a human, become less capable because you've never needed to hone the skills necessary to program without it. Programming without autocompletion is available in any text editor, even on paper.

I loathe this argument. Compilers or interpreters (computers in general) are sticklers for the exact spelling. Humans aren't; I still understood what you meant when you misspelled "Illiad". Why exactly spend the time and brainpower knowing exactly what something's called, as long as you have a rough idea of how the code works. Or, why spend the time typing it fully if you can have it auto-complete? When do you have to program in any text editor? Or even on paper, where the exact syntax can't possibly matter? (Equally, I'm sure that if this was a necessary skill, people could pick it up - occasionally they do, like for whiteboard interviews.)

Humans are very capable, and also lazy (one of the best engineering qualities). Don't mistake having no reason to do something with not being able to do something.

Re:Ligatures in programming fonts: hell no (2019) by atmartins on Tuesday December 21, 2021 @11:43AM (#29639115)
On your last point I'd add that using GitHub copilot has (at times) felt like pair programming to me. It has made suggestions for something I didn't know or think of yet, but I noticed that I remember that next time. So it's possible that I'm actually learning more when aided by tools, much like a teacher looking over my shoulder.

I used to work for someone who was convinced phone gps + maps would doom young people because if they became unavailable, everyone would lack navigation skills. I thought it was absurd. First, who was ever taught how to use a map explicitly (for basic usage)? Second, what is there to learn? I think these kind of arguments forget that most people are pretty bright, especially in times of need. If gps is down, I'm sure people can find their way to Burger King with a paper map and stopping to ask a few of the locals, just like everyone did intuitively back in my day. They just wouldn't have to walk uphill in the snow with onions on their belt, because the war.

Re:Ligatures in programming fonts: hell no (2019) by marginalia_nu on Tuesday December 21, 2021 @11:58AM (#29639307)
> If it's faster to look it up, why bother learning it? Conversely, if someone had to look it up often, I bet it would be learned. Spaced repetition and all.

Because of what I said, knowing something means you always have access to it. Otherwise this type of hypothetical knowledge may be an unknown unknown for you, even though you could look it up, you don't know to do it. You have access to facts, not understanding.

Real knowledge enriches all areas of life. If you for example learn to write with a pen (not just to scribble crow's feet, proper calligraphy), you will never look at letters the same way again. You could go your entire life not acquiring this understanding, but your world would have fewer colors, less nuance. Handwriting also means you must think through what you want to write before you write it, which is another practical skill.

It's similar with music, if you learn to play an instrument, you will never hear melodies quite the same. Better still if you learn to dance, beyond an entirely new connection with your body, music will forever gain entirely new dimensions.

If you learn to cook, you will appreciate flavor in different ways, be able to pick the taste of individual ingredients when tasting a soup. It isn't just just "that's good", or "that's bad", but "oh, is that celery?"

It's not just about what this knowledge let you do, that is the least of my concerns, but how they shape your relationship with the world. If you only have access to the world through tools, you become cut off from experiencing it.

> I loathe this argument. Compilers or interpreters (computers in general) are sticklers for the exact spelling. Humans aren't; I still understood what you meant when you misspelled "Illiad". Why exactly spend the time and brainpower knowing exactly what something's called, as long as you have a rough idea of how the code works. Or, why spend the time typing it fully if you can have it auto-complete? When do you have to program in any text editor? Or even on paper, where the exact syntax can't possibly matter? (Equally, I'm sure that if this was a necessary skill, people could pick it up - occasionally they do, like for whiteboard interviews.)

This is not my problem with autocomplete, but rather that it prompts you with suggestions for things to type. I absolutely use shorthand when I write code by hand. My beef with autocomplete is that your programming turns into a series of multiple choice questions as to what to do next, rather than something you truly drive by yourself. How questions are posed absolutely shape what sorts of answers you will come up with, and if you are not the one posing the question, you will never truly be in control.

Re:Ligatures in programming fonts: hell no (2019) by guitarbill on Tuesday December 21, 2021 @02:15PM (#29640918)
> Real knowledge enriches all areas of life [...] if you learn to play an instrument [...] if you learn to cook

I don't disagree that there's value in knowing something. But I don't have a problem with people choosing what they want to know and invest time in (like cooking or playing instruments), and being able to ignore stuff that doesn't really matter to them (trivia, whether it's information on wikipedia, or random programming stuff).

In fact, that's one of the great things about modern times. There's more information out there than ever, so you can go really deep into an area (like calligraphy), even as a relative amateur. You can't do everything though, so it's a trade-off. Being able to forgo memorisation of things you don't want to prioritise is possibly a boon then?

I'm not sure of the equivalence of "knowledge"/rote memorisation vs doing an activity. We're getting a bit deep here. Personally, I'm not sure e.g. memorising the Iliad makes you that much better at writing epics, at least compared to trying to actually write epics (there's going to be some cross-pollination, but how large is that effect, and can you also get it by studying the Iliad without remembering it in its entirety?). At least memorising poems in school didn't make me better at writing them.

Or closer to home, is memorising random programming snippets (because of the lack of auto-complete) is superior to actually just writing code? Certainly studying e.g. a well designed standard library and noting design patterns is helpful, and knowing commonly used functions will make you more efficient, but there's no substitute for actually doing the thing/activity.

Re:Ligatures in programming fonts: hell no (2019) by elevader on Tuesday December 21, 2021 @12:24PM (#29639642)
But how does memorizing all 33 methods of your AbstractBeanFactoryProviderImpl enrich anything?

Learning to play an instrument is enriching because you start to understand the logic/inner workings behind the music you listen to. You need the same skill for programming, sure, but I don't see how autocomplete would replace that.

Re:Ligatures in programming fonts: hell no (2019) by marginalia_nu on Tuesday December 21, 2021 @12:33PM (#29639770)
> But how does memorizing all 33 methods of your AbstractBeanFactoryProviderImpl enrich anything?

Auto-completion is no doubt a large part of what's enabled your AbstractBeanFactoryProviderImpl to get those 33 methods in the first place. Which is a big part of my point, autocompletion shapes the way you think about code, shapes how you write code.

There are also a lot of examples of functions that, by name alone, do not do what they seem to do. That shouldn't be, you might say. But even in the face of that objection, they do exist. It would be very easy to jump to the conclusion that for example "Boolean Boolean.getBoolean(String)" parsed the string and returned its boolean equivalent.

Re:Ligatures in programming fonts: hell no (2019) by elevader on Tuesday December 21, 2021 @05:23PM (#29642837)
> Auto-completion is no doubt a large part of what's enabled your AbstractBeanFactoryProviderImpl to get those 33 methods in the first place. Which is a big part of my point, autocompletion shapes the way you think about code, shapes how you write code.

Sure, but that doesn't necessarily make it better or worse. People have written horrible code without auto completion, just like they have written horrible code with auto completion. I'm not convinced that you just magically get better at thinking by making your life harder and typing more for no real reason.

> There are also a lot of examples of functions that, by name alone, do not do what they seem to do. That shouldn't be, you might say. But even in the face of that objection, they do exist. It would be very easy to jump to the conclusion that for example "Boolean Boolean.getBoolean(String)" parsed the string and returned its boolean equivalent.

And not having auto complete doesn't help with that at all. Auto complete MIGHT also include commentary for the function and explain what it does (if that commentary exists in the first place) and at least help with the issue.

Re:Ligatures in programming fonts: hell no (2019) by simiones on Tuesday December 21, 2021 @11:10AM (#29638736)
The goal of most work is not to make you, the human performing the work, more capable - even when you're performing it for yourself.

The goal of work is to achieve a goal. Whatever achieves that goal most efficiently while not creating problematic "debt" is always to be preferred.

Your example of "writing code on paper" is a perfect example of a non-problem. When you write code on paper, the name of the function doesn't matter, since this is not executable code. So, whether you call it "sort" or "order" is fully irrelevant. Even if you "call" a function that doesn't exist, as long as the intention is well captured, it's not a problem. Say, if I'm writing "C" on paper and I write `arr.Sort()`, that will not affect anyone: it's simply a way to express what I want to do. If I'm ever going to write this as a program, I may use qsort(), or implement an actual sort function, or whatever makes sense.

Overall, memorizing things that don't need to be memorized "just in case" is more a circus trick than an actual useful skill.

Re:Ligatures in programming fonts: hell no (2019) by elevader on Tuesday December 21, 2021 @12:14PM (#29639494)
> Nobody today can memorize an epic like the Illiad today like people routinely would in Socrates' day. It a bit impressive if you can reproduce a 3 minute song text from memory. The Illiad often took days to recite.

AFAIK this isn't something that was very common back then. Reciting the Illiad was not a hobby but more like a paid profession. People paid for this precisely because reciting something for a few evenings from memory takes a lot of skill/training and most simply couldn't do it. Same as today.

Re:Ligatures in programming fonts: hell no (2019) by marginalia_nu on Tuesday December 21, 2021 @12:51PM (#29640005)
It was an oral tradition. Recitation was how it was passed on before it was finally written down. You see the echoes of this in a lot of early Greek writing, they contain a large amount of quotes out of Homer. Being able to navigate this maze of "Darmok and Jalad"-speak with Homer quotes meant you were well educated.

Only thing I've found that comes close is some of Augustine's writing. He does the same with Bible quotes in his Confessions.

Re:Ligatures in programming fonts: hell no (2019) by elevader on Tuesday December 21, 2021 @05:17PM (#29642785)
I know, I learned ancient greek in school, the history and writing was a large part of that. Most (I'd guess > 95%) of the Greeks weren't able to recite the Illiad if I remember that correctly, oral tradition or not. Even the best educated of them wouldn't really have been able to do so. They were familiar with the content, of course, just like a lot of people in what we consider the West are familiar with what the bible is about. But I'd be happy to be proven wrong about that, school was a long time ago :)
Re:Ligatures in programming fonts: hell no (2019) by tharkun__ on Tuesday December 21, 2021 @11:10AM (#29638733)
I think there's nuance to that. As in I think the truth lies in the middle.

I am someone that wants to know 'enough' about how stuff works underneath. I don't like too many magic tools. I need to understand enough about it to be able to diagnose and work around failures.

I have no qualms about using the tools though. I definitely want the jackhammer and the power armor! I want auto completion. It's awesome. It makes me so much more capable to quickly be productive in an unfamiliar code base or framework (if naming is sane ;)). If I don't have it? Sure I'll read the API docs and swear under my breath. Happens every time I gotta work on our python code. Could I do it better by having it in my working memory? Sure but I don't work with that code often enough for it to make sense to keep in memory (or learn in the first place).

Re:Ligatures in programming fonts: hell no (2019) by iforgotpassword on Tuesday December 21, 2021 @10:58AM (#29638599)
I wonder if it ever collapses. It's probably unlikely, the analogy of layers that strictly build upon each other might not be the best, but on every iteration where we hide complexity, some knowledge from a few layers down is lost, and we might do one thing more efficient now, but another thing in a more convoluted way, without even realizing. So it's hard to say whether it was worth the tradeoff. I guess everyone working in tech for long enough has some pet peeve about where something was way easier 20 years ago, or stories about junior devs frequently not knowing X and doing Y in a really dumb way, and are super surprised when they learn X and then get told it had been around for decades. It's obviously a net gain after all, but if you were able to look at it from a distance with total knowledge, it's also hilariously stupid. But then that's exactly how evolution works, and why there's a nerve going from your brain to your throat taking a detour around the aorta.
Re:Ligatures in programming fonts: hell no (2019) by kodah on Tuesday December 21, 2021 @11:20AM (#29638846)
When I think about the "tower of abstractions" collapsing I usually end up coming back to the thought that it won't be a total collapse. It'll be a collapse to or around a specific layer of abstraction that we need to rework from (eg: something significant changed about a previously safe assumption). Like the 1906 earthquake in SF, it knocked down most buildings that had architecture that could not support the stress of an earth quake.
Re:Ligatures in programming fonts: hell no (2019) by couchand on Tuesday December 21, 2021 @10:51AM (#29638523)
The best programmers I know are able to see through the abstraction and are comfortable getting into the lowest-level details. They have those skills because they've actually used them.

I'm not saying we'd be better off without optimizing compliers, but I do think every programmer should have practical experience taking the lid off and poking around inside.

Re:Ligatures in programming fonts: hell no (2019) by simiones on Tuesday December 21, 2021 @11:20AM (#29638838)
There is a major difference between being able to poke into low-level details and being able to program at full efficiency in Microsoft Notepad or ed (which is what the OP seems to be advocating for).

One is a rare and occasionally extremely useful skill, the other is basically a party trick, like being able to recite the Illiad from memory.

Re:Ligatures in programming fonts: hell no (2019) by seanmcdirmid on Tuesday December 21, 2021 @10:28AM (#29638249)
> An analogy I like is a powered exoskeleton: if you had one you could run faster and jump higher and all these good things: but then when it breaks or you're not wearing it you've less native ability and no familiarity with the unassisted world, which makes you dependent on the tools.

Assistive technology is the result of historical progression, so why eschew auto completion because it might fail when you don’t eschew your computer which might fail as well? Should we all just be programming on pen and paper because that’s lower down the progression stack and has less chance of failing? You know that argument was probably made in the 70s by some old school programmer when those fancy new interactive terminals started coming out (I believe dijkstra actually said something to this effect, but can’t find a source).

Re:Ligatures in programming fonts: hell no (2019) by couchand on Tuesday December 21, 2021 @10:54AM (#29638557)
> Should we all just be programming on pen and paper because that’s lower down the progression stack and has less chance of failing?

Yes. Not because of the resiliency (it's hard to imagine a failure mode where pen-and-paper programming would be the only option) but because it makes you better at your craft.

Re:Ligatures in programming fonts: hell no (2019) by seanmcdirmid on Tuesday December 21, 2021 @11:23AM (#29638881)
I mean, sure. We should always know the stack down to the electrons. Not only should we learn to code on paper, but build our own adders from primitive boolean logic gates. But this doesn't really follow (most of) us out of our BS computer science program (or perhaps until we have to do programming interviews).
Re:Ligatures in programming fonts: hell no (2019) by goblin89 on Tuesday December 21, 2021 @11:57AM (#29639290)
I’m of two camps.

On one hand, I don’t use fonts with ligatures (I use Triplicate by the OP, very happy with it), and usually work without colorful syntax highlighting.

The assumption is that code is read more often than it is written, and I have no idea how my code will be read in future—thus the rule of thumb: if I understand it when it’s plain text monochrome, then the next maintainer (or future me) will be able to understand it with syntax highlighting on. I’m already biased to understand my own code more easily than anyone else, so I shouldn’t need extra visual aids if I’m not the only one who’ll work with it.

Plus, ligatures, syntax highlighting and auto-completion strike me as, in a sense, attempts to create a rudimentary GUI (TUI) to AST on top of plain text—but due to limited capabilities to work with it’s always semi-broken: syntax highlighting is off, ligatures have false positives, etc.

On the other hand, the idea that “we must keep using plain text” strikes me as somewhat stuck in the past.

The age of syntax-tree-driven, program-as-structured-data version control and editing capabilities must not be far off. At that point, we’ll likely get much greater flexibility—highlighting/autocompleting not just tokens but entire patterns (for adequately structured programs), exposing new refactoring operations, and more. We might start seeing cases where a genius high-level architect may not be that proficient at editing programs in plain text, and it’ll be obvious in hindsight.

(As an aside, I’m a little sour that GitHub/MS threw resources onto black-box ethically questionable Copilot rather than structured code.)

On the third hand (one foot?), there’s something to be learned from ligature+syntax highlighting+linting text-based authoring experience as a GUI—generalizing a little, we don’t have many other GUIs that attempt to present source data nicely while maintaining it zero-effort for you to drop into low-level edit mode. I wish whatever next-gen structured code authoring experience comes next has implementations that preserve this feature.

Re:Ligatures in programming fonts: hell no (2019) by CRConrad on Tuesday December 21, 2021 @06:17PM (#29643316)
> On the third hand (one foot?)

OTGH, "on the gripping hand". Like many 1980s - 90s online idioms a science fiction reference, in this case to https://en.wikipedia.org/wiki/The_Gripping_Hand

Re:Ligatures in programming fonts: hell no (2019) by seanmcdirmid on Tuesday December 21, 2021 @12:25PM (#29639651)
Code completion is basically the way you get structured code capabilities in a non-structured editor. Ah, but it was invented to solve an input problem in Alice Pascal (circa 1985) which was totally a structured programming environment, so in a way code completion is a product of the environments you are wishing for.
Re:Ligatures in programming fonts: hell no (2019) by goblin89 on Tuesday December 21, 2021 @12:37PM (#29639822)
I don’t know if I’m “wishing for” such environments, I just strongly suspect they will arrive (or they technically should, if they overcome industry’s inertia).

ALICE offered structured editing in a world where graphical output was so limited (and the lacking capability to just enter text in freeform was definitely a dealbreaker). I wonder how such an IDE could look today if rethought from fundamentals after all the advances in making and displaying GUIs.

Re:Ligatures in programming fonts: hell no (2019) by seanmcdirmid on Tuesday December 21, 2021 @04:28PM (#29642330)
They've been arriving for the last few decades, but haven't been successful yet. No one has really thought through a fluid efficient editing experience for them that can leverage the benefits of structure without the stilted input entry that the structure seems to imply so far...and our understanding of UI hasn't gotten much better than it was before. Someone might crack it someday, I hope.
Re:Ligatures in programming fonts: hell no (2019) by goblin89 on Tuesday December 21, 2021 @05:50PM (#29643062)
The problem is versioning code as structured data. It is not yet here, but there are very recent advances (Pijul et al). Freed from the shackles of LoC, GUIs can do all sorts of magic with structured.
Re:Ligatures in programming fonts: hell no (2019) by KarlKemp on Tuesday December 21, 2021 @11:51AM (#29639219)
I wish people wouldn't indulge in these luddite fantasies of some ancient caste of ninja programmers. It's blatantly wrong to the point where I'm not sure if the above is not meant as a joke.

It's also insincere: do you regularly write out code with pen & paper? No, of course not. Nobody does. Just like nobody reads all the fine print, checks the emergency exits every time they enter a building, has an emergency drinking water reservoir, or a go-bag for volcano emergencies: these are teenage fantasies of what grown-up life should be like. Believing and propagating these ideas only sets you and your listeners up for failure.

Re:Ligatures in programming fonts: hell no (2019) by couchand on Tuesday December 21, 2021 @03:45PM (#29641900)
I spend a lot of time thinking through problems with pen and paper, and also highlighter and printer, and whiteboard. I've found this class of tools often lets me focus on a problem with less distraction.

It's not always the right tool, and of course the code must be typed up sooner or later.

I often work in environments where the development cycle time is terribly slow for one reason or another, which puts a premium on thinking through things ahead of time.

Re:Ligatures in programming fonts: hell no (2019) by CJefferson on Tuesday December 21, 2021 @10:18AM (#29638157)
I'm sure builders would struggle without diggers and cranes, and doctors would struggle without electricity. But why would I purposefully do away with useful modern inventions just so I can remain compitent without them?
Re:Ligatures in programming fonts: hell no (2019) by h2odragon on Tuesday December 21, 2021 @10:23AM (#29638199)
Why would you occasionally lift heavy weights, only to put them back down, repeatedly? But this activity is viewed as beneficial by so many that there's an industry providing for it.
Re:Ligatures in programming fonts: hell no (2019) by simiones on Tuesday December 21, 2021 @10:53AM (#29638543)
The key there is "occasionally". Fitness is deliberate practice: you don't just carry heavy weights when you need to get something done, you explicitly go when you have time to exercise your muscles.

Similarly, if you want to occasionally exercise programming without assistive technologies, more power to you. But if you're tying one hand behind your back while your goal is to actually produce useful code, then you're just being silly. Might as well use a screen reader instead of looking at the screen, or literally tying one hand behind your back.

Re:Ligatures in programming fonts: hell no (2019) by tharkun__ on Tuesday December 21, 2021 @11:26AM (#29638913)
I think assistive tech is awesome but we should so use it to learn. Instead of slowly looking up stuff in API docs and typing it out, running the compiler slowly to let it tell me I have a typo in a long method name I have an IDE with completion and it tells me right away if I did mistype something I didn't autocomplete.

But I should use this to learn too. Learning by doing. Autocomplete to find the method that I need and next time I remember the name already and I don't have to find it in an autocomplete list I type the unique part and autocomplete the rest. I just gained efficiency and I would also be able to program without the assistive tech when needed.

Like making use of the fact that I could walk to the grocers or bike and use that to work out naturally while getting fresh air. But if it rains I'll take the car. No need to pay a fitness studio.

Re:Ligatures in programming fonts: hell no (2019) by wanderingstan on Tuesday December 21, 2021 @10:49AM (#29638496)
In the original case, the goal is to maximize effect in the external world. Here, tools that magnify one’s performance are desired.

In your weight lifting case, the goal is to maximize effect individually in your body. Here, the work of your body is the point.

Re:Ligatures in programming fonts: hell no (2019) by User23 on Tuesday December 21, 2021 @11:46AM (#29639154)
I wonder if it would be possible to hire desk workers for 6 hours a week of manual labor that happens to also be good exercise. Surely there are people that would rather make 300 extra dollars a month for their 6 hours a week of exercise rather than pay a gym.
Re:Ligatures in programming fonts: hell no (2019) by Joker_vD on Tuesday December 21, 2021 @11:08AM (#29638724)
And one of the points of maximizing that strength-building effect in your body is to increase your body's capacity to effect change in the external world (with or without tools), is it not?
Re:Ligatures in programming fonts: hell no (2019) by simiones on Tuesday December 21, 2021 @11:13AM (#29638776)
For most people, it is certainly not. The vast majority of people who exercise do it for health and aesthetic reasons.

If we could have abs and a perfect heart while eating McDonald's and never moving more than 3 steps, the vast majority of gyms would close down.

Re:Ligatures in programming fonts: hell no (2019) by Someone on Tuesday December 21, 2021 @11:02AM (#29638648)
Because we have more efficient ways to lift weights, very few people get paid to do that. So, feel free to lift weights at home, but don’t expect to get a job loading a ship by manual labor.

It’s the same when writing programs: when at home, do whatever you want, but in a job, efficiency is key.

(Back to the subject at hand: I doubt whether ligatures help or hinder much, efficiency-wise)

Re:Ligatures in programming fonts: hell no (2019) by mannykannot on Tuesday December 21, 2021 @11:04AM (#29638679)
So you can conveniently stay fit without limiting your career choices to those involving manual labor.
Re:Ligatures in programming fonts: hell no (2019) by godDLL on Tuesday December 21, 2021 @10:49AM (#29638508)
You and the parent comment are polar opposites, I see.

How about it's fine, as long as I can still put my cursor in between the two underlying characters (edit them separately), and the resulting digram doesn't look so different as to be distracting?

Re:Ligatures in programming fonts: hell no (2019) by blackoil on Tuesday December 21, 2021 @10:42AM (#29638424)
I wear glasses that help me see `better`. When I don't have them I can't see. If I stop wearing glasses I may get adapted to that, but I prefer glasses and I always wear them.

I also like my code colored/beautified/ligtured.

Re:Ligatures in programming fonts: hell no (2019) by Joker_vD on Tuesday December 21, 2021 @11:03AM (#29638667)
"I don't walk/carry groceries/exercise, instead I drive the car around. If I don't, I can't actually carry heavy stuff because of my weak body, and sure, I may get adapted to that (and may even become healthier in process, meh) but I prefer to drive the car and so I always do." That's a different analogy and it suggests a completely opposite conclusion. Which one of these analogies is correct? Maybe they both are faulty?

P.S. I too wear glasses and you know what? I'd rather be able to see well without having to wear them. Alas, the technology is not yet here (well, it is, but I was told the chances of complications that could leave me completely blind were about 20% so uh, I'd just wear glasses even though they're quite a nuisance to wear with a face mask).

Re:Ligatures in programming fonts: hell no (2019) by couchand on Tuesday December 21, 2021 @10:57AM (#29638585)
Intuitively I feel there's a big difference between my glasses and your ligatures, but I'm having a hard time putting my finger on it...
Re:Ligatures in programming fonts: hell no (2019) by michaelrpeskin on Tuesday December 21, 2021 @10:30AM (#29638280)
I mostly agree with you - I hate when my :) it turned into an emoji, or I get smart quotes because the editor has a _different_ code point in there than what I typed. But I do love ligatures because that's just a representation on the screen that makes it easier for me to read. It doesn't change the underlying data, so I'm ok with it.
Re:Ligatures in programming fonts: hell no (2019) by mrweasel on Tuesday December 21, 2021 @10:24AM (#29638221)
Even editors that automatically put extra “ to close a string or ) when I hit ( is problematic in my mind. My workflow means that I often put “ or ( after the editor feel like I should, so I end up with ) in wrong places. It drives me nuts.
Re:Ligatures in programming fonts: hell no (2019) by Joker_vD on Tuesday December 21, 2021 @10:34AM (#29638328)
Nowadays those text editors forcefully ignore extraneous " or ): that is, you press ", the editor prints "" with the cursor between them, and when you press " second time, it doesn't print the third " instead the cursor just moves after the second ". It is annoying in those cases when you actually want """.
Re:Ligatures in programming fonts: hell no (2019) by renox on Tuesday December 21, 2021 @12:08PM (#29639427)
vscode doesn't and it doesn't even respect the setting to not insert " or ). Grrr
Re:Ligatures in programming fonts: hell no (2019) by aidenn0 on Tuesday December 21, 2021 @06:15PM (#29643303)
Font ligatures are always going to be wrong because their logic is both general and simple.

On the other hand, if you actually parse the input and use it to make transformations, it would be possible to show you what the tool your are inputting to believes you mean in a clearer fashion, which is very useful. Automated indenting and syntax highlighting (when done correctly) can catch errors as you type.

Re:Ligatures in programming fonts: hell no (2019) by dkjaudyeqooe on Tuesday December 21, 2021 @11:28AM (#29638933)
> Especially when programming, but also at most other times, I want a 1 to 1, unambiguous correspondence between the symbol I entered and the display on the screen.

Ligatures don't necessarily stand in the way of this. It's a matter between the font and the syntax.