I have never been able to understand the Slack fetish most tech people have. IMO MS Teams is feature-wise better in most cases. Especially functionality for formatting posts is far better in Teams.
"LaTeX is not a word processor! Instead, LaTeX encourages authors not to worry too much about the appearance of their documents but to concentrate on getting the right content."
IMO, the only people that use LaTeX are people who are willing to trade the convenience and productivity of using a sane document authoring format for the warm and fuzzy feeling you get when you use an outdated piece of typesetting software that is a) hard to configure, b) hard to use and c) produces output for the least useful reading platform available (paged pdfs).
> IMO, the only people that use LaTeX are people who are willing to trade the convenience and productivity of using a sane document authoring format for the warm and fuzzy feeling [...]
I hope you are aware that literally all research in mathematics and computer science is typed up and published in LaTeX?
Alternatively, they're people who write documents in a field where LaTeX is the standard, they're not computer savvy enough to try to even look for something new that might be acceptable or might compile to LaTeX, and at any rate they want to focus more on their research than they do on changing the typesetting norms in their field.
(No shade on people who do decide to use alternatives, and Typst is great!)
The major selling point to me, is that I can write the content I want, in a rather straightforward manner, and then just apply whatever formatting is necessary. It makes a lot of sense in the context of, say, university, where you're taking multiple classes, which each use different formatting guidelines, but those formatting guidelines stay the same for the duration of the course. I could just figure out (either using existing formats, or by hand-rolling my own) a document type for each class, and then never think about formatting again, whereas with a word processor, you've got to keep in mind the arcane series of steps necessary format your document in whatever style you require, and then pray that any modifications you make don't break the formatting.
The other place it's useful is heavily typeset documents, especially those subject to somewhat frequent modification, like a resume.
Plain text formats like Markdown work great if you don't care at all about the specifics of the final formatting. Tools like LaTeX are for when you care deeply that the resulting document follows a certain format, but don't want to think about that formatting while writing.
"And, when I was listening to them, they all sounded to me like, to me, extremely bureaucratic programming that came from the mind of somebody that has not written a lot of code, frankly."
Of the modern front-end frameworks: What is the best framework to add some front-end interactivity to a existing server-side-rendered application (Flask, Ruby on Rails etc.), without going all SPA?
I hope the author at some point adds the section on ConfigureAwait. I've seen code bases where the devs have added .ConfigureAwait(false) to all invokations "just to make sure".
In an event loop model, I've never felt the need to reach for ConfigureAwait(false). Maybe there's certain operations that could be sped up a bit by letting them resume on any thread, but generally I want to be sure that the event loop is executing my code. There wouldn't be much of a point to using an event loop if nothing ever returned back to executing on it.
If I understand correctly, when I run a docker image on Linux then the dockerized processes's syscalls are all executed by the host kernel (since - again if I understand correctly - the dockerized process executes more or less like a normal process, just in isolated process and filesystem namespace).
