Re:Brython – A Python 3 implementation for client-side web p...
by jidiculous on Monday July 06, 2020 @05:13PM
(#23752818)
I'd say the advantage is less on the architectural side and more on the team efficiency side – you could possibly have a full-stack team that only needs to do most of their work in 1 language. The benefits of easing task-switching could make it worthwhile as a stack choice.
Re:Brython – A Python 3 implementation for client-side web p...
by ascar on Monday July 06, 2020 @08:23PM
(#23754322)
The thing is that for anything more complex than simple CRUD either side (frontend and backend) is such an inherently different problem domain that I don't see that the programming language is the relevant factor.
Because frontend and backend need a very different skillsets and both need a lot of knowledge and training to become good, there are very few true fullstack engineers. And I would bet that most if not all of those can handle work in multiple different programming languages.
Re:Brython – A Python 3 implementation for client-side web p...
by nawgszy on Monday July 06, 2020 @05:32PM
(#23753029)
Sure, but that's being positioned as a "huge advantage" vs. JavaScript, which I hope I do not need to explain to you the irony of
Re:Brython – A Python 3 implementation for client-side web p...
by hombre_fatal on Monday July 06, 2020 @04:35PM
(#23752455)
It would be nice to use the same BBCode parser on the server and client to give the client accurate previews. Why not just compile that one little module into Javascript and sent it over the wire?
It's a small advantage, practically. There's a limited set of circumstances where this is leveraged in the rare cases that client/server languages are matching (usually the ability to directly copy specific algorithmic implementations). The "advantage" always feels overstated...especially on the web where the frameworks are disparate because the underlying data models are different, ie the DOM.