Construction costs have been outpacing headline inflation by a huge amount. This has accrued to costs of repairs easily exceeding 20-30% over a few years ago.
I applaud the aim to make lean and fast websites, but the lack of timer and drag+drop on this game makes it unusable, so I think this actually makes the reverse point -- one should not put non-functional requirements ahead of the function of a product. In other words, this was not a good compromise.
Ah, that makes more sense -- it might be a good idea to integrate with the upstream library as a submodule rather than lifting the actual .cpp/.h files into the bindings repo. That way people know the upstream C++ code is from a much more active project.
Despite my snarky comments, thank you for contributing to the python ecosystem, this does seem like a cool project for high performance URL parsing!
I guess you are right that there are 2 commits from a different dev, so it is technically not a solo project. I still wouldn't ever use this in production code.
It seems unlikely that this C++ library written by a solo dev is somehow more secure than the Python standard library would be for such a security-sensitive task.
Hard to imagine the tradeoff of using a third party binary library developed this year vs just using urllib.parse being worth it. Is this solving a real problem?
This doesnt take into account capacity factors. A "800MW" solar plant would be expected to actually product 10-25% of that after day/night and seasons are taken into account. Nuclear plants are more of a 90+% capacity factor.
Agreed. I read your original post during a time where I was starting up a solo company and it's great to see you've eventually seen success after all these years! The points you make about which problems seem interesting as an engineer and which ones lead to actual success resonate a lot. Congrats on TinyPilot!
Solar isn't a useful source of energy for heating in California, since the demand is almost entirely during winter mornings/evenings where the sun is down.