3 ms·
So let's say I've decided to sit down and write a digital audio workstation. I've got to pick at least one programming language and at least one general program
by PaulDavisThe1st 6y ago
So let's say I've decided to sit down and write a digital audio workstation. I've got to pick at least one programming language and at least one general programming style. Let's say I pick C++ and (somewhat by implication) a generally OOP style.
Someone comes along and says "oh, you could do this much better with Haskell and functional programming".
How can you argue that the comparison involves an "X and Y" that are not designed to solve the same problem? Advocates for languages and programming styles are generally doing so on the basis that there is a broad class of software development problems/projects that will benefit from the use of their preferred "X and Y".
Sure, there are some DSLs that are clearly not intended to be compared with (say) C++. And there are some overall programming styles that clearly suite certain kinds of software much more than others (e.g. the absence of an event loop somewhat changes everything, as does high level distributed parallelism).
But OOP isn't an example of such a thing.
- jancsika 6y ago> How can you argue that the comparison involves an "X and Y" that are not designed to solve the same problem? Because Y is Haskell and your project has soft-realtime scheduling constraints. But if Y were Rust, point taken.