The 2nd thing is "Ambigious Syntax". I hadn't consciously realised how bad this is until now. "There are two kinds of braces supported by MATLAB, and instead of using one kind for function calls and the other kind for indexing"
Finally onto something that REALLY explains a lot. Some very defensive BS I had to put up with from somebody a few months ago when I told them they should be using try-statements because they are good practice.
-
-
Altho I'd no idea they were coding in Matlab until they claimed Matlab has no try. To which I replied with disbelief and then immediately looked it up. Anyway long story short it does, but it's NASTY. So this explains a little of why they were reluctant to use it, I guess.
Show this thread -
Number 11: "Programmatic error handling is near impossible"


How will students, anybody, learn to code well if they cannot learn to catch errors?!
"programmatic handling errors in MATLAB in a reliable way is near impossible."


Show this thread -
OK, now we're done, if you want to read more — and I suggest you do! — check out the blog post I based this on: http://www.rath.org/matlab-is-a-terrible-programming-language.html … And mine too for a more pedagogical perspective:http://neuroplausible.com/matlab
Show this thread -
I do not want to shame anybody but please, think again before handing down any bad habits & please bear in mind Matlab is not
#openscience not#opensource!Show this thread -
To end, I just wanna say, one of the most heartening things is seeing people like
@inferencelab blog their journey into#opensource and just generally better coding: http://www.inferencelab.com/confessions-of-a-reforming-matlab-er/ … So yeah, mad props to all of you pushing yourselves and (y)our field(s) forwards!
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.