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

Create python FE fatigue blog post #542

Merged
merged 3 commits into from
Jul 12, 2024
Merged

Create python FE fatigue blog post #542

merged 3 commits into from
Jul 12, 2024

Conversation

wwwillchen
Copy link
Collaborator

@richard-to WDYT? :) I'm thinking about publishing this blog post and sharing it on social media 😃

Copy link
Collaborator

@richard-to richard-to left a comment

Choose a reason for hiding this comment

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

I think it looks fine for a blog post. It's a good way to get in that we have web component support.

A few thoughts:

  1. May want to say that it is still an experimental feature
  2. May also want to say that one can write a Mesop app without writing a web component and digging into javascript/html/css
  3. I think the web component feature is still a bit early, so we haven't explored enough use cases yet to truly say if we can avoid bundling use cases
  • It does seem useful for cases where there's a javascript library out there that can be imported through a script tag, then the web component is mainly a wrapper over the library, like the Plotly case and firebase auth case we've seen so far
  1. With Web components, there is now the need to learn javascript and html. And most likely they need to learn Lit. So there is still something to learn on the frontend. So can't get away with just Python. But as you say, at least it seems like something that isn't the latest fad. And it's also good that the code is self-contained. Which I think is fine for more advanced cases. Ideally our ecosystem of web components that get shared and reused will grow into a healthy one, thus making it less common for people to reach into the javascript stuff.

@wwwillchen
Copy link
Collaborator Author

I think it looks fine for a blog post. It's a good way to get in that we have web component support.

A few thoughts:

  1. May want to say that it is still an experimental feature

Yep, it's mentioned.

  1. May also want to say that one can write a Mesop app without writing a web component and digging into javascript/html/css
  2. I think the web component feature is still a bit early, so we haven't explored enough use cases yet to truly say if we can avoid bundling use cases

Softened the phrasing around bundling.

  • It does seem useful for cases where there's a javascript library out there that can be imported through a script tag, then the web component is mainly a wrapper over the library, like the Plotly case and firebase auth case we've seen so far
  1. With Web components, there is now the need to learn javascript and html. And most likely they need to learn Lit. So there is still something to learn on the frontend. So can't get away with just Python. But as you say, at least it seems like something that isn't the latest fad. And it's also good that the code is self-contained. Which I think is fine for more advanced cases. Ideally our ecosystem of web components that get shared and reused will grow into a healthy one, thus making it less common for people to reach into the javascript stuff.

@wwwillchen wwwillchen merged commit e29323d into google:main Jul 12, 2024
3 checks passed
@wwwillchen wwwillchen deleted the blog branch July 12, 2024 18:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants