Markus Kinzler

Seems no problem for embt. If you need it earlier you can apply for the beta.

Not really. OpenGL isn't as good as Vulkan and MoltenGL isn't free as MoltenVK. Now FMX uses: DX11 on Windows, OpenGL on macOS (and Linux inofficially), OpenGL ES on Android and iOS. Instead of a new implementation: DX12 on Windows, Metal on macOS and iOS, Vulkan on Android and Linux it would be better to concentrate on one solution.

The better thing would be switching to Vulkan. One solution for all platforms (Windows, Linux, Android: native, macOS and ios via MoltenVK (included in Vulkan SDK).

At the moment the parsers for the code completion and error inside from the ide differ from the parsers of the compilers.

Promised, not delivered!

On the right side of the Header from the post

Which version of delphi?

Have a look at Image32. Maybe it's better than the standard jpeg support. https://github.com/graphics32/graphics32

@Roland__K MS has started to backpedal their strategy.

We aren't their target market.

If everyone will do this than delphi will be history immediately.

Or the hope more developers would migrate to the more expensive editions.

Perhaps employees. But the decision makers beeing responsible don't take the steps needed.

Because they see no need for impovement here, i don't theink the product would be much better. This wouldn't change much. There's seems no need to invest for earning money. Business isn't to create tools but only to earn more money with less effort.

But you cannot survive just with legacy! The expenses for maintenance would be copable when development would be steady in cadence with the plattforms. It is a great problem when there is the need for "reaction" in hassle. EMBT have ti build a homogenous platform with one front end (compiler) per language and one back end per platform. The development should be decoupled ( compiler, code gen, runtime, ide).