Why would you want to remove it? Do you reasonably see yourself digging into the code to remove that bit, rebuilding and reinstalling, compared to tapping "I have paid" once to dismiss (ideally after you actually have paid)?
SEEKING WORK | Austin, TX (UTC-5) | REMOTE and Austin Local
I have a lot of wide-ranging experience, but will provide the most value to your organization if you need some combination of Rust, AWS/DevOps, and Kubernetes expertise.
That's frequently the nature of "community" projects. They're based in a particular idealism wherein authority is a patchable bug and direct democracy can scale infinitely.
In reality, they are just free-for-all power struggles. What starts out as anarchic fun and inclusivity among ~1-100 like-minded people scales into dysfunctional sectarianism.
What a strange way of looking at it. At any functioning company, toxic employees get fired because the cost of them pushing out other employees is usually higher than the cost of firing them. Open source projects do not hire and fire people but do have the ability to censure toxic contributors.
I know nothing about this particular case, but the general idea of moderating contributors to a project is not wacky as you seem to believe and predates the existence of distributed open source development.
Except in those situations you never weight the amount of people you lose by adding a significant level of "cultural oversight" to a project. I actively avoid projects that spend a lot of time talking about "inclusivity" because to me it's a symptom of a (ironically) toxic environment full of people looking for drama (I am an ethnic and sexual minority myself in case someone wants to throw privilege in my face).
The end result is that you replace one group of people with another group of people, you push away some to gain some. Except people like myself are rarely mentioned when there is a discussion about toxic environments.
> I actively avoid projects that spend a lot of time talking about "inclusivity" because to me it's a symptom of a (ironically) toxic environment full of people looking for drama
100%. I do the exact same thing, for the exact same reasons.
If you see a code of conduct that reads like a political manifesto, that's a red flag, regardless of the particulars of the politics expressed.
> 3. The most impressive part about esbuild development is not just that it's one guy writing it: it is the level of support and documentation he manages to provide alongside.
And the one guy writing it is Evan Wallace, co-founder and CTO of Figma. I don't know how he has the time!
> Instead of attempting to get one of [HTML/SVG/JS Canvas] to work, we implemented everything from scratch using WebGL. Our renderer is a highly-optimized tile-based engine with support for masking, blurring, dithered gradients, blend modes, nested layer opacity, and more. All rendering is done on the GPU and is fully anti-aliased. Internally our code looks a lot like a browser inside a browser; we have our own DOM, our own compositor, our own text layout engine, and we’re thinking about adding a render tree just like the one browsers use to render HTML.
To most people, esbuild would be a full-time job. Based on the above, it seems that to Evan it's a fraction of the work he did in Figma's early days all at once!
This seems like a pet project. Reason I say that is if it was built for work, it would likely be from figma. Instead this project is from Evan himself.
I'm not so sure about that as you. Not all companies are like Google and "steal" the credit of work done by employees, even if done on work time but unrelated to the core business. Plenty of companies let employees work on open source and still remain the owners of the software produced.
everyone on your team should be using a auto-formatter