At risk of by chance being somehow miraculously reached? The climate goals will soon be as dead as the polar bears.

That’s when you set the intern’s IDE to preserve the line endings.

It’s not about feeling better. It’s about getting the other person to understand that Google exists and that they can use it, too. Too many people refuse to put in any effort of their own and go ask someone instead.

IMHO in that situation answering isn’t even the right thing to do, since it encourages that behaviour and prevents the asker from learning to find out stuff for themselves. Something about fishing for hungry people or so…

When someone is genuinely stuck, doing research themselves allows the answerer not to go down the same dead ends, which saves time for both.

You cannot even mark it as duplicate without providing a link to the answer. What are you talking about?

Peple misunderstand “Closed as duplicate” as an insult, when it’s just the hint to look at the provided link. If you didn’t find the answer previously, this just means there are multiple ways to express the problem, which use different words and thus don’t all find the same google result.

Sure you can write foo = 3 in JavaScript. It’s a global variable and can be referenced as either foo or window.foo.

I consider myself climate-conscious, but I’m also a JavaScript developer and have recently got access to Copilot. Thanks for confirming my hunch that all that isn’t great for the climate.

The fines are only proportional for big corporations. Organizations without revenue can still be fined:

Infringements of the following provisions shall, in accordance with paragraph 2, be subject to administrative fines up to 20 000 000 EUR, or in the case of an undertaking, up to 4 % of the total worldwide annual turnover of the preceding financial year, whichever is higher: (a) the basic principles for processing, […] pursuant to Articles […] 7 […];

https://gdpr-info.eu/art-83-gdpr/

In this case, the processing of data hinges upon the data subject’s consent, which is detailed in article 7.

Also, this is not an issue for the developers, but for the admins.

Imagine a car manufacturer building cars without brakes and then saying ‘This isn’t a problem for the engineers, but for the retailers’. Of course the developers can’t be sued for this. But that’s not the point! The point is that this bug or missing feature or whatever you want to call it jeopardizes the admins upon which this whole ecosystem hinges. I can’t believe that that’s in the devs’ best interests.

To be fair, this is a bug that could be the end of lemmy. As soon as one malicious actor sues even a few instance admins, other will get scared and shut down their instances. As the reporter points out, this isn’t just a shiny feature that’s missing. Instance admins lack the ability to follow data protection requirements that their users have a right to. It’s a lawsuit waiting to happen.

I agree commenting that post under every issue was a dick move.

maximising profit is not why we grant them copyright

That’s the only reason copyright exists. Because society decided that if you’re the one to put work into developing something, you should be the one reaping the profits, at least for some time.

I found it interesting how the maintainers reacted to these issues.

Would you mind if we set some of your priorities also? You’re asking us to do free labor for you, that you’re unwilling to do yourself. Do not put ultimatums and demands on people making FOSS, or I won’t hesitate to block you from these repos.

https://github.com/LemmyNet/lemmy/issues/4433#issuecomment-1939275302

Has git never told you that you should use git push -u origin <branch> when you push a new branch for the first time?

But when you do need the comments, you usually really need those comments.

It’s nice to see you sharing my experience. My code is either uncommented or very severely commented with comment-to-code ratios of 10:1 or more. I hate the files that are soo green… :(

If it’s not in the git log, it’s not a comment.”

This is so incredibly dumb, though I’m sure I don’t have to tell you this. That comment will be buried in the git log if anyone ever fixes a typo on that line.

Personal repositories aren’t production code. They’re learning opportunities. You tried adding 100 engines to a plane and learned that that was a bad idea. Who cares if there’s no cockpit if you were test-driving the wings?

It remembers the last input and defaults there.

It never occurred to me that TVs might not do that.

You’re making the claim that mp3 is unsupported while I listen to mp3s on my smartphone, my linux laptop and my MS laptop without issues, my friend.

I am a sky-high developer and know little of such low-level APIs. Please humor my ignorance: Isn’t it bad practice to write a god-method that sometimes uses these parameters, sometimes others? Isn’t this better refactored into multiple dedicated functions?

I found out a long time ago that I can’t hear the difference between compression levels starting at 192kbps. So there really isn’t any use for lossless for me.