MintsJohn

I don't think it's just genetics, or genetics are rapidly changing in the last 100 years.

Personally I think it's some combination of gut biome, all than not messed up childhood eating habits (I've been taught to eat till stuffed, not so great in combination with my next point) , and way too calorie heavy (processed) food (it's not a challenge to find food where a quarter package is a healthy amount, way more challenging to find food where they food for a full package) not too mention it's made to keep you eating (so more is sold, sigh) . I'm always surprised people claiming not to have cravings whatever (even when the stuff is put in front of them), or be satiated by eating what for me is half a meal (even when I maintained a normal weight) .

Regardless eat less and try harder are hard to keep up, for me personally protein doesn't help to satiate me either. Part of it is that (for me) it's much easier to get into a habit to eat too much than to keep up the habit of eating just enough (I dare say 2+ years of keeping it low is a habit, but now for 3 wars annually 5kg was added: next try keto, hope it works as well as advertised)

Needed computing power seems a good enough reason to limit it. But I agree it looks too good to be true, only real use will show how well it really works.

Stop spreading nonsense, NATO (planning on) arming Ukraine with nukes is Russian propaganda, not happening, never happening, very much not the reasob for the Russian invasion

Unlike NFTs there is at least a (physical) product.

(And even in the digital version, you have a limited digital item in a verified/trusted (digital) environment, backed/supervised by an entity (company). In crypto you're backed by a concept (an algorithm))

To me this whole crypto stuff seems like a bigger and better incarnation of the tulip mania (https://en.m.wikipedia.org/wiki/Tulip_mania), very little crypto stuff /coins are backed by anything of intrinsic value. In a way it's the ultimate decadence.

One part strikes me as odd, as it come across as a new problem, while for me it seems the core problem since the epidemic started: “Hospitals have already been transferring patients to different hospitals, diverting new patients, and sending patients out of state to Georgia. And many hospitals are delaying surgeries, like knee and hip replacements and even cancer-related surgeries.“

In my country (the Netherlands) that unfortunately has been the norm since covid struck. The backlog in surgeries (all said the be of the non urgent category, meanwhile there are less cancer diagnosis than ever before...) is enormous by now, estimates are it'll take till the end of 2022 catch up, of course, that's assuming the backlog won't increase while medical personnel gets exhausted and new covid patients need ICU care as well. Since covid started it feels this effect has been underestimated by the public and is too uncomfortable for the government to discus too much

That was my thought as well, when driving in city like environments, its always the cyclists on the right I need to be careful about, traffic I have to cross on the left is clearly visible, the cyclists on the right hide in a blind spot.

Don't sweat it, in hindsight the tool just isn't for me (though it was great while it suited my needs). I'm affraid one reason for these issues is that parcel tries to do everything at once with as little configuration as possible. When it works: great. When it doesn't: not-so-great.

Sure the out of date dependancies thing could be seen as a problem with post-css plugins that require a newer version, but the unfortunate fact is that in webdev land, everything seems to evolve at a breakneck pace, foregoing backwards compatability. And when some part doesn't match, the buildtool suddenly becomes unusable. (webpack is way less easy to setup, the flipside is you can for example choose your postcss version)

Could be nice but I'll be avoiding parcel like the plague after being confronted by its complete lack of maintenance of parcel v1 while v2 is in beta, and not the working kind of beta, the broken kind, while the solution to old problems is "use parcel 2" (https://github.com/parcel-bundler/parcel/issues/5695 https://github.com/parcel-bundler/parcel/issues/5294) . In the end I replaced parcel with webpack, less sexy but it's kind of the standard.

I see the obesity epidemic, notice some brave souls fighting it, but I'm almost sure it'll go from bad to worse. Like many things, humans psyche works against us (or is easily used to trigger us to buy now more more), it isn't meant to deal with an overabundance of bad but delicious foods. As long as it is in the economic interests of the food supply chain to sell more, no awareness campaign no matter how good can stop people from eating the bad stuff that's so readily accessible. Only solution I see is a near ban on the bad stuff, enormous taxes, but I don't see that happening, first because of the industry lobby second because people will see it as too much interference in their lives. In a day and age where individualism and liberatism seem to become core values that's just not gonna happen. So we'll get some awareness campaigns, get some red stickers on a select few products, and in 20 years we'll think every fit person is an athlete.

I tried stadia, didn't convince me at all, it was rather a let down. The most jarring was the sound, it stuttered. The video was fluent enough, but seemed horribly compressed (washed out and artifacts) and low res (but I have a 4k monitor). Yet when I hear others talk about it its nearly the same as running a game local, or even better when, like me, you don't have the latest and greatest videocard. I suppose the bottleneck was my Internet connection, a "lowly" 30 Mbps, but then again, it's good enough for everything else, and the stadia test thingy said I should expect a high quality experience.

Webdev truly is one of a kind. Not only do you have your source code, you also have your build code, oddly dictating the organization of your source code. For extra fun, some libraries don't build with build system a, others require build system b, when you're lucky enough to have a working mix, changing build systems is better to be avoided. Of course periodically the officially blessed build system for your used libraries changes.

The webdev ecosystem is so broken, it's no wonder so many websites deliver assets that are extremely suboptimally optimised, big unused blobs of assets /scripts slowing page load, optimising it all is actually made harder than coding it all.

I feel the biggest problem is most of this happened before there was awareness. This isn't something an individual can stop anymore, it needs an collective massive effort to stop, blocking ads or trackers is only fighting the symptoms not the cause. So we need these practices to not happen, somehow. Legalisation is the obvious answer and there lies the problem, this is one thing where technological advancements fast outpaced legislation, and it doesn't help that big tech generally goes the way of practicing questionable or even illegal methods simply waiting to be called upon, then get away with empty promises, operating internationally they've gotten too powerful for a single government to deal with. So we need intenternational governmental cooperation in an field where those same governments benefit from this data, good luck with that. (is love to have a purely technical solution like blocking ads to work, but the problem isn't a technical one)

I tried D some years ago, my naive program crashed as it wasn't memory safe. Being used to scala this was a surprising to me, I expected "if it compiles it works" but it turns out I had to take lifetimes into account just like c/c++. Rust has this "if it compiles it works" + quality.

Then I needed to create a program that would work both on android and Windows. Still liking D's syntax better funding rust rather verbose I decided to give it another try, but failed, I had to jump through too many hoops to make it produce a library usable on android. While with rust the experience was effortless.

After both experiences with D, I never looked back to it and rust is now my go to low level system language, the verboseness (with lifetimes and types) has grown on me.

It's not at all baffling seeing the recent history of firefox dealing with extensions.

Back in the day, when xul extensions were the way to go, things were great, for years the api was reasonably stable.

Then xul extensions were to be replaced by things created by the addon-sdk. To make things more interesting the addon sdk used a python based tool first, later to be replaced by node-js tooling. So (minor)rewrite needed, even though legacy xul extensions still worked as well.. But not for long, noo, for no good reason (because there was already talk of webextensions in firefox), extensions suddenly had to be signed and often MANUALLY reviewed, xul no longer allowed, perfectly fine extensions would not pass automatic review and would not be manually reviewed for no other reason than using legacy code that was hard to review.

So this meant extensions had to be rewritten to use the addon-sdk and jump through hoops to avoid using javascript libraries that caused the automatic review process to break. This all happened a good year ago.

Now, all these addon-sdk extension have to be rewritten once again, because webextensions.

This whole extension review process for addon-sdk, imho, should never have happened and should simply have been postponed till webextensions are ready (they aren't now, they are buggy as hell, yet currently extensions have to be webextensions in order to be published...). As a matter of fact, the whole addon-sdk should never have happened and mozilla should have moved to webextensions immediately.

To me firefox greatest strength was how moddable it was. Not only is this advantage lost by moving to webextensions, the horrid process from xul to addon-sdk to signing and broken review to webextensions must have cost them much goodwill from extension devs. And yes, it has tainted my view on mozilla, i think they honestly mean well, but they desperately need better management that doesn't jump on any hype laden bandwagon, right now they seem to be pushing out new toys that are watered down half functional versions of what used to available. Google might have a name to abandon their projects, i now have the same level of fate in the continuance of any mozilla project.

Looks neat, but at the same time, really cumbersome. Because it looks neat, I'd guess people will try it, because it will be cumbersome, people will abandon it. So like many of similar fancy ai/recognition apps, i think it's finding a problem for a solution, it's over engineered.

My problem is, taking pictures is more effort than picking an item off a list, as current caloric counters do.

Most people eat roughly the same things on a regular basis, so they'll end up ticking away a meal before/after you have it and be done with it, with this, you'd be taking pictures while having your meal.

another use case is planning a day ahead, again, pics don't work here, can't take pics ahead of time.

And of course, the result from the pics have to be corrected, so the app learns, it seems easier to just get the item from a list immediately, without having to take a pic first, auto completion on an input works wonders (though of course you'd pick from a longer list)

Maybe i'm just old or not enough of a techie, or photographer, but for me typing a short text, even on a phone, is actually faster than taking a pic.