neatcoder
Joined 7 years ago
Karma
54
Submissions
32
Member since
Feb 7
Recent submissions
Comment · 7 years ago
Thanks. Fixed now.
Comment · 7 years ago
For those who are wondering what this refers to, it is writing code like this:
"foo".equals(myVar)
myVar.equals("foo")
Comment · 7 years ago
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.
Comment · 7 years ago
What's your point? Shell is also standardized by POSIX.
Comment · 7 years ago
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.
Comment · 7 years ago
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.
Comment · 7 years ago
Preferably something with the syntax of Java.
Comment · 7 years ago
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?
Comment · 7 years ago
Any recommendations for introductory text for writing compilers and interpreters?
Comment · 7 years ago
Exactly! This looks like an apples vs. oranges comparison.
Comment · 7 years ago
Is there anyone here who still writes code in BASIC? If so which interpreter/compiler do you use?
Comment · 7 years ago
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.
MdMe (https://github.com/susam/mdme): This is pretty much TeXMe without MathJax support.
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.
Comparison of TeXMe vs. Markdeep by the author: https://news.ycombinator.com/item?id=18314175