So what’s next (personal news from developer of popular CoreJS polyfill)

Post by serverholic » Tue, Feb 14, 2023, 2:30 AM UTC

fragmede wrote: post #49

akudha wrote: post #26

In one of my previous jobs, my CTO asked me who I thought was the most important person in the company was. I wasn’t sure. He pointed to the lady who was responsible for entering and maintaining data, on which the entire business was built upon. She was a quiet person, who did her job exceptionally well. Yet, most people didn’t know her or didn’t realize her importance. I am certain she wasn’t paid that well either.…

What I'm really struggling with is how much this contrasts with the story for the developers of Dwarf Fortress, who don't get that same hate and vitro piled on them, and in fact, people throw money at them because they want the developers to have money. To the tune of like $9 million or something! Whereas this guy, pouring his heart into something useful and not for fun, gets all this hate shoveled his way? I really…

Post by ricardobeat » Tue, Feb 14, 2023, 2:32 AM UTC

cyral wrote: post #70

ricardobeat wrote: post #65

I can sympathize with the author's troubles, and wish he finds a well-paid position that still allows him to work on OSS. That said, the idea that companies would pay for a JS library that is patching browser support is wild. Practically nobody pays for JS modules except for very specific niches (e.g. a charting library) or product/technical support. Especially when it's an indirect dependency of tools you use. Maybe…

> - The idea that companies would pay for a JS library that is patching browser support is wild. Companies make more money by having their websites work in older browsers. If it wasn't for core-js, they would be paying developer time to write polyfills or compile and maintain them from various other single polyfill packages. Surely if they are willing to pay developers to do this in return for increased profits they…

Post by [deleted] » Tue, Feb 14, 2023, 2:33 AM UTC

aloisdg wrote: post #68

ricardobeat wrote: post #65

I can sympathize with the author's troubles, and wish he finds a well-paid position that still allows him to work on OSS. That said, the idea that companies would pay for a JS library that is patching browser support is wild. Practically nobody pays for JS modules except for very specific niches (e.g. a charting library) or product/technical support. Especially when it's an indirect dependency of tools you use. Maybe…

https://user-images.githubusercontent.com/2213682/154870832-...

Post by duxup » Tue, Feb 14, 2023, 2:38 AM UTC

jackblemming wrote: post #80

He has made multiple posts like this and it always reeks of entitlement and disdain for his user base. Charge money if you want money. Don't give something for free and then complain. The real reason he doesn't charge is nobody would pay or someone would immediately fork the project and do it for free. The point of large open source projects like this is to parlay it into career opportunities, not expect every instal…

Post by duxup » Tue, Feb 14, 2023, 2:39 AM UTC

phpnode wrote: post #16

It's definitely time for him to let this project go, working on it is a literally thankless task and the level of entitlement shown towards his work has been infuriating to watch. The outrage towards him daring to ask the community for help , something done in an act of desperation, is a real wake up call for open source maintainers - the community doesn't give a fuck about you, they want your code and they want it f…