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.
First time pebble owner, but I'm loving it. Not quite getting the advertised 30 days of battery life, but ~20 days is still more than good enough. It's also a really fun development platform
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.
This is sorta the reasoning behind statements like "billionaires shouldn't exist".
It's not a statement that people shouldn't see fruits of their labor, but that past a certain point, its no longer about the fruits or even the tree, but the power that comes with it. In a democracy, those who get lucky in business are not owed power.
So yeah, billionaires and trillionaires shouldn't exist, because their existence is a side-channel attack on society. Pay enough money and rules don't apply. Past a certain point, that wealth should be heavily scrutinized and audited as if it's nuclear fissile material. Similar to the nuclear material, it can be productive for society, or absolute destruction.
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.
This is it, it's absolutely a filter beyond a certain point. I have a family member, far enough removed I'll never see any of it, that sold a business in his early 30s for something like $35-40M. Set his kids up for life with trusts, bought some toys and a second home, and been just sort of hanging out ever since (this was 15-20 years ago). He's happy, has a ton of hobbies, and if you ever suggested he start another business or start putting his name on cap tables he'd laugh his ass off. It would never even occur to him that he should try to double, triple, 10x his money, because he already has 10x more than he'll ever spend.
And for what it's worth his kids are remarkably well adjusted and nice, if a little bit out of touch about what most people deal with.
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.
Whereas I have an uncle, a retired CEO, with perhaps the same amount of money. The man is a monster. However, per my cousin, I can't say for sure just when that nature revealed itself but certainly no later than 20 years into his career.
I totally understand the point you're trying to make, but also...if your friend put their $40M in an S&P500 index 20 years ago, it'd be worth $238M today. So more like 6x rather than 10x, but still, not bad.
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.
HTMX is awesome. I've replaced several OSS web apps on my home server with HTMX + Go + PostgreSQL replacements. The results are lightweight, responsive, work great on desktop and mobile alike, all with the absolute minimum complexity required. The codebases are easy to understand and modify, and so far I'm going months between updates (mostly just minor bugfixes for my applications). I fully expec my mature apps will go years if not decades between required upgrades.
Are any of these open source? I've gone down the go/htmx/pg path lightly a few times and I haven't loved the feel of it, but maybe I'm doing it wrong. I think just server side templating just starts feeling icky in go so maybe I'm just missing a good pattern or library.
- Standard library http package for the API server implementation
- Standard library template/html package for generating the dynamic parts of the webpage content
- Static web content is embedded within the Go binary (https://pkg.go.dev/embed) and served through server routes
- api served from /api route, htmx webpage served from /
- no ORM, mostly using standard library database/sql package for DB transactions, maybe reaching for a query builder library for more complex queries like complex search functionality
- Local S3 compatible object store for dynamic binary data like user-uploaded images and video. Local filesystem can be fine for small scale stuff.
For my home server I have authn/authz happening at the OS/infra layer, but if you need multitenancy you can pretty easily integrate an OAuth/OpenID authn/authz middleware for login with Google or whatever.
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.
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.
That's great but I believe it's still over-engineered. Unless it's a web site that can tolerate no downtime at all during schema updates, SQLite in WAL2 mode is more than enough. Moreover, in Postgres version upgrades can't be done without significant downtime (or setting up replication and performing a complex dance), so even that isn't so cut and dry.
For some of the simpler sites sqlite would have been fine, but I do need Postgres anyway for some other stuff on my server so the overall burden of standardizing on Postgres only is less than having to do tuning for two different databases. In particular sqlite has worse defaults due to backwards compatibility, so you have to do a lot of upfront config for every table and DB.
Postgres version upgrades are basically painless, at my workplace our upgrades complete in so little time our users don't notice, and we have more data than probably 99.9999% of companies out there (mature company in aerospace industry).
Well if you already have Postgres then yes, sounds fine. I don't really agree that SQLite needs tons of tweaking -- setting journal_mode to WAL/WAL2 is the only real thing worth doing, everything else I would consider optional.
Version upgrades for SQLite are basically a no-op though, that's kinda one of the reasons why it's so great to run in production (and deployment a maintenance being mostly a no-op as well, apart from setting up backups I guess).
I don't actually suggest that everyone should run their production on SQLite, but it's genuinely worth considering especially for small-ish projects.
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.
I personally find Postgres WAY easier than SQLite simply because of the deployment story. I do a lot of hotfixes and dangerous stuff on personal projects, and having two databases complicates that tremendously. I like being able to run hot code on prod.
For the record, this is not the same reason I like postgres for actual production code
I think they mean that they actually do need Postgres for some of their projects, and it's easier to just use Postgres for everything, than to use Postgres for some things and SQLite for others.
Yeah, I mean I guess I could technically connect to the remote SQLite server on my production server. You're right. But I've never done that and that's just not the pattern people use on SQLite
> Unless it's a web site that can tolerate no downtime at all during schema updates, SQLite in WAL2 mode is more than enough.
I do think that people really underestimate how quickly a system starts being "please, no downtime" (or its weaker cousin, "please, don't make your ops people do rollouts at 1AM").
Like obviously it's not the end of the world but the default assumption of "the system is up" makes a loooooot of things downstream of that easier.
Having to do operational bug triage on systems that routinely have blips in availability is unfun.
Trying to have so few blips they're invisible to bug tracking is a very expensive level of uptime. It takes a lot of convenience to add up that high, compared to ignoring errors for thirty seconds at noon.
The sort of real thing is that it's not just about no-downtime deploys, but also stuff like rolling back smoothly, general continuous deployment or even just generally being able to easily move between versions.
I still think there are lines (I have to begrudgingly accept that downtime for PG upgrades is still basically worth it because the effort to not downtime there is so high but the frequency is so low), and it's a spectrum. But I've found that this particular flavor of tech debt tends to hurt quite a lot even with fairly low activity systems
The local car wash has lights that help you park the car pretty precisely under the wash robot. No rails or anything, you park right underneath the robot and it moves around and over the car. The robot doesn't start until you are in position.
The original maintainers moved on to other projects and the new community maintainers came to a consensus through the proposal and governance process.