438 karma · joined March 29, 2018
It's not really that cut and dried, plenty of dev workloads are better served by high top single core, while plenty of gaming workloads are better served by multi core.
I don't disagree, but if that's the argument, then make that argument, instead of nonsense about being raised for slaughter.
If being born and raised for slaughter makes that slaughter justified, then would it be ok to kill and eat humans if they were born and raised for that purpose? This argument doesn't hold water.
I'm a woman who studied physics and astronomy at university. In my final year I taught myself programming in my spare time because I was interested in it, and knew the job prospects were better than in physics. I had other hobbies and an active dating life at the time, but I still managed to get a software job straight out of university, and it's evolving into a fruitful career.
Learning to program in no way requires 3 years of monastic devotion.
To me, this is a sensible decision. The target users of git will use it day in and day out for decades, in this case it makes sense to prioritise experienced usage. For onboarding new users there are plenty of good tutorials, and I think in the long run it makes sense to put the legwork in with those, rather than switch to a more intuitive but less efficient porcelain.
That isn't toxic masculinity, it's a gender norm. What would be toxically masculine about it, is if a man felt forced by society to fulfill that role, regardless of his own feelings and desires.
Feminists challenge that norm and the societal pressure that drives it, but there's nothing wrong or toxically masculine with a man doing that because he genuinely wants to and isn't forcing anyone else into a role.
Sex assignment is the official term used for designating a sex to all babies[0] not just intersex ones. As such it is totally correct to use the terms AFAB and AMAB to describe non-intersex trans or even cis people.
The author most likely just has a bone to pick with trans people for using intersex people for their own ends, without sharing their visibility or talking about our issues. Which is a valid grievance, but this is not a valid outlet for it.
1) A meeting (Important Urgent) 1 or 2 hours
2) Buy a gift for someone's birthday (Important - can be done any time but must be done) 1 hour
3) Check the marketplace for a limited sale (Urgent - much better if done immediately, but doesn't matter so much if not done) 1 hour
If task 1 takes only one hour, I do 3 then 2. If it takes two hours, I do 2.
There's two contexts above. Obviously as you pointed out, once you actually get to doing a task, there's only one context. But the point is that when adding a task to your to-do list you don't yet necessarily know what that future context will be.
Your choices here are to either make a priority queue for every possible future context (reasonable for this simple case, but doesn't scale to a more complex one), or mark tasks with the relevant information that will let you easily assemble the appropriate priority queue on the fly, once the context becomes clear.
It does make a practical difference. Important tasks are higher priority under tighter time constraints and vice versa. I fail to see how this isn't a practical distinction.
>If you always lean towards Urgent things, you will neglect the Important. If you always lean towards Important things, you will neglect the Urgent.
If you do this you failed. The point is lean important when time constrained, urgent when not.
>Conversely: if you have a way to decide which task to schedule first, then (to you) they clearly have different priorities.
They have different priorities IN DIFFERENT CONTEXTS. One is higher when time constrained, the other higher when not. It is clear from reading your comments that you have not understood this.
It also stands to reason that if that many people really are dependent on fish, it will be devastating to them when overfishing and pollution destroy fish stocks. All the more reason to reduce fishing and build alternatives now.
The point was that importance is not the same thing as urgency, which the parent comment didn't seem to understand.
>Choosing between Unurgent-Important<->Urgent-Unimportant is exactly the same problem as choosing between Urgent<->Important.
Sure, in the other formulation you simply make the assumption that the important task is unurgent, and the urgent task is unimportant, and so they are the same, as long as we're on the same page.
>You have two tasks: A or B. Which one should you work on first?
I actually did address this. If you have time for both the urgent one comes first, if you may have time for only one the important one comes first.
Urgent is not a synonym for important, and the point of drawing the distinction is to recognise that relative priorities can be different depending on context, such as how much time is available.
Armed with this knowledge, we can categorise tasks in four: urgent-important, urgent-unimportant, unurgent-important, and unurgent-unimportant. Urgent-important tasks are always the highest priority, and unurgent-unimportant tasks the lowest. Where it gets interesting is between unurgent-important and urgent-unimportant tasks, the former should be prioritised if you do not have time to complete all the tasks, and the latter should be prioritised if you do.
What??? This isn't true at all, you can install deb/rpm packages you download from the internet if you want, there's nothing stopping you. The truth is that you're strongly encouraged to install your applications from a trusted central repository because it's safer and more convenient.
I'd also note that this is not unique to Linux. Android, iOS (this one is actually restrictive), and macOS all use the same model too. Windows also tried it with UWP and their store, and mostly just didn't succeed for legacy reasons.
I don't really understand this. When I'm talking to an adopted child, I have no trouble calling their parents their parents, even though they're objectively guardians. When I'm dining with religious folks, I have no trouble saying "Amen" or some such phrase from their religion despite me being an atheist.
Saying something you don't objectively believe out of consideration for others' feelings is normal, and it's fairly basic manners.
I too am autistic, and it does not excuse this behaviour. Yes people should have compassion and patience with neurodivergent people, and everyone has been with Stallman. This is not one incident, but a string of incidents that show an underlying pattern.