> an open-source application framework, was that hosting that used FastCGI, would not honor Auth headers
So you were writing your application as a fcgi-app, and (e.g.) Apache was bungling Auth headers? Can you expand on this? Curious about the technical detail of (I guess) PARAM records not actually giving you what you expect?
I don’t remember, exactly. Long time ago (I stepped away from that project many years ago).
I just remember the auth headers never showing up in the $_SERVER global (it was a PHP app). This was what I was told was the issue. They made it sound like it was well-known.
This is because of a deeply annoying default in Apache, where for "security reasons" the underlying script doesn't get to see auth details that might already be handled by Apache. At some point they added the CGIPassAuth directive[1] but all kinds of other workarounds are floating around on the internet.
Before making sure you have access to good beans (had to carry on with the theme), make sure you actually want to have "coffee" as another hobby in your life. Maybe it's worth it to outsource to your local cafe the machine maintenance, grind fine-tuning, bean recipes, hours learning milk steaming, hours spent on youtube, coffee forums, commenting in the occasional HN coffee-adjacent articles...
If good coffee is the goal and one doesn't insist specifically on espresso or having steamed milk, the humble pourover is a good starting point. The pourover funnel, filters, and a decent hand grinder are relatively inexpensive and, with only a little practice, the output is as good as any americano produced by the average barista at 1/5 the price per cup.
That's pretty much why I got a semiauto machine. Is it the best espresso ever? Probably not. But I can make lattes in my underwear on Saturday morning that are still better and cheaper than what I'd get at Starbucks. Scratches the itch without being as demanding as a hobby.
Fruity Kenyans and Ethiopians by V60 or Chemex, classic Italian on the espresso machine, the way $deity intended. Acidic espresso is gross, but the juicy acidic coffees shine as pour-overs.
> For those unfamiliar, Slayer is (imo the best) one of the top $$$ machines and pairing it with a budget grinder is a classic sign the owner doesn't know a thing about coffee.
The exception to that rule is Espresso Vivace in Seattle, with (at Capitol Hill location) a couple 3-group La Marzoccos at the bar and a collection of modded Niche Zeros on grinding duty. Nobody can accuse David Schomer[0] of "not knowing a thing about coffee".
I think of it as BSD style, though of course it could be suggested/mandated elsewhere -
[...]Use a space after keywords (if, while, for, return, switch). No braces are used for control statements with zero or only a single statement unless that statement is more than a single line, in which case they are permitted.[0]
As I look, GNU guide is less specific, but examples[1] show the same style.
The good thing is that -Wmisleading-indentation [2] (comes along with -Wall) catches this indentation error.
> C++ is like C with extra features, but you don't need to use them
C++ certainly (literally (Cfront[0])) used to be this, but I thought modern (decade or more) conventional wisdom is to NOT think like this anymore. Curious to hear others weigh in.
To me, it is not "conventional wisdom", it is what a vocal group of C++ guys who look at Rust and its memory safety and don't want to be left out.
Their way is not wrong, new constructs are indeed safer, more powerful, etc... But if you are only in for the new stuff, why use C++ at all, you are probably better off with Rust or something more modern. The strength of C++ is that it can do everything, including C, there is no "right" way to use it. If you need raw pointers, use raw pointers, if you need the fancy constructs the STL provides, use them, these are all supported features of the language, don't let someone else who may be working in a completely different field tell you that you shouldn't use them.
C++ by comparison doesn't stand in your way too much either.
I feel like the biggest gripe Rust has is what happens when you do have to go unsafe.
That seems to be a strong point of contention for many folks.
Maybe all the reasons that lead people to use unsafe rust go away or the attitude about it shifts in some manner.
For me Rust turned out to be less interesting after I saw the whole ceremony about typing.
The amount of things I had to grasp just to get a glimpse into what a library does felt much more involved than any of the things I did with C++.
The whole annotation-ting feels much less necessary and more like a proper opt-in there.
> Who is really running anything like this in 2026 and for what purpose?
Am I parsing your question correctly?
reply