Thu Oct 06, 2016 12:12 am
While I do totally understand certain requirements for having the metarouter functionality, i personally would not use it much (ofcourse that could change if it was a feature that was well maintaned and supported across all routerboards)
What I would love to see is support for containers (like docker), for me, routerOs has 99% of the functionality I need in a router, what it doesn't have is support for a proper programming language.
Just image the possibility of running a docker container that is a container for your application, using the language of your choice, interacting with the server of yours doing anything you want. I know you could hack certain aspects of this together with the API and scripting but its not the same, we could centrally host code via git, push updates seamlessly directly our application on the router. It makes totally sense and Mikrotik wouldn't need to worry about adding support for application X,Y & Z. - even things like TR-069 wouldn't matter anymore, have the container pull the config from your "config server", do a diff on it, if there are changes, push that through to the MT (locally, bypassing any firewall/nat rules).
Although, I suppose ROS is so small and they strip so much out of the kernel that it might just be a pipe dream, but still, let ROS do what it does and let us do what we do by giving us containers.