> A single tool to replace pip, pip-tools, pipx, poetry, pyenv, twine, virtualenv, and more.

> A 2023 survey conducted by Payroll.org highlighted that 78% of Americans live paycheck to paycheck, a 6% increase from the previous year. In other words, more than three-quarters of Americans struggle to save or invest after paying for their monthly expenses.

> Similarly, a 2023 Forbes Advisor survey revealed that nearly 70% of respondents either identified as living paycheck to paycheck (40%) or—even more concerning—reported that their income doesn’t even cover their standard expenses (29%).

https://www.forbes.com/advisor/banking/living-paycheck-to-pa...

> A 2023 survey conducted by Payroll.org highlighted that 78% of Americans live paycheck to paycheck, a 6% increase from the previous year. In other words, more than three-quarters of Americans struggle to save or invest after paying for their monthly expenses.

> Similarly, a 2023 Forbes Advisor survey revealed that nearly 70% of respondents either identified as living paycheck to paycheck (40%) or—even more concerning—reported that their income doesn’t even cover their standard expenses (29%).

https://www.forbes.com/advisor/banking/living-paycheck-to-pa...

But it looks to me there's no integration test in the process at all. They're effectively unit testing the interpreter (template type), unit testing (validating) the "code" (template instance), but their testing strategy never actually runs the code on the interpreter (or, executes the template instance against the template type).

But it's not necessarily `b` that's problematic:

- it may be `a` because it does a lot of stuff on its own, and depending on what `a` is, it might not be expected

- it could be `d` if it's supposed to be super fast (e.g. a logging method)

- it could be `c` because it takes a long time

- it could be `b` if `c` is external code or if calling `c` from `b` is not appropriate for what `b` does

- it might be nothing because there's nothing to optimize anymore, things just take this long

in fact, `b` is the last method I'd look at here

I find that usually if someone says "why don't X _just_ do Y", they haven't really considered what it takes to _just do Y_. Similarly,

> I know the UI/UX isn't the best, but that could probably be fixed pretty easily

could be expanded into 50 points of why exactly it wouldn't be _pretty easy_ to to "fix IRC UI/UX".

Honestly I don't know what answer OP expected here. If it's easy to set up/maintain Slack alternative based on IRC, with fixed UI/UX and appropriate for _most companies_, they should simply start a Slack competition for half the price and rake the profits, I guess

So every major OS update is larger and more complex, so it's to be expected that after ~4 of those my machine lags when doing literally everything? It's not that I'm running tons of background apps, it's a powerful machine lagging on a clean install of a recent macOS version when doing basic operations like opening a webpage.

> My 2021 MacBook Pro 14" is still lightning-fast though, I never wait for anything.

I suppose it's Apple Silicon? Because that would still be in line with Intel-based macs becoming less performant over time

So I don't know if older macs are intentionally crippled or they're just ignored during QA, but I don't believe they're actually intentionally supported

[1] https://apilevels.com/ [2] https://www.composables.com/tools/distribution-chart

Android linter does check that access to APIs added in newer versions is gated behind a version check, for example. But frankly I feel like compatibility with any Android version less than 4 (or even 5) is in practice a non-issue, simply because there are no users with such ancient Android. And the few that would use such devices are so far and between that any issues don't surface

IME biggest dependencies are not compat libraries or _typical_ dependencies that Android apps need (like image loaders), but anything that involves native code. Media capabilities is one thing, but also solutions for analytics/user monitoring/SDKs for integration with Important Companies are more often than not _massive_, and companies like to track the user from many angles ¯\_(ツ)_/¯