My crazy take is that there needs to be a interpretative language alternative to Python which uses brackets to define scope and/or things like elif/else/fi/endif/done. Much easier that way in my opinion, and the ";" shouldn't be necessary. I'm used to Python, but if I had another language which can be used to serve similar purpose to Python with those features, I would never code in Python again when it comes up.
Having to code in Julia and G'MIC (Domain-Specific Interpretative language that is arguably the most flexible for raster graphics content creation and editing), they're the closest to there, but they're more suitable for their respective domain than generic ones.
Ruby does that (well you use the keyword "end" instead of a bracket) but it fell out of favor before it got as big as python, to my knowledge, because of worse multithreaded performance in comparison (which I think has been fixed) and a bias towards unix systems over windows
For me the big issue with Ruby—which admittedly has many fine features I would like to see in other languages—is the lack of a general standard for its operations. There are so many ways to get the same basic logic loop done, it feels like a recipe for either unfollowable code or chaos in programming teams.
Ruby has for, while, do-while, until, rescue, inlined conditionals, optionals, and iterators, for what amounts to the same task; not to mention exceptions (something the C standard has repeated swerved away from, wisely) and lambdas.
I'm not saying that there isn't a time for Ruby, but if you think C falls into the same category then we're very much in disagreement.
How exactly are rescue, inlined conditionals and optionals used for creating loops? Also Ruby's for and while do different things, unlike for and while in C.
Personally staying away from Windows is a huge plus for me. I don’t want to read every caveat about how “this part sucks because Windows is trash” everywhere in the documentation. I do my best stay away from that mess.
My crazy take is that there needs to be a interpretative language alternative to Python which uses brackets to define scope and/or things like elif/else/fi/endif/done. Much easier that way in my opinion, and the ";" shouldn't be necessary. I'm used to Python, but if I had another language which can be used to serve similar purpose to Python with those features, I would never code in Python again when it comes up.
Having to code in Julia and G'MIC (Domain-Specific Interpretative language that is arguably the most flexible for raster graphics content creation and editing), they're the closest to there, but they're more suitable for their respective domain than generic ones.
Ruby does that (well you use the keyword "end" instead of a bracket) but it fell out of favor before it got as big as python, to my knowledge, because of worse multithreaded performance in comparison (which I think has been fixed) and a bias towards unix systems over windows
For me the big issue with Ruby—which admittedly has many fine features I would like to see in other languages—is the lack of a general standard for its operations. There are so many ways to get the same basic logic loop done, it feels like a recipe for either unfollowable code or chaos in programming teams.
So it is a real perl replacement.
This also applies to C.
Allow me to clarify.
C has for, while, and do-while. That's it.
Ruby has for, while, do-while, until, rescue, inlined conditionals, optionals, and iterators, for what amounts to the same task; not to mention exceptions (something the C standard has repeated swerved away from, wisely) and lambdas.
I'm not saying that there isn't a time for Ruby, but if you think C falls into the same category then we're very much in disagreement.
C has for, while, do-while, goto and recursion.
How exactly are rescue, inlined conditionals and optionals used for creating loops? Also Ruby's for and while do different things, unlike for and while in C.
Seems like it got... Railroaded.
Personally staying away from Windows is a huge plus for me. I don’t want to read every caveat about how “this part sucks because Windows is trash” everywhere in the documentation. I do my best stay away from that mess.
Props and big up for the G'MIC shoutout. That thing is a BEAST.
Sounds like Bython is the language for you! (only half-joking)