Lower skill ceiling. One option can be done by pretty much anyone at a high volume output, the other would require a lot training and are not available for your average basement dweller.
Good luck trying to regulate it though, Pandora's box is opened and you won't be able to stop the FOSS community from working on the tech.
Boost really should just update the UI to simply show how many upvotes and downvotes a post has. No reason to stick the inferior sum total of all upvotes and downvotes that reddit prefers.
Localised pricing is good though? Is it really fair ask someone in India to pay the same price as an American? If you can't geo block keys, you can't stop people taking advantage by using a VPN to buy games from whatever country got the lowest price. The result will just be publishers keeping the high price for every country, screwing poorer regions over.
Also, what they did wouldn't really qualify as price fixing.
I get the point the author is coming from. When I was teaching first year engineering students programming, the one on the left is how everyone would write, it's simply how human intuitively think about a process.
However, the one on the right feels more robust to me. For non trivial processes with multiple branches, it can ugly real quick if you haven't isolated functionalities into smaller functions. The issue is never when you are first writing the function, but when you're debugging or coming back to make changes.
What if you're told the new Italian chef wants to have 15 different toppings, not just 2. He also got 3 new steps that must be done to prepare the dough before you can bake the pizza, and the heat of the oven will now depend on the different dough used. My first instinct if my code was the one on the left, would be to refactor it to make room for the new functionality. With the one on the right, the framework is already set and you can easily add new functions for preparing the dough and make a few changes to addToppings() and bake()
If I feel too lazy to write "proper" code and just make one big function for a process, I often end up regretting it and refactoring it into smaller, more manageable functions once I get back to the project the next day. It's simply easier to wrap your head around
bakePizza()
box()```
than reading the entire function and look for comments to mark each important step. The pizza got burned? Better take a look at `bakePizza()` then.Got a few minutes into the context video before I head to close it. Do people actually enjoy YouTubers presenting stuff in this manner?
Python are fine with whatever number of spaces you want to use. You can use 8 spaces which forces you carefully consider each nest, you can use 1 if you're a monster, or you can use tabs if you're enlightened, python only demands consistency.
Nothing you said other than expenses is an argument against nuclear. If anything, the take from you argument is that we should construct even more nuclear, not less.
It'd honestly the funniest thing I've read on this instance. Puts programmer humour to shame. Love it when developers finds the jankiest/unconventional way to solve problems.
Aren't those run by the same people?
I think it's a reference to the fact you got Americans defending a faction that started a civil war over the right to own other people.
What issues are you encountering on android Firefox? I've used Firefox + ublock for years and I don't think I have ever encountered an issue that was fixed by using chrome instead.
The team is fairly unison in wanting to avoid defederation as much as possible and leave it users to filter out content they personally don't enjoy. Programming is a big and diverse field, and we want to make it as open as possible to everyone. Unless the instance breaks our own rules as described in the sidebar under "federation rules", I feel like it would be an overreach by us to defederate an instance due to personal opinion.