Pretty sure that’s what he gave as punishment for eating of the forbidden tree.

That intro and general structure (AI loves bulleted lists but then again so do I) sure sound like a lot of the responses I’ve gotten. As always, it’s hard to say for sure.

deleted by creator

Business continuity plan testing day.

I wish this wasn’t so true.

LMAO we really have Lemmy cliques?

Plus you have plenty of time to tumble once or twice while your large codebase compiles.

Is there a language that anyone would say really does fare well for continued development or is it just that few people enjoy maintaining code? I’ve maintained some pretty old Go programs I wrote and didn’t mind it at all. I’ve inherited some brand new ones and wanted to rage quit immediately. I’ve also hated my own code too, so it’s not just whether or not I wrote it.

I have found maintainability is vastly more about the abstractions and architecture (modules and cohesive design etc) chosen than it is about the language.

I’m not saying it doesn’t suck for this person, but product market fit is a thing for open source too. If people need it they’ll use it and contribute until something better comes along. If not, your idea wasn’t the one. That doesn’t mean it’s not possible. Nearly my whole life runs on open source software, so it’s pretty clearly sustainable.

over the years, using “open source” has become an excuse to avoid paying for software

Um. Yes. And to be blunt: obviously. And in return, I give away software I create for free whether people need it or not, and try to give back in the form of contributions too. But I’ve never once given up my day job for it. Would that be nice? Maybe. But open source software is more frequently sustained by passionate people using and expanding it for their own projects and not by expecting people to pay you for your efforts when you’re likely not paying (nodejs, github, ahem) for the software you’re building it on anyway.

Can we joke about log4shell? Maybe heartbleed?

Can this power be learned?

Yeah, the image (not mine, but the best I found quickly) kinda shows a rebase+merge as the third image. As the other commenter mentioned, the new commit in the second image is the merge commit that would include any conflict resolutions.

Merge takes two commits and smooshes them together at their current state, and may require one commit to reconcile changes. Rebase takes a whole branch and moves it, as if you started working on it from a more recent base commit, and will ask you to reconcile changes as it replays history.

This is floating point. We also need to know what happens when you escape with -0.

And so many other things. I’ve also used it for “cloud saves” back/forth from my desktop to my steam deck on games that don’t support them for various reasons. Dyson Sphere Program being one, because the files can get quite large.

Or homeassistant. Or gitlab/github actions. So much yaml.

deleted by creator

Fair point. There’s a fine line between programming and creating data that a program operates on. I tend to think writing text to produce nontext output is more programming than not.

But also, you’re making a computer do what you want, and something that it wasn’t programmed by the factory to display, when you write HTML. You’re programming.

Yuzu TwoZu: Electric Boogaloozoo.