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.

deleted by creator

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

Ladybird is not usable yet, but it’s an independent browser and engine that accepts donations

repo - https://github.com/LadybirdBrowser/ladybird

youtube channel with monthly updates - https://www.youtube.com/@LadybirdBrowser/videos

kali is for posers, professionals use hannah montana

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.

they do

I’ve used plenty of sshfs a few years ago, but x11 forwarding is a compromise. The latency makes it painful to work with for more than a few minutes.

Same, ranger was painfully slow at times. For some reason it would take multiple seconds to start on a few machines I connected it to.

I can’t believe no one mentioned this, but: remote access.

I spend most of my day connected to machines via SSH and yazi offers a great UX with file previews and all. Using kitty I even get image previews in the terminal.

get rid of companies making money off the FOSS

I’m afraid if we discourage companies from adopting open source we’ll end up with even more closed source garbage.

There are industry sectors where closed source is the norm, and it just leads to more vendor lock-in and less standardization and interop.

I’m a bit young to say for sure, but I believe closed source was the norm in the software world 20-30 years ago and openness was stigmatized. I certainly don’t want to live in that world.

“oh no, anyway…”

GTA online was fun from 2015 until a couple years later before flying bikes and sky races. R* kept pushing updates that appeal to teenagers and absolutely ruined it.

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.