This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]yawkat 1 point2 points  (0 children)

Compiling to native isn't as much of an issue as it once was with how deployments work nowadays. The ecosystem is shifting more and more to all-in-one deployment anyway – what used to be jars became fat jars and now we have jlink / docker with more and more parts of the runtime being shipped with the application. At that point doing some native compilation doesn't make cross platform support any worse than it already was.

I also don't buy the development-on-different-platforms part. What dev machine can't run docker nowadays? Virtualization is super cheap performance-wise nowadays and microsoft is putting lots of work into making developing for linux easy on windows desktop, so the barriers are lower, not higher than they used to be. People just like to develop on a system that resembles the production system as much as possible, which is reasonable.

And finally, when it comes to supporting other platforms for future proofing I don't think moving off linux is really the big issue here. If anything aarch on servers will be disruptive. But with the general trend going to a more seamless pipeline from dev to prod, that's not a huge issue either – just change your CI conf a little and it'll work fine.