A weak type system gives you the freedom to trick yourself.
I don't feel it's a feature.
9,193 karma · joined March 21, 2010
https://romankogan.net/math
A weak type system gives you the freedom to trick yourself.
I don't feel it's a feature.
That's what C++ templates always have been, and got way, way tighter with concepts circa C++23.
Rust's traits are also strong duck typing if you squint a little.
The idea in both cases is simple: write the algorithm first, figure outwhat can go into it later — which allows you to write the code as if all the parts have the types you need.
But then, have the compiler examine the ducks before the program runs, and if something doesn't quack, the compiler will.
My favorite feature of bike lanes there is how highway access ramps straight up cross them -
- creating a flow of cars accelerating to highway speeds coming from behind and sideways from you, while you are in the perfect spot to be obscured by the car's A-frame.
Or perhaps how I had to move away a sign saying "SHARE THE ROAD" (with bicycles, presumably) from the bicycle path. Multiple times.
No, perhaps my favorite is how the Mayor decided to show off our bicycling infrastructure by taking a bicycle ride the first day of the year, and. . .
. . . was promptly hit by an SUV, which broke his bones[1].
If you don't live in San Jose, that's all you need to know about cycling in San Jose.
[1] https://abc7news.com/san-jose-mayor-hit-by-car-bicyclist/500...
Reference: https://www.ribbonfarm.com/2009/10/07/the-gervais-principle-...
That's a common property of all large institutions: the reasons why a decision is made may as well be arbitrary, but by golly will they stick to it and die on the hill, if they can.
You're aware that you don't need a 3D scanner (much less a 3D scan) to produce a replica of a sculpture (..or a replica of a replica), right?
There's this ancient technique, known as casting, still in use today - which was used to produce some of the very sculptures being scanned in the first place!
I also strongly disagree with the author that LF is useless.
So many times in code I need to type:
Function blah(parameter1 = default1,
parameter2, ...)
It would be super nice to move down from the beginning of the word "parameter1" down to the next line even when it's empty to start typing at that position.Sure, there is auto format. But not in this comment box.
And what I'm talking about is exactly what LF was meant to do!
I want all my text boxes to support that, and to have a special key on my keyboard to do it.
Eh.
1) "Typewriters" in parent's comment didn't refer to mechanical typewriters, but
2) Line feed/carriage return semantics, as well as the UX of combining them into one action to proceed to the next line of text, predate electric typewriters and were effectively the same on mechanical ones.
As I wrote in the other comment, the subtle difference in semantics comes from teletypes, which couldn't advance the paper feed and return the carriage fast enough to print the next character in the timespan of one command.
Not that it applied to all teletypes, but it was the case for a very popular unit.
The makers of that machine deliberately didn't include a single command that would do CR/LF so that there'd be no way for the users to notice that.
The ordering, CR then LF, differs from the one on mechanical typewriters, where LF always precedes CR when you use the big lever, allowing one to use the same lever to produce blank lines without moving the carriage (in effect, doing LF LF LF ... LF CR).
On the teletypes though, CR LF ordering was, in any case, a lie, since in actuality, LF was happening somewhere in the middle of the carriage return, which took the time span of two commands.
The CR command had to precede LF on the teletype because it took longer, but since the mechanisms were independent, they could be executed at the same time.
This is the difference from mechanical typewriters.
Typing mechanism was also independent of CR and LF, and running CR + [type character] at the same time was bad. But having fixed-time-per-command simplified everything, so instead of waiting (..which means buffering - with potential overflow issues - or a protocol to tell the sending party to wait, which is a lot more complex), hacks like this were put in place.
My IBM selectric is not functional (got it as a repair project, didn't get to do it yet), so I can't verify, but I'd guess it doesn't need to do CR then LF, since it can simply not process input while the carriage is returning. It's OK for it to do CR and LF in any order, or simultaneously.
If the operator presses and releases a button during this time, the machine can simply do nothing; the operator will re-type the character the next instant, using the buffer in their head where the text ultimately comes from.
The teletypes didn't have that luxury, as the operator on the other end could be a computer, which was told it could send output at a certain rate, and by golly it did. Not processing a command would mean dropping data.
All that is to say that CR and LF are present on both typewriters and teletypes, with the following differences:
* mechanical typewriters always do LFCR due the mechanics of the carriage return lever, which was designed for a human operator;
* teletypes do CRLF because that's how they cope with the typist being a machine that can't be told to wait a bit until the carriage returns;
* and electric typewriters are somewhere in betwen and could do whatever, because the CR lever was replaced by the motor (like on a teletype), but the operator was still a human that could wait half a second without forgetting what it is that they wanted to type.
IMO, it's worth keeping CRLF around simply because it's a part of computer and technology history that spans nearly two centuries, from typewriters to Google docs.
>the lever would do LF, and pushing on it further would do CR (tensioning the carriage spring).
In any case, carriage return is just as important function of the lever as line feed:
- you can also directly do line feed by turning the roller
- line feed, by itself, doesn't need a large lever
- carriage return, by itself, doesn't need a large lever either - you can simply push the carriage
- however, having a large lever is an ergonomic feature which allows you to:
1) return the carriage without moving your hands too far from the keyboard
2) do CRLF in one motion without it feeling like two things
3) If needs be, do a line feed by itself, since the force required for that is much smaller compared to the one to move the carriage (lever advantage!).
The long lever makes it so that line feed happens before carriage return. If the lever were short, you'd be able to move the carriage until it stops, and only then would the paper move up.
So I wondered why the control codes are doing the operations in the opposite order from the typewriter.
Turns out, the reasons are mechanical[1]:
>The separation of newline into two functions concealed the fact that the print head could not return from the far right to the beginning of the next line in time to print the next character. Any character printed after a CR would often print as a smudge in the middle of the page while the print head was still moving the carriage back to the first position. "The solution was to make the newline two characters: CR to move the carriage to column one, and LF to move the paper up.
Aha! Makes sense.
In a way, this was creating a de-facto protocol by usage, in a similar spirit the the author is suggesting to get rid of it.
As in: the existing standard wasn't really supported, but letting the commands go through nevertheless and allowing things to break incentivized people to collectively stick to the way of doing things that didn't result in misprints.
Minor correction: mechanical typewriters do not have a Return key, but they have both operations (line feed, as well as carriage return).
The carriage return lever is typically rigged to also do line feed at the same time, by a preset amount of lines (which can be set to 0), or you can push the carriage without engaging line feed.
Technically, the lever would do LF, and pushing on it further would do CR (tensioning the carriage spring).
It is, however, true that most of the time, the users would simply push the lever until it stops without thinking about it, producing CRLF operation —
— and that CR without LF was comparatively rare.
From a pure protocol UX perspective, it would make sense IMO to have a single command for (CR + LF) too, just like the typewriter effectively does it (push the lever here to do both at once).
It seems weird that the protocol is more limited than the mechanical device that it drives, but then again, designers probably weren't involved in deciding on terminal protocol specs.
https://www.farmanager.com/screenshots.php?l=en
It's Windows-based, but has been open-sourced by the developer, and so it's got a Linux port[1].
The UI is the closest in spirit to Norton Commander[2], which is what inspired them all (and where the term "command-style TUI" comes from).
On the off-beat, the time is ripe for someone to fork one of these 2-pane split commanders, and brand it "Hawk TUI: Split On That Thing"(c).
That's literally what a think tank is.
Or a research university, for that matter. The labs are where our brains grow.
I’m autistic (if that wasn’t apparent), and implications aren’t my territory. Take what I wrote in the most literal sense possible.
I can’t edit that comment, but I’ll surely try to be more mindful next time I write about this.
BTW, what’s everyone’s favorite NFO viewer?
With this font pack, LiteXL/Pragtical would probably do a great job, BRB gotta test it.
My point was that out the lot of disorders listed, ME is the real bitch, and a bunch of others can be grouped together.
Some comments:
-I am not equating ME with fatigue in general;
-The fatigue that I say is not uncommon in autistic people is "I can't get out of bed for a day after making a phone call" kind of fatigue;
-I made no judgement in my comment, period (side note: the phrase "you have not the slightest clue" is a judgement, however).
To re-iterate, my point was that:
- There are significant overlaps between autism and Chronic Fatigue Syndrome (CFS/ME) [1], in both symptoms and comorbidities;
- Autistic people are more likely to experience CFS/ME [2];
- What helps autistic people with fatigue is not unlikely to help CFS/ME fatigue, and vice versa (follows from the above two).
Both of those points are scientifically supported. Please see [1][2], from which the above statements are literal quotes.
The links between autism and CFS/ME are subject of ongoing active research.
I ask you to read this (and the previous) comment, read the two references below, and come back here and comment on what you concluded.
[1] https://neurodivergentinsights.com/blog/autism-and-health-is...
[2] https://www.cam.ac.uk/research/news/autistic-individuals-hav...
Eh, a bunch of those are just a part of the package that comes with AuDHD[0], Specifically these three:
- Pathological demand avoidance [1]
- Rejection sensitive dysphoria [2]
- Sensory processing disorder [3]
Then these two are can easily result from trying to live up to neurotypical expectations at one's expense:
- Persistent adjustment disorder
- Generalized anxiety disorder [4]
...and those, plus compounding trauma/cPTSD, easily yield this:
- Severely deficient autobiographical memory
(Which might, in itself, be a manifestation of Time Blindness [5]).
Personally, I don't consider these two as disorders[6] or limitations:
- Aphantasia
- Autism spectrum disorder
That's not to diminish the difficulty of living with any (much less all) of those conditions; just to say that they are not uncorrelated, and often come together.
The rest (namely, these three) have an overlap in traits with Autism:
- Developmental coordination disorder (Dyspraxia)
- Obsessive-compulsive disorder
- Chronic fatigue syndrome (Myalgic encephalomyelitis)
Of those, fatigue in general is common with autistic people, as masking can result in it.
The PSA here is that techniques, methods, tools, etc. that help Autistic/ADHD people are likely to alleviate the symptoms of everything on this list to some extent.
So if you find the list of issues relatable, but have not yet looked into Autistic/ADHD resources and communities, I would recommend taking a look to see if you find anything that you can add to your toolbox.
_____
[0] Talking from experience. See below; main page: https://romankogan.net/adhd
[1] https://romankogan.net/adhd/#Being%20Told%20What%20To%20Do
[2] https://romankogan.net/adhd/#Rejection%20Sensitivity
[3] https://romankogan.net/adhd/#Auditory%20Processing
[4] https://romankogan.net/adhd/#Depression
[5] https://romankogan.net/adhd/#Time%20Perception
[6] I know two three people with Aphantasia, and one of them was a geometry/topology mathematician (who has since left academia for software). He's at least as good in geometry as I am, and I'm a highly visual person (I'm a mathematician as well), and we share the same interest in photography (we both got Fuji X100), so at the very least, it's not obvious that it's an impairment to him to do anything.
While ADHD traits can be great to have if you are in the right environment, they also come with very obvious drawbacks. Autistic traits, on the other hand, have been a perk for me.
In general, many of the pathologized aspects of the so-called "high-functioning" autism are issues that allistic people have with autistic people, and not something that autistic people perceive as a problem for themselves. Research has shown that e.g. communication issues aren't significant in fully allistic groups or fully autisitc groups, but may appear between allistics and autistics (and therefore amount to protocol difference - which can be solved from either side accommodating the other).
Do you know how subreddits often link to other, related/friendly subreddits in the side bar?
That's a modern webring.
Perhaps we could allow ourselves to be unhappy when spotting such abuse in the wild (ranging from "OpenAI" which isn't open to "genocide" resulting explosive population growth), and all of us will be better off from it.
_____ ¹Like Orwell; see https://www.orwellfoundation.com/the-orwell-foundation/orwel...
There were online chatrooms before that. And forums before that. And newsgroups. And BBS. And FIDO.
The net was social before web even existed.
White your code to work on Musicians, pass Taylor Swift in.
If she's not a musician, your code won't compile.
This is absolutely ridiculous of Thunderbird.
That said:
1. As you said, like Dropbox, it's a local mirror, not a backup. Someone gaining access to your email and mass-deleting everything would delete your local copy too. A an actual backup of Thunderbird mail files would accomplish a backup.
2. Did your ISP somehow allow Thunderbird to log into the mailbox and gave it empty content? Or did they delete content before killing IMAP sessions? If so, it's outright malicious. Otherwise, Thunderbird shouldn't have deleted anything.
3. Having an always-on desktop box with a mail client that gets all email once a week is a lazy way to decrease the chances of being affected by something like that. Having a script that copies mailbox data into another folder (named according to date) is, well, an actual backup.
>Microsoft platform
Are you 13, and living in the year 1999?
>as a hacker, why would you want to work for an employer that uses a Microsoft platform ?
Because I want to work in organizations like NASA.
Out in the real world, people care about what gets things done more than what the FOSS community thinks about that choice.
And recruiters will use whatever platform that will allow them to find the right people.
Your definition of "bad jobs" excludes any job that matters (or pays).
Or the Tits group[2] (I swear, I'm not a member!).
Very tempted to include Tits Alternative[3] as one of my interests on LinkedIn, but I'm afraid the result will be too predictable.
Side note: The two groups that don't satisfy the Tits Alternative are very dear to my heart. Writing software to do computation in Thompson's Group and its generalizations[4] was my introduction to geometric group theory. And I ended up with Grigorchuk as my graduate advisor after learning about the Grigorchuk group.
[1] https://en.wikipedia.org/wiki/Kneser%E2%80%93Tits_conjecture
[2] https://en.wikipedia.org/wiki/Tits_group
Which they do.
Particularly, employers.
That's called "using an email client" to access email.
The way it originally worked, you know, and still does[1].
I use Vivaldi browser, which has a built-in mail client[2]. You can use Mozilla Thunderbird[3], or (gasp) Outlook.
All of them allow you to maintain a complete, offline, up-to-date copy of your mailbox, which you can export and back up if needs be.
[1] https://en.wikipedia.org/wiki/Internet_Message_Access_Protoc...
Most users also don't post much.
Most Facebook posts (as opposed to users) are nonsense and memes.
It is.
Also, when I asked whether they would have the same libertarian attitude regarding a crowd-sourced app to keep tabs on people with net worth over $1B, my modest proposal[1] got flagged and hidden -
- unlike the insulting comment that called the users who have an issue with Pave "schoolmarms" that "infest" the place, like pests to be exterminated.
Go figure.
Hypocrisy is OK on HN, calling it out is not.