3 ms·

Of course when it comes to the web it's three languages underneath. Per the standard, you can't escape that. Now look at apps that are built to run on an OS usi

Of course when it comes to the web it's three languages underneath. Per the standard, you can't escape that. Now look at apps that are built to run on an OS using MVC. It's usually all in the same language. Why? Separation of concerns doesn't imply separate languages. There might be some merit to the idea of a DSL for each concern? But if the end result of that experiment includes CSS, I would call the experiment a failure.

wongarsu 7y ago
Android, WPF and Universal Windows all use XML to specify UI, and the programming language of choice to specify code. That's still two languages, even if it removes the need for a third language exclusively for styles. In each you could use pure code to build the UI but readability and maintainability would suffer a lot, so nobody does that. Once you have the view separated from the controller, writing the view in a language better suited for nested UI seems quite natural. What are examples of MVC using only one language?
- mumblemumble 7y ago
  Perhaps Cocoa development, though it typically used a GUI tool for the UI layout, so not really. Smalltalk, but Smalltalk MVC is different from what MVC typically means nowadays. FWIW, WPF uses MVVM, not MVC. The differences are as subtle and pedantic as they are important.
  - rsynnott 7y ago
    I'm not sure how common vs not common Interface Builder usage really is. At any rate, I'd say "typically" is a stretch.
    - mumblemumble 7y ago
      That's fair. My experience on the subject is admittedly pretty ancient. When I was doing it, back in the early 2000s, IB was how everyone I knew did it.