throw2ih020

> what changed in the perspectives of the language maintainers?

The original maintainers moved on to other projects and the new community maintainers came to a consensus through the proposal and governance process.

Plenty of people run ad-blocking DNS on their router, or mesh VPN software. Handy for devices where you can't install an ad blocker directly, and for working around CGNAT issues due to IPv4 exhaustion.

If my microwave had programmable firmware I'd absolutely reprogram it, get rid of the annoying clock and make my own quick buttons for my most common meals...

I think at this point the zero cal/low cal ones are more popular. I don't know anyone who drinks Black Monster, while White Monster (zero cal) is so popular it's literally a meme. You go to a store and most of the shelf space is the low cal/zero cal options.

This comment feels like reading a forum in the mid-2000s, haha.

The Rip It people are usually vets - Rip Its were the only ones you could get reliably while deployed in the ME.

I don't know anyone who actually drinks Bawls - most of my gamer and IT friends do Monster Zero and Monster Ultra. You can get them basically everywhere and the fruity ones actually taste pretty good.

LAN parties haven't really been a huge thing in a long time, sadly, outside of convention-style events.

> separating the trivial and non-trivial tasks is a famously hard problem (if at all decidable).

Famously, this is also a problem for human coders in sprint planning.

An absurd argument - 75k over a 20 year career as a dev is only $1.5 million (before living expenses and tax), which is a fraction of the $5 million lower bound in my original comment.

The people I know personally with that level of wealth will typically set up family trusts to do that and manage how the wealth is distributed to the family, generally some stipend for living expenses + covering education and healthcare costs. The original people setting up the trust give up direct access to that portion of the money for the benefit of their heirs and beneficiaries. i.e. it's no longer "their" money in the personal sense.

Same, my father was a doctor and had tons of doctor friends from med school and work. Pretty much all of them just cared about 1. making sure the family was provided for and had excellent education, 2. patient outcomes and 3. being comfy at home.

Most "normal" people would hit $5-30 million, realize they have enough money for themselves and their descendants to be comfortable in perpetuity with some decent wealth management, and either retire or change careers to a passion project. Going to 100s, 1,000s, or 100,000s of millions inherently filters for people who have either absurd greediness (seeing wealth as a scoreboard) or a desire for power.

Sorry, I don't follow? I'm just using the templating from Go's standard library. That part replaces existing server-side components of the old applications.

I'm replacing existing third-party applications which have complex JavaScript frameworks with my "in house" apps using HTMX + mostly just HTML+CSS for most pages and functionality. i.e. I'm not introducing a layer, I'm replacing one.

Why not just use html without HTMX you ask? With HTMX I don't have to reload the entire page to navigate, which is especially helpful for making the app responsive even on low bandwidth connections like a bad cell signal.

In a way HTMX is similar to how we used to write websites on LAMP stacks, except with higher quality of life.

Foreign key constraints, sync frequency, busy timeout, strict typing on tables, explicit types for integer primary keys, and a convention for storing dates and times are others I would want to do up front.