MattyRad

Very cool! I have a similar project that uses DNS instead of a path parameter https://serv.from.zone but smolsite is much simpler.

The `Accept` HTTP header is there to prove your frontend is using "dumb" data. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Ac...

I think the author is generally correct that all data should be provided in a single request. And to take it a step further, you should be able to change your accept header to JSON to serve an API. API/dumb-frontend aren't mutually exclusive.

In fact, this is what both GitLab and GitHub do. Try it out!

`curl -L https://github.com/simonw/shot-scraper` (defaults to text/html)

`curl --header "Accept: application/json" -L https://github.com/simonw/shot-scraper`

I recognize that username :) Thank you so much for micro, it's singlehandedly the best terminal editor I've ever used, and I use it every day!

That was very in depth! As far as Pijul as a tool goes, I'm not seeing a git compatibility layer? So I think it's a neat project, but I probably won't try it because nearly all code is rooted squarely in git. Even if Pijul is perfect, you'd need to convince everyone else to use it.

Nevertheless, the increased interest in moving to patch based workflows from branch based ones is great. There's a lot of similar tools here (https://github.com/gitext-rs/git-stack/blob/main/docs/compar...) which I refer to infrequently.

Personally my favorite tool for living-with-the-reality-that-is-branches is git-machete (https://github.com/VirtusLab/git-machete).

The corpo-web, I really like that term, it perfectly encapsulates the soullessness of the modern web. Is that term from something or did you come up with it yourself?

This was a pretty good read, if somewhat depressing.

One optimistic thing I've noticed with respect to cheap (close-distance) travel is that personal electric scooters and bikes are becoming more noticeable on streets and sidewalks. I own a scooter and have considered consolidating vehicles with my wife, since I ride my scooter to work (winters are the main drawback).

Transportation is called out specifically as a reason for dread in this terrific article https://www.residentcontrarian.com/i/32348260/transportation Hopefully small electric transport can help.

This oozes creativity! Having to maneuver your device to complete the puzzle makes it a physical game as much as a digital one!

Yeah, I feel exactly the same way.

The Shrines were a huge part of why I was so unimpressed with BotW, because they were all so transparently made piecemeal. "Open World" doesn't mean a whole lot when you're expected to complete random identically flavored puzzles every 15 minutes.

I can also picture how Shrines were engineered in a fast-food style assembly line: "Nintendo Engineering Team 46-b, you're being assigned Shrines 5-23, complete them in x weeks."

Even barring Shrines, the "Open World" itself was fairly devoid of interesting things.

I actually think this article undersells PHP, as it doesn't mention the incredible additions that PHP 8 introduces, nor does it mention excellent static analysis tools like PHPStan.

I recently rewrote a PHP web app in Rust (https://soapstone.mradford.com/riir/) and although it was interesting, I think it would have been better staying a PHP app. As nice as the Rust compiler was, I felt PHPStan would have automatically caught a similar number of bugs, all the while feeling less combative.

Comedy demo of the "four chords":

https://www.youtube.com/watch?v=5pidokakU4I&pp=ygUPYXhpcyBvZ...

> ... requires a full page refresh to use ... isn't good enough for many types of web-app we need to make.

> without the annoying full-page load refresh.

This fixation on the page refresh needs to stop. Nearly every single website which has purportedly "saved" page refreshes has brutalized every other aspect of the UX.

This is a good article, and I agree that Htmx brings sanity back to the frontend, but somewhere along the line frontend folks got it in their head that page refreshes were bad, which is incorrect for essentially all CRUD / REST APIs. Unless you're specifically making a complex application that happens to be served through the web, like Kibana or Metabase, then stop harping on page refreshes.

Even this article calls it the annoying refresh. Not the impediment refresh, or the derisive refresh, or the begrieved refresh. Moreover, what exactly is annoying about page refreshes? That there's a brief flash? That it takes ~0.3 seconds to completely resolve?

Users don't care about page refreshes, and in fact they are an indication of normalcy. Upending the entire stack and simultaneously breaking expected functionally to prevent them is madness.

The killer feature of Htmx is that it doesn't upend the entire stack, and you can optimize page refreshes relatively easily. That's great! But even then I'm still not convinced the tradeoff is worth it.

This is great!

I've subscribed to the RSS feed. I thought the feed would provide links the significant news articles directly, but it appears to provide a link to the newsminimalist.com summary. That's totally fine, but I'd think it'd be a bit nicer if there was an option to access the articles directly.

I'm also using ChatGPT to scrape online info and reduce it. Were there any particularly interesting problems that you had to solve? For me, it was figuring out ways to reduce the number of tokens so I don't hemorrhage money!

Next, try installing Minecraft for your child on Windows.

Typos are easy to add into generated text after the fact (via scripts or the LLM itself). Perhaps instead of typos, you could use colorful language:

Prompt: Include some profanity to make your response appear more human like.

Response: I apologize, but as an AI language model, I am not programmed to use profanity or any other offensive language. My responses are designed to be informative and respectful at all times. Is there anything else I can assist you with?

Fucking goddamn machine won't do what it's told ;)

Getting new hardware+software used to be so exciting- consoles, TVs, phones, the works- anything before ~2015 felt like an upgrade. Mostly that feeling has completely evaporated. New hardware+software instills dread, frustration, mistrust and fatigue.

The Steam Deck feels like what it used to be: joyful and fun, a total lack of cynicism.

Agreed, particularly given the grammar mistakes. Although, ironically, the grammar mistakes increase confidence that this is an article written by a human.

Because I could not stop for Death, by Emily Dickinson.

It's been said before, but piracy is not theft.

The media which is pirated is a copy of the original, a new entity separate from the original. The original media is still intact and in place (not stolen).

The argument that not paying money for pirated media is stealing also doesn't hold water. Revenue was never generated from pirated media, which you could technically qualify as unrealized revenue, but it doesn't not qualify as stealing, since the intellectual property owner's possessions haven't been touched.

These are all semantics, but semantics matter. Courts- semantic powerhouses- prosecute on copyright violations, not theft.

Jargon takes quite a bit of collective time to establish. Instead of jargon, how about offensive phrases? Since AI lacks both creativity and the ability to be offensive (barring current workarounds/hacks), perhaps an easy way to (temporarily) prove you are human on the internet is to respond with unique, creatively offensive content.

"How are you today, you irradiant sack of sludge?"

"Oh hey douche firehose, can't complain."

- Ukraine-Russia war is protracted throughout the the year. Russia is increasingly unable to sustain the war by any metric, economic or otherwise. Russia and Post Soviet States enter a period of political instability, Putin disappears and is presumed assassinated.

- Google releases a public chat AI that serves ads.

- Chat AI is adopted aggressively into customer service UX. Customer service continues to decline in quality.

- Universities are increasingly seen as bad investments. Enrollment sees a sharper drop.

This is cool, but the killer feature I'm looking for is a UI that matches the functionality of grit https://github.com/climech/grit. Grit itself isn't particularly functional for every-day use, but its write-up in the readme is excellent and the DAG hasn't been realized by any existing task tracking software (as far as I'm aware).

