> FWIW, and since a few of you probably use it… I own the JSON Formatter extension [0], which I created and open-sourced 12 years ago and have maintained [1] ever since, with 2 million users today. And I solemnly swear that I will never add any code that sends any data anywhere, nor let it fall into the hands of anyone else who would.
I’ve been emailed several tempting cash offers from shady people who presumably want to steal everyone’s data or worse. I sometimes wish I had never put my name on it so I could just take the money without harming my reputation, but I did, so I’m stuck with being honourable. On the plus side I will always be able to say that I never sold out.
> I am no longer developing JSON Formatter as an open source project. I'm moving to a closed-source, commercial model in order to build a more comprehensive API-browsing tool with premium features.
> I sometimes wish I had never put my name on it so I could just take the money without harming my reputation, but I did, so I’m stuck with being honourable.
This distills down to: "I don't want to be honourable." They signaled right from the beginning.
Well, all the big tech corps done the same. Nothing to see here. OSS needs proper funding infrastructure. Which all the big players shit on. So, I can't judge him on that. His work, his time.
I’ve made quite popular FOSS dev tools and FOSS gaming companion tools. I don’t nag for donations in any case. Rather ironically, I found that dev tools generated close to zero donations while gaming companion tools generated decent donations (still nowhere close to time I put in if I go by consulting rate, but that wasn’t the goal). Devs just take other devs’ free work for granted. And bitch the most when you try to make money off free work too (not that I ever added or will add ads to any of my hobby work).
Exactly. The cultists are the loudest and at the same time wonder why Linux UI/UX and its apps is still subpar and why MacOS, where asking money for stuff is normal, has quite decent tooling that make your life much easier.
At the end of the day the small amounts are the real thank you and biggest driver for the work you put into something.
> At the end of the day the small amounts are the real thank you and biggest driver for the work you put into something.
I wouldn't say it's the biggest driver but it did have an unexpectedly big effect.
Once upon a time, I decided to set up sponsorship on my GitHub repositories just because I had nothing to lose by doing so. Went about doing my thing, then someone posted it here and suddenly I had a sponsor.
It's not even close to paying my bills, and looking up the top projects in sponsorship revenue quickly disabused me of any notions of sponsored full time work. It still felt really nice that someone out there cared enough about my work to send me money.
Not sure about the Recife protocol, but it's pretty much accepted now that the Milwaukee protocol doesn't work[1][2] - the initial case may have been some other encephalitis mimicking rabies.
Since you cannot forge the CF-Worker header in API requests (this header is added by Cloudflare's back end), it is not possible to send email for any domain that hasn't been locked down to your specific Worker.
I understand where you're coming from here, but the whole point of this article is at the 4-line solution is wrong (and the author specifically mentioned that every other answer on the stack overflow post was wrong in the same way as well). "Seemingly-simple problem where every naïve solution contains a subtle bug" is exactly the right use case for a well-designed library method.
But in a completely benign way. I question why a few edge cases of writing 1000kb instead of 1Mb—so not even a misrepresentation—would ever be worth the code bloat. This is about making stuff slightly more convenient to read.
I agree with you— that was a lot of drumming for what turned out to be kind of a nothingburger as far as the "bug".
At the same time, putting this kind of thing in a library (or even a language's stdlib) is worthwhile for exactly this kind of reason— it allows devs to confidently reach for code that other smart people have really agonized over and which definitely covers the corner cases, similar to other common utilities such as sort methods.
One example: I display available memory in my status bar, which expects strings to be a constant width. If it displayed 1000kb, it would cause alignment issues and annoy the heck out of me
Yeah, copying an incorrect answer from SO thousands of times is much better!
(The subject at hand isn't whether libraries are good or not, it's whether copying something off the internet is. In the post, it turns out it isn't. If it was a library, the author could have fixed and updated the library, and the issue would be fixed for everyone that uses it. left-pad isn't an issue with libraries per se, it's an issue with library management)
I'm hoping the changes will improve latency. I really liked neko, and wanted to use it for hosting watching parties with friends. For testing, I ran neko on a beefy EC2 instance to totally eliminate the chance that my CPU was making it run slowly, but it was still unacceptably laggy for streaming videos.
> Do you have any information about the environment in which a card was used?
That would be even more true for cards owned by non-miners; most miners will operate at a large enough scale to use some best practices, which definitely isn't true about most people who buy GPUs for personal use.
> FWIW, and since a few of you probably use it… I own the JSON Formatter extension [0], which I created and open-sourced 12 years ago and have maintained [1] ever since, with 2 million users today. And I solemnly swear that I will never add any code that sends any data anywhere, nor let it fall into the hands of anyone else who would. I’ve been emailed several tempting cash offers from shady people who presumably want to steal everyone’s data or worse. I sometimes wish I had never put my name on it so I could just take the money without harming my reputation, but I did, so I’m stuck with being honourable. On the plus side I will always be able to say that I never sold out.
https://news.ycombinator.com/item?id=37067908
reply