4 ms·
Even for apple shops, it doesn’t really makes sense. It is a myth to think that you can share anything of value between client and servers, except dumb data typ
by bsaul 4y ago
Even for apple shops, it doesn’t really makes sense. It is a myth to think that you can share anything of value between client and servers, except dumb data types that you’ll probably want to define in protobuf anyway for various reasons.
As for knowing the language, you’d gain the two weeks it takes to learn go, but you’ll loose all the ecosystem of quality libraries.
- pjmlp 4y agoApparently a myth made reality on the Apple shops I know. It is no different from the Android shops using Java and Kotlin for the backend, the only difference being the plethora of options on the JVM ecosystem that they can reach out outside Android.
- bsaul 4y agoI'm really curious to know what code they actually managed to share between client and server. I've been doing fullstack mobile / server dev for 12 years now and i've never ever told myself "what a waste, if only i could reuse this piece of code on/from the server".
- ofrzeta 4y agoDifferent ecosystem but we share Typescript type definitions between frontend and backend. That's not so bad.
- pjmlp 4y agoData models, validation code, business logic that needs to be done on both sides, dynamic UIs. And about protobufs, I am yet to see any production deployment using it.
- ithkuil 4y ago> I am yet to see any production deployment using it. We all live in bubbles. I've seen it, a lot; that's not proof that everybody does it. And the converse is true as well.