Ok, then the squid proxy, the most widely (maybe) used proxy is wrong? The squid.conf is inutile and a piece of nonsense? Computers are tools and i decide what they should do.
all things have its advantages and disadvantages. people on forum post that v3 cache works better than v2.9. but v2.9 proxy was based on squid... and why not select what files should be cached on the basis of its popularity?
(hyperbolized) in terms of bandwidth, it's better to cache one file of 200 Mb, which will be downloaded 3 times, than five files of 1 Mb, that will be downloaded 50 times...
Is not correct to compare a linux squid box with the squid implementation used in version 2.9. In the 2.9 is not possible define the system file type (reiserfs, etc), i/o disk access process (diskd, aufs, etc) and etc, etc. I respect your opinion, but for me the proxy in 3.0 version is very very closed (in configuration options) and buggy. I sent three supouts reports in last week with confirmed bugs and the mikrotik team have promised to try correct until next version. About the speed in 3.0, is not possible attribute to the proxy only, the linux kernel is new and more efficient etc. Ex about the closed thing: i would like show the proxy errors messages in the native language of my clients (brazilian portuguese), it's possible? No. I have used RouterOS since 2.7 and always existed weak points for improvement. If we follow the simplicity line, because then so many options in the firewall? Should not everything be smart and automated? It's all about freedom, and i love the RouterOS for this, but i want more.