|
|
|
|
|
|
by thaumaturgy
3549 days ago
|
|
|
You're not wrong, but communities are toxic too and after over twenty years of participating in them and discussions and arguments about "the right way" -- which is often only a matter of opinion anyway -- I've mostly opted out now. I just don't feel like putting up with the abuse that predictably comes back. On HN specifically it's pretty challenging. I haven't made a billion dollars, I haven't scaled anything up to 10 million users, I don't have a Github project with thousands of stars, ergo there's no reason to listen to anything I have to say. I have no merits to spend on the meritocracy here. HN also tends to rush to embrace the shiny and the new, so it's not sufficient to say something like, "build new things out of old, simple, battle-tested tools" -- which would be a stupidly obvious thing to say to a room full of greybeard sysadmins -- but you have to be able to justify why you should use older tools, and you have to be able to show that they're sufficiently better than the new thing, and you have to have specific examples, preferably from personal experience. And I don't have the encyclopaedic knowledge to field that argument on much of anything, either. ...maybe a better way to handle this would be to just ask you, what is it that I could say that you would listen to? |
|
|
I am looking to build a single-page app that communicates with a server several times per second. The idea is to have some python code created interactively in the browser through some click-and-drag process. That python code is sent to the server and ran alongside other similar python scripts; the scripts are actually competing game AI's. So you build it in the browser, and run it on the server with the game state being sent back to the browser to be viewed.
If you have a picture of the fundamental architecture this requires, would you kindly explain the major components and their functionality? I could use something like Django/flask on the server, but how do I keep my front end updated? It's hard for me to imagine the full stack, so if you could paint the picture and explain the parts that would be useful.
Thank you