This whole article is red flags. (Mental health issues including narcissism?)
- No mention of what specifically it does
- No mention of the advantages and stated reasons for having small std and core libs
- Libs mentioned as being "shipped" by the author have no commits by him or her.
- No comparison in the specifics to how it's handling
- Uses phrasing which might (IMO deliberately) confuse people into thinking this is official.
up until maybe 200 years ago famines were a genuine and consistent threat even to places like Europe.
food wouldn't just have sucked, in many cases all you could eat would be some dried grain boiled to porridge, or the handful of semi-mouldy veggies that made it through winter months -- and many would often be lucky to even have that
Recipes were the province of the wealthy. The average person would have had a very repetitive, bland, and potentially malnourishing diet. They might have had some herbs or even foraged like you say, that still is very bland and boring compared to what we’re used to.
From what I have read the diet of people in classical antiquity was only terrible for the very poor. Most people in ancient Rome got to, at least rarely, eat honey cakes and fresh fruit and dried fish and maybe once a year at festivals even a small chunk of meat. They grew chives, dill, garlic, asparagus, radish, parsley, thyme, mustard, cumin and many other spices. And they made vinegar and olive oil and garum (fermented fish sauce) on an industrial scale. Mostly these would be used as sparing garnish to the grain-centric diet. But usually present.
one thing to note is that while they may have consumed it they probably weren't making it. Particularly for urban dwellers, kitchens were very rudimentary if you even had one.
A lot of AWS is built on open-source. This is obviously ignoring hardware costs. I don’t know if it is all that ridiculous anymore. These models are very good at wiring together open-source systems. The world is crazy right now…
AWS has over 200 services, so that's a little over $2 per service. Yeah, a lot of it is built on OSS, but there is a ton of it, and there is also a lot of work involved in building the APIs and web UI, and making it scalable , secure, and resilient.
Now, you might be able to make a version of some small subset of aws services that runs works ok for a small scale for with relatively simple needs, for that many tokens, but I don't think that's what they were going for.
I’m on your side in that I would never take a contract to actually do this, but…
If we swapped out the IAM backend for something extremely simple like just private keys (one per allowed service or JWT-style list all services in the key), then we could have something that looks/feels pretty similar. With a 2$ token spend.
Not at all the same but it would look/feel pretty close.
I tend towards using key-value databases as I find them general purpose enough while being much more robust. I'm not married to any one in particular, depends on the requirements.
strict type checking is an incredibly useful tool for cases when you really want to make sure your code is correct and behaving as expected (one of many tools).
There are lots of people who like python and want to use it for things that where incorrect code has serious consequences. Type checking is helpful in these contexts.
Type checking remains optional for the masses and is not practical in many cases. Still, pushing away people who want to use all available tools for writing correct python only hurts the community.
The author is an individual claiming the ability to author and maintain a standard library
… to be used by small orgs who do not have the resources to author and maintain a standard library.
reply