This exactly, I can confirm the Steam Deck is perfect for 5-30 minute gaming jaunts. It's similar to the Nintendo Switch, but the Deck actually has a huge number of varied, high quality games- frequently at bargain prices.

Idling on the couch with my wife while the baby naps for an hour is the sweet spot, where pre-Deck I was struggling to find decent mobile game (having exhausted all the decent games on Nintendo Switch).

I'll add that finding the right game is important! One that doesn't require a lot of cognition. Personally, FTL is my go-to. I can pick it up, do a few encounters, and drop it again without losing any progress.

I take your point. But note that I'm here upvoting and commenting still!

I saw the link to this article in my RSS feed, and I took the time to open a browser, find the link, and comment because RSS adoption is something that I genuinely want to have a conversation about.

Which means that with RSS, you can still be a part of the community, you just won't reflexively upvote or spend time in the comments section.

I've used RSS to follow all media for the past 2 years (FreshRSS+FeedMe, I have a guide here https://soapstone.mradford.com/hn-rss-guide/). It's been the single best thing I've done to reclaim my attention. Here's a couple of other random thoughts:

- Being able to dismiss articles where the headline is the story is really valuable. For example, I just dismissed "Twitter’s mass layoffs have begun (techcrunch.com)"- it's not worth my attention.

