Obviously floating point is of huge benefit for many audio dsp calculations, from my observations (non-programmer, just long time DAW user, from back in the day when fixed point with relatively low accumulators was often what we had to work with, versus now when 64bit floating point for processing happens more as the rule) - e.g. fixed point equalizers can potentially lead to dc offset in the results. I don’t think peeps would be getting as close to modeling non-linear behavior of analog processors with just fixed point math either.
Audio, like a lot of physical systems, involve logarithmic scales, which is where floating-point shines. Problem is, all the other physical systems, which are not logarithmic, only get to eat the scraps left over by IEEE 754. Floating point is a scam!
Nah, Python 2.7 got way more support than it ever deserved because people just refused to switch to 3. Hell, people were starting new python projects on 2 after 3 came out.
For about the first five years of its life, it was eclipsed by Perl. That’s about it. I don’t think anything will ever unseat Python as too many people’s first and last language.
BASIC was meant as a teaching language. Python is a real language that’s simple enough to be a teaching language. It also runs the same dialect on every machine, which BASIC never did.
Being the second best language at everything, it gets used for everything because people don’t want to learn the first best in any given niche. Python isn’t the best choice for numeric applications, but with NumPy, it’s adequate, so why bother learning R? Even if you knew R already, you’re going to run into a lot of Python code for that domain from other people. You’ll be swimming against the current, and why bother?
Python is one of my primary languages (the other one being Rust). But it honestly isn’t the easiest language to teach - I’m saying this from experience. There are so many concepts at play - name binding, iterators, generators, exception chains, context managers, decorators, … . I could go on and on. Teaching becomes hard because any basic question could become a journey into the rabbit hole of python semantics.
Python is, however, a good first language for self learners. (Note: teaching vs learning). Python behaves intuitively. It’s designed in such a way that if you guess something about the language, you’ll probably be right.
Web testing is also done in python. Selenium has support in all major Python test frameworks. I’ve done SE-only tests in Robot, hybrid SE/Python using BDD with Behave, etc.
Unless I’m testing a language-specific API, I’m probably going to use Python…
I’m guessing that’s because you’re a python developer though. If you’re a frontend developer who knows JS then why wouldn’t you use that for your tests? (Apart from the fact that JS is horrible, but you’ve already accepted that suffering by becoming a web dev)
Great, now consulting a search engine on questions about vim the text editor will yield equally awkward results as consulting a search engine on matters concerning latex the typesetting system.
While I understand the idea behind the naming scheme of matrix, it’s an awful name. The naming behind synapse/dendrite is better I believe. But I don’t have a better idea.
It was renamed, thats what pisses me off. The client was renamed from riot (much more unique in software context) to element. I assume riot was not investor friendly which is a lame ass reason too.
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.