igsomething

I do agree with your comment.

not not

On one hand I agree genders are pointless for chair and book. On the other hand, many nouns are the female or augmentative version of the base word. From your examples: "silla" (f, chair) vs "sillón" (m, sofa), and "libro" (m, book) vs "libreta" (f, notebook).

In languages with genders you need fewer unique words for gender-related concepts. For example English (genderless) has "boy" and "girl", while Spanish (male and female) has "niño" and "niña".

I am almost sure they don't and instead they query selfies and documents on-demand from their KYC provider.

It wasn't about diving in particular, but rather post-match revisions and sanctions becoming more common to punish unsportsmanship. Add VAR in recent years, and the newest "1 minute out" rule for fake injury, and today players don't gain anything from diving.

The language also takes backwards compatibility very seriously, anything that goes into std "must be maintained forever". It is also argued that a large stdlib means the maintainers have less time to work on the language itself.

I understand not every language can have Go's amazing stdlib, but I would much prefer Pyhton's approach where every now and then some package/function from the stdlib gets deprecated/removed. Rust's 3rd party ecosystem is the worst thing from the language, worse than the compile times.

I think a good metric for "boring" technology, at least for languages/frameworks, is how painful the process of updating an abandoned/unmaintained project after 9-12 months is. NodeJS itself qualifies as boring, but the entire ecosystem around it is still a mess.

The same UEFA that added redundant matches and teams to the Champions League for money, and that came up with the Nations League because they wanted to extract more money from the national teams?

Currently working on a CLI tool that performs property-based testing from Arazzo documents: https://github.com/IgnacioGoldchluk/cuerdo

I agree, but one thing is to demand all your users to be on the latest Chrome, and another one is to support browsers that are no longer maintained and contain security issues (IE). If we discourage people from driving old insecure cars, we can also discourage people from using old insecure browsers.

For public services you can tell people to use another device, or provide a way to schedule an appointment in-person that is accessible using old browsers.

Maths IS pattern recognition

I had a contract once to save a government website that had serious performance issues, it was so unusable that people preferred to go in-person and wait 4h in a queue rather than try to fill the forms online.

The frontend was in React because the company that got the contract initially used React for everything. The frontend was a 5MB SPA, but it could've been (mostly static) HTML files with some interactivity for forms like TFA. Everyone working on the project agreed React didn't make sense, but we couldn't do anything about it because someone from the government IT department would have to admit they made a mistake. There was no budget for rewrites in the contract. The few times a developer attempted to remove any "React monstrosity" they got in trouble.

Sometimes developers care, but the people in charge don't, and in government environments every change must go through them first.

One important thing that is often not mentioned is the lack of operator overloading. In Elixir if you have "a + b" it means "a" and "b" must be numbers for the code to succeed, which narrows down the possibilities significantly. Compare that to Python, where "a + b" applies to numbers, string concatenation, and any object that implements the __add__ or __radd__ magic methods, it becomes a nightmare to type.

Then people from a sanctioned countries are blocked from open source, or worse, you have to explain to the bank and/or the government why you sent 20USD to someone in Venezuela.

It is a negative feedback loop, so yes, it makes systems stable.

Dependency hell. Usually how it goes is you have to develop a new feature, you find a library or a newer version of the framework that solves the problem but it depends on a version of another library that is incompatible with the one in your project. You update the conflicting dependency and get 3 new conflicts, and when you fix those conflicts you get 5 new conflicts, and repeat.

Server Side Public License? Since it demands any company offering the project as a paid product/service to also open source the related infrastructure, the bigger companies end up creating a maintained fork with a more permissive license. See ElasticSearch -> OpenSearch, Redis -> Valkey

Going from Django to Phoenix I prefer manual migrations. Despite being a bit tedious and repetitive, by doing a "double pass" on the schema I often catch bugs, typos, missing indexes, etc. that I would have missed with Django. You waste a bit of time on the simple schemas, but you save a ton of time when you are defining more complex ones. I lost count on how many bugs were introduced because someone was careless with Django migrations, and it is also surprising that some Django devs don't know how to translate the migrations to the SQL equivalent.

At least you can opt-in to automated migrations in Elixir if you use Ash.

Hey, first I want to say that Oban has been a lifesaver for me and it is the tool I miss the most from the Elixir ecosystem when doing work in Python. Thanks so much and congrats on the release.

I have one question: are there any plans for interop between Oban and the new Django Tasks[1]?

[1] https://docs.djangoproject.com/en/6.0/ref/tasks/

As another 3rd world citizen living in Northern Europe, I usually describe it as "processes and rules over common sense". They understand your situation, they agree with you, they can solve your problem, but they will not do it because it goes against some obscure rule, or it would not follow a specific mandatory procedure step by step, and who knows what are consequences.

Keep in mind in Argentina public domain works are not free (free as beer) of use, you have to pay a fee to the government, for example if you play Beethoven music in your short film or any work you created.

This is likely going to change since the organism responsible for collecting the fees is undergoing a big restructuring.

Electronic Enginering is also not that old and it has been a proper engineering discipline for many years already

In an ideal world none of the past 70 years of conflicts that led to this unrecoverable resentfulness would have happened. Unfortunately the only peaceful solution I can imagine is for Israel to let Gazans move to other Arab-world countries, let Israel annexate Gaza, and then imposing strict border controls and watches such that if Israel attempts any ethnic cleansing or illegal occupation they get severly sanctioned.

It would be useful to compare with other leagues where home field advantage is significant. I do not have any data but as a football fan I suspect the following variables are important:

- England is an homogeneous country in terms of geography. There is no 40C degree temperature difference between north/south clubs. Playing in weather conditions one is not used to can affect the away team.

- England is also a small country. The away team can arrive at the stadium within the day. Not only it means they are better rested but also home fans cannot bother them at the hotel making noise, throwing fireworks, etc. preventing them from sleeping.

- The FA is not as corrupt. Sure, certain teams can get away with playing dirty, but in general referees will show red card to a home team player, or call out a penalty for the away team.

- Less threatening environment at the stadium, both for the away team players and the referees. Nobody is throwing food, beer or anything at the players during the game, and hooligans will not try to harm the referee if the home team loses.

Surprisingly, no. Milei's party does not have majority in the Congress, he does not have much power, and the best example is his omnibus bill [1]. Initially Milei's party attempted to pass a massive 300-page reform, consisting primarily of deregulations and paving the road for a more free-market government model. The reform was debated for almost 6 months, and the accepted version was about a 3rd of the original one.

The president has power to make only small changes in Argentina, but the previous system was so flawled that any minor change resulted in noticeable changes to the general economy.

[1] https://en.wikipedia.org/wiki/Law_of_Bases_and_Starting_Poin...

That is not the definition of fungible. You can put a mark on a USD$100 bill and trace it, but it still has the same value as any other USD$100 bill, or 5 20$ bills, etc.

The map '%{username, age, first_name, last_name}' would be 1 character away from the tuple '{username, age, first_name, last_name}'. It is easy to miss the '%' character and you'll waste some time figuring out why your code is throwing match and/or function clause errors at runtime.

They are different.

    def square_vals(x : list):
        return (val * val for val in x)

is a function that takes a list and returns a generator. While

    def square_vals(x : list):
        for val in x:
            yield val * val

is a generator itself.

The first case creates an anonymous generator. When in doubt you can always use the dis module: https://docs.python.org/3/library/dis.html

.rs (Serbia) for Rust projects.