Totally agree with the 'It's the platform, stupid'. However, I do wonder if for javascript/typescript that's only for 'in browser' stuff. If you look at the s

Totally agree with the 'It's the platform, stupid'. However, I do wonder if for javascript/typescript that's only for 'in browser' stuff. If you look at the server - one of the best platforms is the JVM - lots of quality libraries - easy to write stable long running processes etc. ie if you are driven by platform isn't it Javascript on the browser and Java on the JVM on the back? ( typescript or kotlin are both moving a bit away from the platform ). The beauty of the network ( message passing ) means the stuff on the server doesn't need to be in the same language as that on the client. Now I'll admit there is some benefit to having front and backend the same, in terms of validation code, or perhaps occassionally moving logic from server to client or back - but does this override the platform effect? Also note you can run js on the JVM/GraalVM - so client/server validation libraries could be written in js and reused both sides.