I would like to formulate my Rant of today in a positive way: Microsoft remains true to itself: Embrace, extend, and extinguish.

If you don't know the source: https://en.wikipedia.org/wiki/Embrace%2C_extend%2C_and_extinguish

Nice try to lure developers with .NET Core, to write cross-platform applications and now let it all run back to Windows as we clearly see on BUILD 2018. I don't want to know how many lemmings have fallen into the pit full of technical debts. And since this term is unknown to many newly graduated business yuppies in decision-maker positions: https://en.wikipedia.org/wiki/Technical_debt

I am glad to have XOJO as a real cross--platform-solution for business apps.
Now get back to work!

:)
I would never trust Apple or Microsoft promoting or even selling a cross-platform dev tool ...

@Jean-YvesPochez I would never trust Apple or Microsoft promoting or even selling a cross-platform dev tool ...

And even for Xojo it's hard to deliver same quality for multiple platforms.

Well having worked with .Net Core on a Mac to build business services I’d have to say it is an excellent start to the world of micro services and without it MS would be out of the game. Corporates are moving away from building cross platform applications to building container based solutions and while the technology is impressive, it is the overall cost savings that drives it.

Docker is the main player in the container world, it is open source and all the main players are there, including MS. It is a paradigm shift in terms of testing, deployment, security and scalability. MS have had to put a lot of effort into getting docker to run on their Windows servers because it is based on a Linux kernel and .Net Core is a key part of making it all happen for .Net developers in the corporate environment.

I can deploy a standalone XOJO web application to a docker container and then spin that container up on a Raspberry PI in a couple of minutes without ever compiling it for the Raspberry PI, that is the power of container based solutions.

Nice to see you back here @Tomas J.
You have been quite busy the last 6 months, haven't you?

@James D I can deploy a standalone XOJO web application to a docker container and then spin that container up on a Raspberry PI in a couple of minutes without ever compiling it for the Raspberry PI, that is the power of container based solutions.

And that discussion is a serious Webinar in itself. You and @Paul L should get together on that one.

@James D I can deploy a standalone XOJO web application to a docker container and then spin that container up on a Raspberry PI in a couple of minutes without ever compiling it for the Raspberry PI, that is the power of container based solutions.

Code in the container still has to be compiled for the running target. Containers use the host OS and kernel. You'd need to make two containers if you want one for x64 and ARM.

@Phillip Z Code in the container still has to be compiled for the running target. Containers use the host OS and kernel. You'd need to make two containers if you want one for x64 and ARM.

Not the case

@James D Not the case

I’d consider myself a Docker expert on Linux as I’ve built large orchestration systems with it. Docker on Linux uses Linux kernel name spacing and each container uses the host kernel. It’s not possible to run code compiled for a different architecture using Linux containers or Docker. I’m not certain about portability on Windows as containers can be thin or full VMs using Hyper-V. Even then Hyper-V doesn’t emulate ARM.

Now let’s say you’re running PHP or Node in containers. Certainly that runs on ARM if the container image has the scripting environment installed. Static binaries though do need to match the host platform.

@Julia T Very nice illustration here https://www.docker.com/what-container showing the difference between the docker and VM approaches.

The growth curve shown at the bottom is totally bogus! It is so bad that I would call it fraudulent.

Instead of the exponential growth shown it is actually slowing down and approaching saturation.

2015/2014 = 10x
2016/2015 = 6x
2017/2016 = 2x
2018/2017 = ?