The way I do it, patches are backward-compatible bug fixes. Minor versions are additional features that don’t change existing functionality. Major versions include breaking changes. I totally get that it seems crazy to bump to another major version just over a string format change. But overall the philosophy works well IMO.
IMO it doesn’t really matter what you said the method was for. If you change the format of a string that is returned by a method that returns a string, there’s a risk of breaking user code, even if it’s just in the context of their dev environment.
Philosophically, whether or not the behavior of your API has changed is completely disconnected from whether or not others are using it “right”. If I can depend on a function to return a certain type of value when given certain arguments, and if it doesn’t produce other side effects, then it doesn’t matter what the docs say or what the function is named, I can use it in any context where I need that type of return value and have this type of arguments available. This type of function is just mapping data to other data. If you modify the function in such a way that the return value changes after being given the same arguments, that’s a breaking change in my book.
This sounds terrible. My daughter recently got an autism diagnosis which we’ve been able to use to help get her better accommodations in school. Would you mind clueing me in to some of this abusive therapy stuff so that I can recognize it if she ends up in a situation like that?
AI will bring new jobs
I would not be surprised at all if “LLM Prompt Engineer” becomes an official job title in the near future.
Is “to x” a verb now as well? I assume that’s the idea. “Today I was xing about Lemmy.” “I’m gonna x that.”
This is immensely sad because now future generations will not be able to fully appreciate the highly nuanced and layered joke in Moana where Maui says “When you use a bird to write, it’s called tweeting.”
I think fundamentally most people would agree with that. The problem with communism though is that it’s not just a staple of the USSR. There is something on the order of 48 countries that have experienced state-sponsored communism in relatively recent times and it has never once succeeded in achieving these goals but tends to exacerbate poverty, class division, and government oppression of human rights, if not resulting in completely failed states.
Some will read this and assume I am advocating for capitalism. I am not. Asserting problems with communism does not imply capitalism is perfect or even good. But if we do choose to abandon capitalism, the wrong decision is to move to a system with a 100% failure rate of achieving its goals over dozens of historical attempts. As the meme suggests, many Eastern Europeans are old enough to have personal experience with those failures.
Where communism can work well is on a smaller, voluntary scale. When people choose to get together and establish their own rules for pooling resources, small communities can sometimes live quite satisfactorily this way. But no, if we are willing to call capitalism a failure based on its history we have to be honest enough to say the same thing about state-sponsored communism.
Haha, makes sense. For me, I just learned to accept it.
I got my diagnosis as a teenager. I am now in my 30s. To this day I continue to have realizations about how I’m not actually just a lazier piece of crap than everyone else around me.
That one in the middle is sick
As a developer who specializes in frontend and specifically JavaScript, there is no justification for that book being that long.
Yeah it’s interesting because JS is interpreted, not compiled. The proposal allows for type annotations in the syntax but no actual interpreter consequences. On the one hand that makes sense because otherwise you’re in the territory of runtime type-checking which would be a huge performance hit and would sort of defeat the purpose of static types anyway. But that means you still have to rely on your IDE or a linter for this to be useful.