I stayed in a house in Rome that kept out the fierce summer heat, because of thick walls. AC would be redundant. In other places, like Hong Kong, the thin walls of the apartments need AC to remain liveable in summer. I've read about the lack of shade in many built environments. Seen TV shows where someone builds floor-to-ceiling panoramic windows in a location that would be below 0 for much of the year. Unsustainable construction drives AC use and greenhouse gas emission that makes the problem worse.
Readit Newsf4c39012 commented on Europe's crusade against air conditioning is insane noahpinion.blog/p/europes... · Posted by u/paulpauper
f4c39012 commented on Vanishing from Hyundai’s data network techno-fandom.org/~hobbit... · Posted by u/pilingual
If someone is tailgating me I just slow down gradually until they get mad and pass
To a degree this is sensible, if someone is tailgating you and you need to perform an emergency stop there's more likely to be a collision, so you need to increase the space in front of you for more gradual braking.
Deleted Comment
f4c39012 commented on Emailing a one-time code is worse than passwords blog.danielh.cc/blog/pass... · Posted by u/max__dev
Some sites make this into a problem accessing their site by having an unsubscribe that doesn't account for this login method. Unsubscribing from marketing means I can no longer login
f4c39012 commented on NIH is cheaper than the wrong dependency lewiscampbell.tech/blog/2... · Posted by u/todsacerdoti
NIH is amazing as long as you are realistic about what you are taking ownership of.
For example, the cost of maintaining a bespoke web frontend "framework" that is specific to your problem domain is probably justifiable in many cases.
The same cannot be said for databases, game engines, web servers, cryptographic primitives, etc. If you have a problem so hard that no existing RDBMS or engine can support, you should seriously question the practicality of solving your problem at all. There's probably some theoretical constraint or view of the problem space you haven't discovered yet. Reorganizing the problem is a lot cheaper than reinventing the entire SQLite test suite from zero.
i can think of two reasons for using a third-party dependency
1) a dependency on a third-party service provider that publishes the dependency. So long as that service provider is current, the dependency should be maintained 2) short-cut to code i don't want to write
I have no arguments with (1), there's a business reason and the lifecycles should match. However, I should still expect major version breaking changes in order to keep my application running. For (2), the wins are less clear, more dependenent on the perceived complexity of what I can avoid writing.
Taking on any kind of dependency means that someone else can dictate when I need to spend time updating and testing changes that don't add anything to my product. Taking on a third-party dependency is always taking on a responsibility to maintain a codebase or the risk of not doing so.
f4c39012 commented on NIH is cheaper than the wrong dependency lewiscampbell.tech/blog/2... · Posted by u/todsacerdoti
Completely agree. It's one of the most important skills to know which dependency is good and which is bad.
My two cents. If a dependency is paid, than it is usually bad. Because the company providing that dependency has an incentive to lock you in.
As another point, "dependency minimalism" is a nice name for it. https://x.com/VitalikButerin/status/1880324753170256005
https://opensourcemaintenancefee.org/ uses payments as an incentive to keep projects going, so dependencies can be updated. .NET Rocks! interviewed them https://www.dotnetrocks.com/details/1948
Lorem Bel-airum - Lyrics of Fresh Prince of Bel-Air _but in Latin_