The Handlers implement behavior, sure. But from the perspective of the `app` object, the handler function objects are state. You can tell, because `app` is an instance of the Flask class and the Handlers are added to the instance by way of a function call.
So, Handlers are functions that "handle something", but they are also part of the app object's state, not its behavior.
But that's missing the GP's forest for the trees (pun intended). Liu Cixin's work popularized the theory and phrasing by a massive amount both in comparison to the works that came before and as well as after.
The core point seems to be the flippant assignment of origination irrespective of the scale of contributions.
I've been experimenting a lot with using Jupyter Notebooks (http://jupyter.org/) to get many features of literate programming.
The tooling can be a bit clunky -- though JupyterLab and some plugins can go a long way. Importing notebooks into other notebooks or modules is still kind of weird even with the `ipynb` library.
However, on the otherside of it all, you have a collection of documents that contain documentation, code, and tests, all side by side and storable with proof of past execution.
I'll take this arrangement over someone's unit test and CI suite every day of the week.
Landscaping is a perfect example of how an individual can instantaneously create value in the economy. Banks can create currency, but individuals can magically create value.
How? Decide you want your yard to look different. On a whim. Just decide you want a hill over there with a ring of bushes on top. Congratulations, you have created demand. Pay a local crew to have it done, money flows into the economy, everybody eats.
For greater effect, manufacture a cultural preference so that entire country clubs of people at a time decide that all hills need bonzai trees at their crest -- have all the clubbers pay all the landscaping crews.
Without context, the animation applied to a basic interaction seems like it's getting in the way of User Interaction
But as you hint, in many situations a gradual change of the presentation will allow a user a lot more awareness of the presentation and it's interconnections as a whole.
With scrolling, the idea is usually you're looking at a massive block of text with some images. Why are you scrolling?
Sometimes, you may know exactly where on the page you're trying to go -- in which case lerp will interfere with the interaction.
But in most cases, your using the scroll feature to skim and find the correct place, in which case an animated scroll will serve the user better since the content will have a predictable location throughout the presentation.
Whether or not the button exists in someone's interface is likely separate than the means used by GPT to reason it was the case.
GPT responds that there is an upload button because a lot of interfaces are described that way around the web -- there is not likely a hard reference for its answer in regard to its own interface.
The challenge of a profitable, open source business model is very real, but also very surmountable -- as evidenced by Prusa's existence in the first place.
Thinking one has to straddle the line between philosophy and pragmatism is a false dichotomy. Open Source is a movement, not a binary.
Prusa exists in what I hope is a time of transition from capital/ownership mindsets into a new type of open market. Wanting to straddle the fence in the name of profits shows once again Prusa only partially understand the movement they benefit from and namecheck frequently.
Comparing Prusa to Marc Jacobs to emphasize the brand over the product is genius.
I appreciate the academic frameworks that have led to the development of systems, however as a working engineer, ignoring where the rubber meets the road is my entire complaint.
For years I struggled to grok the difference between regular expression and parsing. The conversations I would hear about the topic always left me feeling there must be some interesting meat to the difference...and so I would go read up on it only to find myself with the same problem a few months down the line.
The only difference is layers. Enough regular expression becomes a parser. A slim enough compiler is just a templating engine.
Insisting it's a deep, dark magic and not the advanced application of `str.replace` does the industry a disservice.
If a project calls for 3+ of the same board, then PCBs become worth it quickly, in my opinion.
Even more than aesthetics, I've had a few projects where an unpopulated board outlives any other remnants of a project and so becomes the last remaining document/example of how it was done.
For prototyping, RaspberryPis will get you where you're going faster than anything else. The Linux environment gives you speed of development. The form factor let's you toss it in a parts bin. The GPIO gives you direct, easy access to the physical world.
After prototyping, redeveloping for a different platform is often not worth the cost. If you didn't use the GPIO, switch to a NUC or similar. Or don't.
Raspberry Pis are in data centers now, occupying server racks. Don't fight the signal; retransmit.
Python's organic growth and adoption is more of an OpenCola model.