The front page of the web site is excellent. It describes what it does, and it does its feature set in quick, simple terms.
I can't tell you how many times I've gone to a website for some open-source software and had no idea what it was or how it was trying to do it. They often dive deep into the 300 different ways of installing it, tell you what the current version is and what features it has over the last version, but often they just assume you know the basics.
actual, Constitutionally defined treason?
The kind where you actually have to be in a state of war with another country? A war that was legally declared by the US congress? Since the last time the US declared war was during WWII, and every enemy country in that war was defeated, I don't think "actual, Constitutionally defined treason" is possible today.
You sound like someone who frequently accidentally brings up the emoji keyboard when you're trying to go to the end of the line here on Lemmy.
I've done that, but that's ugly.
Also, you can use this for more than just arithmetic. The first thing in the list is the name of the function, and everything else is something that you pass to the function. So you could instead write
(plus 1 2 3 4)
Which would be like plus(1, 2, 3, 4) in other kinds of programming languages.
So, if 2 5 8 5 - × + is "RPN" does that mean that the LISP version is Polish Notation?
Brackets and Orders, not that anybody calls "(" a bracket or "^" an "order".
You don't necessarily have to do parentheses first. What matters is that the things inside the parentheses are a group that you can't break apart. If you have 10÷2+3-2*(2+1) you can do the division first 5+3-2*(2+1) then the addition outside the parentheses 8-2*(2+1) It's just that before you do the multiplication of the term outside the parentheses, you have to handle the parentheses group, so you get 8-2*3 -> 8-6 -> 2
I got really angry because the prettier code formatter insists on removing parentheses, making things less clear. Because it's an "opinionated" formatter you can't tell it not to do that without using ugly hacks.
Sure, logically there are times when you don't need them. But, often it helps to explain what's happening in the code when you can use parentheses to group certain things. It helps in particular when you want to use "&&" and "||" to say "do X only if Y fails".
Depends on the language.
I don't see anything unprofessional there. Just naughty words. But, the naughty words are somewhere where they warn you that the code below doesn't behave as expected, or complain because there isn't a better way to do something. That seems like the best time to use strong language.
Cleaning it up is a great idea in theory, but in practice almost everybody has higher priority things to be doing. Leaving a comment in the code for why something is ugly is the best thing you can do when you don't clean something up, so that someone coming along after you doesn't struggle with it. We have no idea how many "naughty" comments are no longer there because the issues they addressed were cleaned up.
Wouldn't changing your birth name require time travel?