Hacker News: angrybards

New comment by angrybards in "Octane – React’s programming model, compiled"

angrybards — Mon, 03 Aug 2026 22:09:55 +0000

I've been working on my own framework for several years now. I chat to AI about it but otherwise it is hand coded. It is interesting looking at how much effort goes into framework development when in theory an AI can spin up precise code that does just what is needed for the situation, assuming it isn't hallucinating or going off the rails of course. But I don't think we have seen a truely vibe coded, AI just doing what is optimal framework come out of the woodwork even though the space has had a lot of time to show something. I'm interested to see what it looks like when it happens.

New comment by angrybards in "The Difference Between a Button and a Link"

angrybards — Wed, 29 Jul 2026 07:22:57 +0000

Yea I think a form that posts is the right tool for the job here. It is clearly unsafe semantics.

New comment by angrybards in "The Difference Between a Button and a Link"

angrybards — Wed, 29 Jul 2026 04:27:33 +0000

I wasn't under the impression it is a W3C site, for all I know it is AI generated and looks it to me. But, there are other blog posts I've coming across where this is discussed and that site did outline my point well enough which is changing norms like this can be hard for screen reader users who need to adapt to ,

New comment by angrybards in "The Difference Between a Button and a Link"

angrybards — Wed, 29 Jul 2026 03:49:46 +0000

REST doesn't care about the content of your URI path / query as long as it is unique to the resource and POST's semantics are so flexible you can perform any action with it:

> The POST method requests that the target resource process the representation enclosed in the request according to the resource's own specific semantics. For example, POST is used for the following functions (among others):

https://httpwg.org/specs/rfc9110.html#rfc.section.9.3.3

There are some niceties to using PUT and DELETE, but different reasons.

New comment by angrybards in "The Difference Between a Button and a Link"

angrybards — Wed, 29 Jul 2026 03:42:18 +0000

Screen readers use the clear semantic difference between a button and a link to make sure the user knows what to expect and users are used to the different keyboard shortcuts. I saw in your specification an example where a website made effort to work around this clear separation and from what I could tell there may have been user testing, but in other places I see that usability is best for screen reader users where the semantics are clear.

This proposal would standardize an in between element, adding a third form they have to understand with different behaviors. I guess just make sure you get some experienced accessibility feedback in your submission.

https://www.thewcag.com/examples/buttons-links

New comment by angrybards in "JSON-LD explained for personal websites"

angrybards — Mon, 22 Jun 2026 02:51:54 +0000

If you feel like it, tell me what you think of this. It is just surface level to what I'm working on. The starter project I'm making with it supports screen readers with rich webapp experiences and nojs w3m. But it is a fully Javascript SSR framework.

https://codeberg.org/occultist/octiron#readme

New comment by angrybards in "JSON-LD explained for personal websites"

angrybards — Sun, 21 Jun 2026 23:23:53 +0000

I don't fully understand XSLT, but I've been building something which I believe solves a similar problem (albeit JSON-LD and Javascript). The general XML ecosystem of solutions have always looked really complex to me. You need to understand a lot more types/elements than I think is reasonable for people to author with but they are from before my time. I took a look at XForms 2 and it had its own way of defining functions which on top of the other XML quirks has security concerns.

New comment by angrybards in "JSON-LD explained for personal websites"

angrybards — Sun, 21 Jun 2026 22:38:14 +0000

HTML markup designed for presentation doesn't always map well to the relationships JSON-LD is used to describe which I imagine is probably why Microdata didn't work out. I have an idea which might use it, but it is a simple use case that doesn't try do too much. Microdata requires the agent supports a more complex HTML parser, Finding a script tag in the document head is probably simpler.

I wouldn't dismiss REST because of RCP though. HTTP and HTML's success probably relate to how Roy Fielding's REST constraints kept the HTTP protocol lean and extendable. It is more like RCP is being used as a layer over top of REST because of HTTP's and HTML's success as being good technologies for web scale.

Show HN: I built an extendable full document markup language

angrybards — Fri, 19 Jun 2026 22:50:22 +0000

Hi HN, I've been working on an easy to read and write extendable markup language that can express any HTML element and structure. Longform can be used in most situations Markdown might be used, but is better suited for situations where structure and semantics are a requirement of the output and are understood by a document's authors.

Longform exports full documents or HTML fragments, allowing a parent program to piece together the fragments into its own markup. And directives can be used to extend the language.

Take a look at https://longform.occultist.dev for the working spec. If you want to test it out, I've built a really basic static site generator at https://stat.occultist.dev.

Comments URL: https://news.ycombinator.com/item?id=48604223

Points: 3

# Comments: 0

New comment by angrybards in "RFC 10008: The new HTTP Query Method"

angrybards — Wed, 17 Jun 2026 22:35:28 +0000

GET with only a URI has the semantics of retrieving the current representation of the resource. This is the most basic form of hyperlinking and quite important to how the web works. Adding a body parameter to GET would break that constraints of the method as you couldn't treat two requests using the same URI as referencing the same thing.