11–20 of 72 posts
Is there something like this (show memory use and call times for a Python process) that just runs on my computer to help me profile a long-running Python process?
This is an interesting project. It appears to me, based on the README and the name, that it was primarily intended to profile backend services in a web app. I have a question for hacker news. Does Python still have a lot of momentum in this area? I love Python and use it whenever I can, but I find these days that most web frameworks assume right off the bat that you are using Node. The frontend landscape is so heavil…
How's it different from DataDog? considering you have same price tag
Earlier quoted context omitted.
There is tons of python work available (I weighed the unwritten src myself). Maybe the node/js news headlines are creating a recency bias?
Sure, this is possible, but I'm not basing my concerns on headlines so much, but rather what I'm seeing out there when I try to educate myself on what is going on in the frontend world. Once you get past basic JS and JQuery, everything seems to just take for granted you are using a toolchain that doesn't leave much room for Python.
Render services [1], Sidecar processes [2], not-doing-universal-rendering, or just running a simple universal nodejs server with an entirely separate API backend.
[1]: https://github.com/airbnb/hypernova [2]: https://blogs.msdn.microsoft.com/webdev/2017/02/14/building-...
Integration is not typically that difficult. It takes a day or two of sitting down with docs and intentional effort, sure.
Worrying about wasted effort is silly though. The amount of choice these days is crazy, and web development lately is mostly hype-driven, though it doesn't really need to be. We end up solving the same problems over and over again with a slightly different set of technologies (which has it's good notes and it's bad notes).
For many companies the backend is several orders of magnitude larger than the frontend (hundreds of separate backend services/daemons/etc in any variety of languages), so optimizing the whole stack for the sake of the frontend would be nuts
This is an interesting project. It appears to me, based on the README and the name, that it was primarily intended to profile backend services in a web app. I have a question for hacker news. Does Python still have a lot of momentum in this area? I love Python and use it whenever I can, but I find these days that most web frameworks assume right off the bat that you are using Node. The frontend landscape is so heavil…
I'd say python is slowly growing if anything. The javascript world is probably growing faster, but then you are competing in a much bigger field.
Are there any plans for porting this to Android? For example by using Kivy?
This is an interesting project. It appears to me, based on the README and the name, that it was primarily intended to profile backend services in a web app. I have a question for hacker news. Does Python still have a lot of momentum in this area? I love Python and use it whenever I can, but I find these days that most web frameworks assume right off the bat that you are using Node. The frontend landscape is so heavil…
Now, I am surprised I didn't push it forward.
This is an interesting project. It appears to me, based on the README and the name, that it was primarily intended to profile backend services in a web app. I have a question for hacker news. Does Python still have a lot of momentum in this area? I love Python and use it whenever I can, but I find these days that most web frameworks assume right off the bat that you are using Node. The frontend landscape is so heavil…
While I've used Node, and I think it has its place in certain kinds of application, I would never pick it for the main backend language. Adding a chat service to an existing larger codebase, maybe, but JS isn't particularly well suited to larger applications (yet, it's improving) and the frameworks are still less mature than things like Django and Rails.