I hope they lose so that the wishes and legal rights of the people who made GitHub great in the first place remain respected.
GitHub is almost like a social network in the way it relies on "the community". Stealing people's code (who made it great) by regurgitating it through an ML code laundering machine, isn't very fair imho.
ah yes, copy 'n pasting (or the ML equivalant) is truly learning.
You can learn from code by just looking at it, working with it (i.e. transforming it into a truly derivative/creative work) there's little value to be had in having some automated program spit out chunks of code (ripped from their original context) that you don't fully understand or without the tool never could have conceived.
Also looking at some publicly available code (to learn) still respects the license, co-pilot possibly doesn't.
But Microsoft isn't being sued to stop copilot (which is trash really) it's to stop further development and an AI which will be to programmers what AlphaGo was to human players.
The workforce in the industry is desperate for a way to slow AI down (every industry workforce) and they found a way to try.
Sounds like you might like: https://sourcehut.org
(it's also completely free of crypto/web3 schemes, as an added bonus)
If GitHub (M$) continues this path of stomping on licenses/copyright of the people who made it great in the first place (i.e repo authors/contributors), I'm definitely gone.
There's probably an additional layer of substantial selection bias here. But maybe that explains the effect in the first place, greybeard Tcl users possibly didn't bother to take the survey while Clojure and Rust evangelists did.
Honestly none of them will be daily driver ready, given how broken the Quectel EG25 modem is.
I would never want to, have to call emergency services with my Pinephone while the modem is down
It appears top be a luck of the draw in either case.
For me the Quectel firmware was very stable whereas the OSS firmware wasn't. "Stable" as in it would periodically crash, but would come back on its own within a minute. The OSS firmware would also crash but would usually not come back until a reboot.
This was with v0.5.5 IIRC. It seems to have gotten better since the 0.6.x versions of the OSS firmware.
Really the bigger reason to switch to the OSS firmware is that there's a privilege escalation vulnerability in the Quectel firmware that IIRC they still haven't fixed. In any case even if they fixed it in a new firmware release you wouldn't hear about it to know you should install it, whereas the OSS firmware is now being distributed through fwupd so it could be almost as mindless as updating your distro.
It‘s not just the Modem Firmware, it’s also how the distribution manages the modem. I am mostly using DanctNIX (Arch Linux ARM) to test apps for [0], but also have postmarketOS stable installed (on eMMC) as a backup for when I need "phone things" to just work - postmarketOS stable is very good at that.
I no longer use the Pinephone because of the aforementioned issues, however at that time, I'm pretty sure I was at the latest and greatest firmware version available (which one that specifically was opensource or proprietary, I can't remember).
The experience was so horrid, I just quit using it all together and never looked back. But maybe if things have improved, I should give it a shot again.
What exactly went wrong in your experience when you tried out the PinePhone? Did the modem randomly die without you doing anything? Or under high load it gave out sometimes? Some more details would be wonderful.
Maybe you could share if you tried it with the normal PinePhone or the PinePhone Pro as well.
I have only tried the regular PinePhone (since I only own that version) they both share the same modem (iirc), so there shouldn't be much of a difference.
> "Did the modem randomly die without you doing anything"
Yep
> "Or under high load it gave out sometimes?"
No, it would be just idling/sleeping and it would crash on me. It's not like it would automatically restart itself either. It was just dead until I rebooted the phone (which is slooowwww), restarting the modem manager and the modem it self, didn't fix it reliably for me either, only sometimes that would actually work, that whole process of restarting the modem and reentering your PIN could easily take multiple minutes.
Under load (e.g. Firefox) it would just have the same (crashing) behavior.
I have had more missed phone calls because of it, than I'd like to count.
It has kinda always baffled me, why some people think web scraping wouldn't/shouldn't be legal.
I mean the second you put something out on the internet, you should expect it to be public, and as a consequence of that, to be scraped.
Well, I can think of at least a few possible reasons. Not claiming those are right at all, but I do think they are the reasons why some people think/thought that scraping could be illegal.
1. It's hard to distinguish scrapers from DoS attackers, which we do expect to be illegal.
2. Depending on the use of the data after scraping, and the nature of the data being scraped, you may expect copyright laws and things like the GDPR to prevent any possible use of the data, so the very collection of it may be suspect.
3. Even for public data, a site may have Terms of Service that don't permit scraping, and some may expect to be able to enforce these
GitHub is almost like a social network in the way it relies on "the community". Stealing people's code (who made it great) by regurgitating it through an ML code laundering machine, isn't very fair imho.