margin-inline-start: -1.25rem for the internationally-minded & accessibility-minded developer

80 char line maximum? I read that as minimum. My bad.

Acronyms/intialism use capital letters to encode information about words. Losing that information is a mistake. SᴍᴀʟʟCᴀᴘCᴀsᴇ is now considered a best practice.

…Or I dunno try snake_case or kebab-case 🤷

ATS blasting in here to give you linear types, dependent types, & refinement types with the literal performance of C—& safety beyond all 3.

It’s all proprietary drivel & should be avoided.

Proving that adding the class keyword to the ECMAScript spec was a mistake that leads folks down a path they should not travel 🙃

I think you could make an argument about depth & shadows being more difficult with a black background but I would question your design if those were imperative to the design.

I wrote a whole post last year about how using #000 is often preferred. It’s incredibly annoying how hard it actually is to find themes that are optimized for OLED on desktop. Mobile is less bad but often, particularly in FOSS apps, black is an option.

You can write a stateless server. You can’t do stateless front-end since you have to deal with user interaction.

This isn’t speaking, but writing (or typing). Using ‘correct’ spelling & grammar helps ESL speakers read the language as well as those relying on text translation software. Some folks make typos & it’s fine to make mistakes but it’s also strange to act like it’s just as easy to understand. Apostrophes have a specific meaning & many folks rely on them for understanding.

I’m learning a foreign language now & I can tell you it is a massive stumbling block when you run into what you think is a new word, but is ‘just’ a misspelling.

My issue with this account is not its corrections, but if you want to be the correction bot, at least get the typography right too. ' is as ASCII holdover & it should be ’.

npm, Inc. (a subsidiary of GitHub, a subsidiary of Microsoft)

– https://en.wikipedia.org/wiki/Npm

Use them reluctantly & push back against it until you can free yourself from them. Let folks know you are unhappy about it or powers at be will think everything is okay. Surely we can agree fundamentally that Microsoft should not be controlling these spaces as it does with the platform lock-in.

Microsoft products you can start saying no to: Windows, WSL, GitHub, Sponsors, Copilot, VS Code, Codespaces, Azure, npm, Teams, Outlook, Office, & LinkedIn.

Could be their most used application too https://profanity-im.github.io/

The best languages about really embracing punctuation as you would in English is Prolog & Erlang with their periods, semicolons, & commas.

With indentation-based languages the bad coding style we are talking about is putting multiple statements on a line or unindenting a block …& never has that been something I wanted to do. I would rather this aspect be enforced at the language for readability where there is still room in all other aspects to try out other styles.

But newlines + indentation are supported by a lot of languages & when it is, it’s easier to read since the prevailing convention is already to newline, then in indent. When you follow the usual coding styles or autoformatted & removed the semicolons, you’ve gained nothing for readability & added noise. I much prefer the languages that take this convention & bake it in so you don’t have to have that that visual noise—and in these languages, I never felt the parsing rules were ambiguous.

Folks acting like Python is the only language without semicolons. 😏

I got tripped up so many time in the last 3 weeks using PHP after years in ML family languages. I am already newlining & it’d be poor style to put more than one statement on a line so what is the point of these semicolons?

Being attached to the CLR isn’t my cup of tea, but I have been learning its older cousin OCaml off & on the last 1½ years

I’m already annoyed by the end of public static final string that the variable name doesn’t even bother me in these sorts of langauages. All things should be public, static, & final, by default so they aren’t necessary to write. You should only have to write what unsafeties you are opting into.