Isn't that the right DOSBOX behavior? I think it should maintain the original aspect ratio as it looked in the old CRT monitors. I remember drawing circles in CRT monitors on IBM PCs and the circles did look vertically squished. Why should DOSBOX or FFMPEG alter that original aspect ratio? Altering that artificially would be like lying about what the real output looked like in the good old days.
That's not how I see it. Yes, the employer (the organization) may be psychopath but I am not interacting with an organization while having a difficult conversation. I would be interacting with a manager or a colleague or someone who reports to me. These are human beings who are not psychopath. These are also not short-termist. Sure, we would all change jobs sooner or later but I would sure like to maintain good relationships with them and hopefully work with them again in future. So it makes a lot of sense that while talking to them I talk to them with some empathy which I think they deserve.
Does AsciiDoc have a nice way to ignore all LaTeX code enclosed within $...$ (inline math), $$...$$ (displayed math), \(...\) (inline math), and \[...\] (displayed math)?
I think one of the problems of Markdown is that it does not provide a way for the Markdown parser to ignore any text within certain delimiters (I especially care about ignoring text within Latex math delimiters). This is the most crucial reason why I am using tools like TexMe or Markdeep.
Is AsciiDoc better in this area? If yes, it would definitely solve a big problem for me that Markdown does not solve.
Wow! Can you share your story more? What does your application do? Why did you choose BASIC 35 years ago? Did the question about rewriting it another language come up anytime? How did such discussions go? Do you enjoy writing BASIC code?
Similar topics are coming up often on HN recently. I think it's time Markdown should be supported natively by browsers. Until then, there are things like:
TeXMe (https://github.com/susam/texme): This is my personal favorite because it supports the CommonMark standard of Markdown and also LaTeX via MathJax. I like standards so that I know that the Markdown I write (especially nested lists, code within nested lists, etc.) get rendered the same way everywhere. I write some math too, so MathJax support is useful. If you are looking for something where you can just slap together Markdown and LaTeX and turn the document instantly into a paper-like finish, this is a good choice. The output can be saved as PDF or printed too just like you would print any paper.
Markdeep (https://casual-effects.com/markdeep/): This is like TeXMe but it supports a lot of features like diagrams, tables, etc. But it comes at the cost of standard conformance. Markdeep does not conform to CommonMark. I don't need these additional features for most of my writing but I care about standard conformance, so I go with TeXMe but if you need these features then Markdeep is a good choice.
When we go from 2 pairs of rabbits to 3 pairs of rabbits, we see a brother and sister rabbit mating to produce a pair of offsprings. This does not sound realistic and could also be disturbing to kids.
But for some reason, I have seen this example cited in many places. Why is this example so popular despite the implication of siblings mating while going from 2 to 3? Surely, we can come up with better illustrations if we try!
I have a similar but simpler setup. The crucial difference in my setup is that instead of using full blown LaTeX, I use TeXMe -- https://github.com/susam/texme -- which supports Markdown and LaTeX.
So I write plain text files with Markdown + LaTeX, slap a single line of TeXMe JavaScript either at the top or bottom, and open the file with browser to see the rendered math.
Like the OP I use Vim too with some customization with :ino and :ab. Nothing beats the editing productivity and convenience of Vim!
I can read color hex codes just fine. In fact, while writing my CSS, I often have a shade of color in mine and I just go ahead and type out its hex code by guesswork and then fine tune it by changing the R, G, and B values. I am not colorblind. I never thought this is a special skill! It's just basic understanding of hexadecimal, the RGB color model, and additive color mixing.
The nice thing this video helps me with is to give a name to every RGB color code. This is something I had always found difficult even though I knew what each RGB color code would look like. Giving a name to every RGB code makes it easy to communicate colors to others.
If whiteboard job interviews with clever algorithm problems are so bad, how is it that successful companies like Amazon and Google do it and they are both hugely successful?