Top all-time · #3025
JASON Format
Personal blog · jasonformat.comwebprogramming
JASON Format is a personal blog at jasonformat.com about web and programming. Since 2017, 24 different Hacker News readers have linked it 25 times, most often “Islands Architecture – when SSR meet micro front end”. The last post was in 2021, but the archive is still widely read.
Too few sampled comments (10) to say how often HN recommends it.?
Why HN links it
HN readers link Jason Miller's posts on islands architecture and partial hydration, and his JSX explainer, as background reading on these topics. Most comments only cite them.
Summarised by Claude from a sample of 10 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- Islands Architecture – when SSR meet micro front end9 people · 9 mentions · first linked 2020-08-11
- Application Holotypes: A Guide to Architecture Decisions5 people · 5 mentions · first linked 2019-02-15
- Modern Script Loading3 people · 4 mentions · first linked 2019-07-25
- Rome, a New JavaScript Toolchain2 people · 2 mentions · first linked 2020-02-28
- WTF Is JSX2 people · 2 mentions · first linked 2017-09-08
What Hacker News says?
https://jasonformat.com/islands-architecture/
Comment linking /islands-architecture/
on “Fresh – Next-gen web framework”Submitted Modern Script Loading as a story · 105 points
HN discussionIt’s actually not gibberish. * Island refers to this https://jasonformat.com/islands-architecture/ * Island based hydration is a form of partial hydration where the boundary is the component islands.
Comment linking /islands-architecture/
on “Fresh – Next-gen web framework”Submitted Islands Architecture – when SSR meet micro front end as a story · 28 points
HN discussionFrameworks like Next or Nuxt often render each page server-side, shipping HTML to the client, but then also send enough javascript and json data to the client to "hydrate" the page back into fully interactive components. The whole site, then, really acts as one large javascript app once fully loaded. The islands approach is different: pages are server rendered, but you can easily define islands of interactivity (lik…
Comment linking /islands-architecture/
on “Fresh – Next-gen web framework”Submitted Rome, a New JavaScript Toolchain as a story · 5 points
HN discussionI had the same thought. I read the islands overview and was had a little "what's old is new again" chuckle. https://jasonformat.com/islands-architecture/
Comment linking /islands-architecture/
on “Fresh is a new full stack web framework for Deno”Submitted Application Holotypes: A Guide to Webapp Architecture Decisions (2019) as a story · 3 points
HN discussionThe post seems to claim that there is no drawbacks others approach with the 0 bytes of js, and link to a blog post [1] that absolutely tells nothing how to properly manage back/front state and rendering consistency between the rendering and the «islands» on the client. [1] https://jasonformat.com/islands-architecture
Comment linking /islands-architecture
on “Fresh is a new full stack web framework for Deno”Submitted Modern Script Loading as a story · 3 points
HN discussionDiscussions about website architecture become a lot more productive when you use Jason Miller's holotypes idea [1] as your starting point. "Holotypes" is kinda just a fancy word for the common top-level uses of the web. E-commerce, search, media player, etc. With that foundation it becomes obvious that SPAs make a lot of sense for some holotypes and a lot less sense for others. We waste time when we talk as if MPA o…
Comment linking /application-holotypes/
on “The balance has shifted away from SPAs”Submitted Islands Architecture as a story · 3 points
HN discussionCheck out the islands architecture info, or search around for info on partial hydration. It's similar to how things worked in the jQuery days--you serve up plain old HTML and have a JS function that runs on page load to attach all the event handlers (onclick, etc.) to your dynamic elements (i.e. 'hydrating' the static HTML into dynamic HTML + JS components). The thing with frameworks like Astro is that they try to a…
Comment linking /islands-architecture/
on “Astro: Ship Less JavaScript”Submitted Rome, a New JavaScript Toolchain as a story · 3 points
HN discussionThere's many reasons to have a JS compilation step: - Still targeting legacy browsers like IE11 - Using React / JSX syntax - Using TypeScript - Using other brand-new JS syntax that hasn't trickled out to wider support yet - Using custom JS transforms for libraries like `styled-components` (see this Next.js discussion thread for examples of the many different non-standard Babel transformations that people are using:…
Comment linking /enabling-modern-js-on-npm/
on “Rust Is the Future of JavaScript Infrastructure”Submitted Application Holotypes: A Guide to Architecture Decisions as a story · 3 points
HN discussionAnother good resource to learn about JSX (by the author of Preact): https://jasonformat.com/wtf-is-jsx/
Comment linking /wtf-is-jsx/
on “JSX in detail”Submitted Element Worklet as a story · 2 points
HN discussion> Do you realise that you are talking of a really small minority of what these tools are used for? I absolutely do realise that; but the author seems to ignore them altogether (which is a bit odd, given his normally commendable spirit of inclusion). Contrast this with Jason Miller's (another Googler, author of Preact) guide to different architecture decisions based on different product requirements [0]: [0] - https:…
Comment linking /application-holotypes/
on a deleted threadSubmitted Islands Architecture as a story · 2 points
HN discussionSubmitted WTF Is JSX as a story · 2 points
HN discussionSubmitted Modern Script Loading as a story · 2 points
HN discussionSubmitted Application Holotypes: A Guide to Architecture Decisions as a story · 1 points
HN discussionSubmitted Islands Architecture: A Model for Better SSR/Hydration as a story · 1 points
HN discussionSubmitted Modern Script Loading as a story · 1 points
HN discussion
