natnai
Supremacy Member
- Joined
- Nov 6, 2007
- Messages
- 8,020
- Reaction score
- 1
Interfaces is what brings a lot of dynamism into the language. Much of the flexibility in a strictly typed class system is using the basic inheritance model. Without it, the language is pretty much as static as it seems on the code level. The indirectness offered by the inheritance model is the abstraction and vagueness to encourage logic encapsulation between modules in the ecosystem.
Java alone didn't really fill the space with complexities, I must say frameworks like Spring really _helped_ to add on the complexities with tons of XML, Annotation and properties files![]()
Spring seems pretty similar to Symfony. It seems like Symfony was modelled on Spring's architecture, especially the IoC, loads of annotations, and the config files. The config files are just...:/ XML is so verbose, in Symfony I always just used YAML. XML is just....:/
Maybe there's some Gradle plugin I can use to parse YAML into XML. I'll have to look into that. Saves the trouble of having to type so much.
I never liked using them in Symfony. So far Spring hasn't done anything particularly bad to me, but then this isn't even close to a working prototype yet, so I'll reserve my comments. The other thing I want to try out is how WebSocket support is in Java. It's really very simple in a Node server, but something tells me it won't be so simple in a Java environment. Looking forward to it anyway.
Ask a question then disappear?