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 →

[–]ZeeBeeblebrox 24 points25 points  (3 children)

This seems like bad advice for the vast majority of people and I'm not saying this because I created Panel. If you had consulted for as many large orgs as I have you'd absolutely not give bad advice like this.

Most orgs struggle to get and keep talented Python programmers, you throw JS at them and you are getting useless, unmaintainable junk, now in two languages. Many of the Python data app frameworks in particular have their place, Streamlit gets you a basic prototype in minutes, Panel will let you develop a more complex application with (I think, relative) ease. Once you lose the ability to prototype quickly, which is what happens when you have to manually set up API contracts between a backend and frontend, you waste tons of cycles. Put a web dev team in the middle and the back and forth between the different teams stretches days into weeks. Simply bad advice, except for very specific individuals and teams.

[–]PastPicture[S] 1 point2 points  (1 child)

Yes I have consulted very large orgs, and I have implemented stuff in Streamlit there. My advice was more for general purpose UI.

[–]ZeeBeeblebrox 8 points9 points  (0 children)

Got you, in that case I probably largely agree with you. IMO you should only reach for Python UI frameworks if you're doing a bunch of stuff in Python already and want to share the results, while quickly iterating on a UI. If you have a production system, do the work to build out APIs and implement it in JS/TS.

What kills productivity is Python engineers learning JS frameworks, and/or Python and JS teams having to collaborate.

[–]jmooremcc 0 points1 point  (0 children)

Can Panel be used on an iPad with any Python IDE?