Native German here: In my experience the issue is in most cases not compounds, but the domain language.
There are terms that are specific to certain domains and used by everyone to precisely name a certain process. Belegprüfung, Indexpartizipation, Zessionär, etc.
Sometimes germans outside of your field of work don’t know these terms either, but those who do all use the same term. If you use english expressions you have to replace a domain term with one of multiple possible translations, making it confusing in many cases.
We have the same with translated documentation. Ever read the german version of Azure Docs? I have no clue what they are talking about until i switch to the english version.
Whats hard (and impressive in regards to those who came up with meaningful patches in the 80s) about starting with FM synthesis isn’t only the programmability (modern FM synths have that covered, see the other comments). It’s not an intuitive thing to work with algorithms and you need to learn what is happening.
I can recommend FM Theory and Applications by Musicians for Musicians for everyone who wants to create own patches:
In addition to this wonderful resource, I can also recommend getting Dexed and just playing around. It's free, open source and, importantly, as unintuitive as an actual DX7. Great for digging deep into how and why a change in an operator creates a change in a sound.
As I noted in another comment, you can start out, and get pretty far, with just a single operator pair, which basically determines the waveform and spectral complexity. For me it has a similar feel (unsurprisingly enough) to analog FM, ring modulation, or oscillator sync.
What‘s rubbing me the wrong way is the author pitting against NodeJS/Typescript on the front page without real arguments. You can pit your framework against another, but show me how it makes my life easier in comparison. Argue with features and developer experience, not with personal opinions.
„and unlike a lot of JavaScript web frameworks, Spark won’t be deprecated tomorrow.“
Especially if you can’t hold your promise. Deprecations are a normal thing in every software driven by individuals. We lose interest, get kids, etc.
The funniest part is comparing it to expressJS, which hasn’t changed much in 10 years, and saying unlike JS frameworks, it won’t be deprecated tomorrow.
There are terms that are specific to certain domains and used by everyone to precisely name a certain process. Belegprüfung, Indexpartizipation, Zessionär, etc.
Sometimes germans outside of your field of work don’t know these terms either, but those who do all use the same term. If you use english expressions you have to replace a domain term with one of multiple possible translations, making it confusing in many cases.
We have the same with translated documentation. Ever read the german version of Azure Docs? I have no clue what they are talking about until i switch to the english version.