Doing concurrency in Rust was more complex (though not overly so) than doing it in Golang was, but the fact that the compiler will outright not let me pass mutable refs to each thread does make me feel more comfortable about doing so at all.
Meanwhile I copy-pasted a Python async TaskGroup example from the docs and still found that, despite using a TaskGroup which is specifically designed to await every task and only return once all are done, it returned the instant theloop was completed and tasks were created and then the program exited without having done any of the work.
Does it really? Because I see some quite fine code. The problem is assumptions, or missing side effects when the code is used, or getting stuck in a bad approach "loop" - but not code quality per se.
I'm going to speculate that it won't "add" ships at all
As you say, ships are moving in and out of the EU each year - the question is, how many have "back loads" - if some percentage of the ships leave Europe empty to return to Asia for more manufactured goods, then it seems very likely that they can have the containers of unwanted clothes as part of the trip.
Oh cool, so I can fly commercial all I want at zero marginal CO2 emissions just because they don't have to build an extra plane just for me? I can burn that jet fuel and not feel bad because they were going to burn that gallon of fuel anyway?
Some of these arguments are so silly that I'm starting to understand why the EU thinks regulations are a free lunch to improve the environment with no costs whatsoever.
Airlines adjust capacity to demand — empty seats represent foregone revenue and future flights get cancelled or downsized.
Cargo ships don't work that way. A container ship returns to Asia whether it's carrying 1000 containers or 5000. The marginal emissions of an additional backload container are genuinely close to zero, not as a rhetorical trick but as a structural feature of how bulk shipping economics work.
Australia currently bans the sale of "recycling" plastic and e-waste to certain countries in South East Asia because of this problem (dumping to companies that have no qualms about throwing the waste into waterways etc)
The waste is still making its way to those countries, and the way that we know is that NGOs are tracking it[0]
I suspect that clothing will get similar treatment - initial illegal dumping as you predict, followed by determined NGOs holding the supply chain to account.
The number of different cultures in Africa, each with its own set of traditions and ceremonies makes that a very difficult question to answer in a generalised way.
Fair. I was curious since English only started having last names in the 11th century, once the population has grown too large for local governments to effectively govern without some way to better differentiate people.
As an ENG - I REALLY dislike teams - but I also dislike Slack
Slack should be emails that have been arranged into different folders - it just doesn't vibe with me for much otherwise (oo look you have 200 channels on unread - or, if you are the reverse, ooo look 200 channels with people chatting and I have to check every single one of them :(
Yeah, I mean the first thing we all do when we get one giant unified inbox is write a bunch of rules to break it back out to a set of folders so that we can triage it appropriately. Slack channels just do this from the get go.
I'm not saying you're wrong - but I do detest that attitude myself
As you say, trust is a two way street, and first time contributors are being expected to trust that it's not personal when they are met with brusquerie.
I know it's hard when it's the 99th person and you've had to deal with 98 less than nice individuals, but defaulting to an abrupt or blunt manner does nobody any favours.
The demands here are effectively extensions of netiquette[0] and "how to ask good questions"[1]. Every code contributor should at least understand what is asked of them.
[Julia's post sadly does not include the blunt expression "demonstrate that you have done your homework", which is a fundamental tenet.]
What’s the solution then? This is one of those emotional-labor questions.
Who is responsible for new contributors having a good experience? Especially thousands of eager, misinformed contributors?
It’s a DDOS that exhausts and burns out the maintainer even while the supply of newbie contributors is rarely meaningfully impacted by maintainer conduct.
The world has givers and takers, and we are all both at different times. The newbie thinks they are a giver, but mostly they are a taker.
I've also seen maintainers complain about "drive by contributors" where one complaint is that the submitter has provided a good patch/PR, but doesn't stick around to support it.
From the submitters point of view, why /would/ you stick around if your first (and only) interaction with the project is less than "ideal"
FTR I absolutely understand the "burnout" maintainers experience dealing with contributors that drain energy as well.
I mean, once Starbucks have it, then the customers get it back via product (that has a margin included), or just leave it forever (free money!)
I have a firm "No vouchers" rule because of this, the vouchers in my part of the world inexplicably "expire" if not used within a certain amount of time, cannot be redeemed for cash, and will not be honoured if the business goes belly up
According the laws here they have to. Doesn't mean they won't make it difficult. And it needs to be in a separate account and business (to avoid it being drawn into a bankruptcy). Not that this has ever stopped businesses from abusing it anyway. I doubt this voucher option is available in the Dutch app because of this but I didn't bother to check.
reply