You're paid by writing code. The code is the company's capital, YOU are the company's labor. Unless you somehow expect to spend yourself at the grocery store, you've never been capital.
> It's hard to understand the mindset of "I'd rather just be powerless in the job I have because that seems easier."
Because that’s not the case? In America it is still extremely easy to find alternative lucrative work, or simply start your own business; because in software development the worker basically owns the means of production - himself. This is an extremely powerful bargaining position and it’s why SWE pays so well here.
Athletes, actors, doctors, and other professions still have to negotiate with centralized capital to some degree in a way SWE never will
This doesn't alter anything about what I said. It's still goddamn evil how bad we are at distributing resources in this world. Justice would look like actions that are not legal to advocate for in this country.
Most resources go to average people, how is that bad? Wealth is not resource distribution, consumption is, and by far the most consumption is done by the middle class.
Consumption tax is said to be regressive since it doesn't work on rich people since they invest, that should tell you that consumption is much more evenly distributed than wealth is.
> It's still goddamn evil how bad we are at distributing resources
How. How on earth is it evil if you or I have a bit more wealth than the other? Who gives a flying fuck, except... except those who seek power. Total power. You can't have peace as long as you or your preferred leaders are not in total power, and you won't let the rest of us have peace either.
Dear PEP 810 authors. The Steering Council is happy to unanimously [4 votes, as Pablo cannot vote] accept “PEP 810, Explicit lazy imports”. Congratulations! We appreciate the way you were able to build on and improve the previously discussed (and rejected) attempt at lazy imports as proposed in PEP 690.
We have recommendations about some of the PEP’s details, a few suggestions for filling a couple of small gaps, and we have made decisions on the alternatives that you’ve left to the SC, all of which I’ll outline below. If you have any questions, please do reach out to the SC for clarification, either here, on the SC tracker, or in office hours.
Use lazy as the keyword. We debated many of the given alternatives (and some we came up with ourselves), and ultimately agreed with the PEP’s choice of the lazy keyword. The closest challenger was defer, but once we tried to use that in all the places where the term is visible, we ultimately didn’t think it was as good an overall fit. The same was true with all the other alternative keywords we could come up with, so… lazy it is!
What about from foo lazy import bar? Nope! We like that in both module imports and from-imports that the lazy keyword is the first thing on the line. It helps to visually recognize lazy imports of both varieties.
Leveraging a subclass of dict. We don’t see a need for this complicated alternative; please add this to the rejected ideas.
Allowing ’*’ in __lazy_modules__. We agree with the rationale for rejecting this idea; it can always be added later if needed.
One thing that the PEP does not mention is .pth files, which the site.py module processes, and which has some special handling for lines that begin with the string 'import' followed by a space or tab. It doesn’t make much sense for .pth files to support lazy imports, so we suggest that the PEP explicitly says that this special handling in .pth files will not be adapted to handle lazy imports.
There currently is no way to get the active filter mode, so please add a sys.get_lazy_imports() function. Also, do you think appending _mode to their names makes the purpose of these functions clearer? We leave that up to the PEP authors.
The PEP should be explicit about the precedence order between the different ways to set the mode, i.e. $PYTHON_LAZY_IMPORTS=<mode>, -X lazy_imports=<mode>, and sys.set_lazy_imports(). In all expectation, it will follow the same precedence order as other similar settings, but the PEP should be explicit.
We agree that the PEP should take no position on any style recommendations for sorting lazy imports. While we generally like the idea of grouping lazy imports together, let’s leave that up to the linters and auto-formatters to decide the details.
That should just about cover it. Again, thank you for your work on this, as it’s been a feature so many in the Python community have wanted for so long. Given the earlier attempts and existing workarounds, we think this strikes exactly the right balance.
“””
Unfortunately, it doesn't seem as though you can get great stock picks just by going to ChatGPT and asking it to recommend some investments. And yet financial firms of all sorts — including trading firms — say they're increasingly using AI. But are the tools actually being deployed? And how do these tools differ from traditional machine learning or algorithmic approaches to trading, the likes of which have been used by quant firms for decades now. On this episode of the podcast, we speak with Iain Dunning, the head of AI research at Hudson River Trading, a major US market maker. We discuss the firm's attempts to use AI not just for more efficient trading, but also to make short-term predictions about price, which further gives its traders an edge. Dunning walks us through his work, his views on the main constraints facing the space (labor, power, chips, etc.) and how his work is both different and similar to what's happening at the major cutting edge research labs like ChatGPT.
“””
super excited for relaxing the RDB constraints. If you accidentally upgraded beyond Redis 7.2, you likely can just upgrade to valkey without too much effort or any downtime
note that protobuf attributes are 20-50x worse than this
reply