I am learning about programming languages in general, and have a few questions about sclang.
I’m sorry if these questions don’t make sense. Thanks if you even answer 1 of them
– SCLange would be considered a dynamically-typed, imperative, strict evaluated, and interpreted language, right?
– Is sclang a “complete” language comparable to any other language, the only difference being that it’s “ecosystem” is all audio-related? i.e. if you took away all the classes, could you do the same things as in C++ with it’s standard library (or some other language)? If not, what’s the difference?
– What files would one look at to see what is “exposed” on the server, so someone could interact with it from other languages?
– I’ve seen people complain about sclang. Are their complaints mostly over syntax and personal preference, or are there legitimate problems with the language that are limiting? Ones that may eventually make it no longer able to keep up with other languages?
– Can you do lower level stuff like defining types, moving bytes around, and pointing to specific places in memory?
– Since it’s written in C/C++ and open source, does that mean one could potentially do anything to extend it? For example use JUCE for UI stuff instead of QT?
– People seem to make a big deal about languages being able to at least DO functional programming now. Doesn’t sclang have that ability? Are functions “first-class”?
– Is the “JIT” library compiling to byte code right before executing on the server?
– I see you can use QT stuff with SC. I’m curious why this was chosen over other frameworks?
– In your opinion, is SC development just as active as ever, slowing down, needing more developers, or something else?
I really love SC. I’m really passionate about it and have been for a decade now. I’m finally learning programming , although I chose to learn Haskell first and that might not be so helpful here. I’m just asking these questions so I can maybe have a better overall idea of stuff.
I don’t expect any one person or anyone to answer these really.
Thanks for reading!