Live data from Hacker News

Google Mesop: Build web apps in Python

github.com

31–40 of 78 posts

Re: Google Mesop: Build web apps in Python

#31

Remember, this is from the company that thought that laying off their Python team was a good idea. https://news.ycombinator.com/item?id=40171125 Draw your conclusions of the level of support for this library.

I don't think you need to draw your own conclusions: "This is not an officially supported Google product".

Re: Google Mesop: Build web apps in Python

#32

It's funny how much negativity was/is around things like NodeJs when so many back end engineers railed against frontend folks for only wanting to use JS and not adapting "proper" languages when they always go and try to go out of there way to do the same thing in reverse. Not that this isn't worthwhile or interesting

Having the same language on both ends (plus mobile devices, where the synergy is much larger) is a good idea! It’s just that JS sucks.

Re: Google Mesop: Build web apps in Python

#33

> Build delightful web apps quickly in Python What makes them delightful? The Steve-Jobs-ification of marketing copy continues unabated.

bro. you don't get it, do you. this sort of copy is just table stakes in hi(and bye) tech nowadays. you know, for these times when there is nothing under the table. not even legs*, I mean. *as in, "this thing has legs".

snicker.

as usual, the hacker news subset consisting of the echo chamber / hive mind / tech bosses' slave crowd, can't digest / handle comments like mine above, while at the same are fine with the comment in a similar vein by paulcole, to whom I just replied above.

long live discrimination on hacker news! hip! hip! horror!

Re: Google Mesop: Build web apps in Python

#34
post #31

Remember, this is from the company that thought that laying off their Python team was a good idea. https://news.ycombinator.com/item?id=40171125 Draw your conclusions of the level of support for this library.

I don't think you need to draw your own conclusions: "This is not an officially supported Google product".

For small time developers and normal users, "Google support" already feels like best effort community support.

Re: Google Mesop: Build web apps in Python

#35

Remember, this is from the company that thought that laying off their Python team was a good idea. https://news.ycombinator.com/item?id=40171125 Draw your conclusions of the level of support for this library.

You’re totally missing the point. The point is: you have some Python script, and you don’t want it to disappear into the sad world of a ticket attachment, and if you add the 5 lines of code and have a nice onboarding experience, it doesn’t have to disappear into a ticket attachment, it can instead disappear into your browser bookmarks. You should never test the limits of this framework because if it’s anything other than putting a simple script into a webpage, you shouldn’t be using this. It’s rot proof.

Re: Google Mesop: Build web apps in Python

#36

I'm struggling to understand this demo app. You type in some text and it echoes the exact same text back to you? I assume the project just hasn't fully fleshed out the readme

I'm noting the use of "stream" and that the upper_case function is a generator (see the `yield` keyword) which I take to mean any asynchronous process could be placed there. e.g. a call to a chatbot api.

Re: Google Mesop: Build web apps in Python

#37
post #9
post #8

Earlier quoted context omitted.

What about "Visual "? Since, you know, it's visual. This idea sounds promising. Who knows... you might even get one of the tech giants interested! Some of them have a lot of business customers that could use something like this.

Strong! I feel like we both see the future

> Strong! I feel like we both see the future

You must be the Oracle of Delphi. Now that would be a nice product name for a visual IDE.

Re: Google Mesop: Build web apps in Python

#38
post #15

Earlier quoted context omitted.

Don't you think that would be going too far? I worry what unholy creations people might come up with... A tabular data tool with a full development environment might just be too much power concentrated in a single application.

Nah people will just use it to run football pools and fantasy baseball leagues. It won't be a serious thing.

The dialog of this thread could fill out three panels of an XKCD comic quite nicely.

Re: Google Mesop: Build web apps in Python

#39
The issue that stands out to me with this is its not using coroutines. Python developers who don't know everything about the GIL, threading, blocking v non-blocking sockets, processes, all of that can of worms, are going to try regular blocking I/O (that they might have done fine in PHP) leading to horrible performance. I think the choice to do this with 'threads' in Python (not real threads) = very bad. I think you can have multiple processes here but if you're using just Python for the web server the overhead is going to be massive for an interpreter...

The correct approach would have been to have an event loop in every process handling 1 - however many clients for the server. Then async I/O functions can be done inside the app routes without potentially impacting the performance of every other client being processed. The software here seems to use Flask for the underlying server stuff (when running from Python.) But anyone whose tried to use flask for a web project before knows that its slow AF since it loads everything one after the other. When looking that up I think you can tweak the number of processes it uses but IMO: it's not the right approach.

Re: Google Mesop: Build web apps in Python

#40

Remember, this is from the company that thought that laying off their Python team was a good idea. https://news.ycombinator.com/item?id=40171125 Draw your conclusions of the level of support for this library.

The US Python foundational team was less than 10 people. If you think any 10 person team in a 200,000 employee corporation is that critical well I’d have to disagree

When their jobs were moved to Munich there was a lot of discussion about how important they were, but something else stood out to me. One of the things they accomplished was taking over a year to make sure the monorepo can be upgraded to the latest version of python

As an outsider this definitely smells like an org creating work just to justify its budget. You have a single team of a handful of engineers doing the python upgrade work for tens of thousands of engineers. Doesn’t feel right out of the bat

I’m sure soon enough with the role moving they’ll find out if the team is needed at all

Post reply on HN