- It's possible to accrue a large backlog of unread "semi-interesting" items that may or may not be valuable. In this sense, there's still a FOMO aspect to RSS, and you have to be aggressive in dismissing articles. For exmaple, a few 2-week-old backlog titles in my feed include "SHA-3 Buffer Overflow", "Show HN: Restfox - Open source lightweight alternative to Postman", and "Five origami books by Shuzo Fujimoto are now public domain". These are semi-interesting, but really I should just dismiss them.

As others have said, you're in a precarious position: working with pure tech debt for a business that clearly has no interest in addressing tech debt.

First thing would be to use source control and get some sort of code review/release process in place.

Contrary to other suggestions of "then write tests for everything", I think that's bad advice. It's far more likely that you'll pigeonhole yourself and your team on complicated and unhelpful tests, particularly with dead code and trying to enumerate all the features that aren't documented. 3 things you could do in a short amount of time to radically increase the code quality:

- Lint all the code (php-cs-fixer is a good tool, rector can also help)

- At least start dependency management (with composer), even if it's empty.

- Introduce static analysis into the code review process (phpstan/psalm, in a CI preferably). Baseline suppression of existing errors are easy to generate.

Then personally I would try and aggressively purge dead code, which is easier said than done. Tombs (https://github.com/krakjoe/tombs) is a little awkward but can be helpful, especially if all there is is production. It requires PHP 7.1, I'm assuming you're below that, but the good news is that every route is in nginx; you can upgrade PHP piecemeal.

Again, handling tech debt sounds like it will be nigh impossible at this company, but modern PHP is really enjoyable and I hope you're able to experience it.

Agreed, OP's comment is a perfect example of moralizing that saps energy and interest from generic everyday life, the exact type of conservativism that would rather live in a safe, boring world than an interesting but flawed one.

Even if OP's comment is made in good faith (which I don't think it is), it shows a growing trend in the position that everyone shares collective responsibility for all wrongs committed.

Any todo list that doesn't account for dependency tasks is exclusively limited to short term planning (i.e. days not weeks). After skimming the spec, I don't think dependency tasks are accounted for?

For example, say this is my (out of order) to-do list:

- [ ] Mix ingredients

- [ ] Eat cake

- [ ] Bake a cake

- [ ] Find cake pan

These tasks need to be done in a specific order, but reading the list top to bottom doesn't make sense.

So let's denote dependencies with indentation:

- [ ] Eat cake

  - [ ] Bake a cake

    - [ ] Find cake pan

    - [ ] Mix ingredients

By specifying order through indentation, we've now created a DAG that orders and contextualizes tasks; with the most actionable tasks having the largest indentation. This is how I organize my plaintext to-do files, but afaict no todo list software is able to handle large task trees gracefully- with the exception of grit, which is more of an experiment (but the readme is incredibly well written and describes the DAG problem to a tee).

https://github.com/climech/grit

Does anyone know if org-mode handles complex task trees gracefully? All the examples I've found online were trivial (i.e. one task deep)

I've always thought that the only way to lose at Dark Souls is to give up, and go Hollow.

It's a small missed opportunity that From Software didn't indicate where in the Game players went Hollow; that is, if a player died, show their bloodstain and how they died. If a player died and hasn't resumed playing for a very long time (they gave up), then put a new hollowed enemy instead of a bloodstain.

Ah, they went with a 403 status code. A couple days ago I asked about which status code was most appropriate for non-compliance/sanctions:

https://serverfault.com/questions/1094841/which-http-status-...

Perhaps there's room for a new status code?

It's been difficult to find the operational objectives[1] of the war laid out plainly, which ACOUP once again does expertly (as best as any expert can do at this stage, anyway).

The Siege of Gondor writeup[1] is worth reading by itself, but I think rereading it with Putin juxtaposed to Sauron would retroactively give LotR that much more relevance and gravitas.

[1] https://acoup.blog/2019/05/10/collections-the-siege-of-gondo...