dschuessler

You should be able to automate installing programs with homebrew.[0]

[0]: https://brew.sh/

Didn't need to. When hosting per `python -m http.server 9000` I get the same result as you. Very interesting. Thank you for bringing this to my attention.

I cannot reproduce this. I used VSCode's live previewer to host the file on localhost (macOS) and tried with the browsers you listed. Removing the meta tag or changing the doctype did not make a difference.

Is it possible that you accidentally deleted the `<plaintext>` tag when making your changes? That breaks the page for me.

Ok, thanks for the clarification! I took "Without this, text encoding sniffing takes place" to mean that this happens in general.

> <meta charset="UTF-8"> is real. Without this, text encoding sniffing takes places and some browsers just displayed rubbish.

I am curious. Which browsers do this? I thought this tag is unnecessary in HTML5 because the information that the page is UTF-8 encoded is already implicitly conveyed by the DOCTYPE. (UTF-8 is the only encoding allowed for HTML5.)

This is fun and I understand it's a joke.

But since so many people do not understand the importance of HTML for accessibility, I feel the need to stress that this page may be a horrible experience for non-sighted people.

To sighted people, obscure unicode characters may look like text in a different font, but do they for screen readers? The same goes for ASCII art and the tables on this page.

Do all the fun stuff! But please draw the right conclusions for real-world projects.

Enums are one example. They are compiled to objects existing at runtime rather than stripped out like types.

I want to like them because they save vertical space, and you can always read the page titles, regardless of how many tabs you have open.

But as with you, my muscle memory gets in the way.

I think the idea behind these products is that network requests and responses containing sensitive data never reach their target in the first place. So if someone tries to tell ChatGPT sensitive data, the outgoing request is simply blocked. Harmless content goes through, though.

There are interesting technical solutions for preventing sensitive informations from leaking that could probably enable a somewhat safe use of ChatGPT and the likes in a corporate context.[0]

[0]: https://www.cloudflare.com/products/zero-trust/dlp/

There's no way to get around YouTube-the-service, but at least you can get around YouTube-the-client: https://piped.video/

Frame challenge: You already have decided not to care about online privacy. It seems you are not looking to be convinced but rather for selected opinions making it easier for you to justify your decision to yourself.

If I am right, I suggest just moving on with your life. That is your ultimate goal, and your search for the articles and videos you requested is getting as much in the way of that as your struggle for online privacy.

Maybe https://hurl.dev/?

The author of swc is currently working on a Rust-port of the type checker: https://github.com/dudykr/stc

Here is an interview with them: https://www.totaltypescript.com/rewriting-typescript-in-rust

DeepL and Grammarly are probably the only AI-powered tools I am using in an academic context right now.

I plan to dabble with ChatGPT to bounce off ideas. Maybe emulating conversation helps against writer's block as well as the real thing. When real conversations helped me, it was not necessarily the expertise of the other person but the process of articulation that was valuable.

I recently found out that the author is John MacFarlane, a philosophy professor I have read papers from in totally unrelated contexts. I was more than surprised to see that he is the original author of pandoc. It boggles my mind how someone with an academic career in a somewhat unrelated field can have a GitHub profile like him. It's really impressive.

On topic, though, preceding sublists with empty lines is a complete non-starter for me. However, since I don't hard-wrap lines (goal 7), but use soft-wrap only, I am not in the target audience anyways.

The producer's name is Aubrey Hodges. He also made the music for Doom 64. You can find (and buy) both soundtracks on his webpage: http://www.aubreyhodges.com/discography/discography/

For those who don't know: Nitter is an alternative self-hosted Twitter client.

One public instance: https://nitter.kavin.rocks/

Github repository: https://github.com/zedeus/nitter

What a beautiful little treat. For everyone curious, it took me less than ten minutes to play through. Well done!

I am on macOS. Keybindings are probably different for Windows and Linux.

I use VSCode and mostly navigate via:

F12: Go to definition

Shift+F12: Go to usages

Ctrl+-: Go back

Ctrl+Shift+-: Go forward

Once you get used to it, it's as easy as browsing the web.

Since I started using VSCode I did not have to work with codebases that were complex enough to make these features valuable but some VSCode language extensions support tree views of call hierarchies and type hierarchies. Here's the documentation for the Java extension.

https://code.visualstudio.com/docs/java/java-editing#_call-h...

https://code.visualstudio.com/docs/java/java-editing#_type-h...

You can set keybindings for them too.

I have no experience with it but you made me remember Enso (previously known as Luna).

https://enso.org/language

Genuine question: What's the appeal of ligatures?

I never got the point. I want to see exactly what's in the document. With ligatures I have to translate what I see back to what I get. It seems like unnecessary cognitive load to me.

I settled on SF Mono long ago.

Nice explanation! As an aside, I wonder how the illustrations and diagrams are animated. What tools are used for this kind of content? I genuinely don't know.

Personally, I prefer "What do you think about extracting this into a separate function?"

Unlike in any of your examples, the subtext is: "I anticipate you had reasons for doing it the way you did and I am open to listening to them." It engages the author on the same footing, leaves the door open for discussion but still communicates your intent in a straightforward manner.

Throwing in a rare case of a descending shepard tone for good measure. It appears as background sound in the canceled Star Wars 1313 game: https://www.youtube.com/watch?v=j3TZFZ1fHhA

Right next to your terminal should be a tab called "Gitlens: Visual File History". I do not want to argue whether its contents qualify as nagging but it might be what OP is referring to.

Until February I used a 2013 Air with 8 GB. It was perfectly fine for web dev, even with Docker.

The current model will probably not even notice what you throw at it.

Concerning collapsible points and styling: You can use inline HTML at every point in Markdown. So you can use <details> tags for the former and <style> tags for the latter.

Of course, these are only valuable if you use a Markdown editor that renders a preview.