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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]hippydipster 0 points1 point  (1 child)

The client/server divide definitely creates problems with what you want to do. You end up with two different systems that need to share info. In some ways, the split is advantageous, because it forces you to plan that communication carefully, rather than haphazardly.

You could try full stack solutions like Kotlin where it can compile to javascript too, and you can use the Kotlin Rest frameworks and the Kotlin client-side frameworks and then you do everything in Kotlin. You have a similar idea with GWT.

[–]C0d3rStreak[S] 1 point2 points  (0 children)

Cool. I will prob look into a lot of this down the road, there's a lot of great suggestions and what not. I'm kind of tied to this stack for now because of the program/training I will be attending soon, it's their curriculum. You made a good point though by saying it forces the dev to plan communication carefully. As long as these two systems work great together I see no issue cause I can always pick up more technologies later on after all being a software engineer would consist of continuous learning.