J
jankeir
Guest
Now don't take this the wrong way, choose your frameworks wisely, if it's all or nothing it may not be what you want and sometimes wrapping it in some classes so that your own code doesn't use the framework/library directly may be desirable (in fact, it's a good test if the framework allows to be replaced with something else => no lock in, to try to wrap something around it and not expose it directly to your business logic.) The fact that Mike's framework was designed with .NET GUI in mind, yet quickly allowed adding support for REST, web ui's and lately angular in a very lean way (it doesn't feel like a bolted on hack, but as if it was always there) proves that it doesn't cause the typical vendor lock in that can be seen in some earlier framework attempts.
Continue reading...
Continue reading...