Yeah fair I was just assuming this was standard library, I see your point now.
Yeah fair I was just assuming this was standard library, I see your point now.
Being able to get the line number is very different from comments being parsed.
I have no context here, but isn’t getting a similar level of pushback from the community under a second alias evidence of some of it being justified? Or did people somehow discover it was the same person and then the abuse started?
When combined with sed, sure, but the difficulty ratings should be swapped.
GitHub (since the Microsoft acquisition) is good to users because that’s their MO, it’s called Embrace, Extend, Extinguish, and the whole point is to centralize users and projects and make them dependent on the Microsoft ecosystem.
Of course now there’s also the whole issue of Copilot, which means any code you put on GitHub could very well show up piecemeal in someone’s AI-generated code. If it wasn’t for that novel avenue of monetization, you can bet your ass GitHub would have already made the free user experience a lot shittier.
Every device with extra swappable batteries that I’ve used has a charging station that you can just keep the extra battery in. Not really anything to “manage”, it just effectively removes charging time from the equation.
Devs ITT biting every single argument in the article and then saying “but it’s easy” is extremely ironic
Literally how
You’ll need a decent GPU to decode HD video, which led me to just put together what’s basically an outdated gaming PC from old parts and a couple cheap ones I had to order. Works great as a jellyfin server.
So like Rust?
It’s the literal job description in many cases.
From the comment thread it sounds like the contract might be on shaky ground. The original dev seems to be under the impression that a project licensed under GPLv3 can just be freely changed to another license, which it cannot without explicit consent from all contributors. We don’t know the contract language of course, but the dev said it would “likely” not remain open source, which indicates that he told them they could change it. ZippApps’ lawyers will hopefully notice that and refuse to buy, though either way we shouldn’t trust this maintainer again and should move to the forks.
The fundamental problem is that a web engine is one of the most massively complex pieces of software that we currently use. There are a ridiculous number of standards and behaviors that a modern web browser needs to implement, as well as a whole host of security implications that need constant updating. It’s not like the majority of other software projects, where a determined solo dev or even small group can strike out on their own. It really requires a team of dozens or hundreds of developers putting in consistent effort, which basically means a corporate entity.