>There are "experts" which do divide parts of the model that are found to activate together for specific tasks, so they can be processed in parallel to join the result at the end, but it's nowhere near the granularity of a SwiftUI expert and a python expert. The difference in those things is so trivial from an abstract point of view that it would make no sense. They would be 99% the same.
I think you're missing the point of the article though, which suggests not to mix reasoning capacities with actual knowledge. Sure working with Swift and Python is basically the same, it's programming, with the same concepts etc. Much closer than the ability to drive a car. But the point is, the methods, libs etc are all different and things are changing each time a new version of the language is released. Like you don't need to relearn how to drive a car if you go to the UK but you have to known the wheel is on the right. Knowledge shouldn't be stored in the weights.
I think you're missing the point of the article though, which suggests not to mix reasoning capacities with actual knowledge. Sure working with Swift and Python is basically the same, it's programming, with the same concepts etc. Much closer than the ability to drive a car. But the point is, the methods, libs etc are all different and things are changing each time a new version of the language is released. Like you don't need to relearn how to drive a car if you go to the UK but you have to known the wheel is on the right. Knowledge shouldn't be stored in the weights.