it does provide rotational stability (along with the PCL, between the femur and tibia; the condyles help here too) but it’s primarily job is lateral stability in the front-to-back direction, because without that, you cannot negotiate uneven terrain at all. this is vividly illustrated in a dissection by manipulating the knee with and without cutting the ACL. with no ACL, the knee is a wobbly mess, especially in the front to back (ventral-dorsal) direction.
ACL injuries have long been known to be worse in women because of anatomical differences in weight distribution relative to hip to femur to tibia angles, both statically but especially in motion.
it's less about what foods to eat and more about eating much less: one modest-sized meal a day. that's all we "need". we eat too much of everything and our bodies are not evolved for such excess. this is literally the biggest bang for buck for chronic diseases like this, but also the hardest thing to do because of socio-cultural considerations. it also takes some time to train your digestive system down to that level.
once you have amounts under control, then you can taper off the processed foods, especially sugary things like soda/juice (fruit is ok because it comes with fiber), salty things like chips/frozen dinners, and bread/rice products (a little whole grain here and there is ok). minimize processed foods but don't worry too much about the mix of foods otherwise (protein/fat is fine, just don't overeat).
then taper up anaerobic exercise to 2-3 times a week. find a sport or activity you like (e.g., tennis) and pay for an organized league/class so that you stay committed. (aerobic) walking, for instance, is not typically strenuous enough for your body to process the excess nutrients and improve cardiovascular fitness, which is what's needed to help keep heart disease under control. you can start with walking if you're in bad shape, but you'll want to graduate to anaerobic exercise as soon as you can.
no one should worry about CO₂ at all in their homes or offices. only workers in certain industries/factories, where CO₂ can get several orders of magnitude higher, need to be concerned at all about it. you (here and in your marketing materials) are stoking needless anxiety over a gas that life on earth literally requires.
pollutants, on the other hand, and particularly particulate matter (especially chemicals that we've manufactured recently in human history), do have proven negative health consequences and should be monitored and mitigated in the home and office. it's estimated that over a million people a year die prematurely of respiratory and cardiovascular complications due to pollution.
in short, a lack of CO₂ monitoring in favor of PM and VOCs by ikea should be seen as a plus, not a minus here.
now that physical branches are not really a differentiator of big banks, a couple hours of your time spread out over a couple months is totally worth the switch to a credit union in lower fees, better service, and supporting a more local economy.
it's completely, undeniably worth it. unless you're a real big shot (worth millions in assets to the bank) who doesn't have to deal with the dehumanizing aspects of corporate "customer service", there is zero reason to be with anything other than a small local bank/credit union.
i've played with nesting on firefox and, much like the :has() selector, it seems good enough for the 80% case, so i wish they'd unflag it so we could get the clock started on having it be commonplace in a year or two to use it confidently.
safari and chrome have had :has() for a while, but it's behind a flag in firefox. the firefox version is good enough that i wish they'd unflag it already (as in, it's good enough to handle this particular input/label issue for instance, but not really complex selector combinations and edge cases).
real world boston was the only reality tv show i watched more or less all the way through. it was fun while it lasted but once it was over, reality tv felt "done" and i didn't really want to watch much more of it. i still don't understand the lasting appeal tbh.
again, CO₂ doesn't matter, despite the mediopolitical hysteria over it. it's a gas that life depends on and is well-adapted to. but pollution has been killing millions of people a year for at least a hundred years already and will continue to do so for the foreseeable future. generation and transportation account for the majority of that pollution.
instead you get to breathe in that sweet, sweet tire dust, which hybrids and EVs tend to make more of because they're typically heavier than their ICE counterparts.
but until the electrical grid is moved to cleaner sources (including nuclear for baseload), it doesn't make much difference what you drive. with the current distribution of generation, we'd be mostly shifting the pollution from tailpipes to smokestacks (especially at the margin) rather than getting rid of it--coal emissions are many times worse than tailpipe emissions, not to mention the pollution from coal, oil & gas extraction.
and pollution is exactly what we should be worried about, not CO₂, which is the worst sort of distraction when trying to make sense of the environmental dangers we're creating (it muddies the waters to create uncertainty and inaction).
that's an astute observation. i think the current administration designed this legislation for maximum airtime by trying to go all-in on debt forgiveness, without any conviction about whether it could actually withstand challenge.
if they were interested in actually helping the disadvantaged, then there are plenty of workarounds, like forgiving the interest and fees on student loans rather than forgiving principal. this would be more impervious to the idea that the executive branch was trying to wholesale rewrite legislation, rather than tweaking it on the margin, which was part of the court's rationale in this case.
you've done a great job on the overall UI/UX, but as always, for me the question is where and how the product fits in the overall marketplace. this is true even for free/open source products, as it's hard to maintain momentum on stuff no one else really notices or uses.
is there a pain for managing content for technical writers? yes, probably. not many products target this niche. is the pain big enough to overcome inertia? that seems questionable, but perhaps it is big enough. i doubt large businesses would even look at a fledgling product like this, as it doesn't solve enough pain for them. it seems that there might be a market in small-to-medium-sized technical businesses that have like 1 technical writer and a few guest postings to use a platform like this.
but does it make sense to target developers at all? perhaps for initial marketing, but i'd conjecture that devs mainly just want to get something out on one platform (whether their own blog, or dev.to, or whatever) and perhaps secondarily on twitter (or similar) for more reach and discussion. it seems to be an uphill battle to get them to switch over to a completely different tool that requires integration to get content flowing to all the right places (which is what a headless cms requires).
in any case, the positioning as a headless CMS falls flat to me. that seems to be leading with a technical detail ("headless") rather than the pain and the solution. my off-the-cuff suggestion is something more like "Content Automation" as the descriptor. similar to "Marketing Automation" (e.g., buffer, hubspot) yours is a CMS plus and an automation platform (in the making). it helps people crank out technical content and put it in all the right places to be seen by the people you want to target.
i don't have rigorous data at hand, but browsers and mobile hardware are now good enough that most apps are just fine being developed using cross-platform web tech rather than java or swift. plus, apps no longer attract and retain users as they once did (we're past the hype cycle). native mobile, as a result, has retreated to domains where the tighter integration has benefits, like games, health, IoT, etc. even apple is loosening its iron grip over its app store as the tradeoff between integration and flexibility no longer makes sense for most apps. apple now focuses more on content and on integrating more functionality into iOS itself because of that.
not sure what point you're making here, but my point was that there is room for little PE, but not big PE, because little PE can have the effect of making capital more efficient for the overall economy. it's the same with arbitrage--a little arbitrage is good for the economy, but large, systemic arbitrage is extractive for no overall benefit.
the principal-agent problem emerges in any business where professional managers are employed (which usually happens when a business gets too big for its britches), so it's not PE-specific.
to be clear, PE isn't always purely extractive, but when it is, it can be highly destructive. sometimes a business is so mismanaged that debt (and the pressure it adds) and new management is all that is needed to right the ship.
PE itself is a bloated industry because we have too much money being extracted out of the real economy going into the pockets of the already wealthy who don't know what to do with it, so they hand it to a money manager (i.e., PE) to make more money for them, not knowing what to do with those potential future earnings either. this is the kind of economic inefficiency that concentrations of capital brings, in direct refutation of the common economic argument that the wealthy are better at investing money (i.e., more capital efficient, which in turn supposedly adds more real productivity to the economy).
small, local amounts of wealth are more capital efficient, but large, distant amounts are not.
thanks for that tip, i have PYREX measuring cups bought over 20 years ago that are still going strong, but this is good to know if i ever need to replace them with the same quality product.
i think if rails continues to push hotwire (turbo + stimulus, and perhaps strada?) and get a coherent story on view components, it will continue to take mindshare from the js hype of the last decade. mobile dev is in decline, and browser makers just released web notifications, web app support, webtransport, page transitions, etc., so the backend has largely reached parity for cross-platform development. no longer is json the natural data exchange medium for apps, but rather chucks of html that can be plopped right into the dom without js having to massage the response into shape on the frontend. js can return to being a frontend scripting language, its natural habitat, rather than being shoehorned into being a do-it-all platform language.
spacex, as far as i can tell, is a research company that launches satellites to fuel its space exploration research. the research side couldn't stand alone, as that's not a viable business in itself, so the satellite business is really the core "business" here. the making of rocket engines could possibly be outsourced (or turned into a separate business), but those customized engines are integral to its competitive advantage in more efficiently sending satellites into space than its competitors (and in sending people to colonize mars, its long-term mission). core competencies like that aren't separate businesses; they're the business itself. if spacex decided to write its own accounting software and then sell it to others, then you'd have a breach of the single business focus.
apple, however, is in something like a dozen different businesses that are completely viable as stand-alone entities that don't gain much from being consolidated (brand value, for instance, can be franchised if a unified brand face is desired, like mcdonald's does). incidentally, apple wasn't a hardware company that morphed into software, but rather, it was always a computer marketing business (then more broadly consumer electronics, and now encroaching upon consumer entertainment). nest is a good example of what a spin-out company in an apple breakup might look like.
of course, but i'd argue that too much of a single field is usually a case of a company that's actually in multiple businesses (see the mcdonald's example in a sibling thread).
my simplified perspective is a melding of the brandeisian (big is bad) and the chicago schools (economic efficiency for the win!), touched on in the article, so i certainly have no problems with synthesis in matters of antitrust. =)
ACL injuries have long been known to be worse in women because of anatomical differences in weight distribution relative to hip to femur to tibia angles, both statically but especially in motion.