We've got to get out of the business of these pairwise language interop solutions.
Totally, let's bring back CORBA!
NodeSwift: Bridge Node.js and Swift
21–26 of 26 posts
Re: NodeSwift: Bridge Node.js and Swift
#22Re: NodeSwift: Bridge Node.js and Swift
#23Earlier quoted context omitted.
Totally, let's bring back CORBA!
This but unironically
Apparently some do miss it, https://component-model.bytecodealliance.org/
Re: NodeSwift: Bridge Node.js and Swift
#24We've got to get out of the business of these pairwise language interop solutions.
You mean there should be a general solution (not just pairwise) or none at all?
Re: NodeSwift: Bridge Node.js and Swift
#25Oh my, yes! We have some legacy microservices written in Swift/Vapor (while our main stack is NestJS) and instead of rewriting them to TypeScript, we can use this. Cool!
What drove the switch from Vapor -> Nest?
Actually, we are using Node/Nest from the start. A significant amount of our business logic was written in Swift for our iOS mobile app, which we eventually moved to the microservices (Vapor). This was because we needed to create an Android app and didn't want to write new code from scratch.
Re: NodeSwift: Bridge Node.js and Swift
#26I get paid to write Swift code at the day job, at night I write a lot of node backend code for a side project. I have to say that it's pretty refreshing to jump in and not have the (increasingly) opinionated Swift compiler barking at me for everything I do. Unfortunately Swift has also made me extremely paranoid in JS, where I find that everything I write is checked for null, but I don't think I'd trade the freedom i…
> I don't think I'd trade the freedom in nodeJS for Swift's type safety
Surely you have considered TypeScript for your Node project then?