> > That's a terrible excuse for the shitty concepts behind MikroTik's CLI. >
Fear of being sued into oblivion by a massive corporation, even if they're in the wrong, has influenced many choices in technology. To be clear, I am not stating that Mikrotik made the CLI choices they did BECAUSE of that concern. I have no knowledge there. I do know that Much Larger Vendors have absolutely made tradeoffs because they didn't want to deal with legal actions from Another Large Vendor or Patent Troll, so it's not exactly uncommon. On Tue, Aug 15, 2023 at 5:43 PM Chris Cappuccio <ch...@nmedia.net> wrote: > Tom Beecher [beec...@beecher.cc] wrote: > > > > > > It should be a huge embarrasment to the designers. They survive on low > > > price and unique features. It would be quite amazing to have a CLI > without > > > the nonsense. > > > > > > > That ship sailed years ago. Even though the legal precedent was set after > > Cisco vs Arista that CLI elements that are of common , standard usage > > aren't copyrightable, nobody wants to take the risk. So they come up with > > other ways that tend to be not good. > > > > That's a terrible excuse for the shitty concepts behind MikroTik's CLI. > > I'm not saying my stuff is much better, but yeah, actually I am. >
