I’ll assume you’re asking for Linux; I have tried several ways of blurring the background of Firefox window components with page content in the back without success. It seems they’re rendered in entirely separate contexts, as blur effects don’t apply; nor does any other filter that would combine window and page content.

My use case was to blur the background of collapsible vertical tabs when expanded, and blur the bg of the URL bar dropdown. Changing background opacity works, however.

Wireless devices let me use 2 different tables and an armchair+TV. That would simply not be an option otherwise.

The benefits of going wireless vastly outweigh an occasional connection annoyance to me. And worst case I can still plug them in.

I use rustdesk for remote desktop. Screen sharing is usually on zoom as it’s what my workplace uses.

Physical connectivity comes courtesy from an RJ45 socket, a pair of USB-A ports, a sole USB-C connector, a microSD slot, and an HDMI connection

wasn’t expecting that

deleted by creator

Also, folding encourages 1000+ line files and several indentation levels, like in their example.

kali is for posers, professionals use hannah montana

C was my first language some 18y ago, and I wouldn’t recommend it to anyone starting today. If anything, learning C is a great way to teach why, maybe, we shouldn’t be using it to build customer applications, web servers, and whatnot.

Keep your gold, I’ll stick to sane error messages, memory management, a packaging system, and a dozen other things that actually make working on multiple projects somewhat doable and not a constant fight against seg faults.

that’s one way to swing the pendulum all the way back to the 1970s

You probably don’t have to write to specific broswers. Just stick to the baseline and you’re golden. Optionally use a headless chrome for e2e testing to be sure.

I’ll admit that in 10 years using git, I don’t think I’ve ever used reflog once.

tldr

1. Keep Commits Small: Ensure commits are small and manageable to facilitate easy reverts and debugging.
2. Continuous Refactoring: Prioritize frequent, minor refactorings to simplify future changes.
3. Deploy Continuously: Regularly deploy code to ensure it works in production, as working software is progress.
4. Trust Frameworks: Avoid over-testing framework capabilities; focus on application-specific logic.
5. Create Independent Modules: Place functions in new modules if they don’t fit existing ones, preserving code organization.
6. Write Tests Early: Use tests to design APIs and guide development, but don’t be rigid about TDD.
7. Avoid Duplication: Prevent repeated code by abstracting similar implementations after copying once.
8. Embrace Change: Accept and adapt to evolving designs, understanding that change is intrinsic to software development.
9. Manage Technical Debt: Focus on minimizing immediate blockers and plan for potential future issues.
10. Prioritize Testability: Ensure that your code and design facilitate easy testing to maintain code quality and coverage.

mah man

man man

oh man

Because you’re assuming foo won’t be renamed when it becomes a function. A function should start with a verb, say get_foo(), because just foo() tells me nothing about what the function does (or what to expect as output). If you make it a property, get_ is implicit.

So if the age is computed from the year of birth for example, it’s really e.g. thing.age or thing.get_age() - both of which are fine, but I’d pick the property version.

that we agree on: properties should be cheap to compute.

Making a simple ternary condition as a function instead of property is a wasted opportunity to make its usage cleaner.

Properties make semantic sense. Functions do something, while properties are something. IMO if you want to name something lazily evaluated using a noun, it should be a property.

The misleading behavior is about what you expect to execute in the source code you’re looking at vs what’s actually executed.

What you describe is a logic ambiguity that can happen in any program / language.

Totally agree. The hardcoded isAdult: true repeated in all #2 examples seems like a bug waiting to happen; that should be a property dynamically computed from the age during access time, not a static thing.

deleted by creator