quoting OP:
All platform released that !!!!!
vs
quoting article which OP linked:
But sadly on the Linux front, the kernel bits still have yet to be mainlined.
Windows client is still on its way but is taking a while due to writing a new TUN driver for Windows 7 and newer.
lets summarize it:
- Specs are subject to change and whole code is in experimental stage (source: https://www.wireguard.com/#work-in-progress )
- Author of WireGuard released client for iOS and macOS only. (minor mobile and desktop platforms)
- There is no stable client for windows (major desktop platform)
- There is no stable client for linux (major mobile and server platform)
- All clients are so far developed by author of WireGuard, not by platform developers itself so there is no native implementation in any of systems.
- In reality it is a one-man project which means if Jason gets bored, the project is dead.
- Jason even owns a trademark on logo and name! That is so typical for "start free, become paid" platforms...
So in the end, you want mikrotik staff to implement a platform, which is officially considered to be in experimental stage, therefore will be outdated within couple of weeks or months (and will require developers attention to fix it again), It can bring hidden fees at any single time due to trademarked name or can disappear anytime if author decides to do something else?
I really like all things promised by wireguard but we really don't need another unstable attempt for tunnel, which will deplete resources of developers even more. We didn't even got an OpenVPN over UTP yet. EoIP crashes whenever it transmits an STP frame. ROMON is not stable when it runs through VPLS or EoIP on CHR, bridged VLANs don't really work on CHR, Whole CCR1072 will freeze in when src-nat runs out of available ports... I could go on but I think you already got my point - I don't think we should ask for another unstable technology.