Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added explicit comparison to JS #3168

Merged
merged 1 commit into from
Mar 13, 2023
Merged

Added explicit comparison to JS #3168

merged 1 commit into from
Mar 13, 2023

Conversation

jbednar
Copy link
Member

@jbednar jbednar commented Feb 2, 2022

Added a section to comparisons.rst comparing and contrasting using Panel with developing directly in JavaScript/HTML/CSS.

@philippjfr philippjfr added the type: docs Related to the Panel documentation and examples label Mar 13, 2023
@codecov
Copy link

codecov bot commented Mar 13, 2023

Codecov Report

Merging #3168 (f8a1282) into main (817363f) will decrease coverage by 0.20%.
The diff coverage is n/a.

❗ Current head f8a1282 differs from pull request most recent head bb03d2e. Consider uploading reports for the commit bb03d2e to get more accurate results

@@            Coverage Diff             @@
##             main    #3168      +/-   ##
==========================================
- Coverage   83.17%   82.98%   -0.20%     
==========================================
  Files         247      192      -55     
  Lines       36337    25502   -10835     
==========================================
- Hits        30224    21163    -9061     
+ Misses       6113     4339    -1774     
Flag Coverage Δ
ui-tests ?
unitexamples-tests ?

Flags with carried forward coverage won't be shown. Click here to find out more.

see 235 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@philippjfr philippjfr merged commit e97f086 into main Mar 13, 2023
@philippjfr philippjfr deleted the comparejs branch March 13, 2023 17:54

- Does the app depend on sources of data or other tools already available in Python? If so it will normally be much easier to build in a Python framework like Panel.

- Do the people building the app normally work in Python? If so, they are likely to be much more productive in Python, both directly for writing the app's code and indirectly by being able to use all of their usual support tools and infrastructure (and from not having to learn JS).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In trading the users (i.e. traders) often have the requirement that they need to be able to read and review the app. They are actually responsible for what ever happens in the app whether its a model providing insights or prescriptions or whether its a button that triggers an algo to start trading by sending data to a REST API. So Python is a good choice for the entire app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: docs Related to the Panel documentation and examples
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants