Every gram of body weight needs energy to stay alive. If you are in a caloric deficit, you will lose weight until your energy expenditure matches the caloric intake.
If you stay in "caloric deficit" forever you will actually starve by definition.
Properly defining what you mean (comparatively low caloric intake without defining it via the current weight) is actually quite tricky, as your height, body composition and physical activities are all inputs to what counts as a "normal" caloric intake.
Since we're selling them the disease and the cure, and society has to pay for both
What about all the other way to solve the problems and improve their lives? It's like people who think you cure depression by lifelong antidepressant treatment...
Vertical tabs are only better because there is more horizontally space on a as screen and listing things vertical allows you to both gauge the list size and keep a mental reference of what slot a tab was. And those tab headers don’t move because of resizing when the width fills up.
But horizontal tabs are still better. Not technically better or ascetically better. Some other immeasurable, indescribable better.
I'm with ya at 29.4. I carry a lot more muscle than the average populace, so I'm both high BMI and appear to be "fit" to casual onlookers. But dexa says 26% which is about double what I would like.
Python’s backward compatibility story still isn’t great compared to things like the Go 1.x compatibility promise, and languages with formal specs like JS and C.
The Python devs still make breaking changes, they’ve just learned not to update the major version number when they do so.
Indeed, Python's version format is semver but it's just aesthetics, they remove stuff in most (every?) minor version. Just yesterday I wasted hours trying to figure out a bug before realizing my colleague hadn't read the patch notes.
I would argue that the libraries, and specifically NumPy, are the reason Python is still in the picture today.
It will be interesting to see, moving forward, what languages survive. A 15% perf increase seems nice, until you realize that you get a 10x increase porting to Rust (and the AI does it for you).
Maybe library use/popularity is somewhat related to backwards compatibility.
Python it's a language that really good libraries for different domains. like web: django/flask AI numpy pytorch and more. All the ecosystem for scripting and being already installed in most linux distros and on macs. For GUI it has really good bindings for the major frameworks QT,GTK.
Python does not take backwards compatibility very seriously at all. Take a look at all the deprecated APIs.
I would say it's probably worth it to clean up all the junk that Python has accumulated... But it's definitely not very high up the list of languages in terms of backwards compatibility. In fact I'm struggling to think of other languages that are worse. Typescript probably? Certainly Go, C++ and Rust are significantly better.
Python does not take backwards compatibility seriously. 2 to 3 is a big compatibility break. But things like `map(None, seq1, seq2)` also broke; such deliberate compatibility break is motivated by no more than aesthetic purity.
It's very clear that the consumer is getting a worse experience than what is technically possible. There is no good phone-slash-laptop, purely because it's less profitable than locking down the devices and selling them separately.
I used it for years with a Nexdock. I just don't really use a phone anymore (mostly Daylight computer, where attaching a keyboard and most mostly gets me what I want).
reply