HackerTrans
TopNewTrendsCommentsPastAskShowJobs

jbluepolarbear

no profile record

comments

jbluepolarbear
·vor 4 Jahren·discuss
Both Jonathan Blow and Casey Muratori have a history of being toxic and dismissive in their own right. I can’t really fault Microsoft here because of how argumentative and arrogant Casey has acted in the past. And Jonathan should have stayed out of this whole thing.
jbluepolarbear
·vor 4 Jahren·discuss
These are two very different sentiments. The first is buy things for you not to impress. Yours is insulting and it’s like saying “I don’t care about your hobby and I’ll insult you for having one you spend money on.”
jbluepolarbear
·vor 5 Jahren·discuss
This is so true for me, only had yearlies and occasional family events. It’s really cool to be able to look back through the years of pics I’ve taken of my kids.
jbluepolarbear
·vor 5 Jahren·discuss
I’ve been in software a long time and I’ve had to navigate the gpl and it derivatives the entire time. I primarily work in games and I’ve run into a lot of issues with gpl along my career. For most of my career lawyers dictate what is and isn’t acceptable for software licenses and gpl is always the biggest issue. Which gpl license? Is there a single license holder? I feel the gpl was enacted with good intentions, but I feel the wrong people enacted it. Too radical in many ways, too restrictive, and so aggressively enforced that it at least makes using gpl libraries a hard decision.

I think that open source projects, that aren’t gpl, have proved that you can build software and still money from it. Godot, React, Chromium, and Node to name a few. Active development is worth much more than the actual code and encouraging your users to contribute back without the cost of giving away their product has allowed these and similar projects to grow.

I think ID would have had a similar experience had they gone with a different license.
jbluepolarbear
·vor 5 Jahren·discuss
It really bothers me how you gpl assholes think you own everything that touches your shit. Your toxic code has been intertwined so deeply with software and operating systems that it’s a literal minefield. You and people like you have cost countless headaches, lawyer fees, stress because you fee your code needs to be used and contributed to. It’s a fucking narcissistic license.
jbluepolarbear
·vor 5 Jahren·discuss
I know a lot of game developers that have never messed with Id tech because of the license, so what Carmack is saying makes sense. Yes I’ve read the Id tech code that’s been released but I’ve never thought for one second to use the code because of the license.
jbluepolarbear
·vor 5 Jahren·discuss
No you’re smug because you want to own my changes that I made to facilitate my needs. Even worse if you feel my changes aren’t acceptable I’ll have to fork your project and maintain a divergence anyway. So yes GPL is bad and is a poison.
jbluepolarbear
·vor 5 Jahren·discuss
That’s only if their project hasn’t been tainted by other gpl poison contributions. Cause I’d then have to find that person and get a license and so on.
jbluepolarbear
·vor 5 Jahren·discuss
That was the intention on the GPL? To discourage use and sharing code? Because people still share a lot of code, they just choose a better license. I say better because the GPL is bad, it is the worst part of the Linux ecosystem and the worst part of embedded systems tool chains. I’ve contributed to a few open source project, but never a gpl one. Smug programmers like you are the worst part of open source.
jbluepolarbear
·vor 5 Jahren·discuss
You sound like a great person to be around. Why would I pay you to use your foss when I can read it, understand it, improve it, and never even let you know about it because I decided to write my own version instead. Happens all the time because GPL is so restrictive. It’s easier and more cost effective to just rewrite the whole library than use a GPL one.
jbluepolarbear
·vor 5 Jahren·discuss
Regardless on how I feel about this usage, I’d be more concerned with the very real possibility of introducing vulnerabilities this way. Say the copilot takes a snippet from a code base. That snippet had a vulnerability and was fixed by the team that understood the what and how. How does that vulnerability get fixed? Does copilot let the user know months later that snippet used actually is very bad and that the company that originally implemented fixed it and you should too?