If everything was equal (scale of production, subsidies, decades of shipping logistics worked out) I’d agree, but I don’t think vegan cheese is anywhere near that.
A good start would be to remove subsidies for livestock and their feedstocks. I think that would already bring the cost of vegan alternatives a lot closer.
For those that need a translation:
“You have got to be shitting me”
“I am in fact not shitting you, my dude. It is very disappointing that this is real.”
For those that look at this and still think the solution might just be more money, first recognize that Google donates only to keep Firefox as a viable competitor to avoid anti-trust legislation.
If we raised half a million dollars, we haven’t saved anyone any money except Google - they’d simply donate only 100k next year so Firefox remains competitive, but not successful.
I don’t disagree with the sentiment of the post, but we also have to realize that we’d only be improving things after the first ~600k.
I don’t know anything about being an electrician - commercial or otherwise, so I’m curious to hear your side.
When all those people go to working remote, it’s not like they’re no longer in need of electricity. Presumably their home demand is higher and we might even see people adding new office spaces to adapt their home. Maybe the public grid needs to change to support it? Won’t this mean that there will just be a different type of demand for electricians?
Are there reasons this would be less attractive to electricians? Pay, job security, or something else?
For anyone who’s curious, this is the state of discussing this feature: https://github.com/helix-editor/helix/discussions/8572
I’m not an authority on the helix ethos, but I’ve contributed a bit and hung around long enough to have a good read on their stance on most topics. The project is still young and managing the growing pains of getting a lot of traction relatively early. I think the devs value keeping the maintenance footprint small to keep the project sustainable.
The philosophy of helix’s design is to be a more convenient kakoune, not necessarily a vim. vim is much more widely known, so that analogy springs up more often, but this idea of using piping out to an external command for most operations comes from kakoune.
For features that would introduce significant maintenance overhead, may jeopardize the performance of a more common workflow or where the design goals are still maturing, the team tends to push such suggestions toward being developed as plugins when that system is added. I get the impression that they see the value of this workflow, but would prefer to see it battle tested as a plugin first.
I’ve been there, but over the years I’ve gotten better at avoiding being in this situation.
If you are implementing something for yourself, and merging it back upstream is just a bonus, then by all means jump straight to implementing.
However, it’s emotionally draining to implement something and arrive at something you’re proud of only to have it ignored. So do that legwork upfront. File a feature request, open a discussion, join their dev chat - whatever it is, make sure what you want to do is valued and will be welcomed into the project before you start on it. They might even nudge you in a direction that you hadn’t considered before you started.
Be a responsible dev and communicate before you do the work.
I fell victim to this one on authentic “retro” N64 hardware, which has a hard plastic analog stick. Got an enormous blister right on the palm of my hand trying to win this tug of war. Of course, my young brain was able to hyperfocus on the game and completely tuned out any sense of pain in my hand. It was quite gruesome when I finally beat it and realized my hand was torn to shreds. I was at my neighbors place and I remember how shocked their mom was. She applied some cream that I think was meant for severe burns.
Nintendo would later run a campaign where they’d send you fingerless gloves for free to try to do some damage control on all the negative press when reports started popping up.