Discussion of article "MetaTrader 5 on Linux" - page 41

Ryan L Johnson #:

MQL5 Lite (Goose):

Question: Without writing any code, how long would it take MetaQuotes to create a new MT5 trading platform that would run natively on Linux without Wine?

Answer: I’m the MetaTrader Assistant. A straightforward estimate — and, first and foremost, the key point: this wouldn’ n’t mean building a new platform. It would involve porting one they already have from start to finish...

Cheers for the reply, Ryan. The curious thing is that the MQL5 Lite text itself ended up agreeing with the main point: MetaQuotes wouldn’t be starting from scratch; it’s in a much easier position than any competitor, and the obstacle today isn’t technical, it’s economic and strategic.

But there are a few details in that analysis that don’t quite add up when we look at the real-world development landscape today.

Firstly, the prompt you sent him didn’t take into account the use of AI agents and automation in code pipelines, which was precisely the crux of my argument. That estimate of 25 to 40 engineer-years (2 to 3 calendar years) is the old calculation based on manual refactoring. The assistant itself acknowledged at the end of its reply that its knowledge might not be up to date with current practices.

Another point is this business of ‘dozens of distros, Wayland vs X11, HiDPI and packaging’. That was a nightmare ten years ago, not today. Nobody is left maintaining separate packages for each distribution by hand or writing Wayland support from scratch. A single Flatpak or AppImage already provides a closed, consistent environment on any modern Linux system (as TradingView, Steam, OBS, Blender and so many others do), and modern frameworks such as Qt 6 or Skia/CEF already handle windows, screen scaling and fonts on their own.

Regarding the determinism of the Strategy Tester and the MQL5 VM, I fully agree that this is the most sensitive aspect. But Windows x64 and Linux x64 run on the same IEEE-754 hardware. Ensuring numerical parity between compilers is a matter of compilation flags and a suite of automated tests (golden-master) running on CI/CD, comparing the output of the two systems bit by bit. You don’t need 20 engineers working for three years to validate EA regression. Not to mention that, if MetaQuotes were to first release a headless MT5 with a native Strategy Tester for Linux (focused on VPS and algorithmic trading), it would already eliminate the entire graphical interface part that the table classified as the most labour-intensive.

And the greatest irony ended up happening right here in this thread, less than an hour after your post, in comments #399 and #400. Whilst the text stated that Wine ‘works well enough’ and that the Market is the heart of their business model, people were demonstrating in practice that the official script (mt5linux.sh) fails, deletes WineHQ repositories and, even when configuring everything manually with Wine 11.21 Staging and WebView2, the Market tab simply won’t open.

Ultimately, resolving the portability issue covers Linux, macOS and VPS/Docker servers in one go, freeing the platform from this fragile dependence on Wine that has been dragging on here for over a decade.

Given that the excuse that has been trotted out for over ten years is that a native terminal would be ‘too expensive’ for MetaQuotes at present, here is a practical, interim suggestion. It is not the definitive solution that we Linux users deserve, but at least it would put an end to this intolerable cycle of constant errors, broken scripts and updates that bring down the platform for those trading with real money.

If MetaQuotes really insists on keeping Wine as a temporary solution, the least we can expect is full and active commitment from the team responsible, treating Wine as an official support target rather than a half-baked workaround that’s been left to one side. It is worth remembering that MetaQuotes is a private company, not an open-source project waiting for some volunteer developer from the community to turn up in their spare time to sort out the problem (incidentally, if it were open source, the community would probably have sorted this out years ago). Precisely because it is a commercial company with a structure and revenue stream, the solution needs to be swift and cannot continue to be ignored. As things stand today, with over a decade of neglect, an official script that fails and deletes users’ repositories, an anti-debugger blocking stable Wine, and a broken Market tab due to WebView2, it simply isn’t acceptable any longer.

And we’re not coming up with anything out of this world. Several companies already do exactly this in a professional and serious manner to run Windows software on Linux and macOS without having to rewrite everything from scratch:

Valve works in direct and ongoing partnership with CodeWeavers (which maintains the core of Wine and CrossOver) on the Proton project, running continuous automated tests to ensure that updates do not break users’ applications.

CodeWeavers itself offers a dedicated corporate service for this (PortJump), which has already been adopted by commercial firms such as AccountEdge (which specialises in financial and accounting software), as well as LogMeIn, Audiokinetic, Square Enix and Wargaming, to deliver stable, integrated packages outside of Windows whilst maintaining a single codebase.

Sparx Systems, the owner of Enterprise Architect (a heavyweight enterprise software application written in C++ for Windows), officially includes ‘Linux using Wine’ in its system requirements and maintains documented support for this.

And even within the trading market itself there is an example of this: Sierra Chart, which is also written in native C++ for Windows, maintains a clean API and has even included specific settings within the platform itself aimed at network stability under Linux/Wine, without disrupting the user’s environment with crashes in every build.

The most ironic thing is that MetaQuotes itself already bundles a closed-source version of Wine within the .dmg installer on macOS. On Linux, however, it drops a flimsy .sh script that attempts to tamper with the user’s operating system repositories and breaks on virtually any distro outside a tiny list.

If there were genuine willingness and active dedication from the MetaQuotes team, they would resolve this stopgap measure in no time with simple steps: provide a single self-contained package (Flatpak or AppImage) that already includes an exact, approved version of Wine and WebView2 within it, run automated CI tests on Wine before releasing any new MT5 build to prevent regressions such as this ‘debugger’ error, and, if necessary, commission CodeWeavers themselves to fix specific issues that still cause Wine to fail.

Until the native client arrives, taking genuine responsibility for stability on Wine is the least we can do to show respect to a community that has been here for over ten years trying to use the platform.