And then revisionists like you come along and start questioning things because you in person haven't seen it. Well, I guess lucky you.
2,257 karma · joined July 19, 2013
And then revisionists like you come along and start questioning things because you in person haven't seen it. Well, I guess lucky you.
Game dev is an arduous and draining process that both requires the patience to go through periods of dreary work where no progress seems to be made and yet the creative spirit to devise art, concepts, mechanics, rules, etc. If I had the time, I could easily see myself spending multiple years on a project like that without the need to see any financial reward. I wouldn't see it as work, I would see it as Work with a capital W. A hobby that requires a lot of personal effort but something I do because purely for the joy of doing it.
But yes, let's go throwing around thinly veiled insults instead. This tells me everything I need to know about you :)
Whether we'll be able to replicate it profitably at small scale is a question.
Stocks are not my area of expertise so I gloss over a lot of details... maybe and equity trading specialist can chime in?
If this business proposes to be profitable by harvesting the borrow fees, then them being cheap is really disingenuous because they give you with one hand and take from you with the other.
I'm sorry to sound negative, I really wish you all the best, but even from your post it looks like you had little to no idea what you are doing when you started this (you didn't know stock tickers are ephemeral?). And yet you are asking people to trust you with their money? With the only selling point being that you seem to be unsustainably cheap? What made you decide that you have the knowhow to do this well and safely?
My objections are to the fact that someone had to build this atrocity of a Venn diagram just to illustrate the python ecosystem: https://alpopkes.com/posts/python/figures/venn_diagram_updat...
And in this very thread, people seem to accept that this is fine. There's nothing wrong with the fact that there are 6 separate tools just for building a package, some support publishing, some don't, some also manage environments or python versions? Which of these are currently supported, which are deprecated, which are going to become deprecated in 2025?
But also there's a tool which only does publishing (twine)? The diagram is not even correct, because conda itself requires package building, except it's about building conda packages, which are cross-platform/language and separate from building a python package.
Why is there a separate set of tools for package management and package publishing?
The blog post is indeed helpful to allow someone new to python to at least see what options there are and roll the dice, but it will also raise extremely serious alarm bells that there's something fundamentally rotten at the core of the python ecosystem.
The fact that I need to read some unofficial post from 2023 to gain an overview of the python packaging and environment management ecosystem is itself completely nuts. And I can guarantee you that by now this blog post is getting outdated, because some mad genius is cooking the new best tool and ready to unleash it on the unsuspecting world.
This is a bad joke. It's a mature language where the answer to: "I want to manage my programming language version and installed libraries" is that you have to try a dozen different tools, each of which will cover some but not all of your requirements to do this one simple thing.
> I've used all of these tools successfully (at different times and/or for different use cases).
And you see nothing wrong with that? Pretty much every modern language has one way (or at most just a small handful of ways) to build a library and manage your dependencies/environment. The reason is that packaging and environment management is a side show. A necessary evil we have to do so that the actual crux of our work can be done. When I set out on a project, I don't say: "I want to spend a week figuring out which is the current environment management tool supported by the python mindshare". I don't want to deal with a dozen different ways of installing the dependencies of a package. This is insane. When I pick up a language, I want to know what is the way of managing dependencies and packaging up my stuff. And I don't want this to change on a yearly basis, doubly so for a mature language.
> If you think a language that has just one tool is better, then it just means your use-cases are very narrow.
Yes, I prefer that there's a choice of tools for say time series analysis or running a web service. Competition in those areas is good. That's how innovation is driven forward.
When it comes to package and environment management, I don't want innovation, I want stability. I want one agreed way to do it so that I don't need to fuck around with things which are completely orthogonal to the work I actually want to do and that will put bread on the table. I don't want to spend brain cycles keeping up to date with yet another hare brained way of defining what is a python package.
In my view, the reason why we are in this quagmire is because the roots of python are in a fairly simple scripting language, and the packaging has not well escaped these roots. You can have loose python files, you can have directories containing python files which are automagically modules, then we had to hack in a way to package collections of modules and manage their different versions. It's all hacks upon hacks upon hacks, and it has to be backwards compatible all the way to being able to run a loose python file.
I'm not saying this is easy to solve. It's the posterchild of the "Situation: there are 15 competing standards" XKCD. The time to solve it would've been 15 years ago while Guido was still the BDFL. There are too many stakeholders now to get any sort of consensus.
Happily, I haven't yet been afflicted by a strong urge to build python packaging tools and inshallah I will escape this dreadful fate.
Rust programmers seem to be lousy with ECS frameworks that never get used in any games but seem hell bent on proving that rust is the best language for game programming, and python programmers seem to break out in a case of "packaging tool building". I don't know what causes this. Perhaps some sort of pathological thinking that "I can do better"?
I really like python (and I like rust too), but if I were to take an honest look at the python packaging and environment ecosystem, I'd think that I'm being trolled. I lived through the age of setuptools.py, and while it was not good, at least there was only one approach really. Now we have a bazillion approaches that are all good, and zero consensus on what to use. Each individual tool is much better than what we had before, but the landscape has become so fractured that as a whole it's a complete shitshow.
</old man yells at cloud>
> df.resample("BME").sum()
Assuming `df` is a dataframe (ie table) indexed by a timestamp index, which is usual for timeseries analysis.
"BME" stands for BusinessMonthEnd, which you can type out if you want the code to be easier to read by someone not familiar with pandas.
> my_df.resample("BME").apply(...)
Done. I don't think it gets any easier than this. Every time I tried something similar with polars, I got bogged down in calendar treatment hell and large and obscure SQL like contraptions.
Edit: original tone was unintentionally combative - apologies.
df.resample("BME").sum()
Done. One line of code and it is quite obvious what it is doing - with perhaps the small exception of BME, but if you want max readability you could do:
df.resample(pd.offsets.BusinessMonthEnd()).sum()
This is why people use pandas.
Does this require further work? Yes of course. We are definitely not there yet, and we may never get there. But let's not pretend that this is an insurmountable problem.
You can do the same with Polars, but you have to start messing about with datetimes and convert the simple problem "I want to calculate a monthly sum anchored on the last business day of the month" to SQL-like operations.
Pandas grew a large and obtuse API because it provides specialized functions for 99% of the tasks one needs to do on timeseries. If I want to calculate an exponential weighted covariance between two time series, I can trivially do this with pandas: series1.ewm(...).cov(series2). I welcome people to try and do this with Polars. It'll be a horrible and barely readable contraption.
YC is mostly populated by technologists, and technologists are often completely ignorant about what makes pandas useful and popular. It was built by quants/scientists, for doing (interactive) research. In this respect it is similar to R, which is not a language well liked by technologists, but it is (surprise) deeply loved by many scientists.
That's just down to charging infrastructure no? Sure, there are physical limits to how much electricity one can move in a given time, but we are nowhere at those physical limits.
So it's just down to infrastructure in the end. If there was infrastructure to quickly and reliably charge EVs, ICE would only have niche advantages.
You can get an EV, and then have to deal with half a dozen barely competent charging networks each with their own donkey, slow and insecure app, their own quirks and pricing schemes, etc. For some, the tradeoff is worth it, for others it isn't.
You can also get a PHEV, which could allow you to use one car for commuting purely on electric power - even if you are lugging around an entire ICE power train - and then also take the family out to the countryside over the weekend. Without the having to deal with a bunch of annoyed passangers when you are stuck midway through your journey and the charging station you are trying to use is giving you the massively helpeful error message of "Charging failed, please try again later".
That being said, heroin is one of those things that are genuinely dangerous to try. It's so easy to become addicted to the stuff, and the costs to society are so high to get an addict clean, that one has to at least consider the pros and cons of prohibition. In an ideal world, all consenting adults should have the free choice to ruin their life if they wish, and perhaps in a post-scarcity society this is what we should allow everyone to do. But while resources are still limited, heroin addicts (and by extension opiates) create a lot of negative externalities. Personal freedom is all good, but where does it end? Should a person be free to ruin the lives of others when they cannot get their fix other than to rob people? And when someone is getting withdrawal symptoms, they have no more free will, they'll do anything to avoid that suffering.
It's tricky to say what would be the marginal increase in heroin users if it was easily available. I agree with you that rational people with well balanced lives and a strong safety net in terms of family and finances are unlikely to go out and buy heroin. People who are bored, in a bad spot, depressed, etc... might just go out and do it if all it takes is a short walk to the nearest shop.