• 0 Posts
  • 29 Comments
Joined 2 years ago
cake
Cake day: August 13th, 2023

help-circle

  • Moving fast doesn’t have to mean poor workmanship.

    To make an analogy, if you want to be able to make a cup of coffee fast, you need to make sure that the coffee beans, the water, and the brewer are all near each other, that there is electricity and that the water is running. These are all things that enable you to move fast, but they don’t decrease quality, if anything they increase quality because you aren’t wasting time and effort tackling obstacles unrelated to brewing.

    Which is in fact the point of the article. That you should make sure you have a good development environment, with support systems and processes, so that you can work effectively even if your developers are not savants. Rather than trying to hire people who are good enough to do a decent job even in the worst environments.







  • How many of these “lacking features” are actually standardized? Of course some draft under development by Google will only work in the latest version of Chrome. It might not even work in future versions of Chrome, since it’s not standardized.

    If you built something that requires such a feature, it’s you who is choosing to write code that is incompatible with the standards and only works on a particular browser version. You can’t blame others for that.




  • It’s essentially just a bunch of pre-made css classes that do a specific thing that you mix and match from.

    AFAIK the programmatic part is so your served CSS file will only include the classes you actually use, rather than all available ones. You could always just not do that.

    It always seemed to me like one of the least overengineered front end tools.







  • The massive negative outcry over this fairly uninteresting change certainly seems oddly overblown, almost as if there are parties trying to turn it into a big political issue to paint Russia as a victim. But idk, nerds freak out over stuff all the time completely on their own.

    Giving them the benefit of the doubt, I think the Linux Foundation has a hard time being clear on the matter because it just isn’t clear. These are new laws and a global open source cooperation run by a non-profit is likely a corner case that the lawmakers did not think about at all when making them.


  • Yes, the sanctions against Russia, as mentioned by Linus. The change also said the maintainers “can come back in the future if sufficient documentation is provided”.

    My guess is that the Linux Foundation must ensure that none of the people they work with are in any way associated with any organisation, person or activity on the sanctions list. And that they preemptively removed all maintainers that might risk violating the sanctions while they work with them to establish whether they might be covered by the sanctions or not.

    Regardless of what you or they think of the sanctions, they are the law, and I don’t think anyone wants the Linux Foundation to have to spend their money on lawyers and fines because they had a maintainer who also worked on a research project funded by a sanctioned entity. (If that is how it works, IANAL)


  • Yeah the tech labor market has really proven that the idea of employment contracts being negotiated between equal parties isn’t true even in the best of circumstances.

    Even when companies are desperate for talent, and willing to spend ridiculous amounts of money on salaries and perks, they are not willing to negotiate on anything outside of that. They still have terrifying contracts with non-compete and damages clauses they could use to wreck your life, no workplace democracy, unpaid overtime and whatever other shit is legal.

    But hey! You get free snacks and enough money to buy the dinners you don’t time to cook and save up to survive your inevitable burn out!