HNHacker News
TopNewBestAskShowJobs

nickreese

1,430 karma · joined August 31, 2009

Current:

* https://nicholasreese.com old blog.

Background in marketing, js, front end dev, and SEO.

Now working on a new side project and advising startups.

Email: nick[at][pickawebsiteabove].com

submissionscomments
nickreese··on How I built a modern website in 2021
This seems insanely over-engineered.

Yet, look at the source and the first thing that pops out is:

  // this is a temporary solution until I can figure out a safe way to do this on the server
  if (window.location.protocol === 'http:') {
  window.location.href = window.location.href.replace('http:', 'https:');
  }
nickreese··on Cloudflare's Disruption
I was referring more to the context that the CEO is “one of us”, he is regularly on HN, and is available via Twitter/email to constructive criticism. I interviewed with CF earlier this year and ultimately decided the timing wasn’t right.

Love the company but the touch that the CEO gives a ____ really matters to me.

nickreese··on Cloudflare's Disruption
I love this so much. THIS is why CF is one of the only companies I'd ever consider working for.
nickreese··on Red Ventures has turned very specific advice into very big business
I may have linked to the wrong one. They have 2 active owned via AllConnect patented by Glenn Goad. One is zip code availability lookup/search and the other is address level search for availability of services. They also have a 3rd more aggressive one that the patent examiner gave them headaches over and they ultimately abandoned.

—-

We were sued in 2018. My knowledge of their patents is from then. They may have abandoned some since then.

nickreese··on Red Ventures has turned very specific advice into very big business
RedVentures is pretty much the 1000lb gorilla in SEO lead gen. They also have a pretty large patent library and aren't afraid to use it. This includes a patent on zip code search which our last startup was on the receiving end of an infringement claim.[1]

If you are a reporter or investigative journalist I'd encourage you to do some poking around into the business model behind APlaceForMom.com and the FTC action to spin off Caring.com and the overall effect on the nursing home industry.

I can go on a major rant about RV, their moves to rollup the majority of the lead gen industry but due to prior legal interactions with them I'll refrain from painting a target on my back any further than I have.

---

[1] https://patents.google.com/patent/US20140149249A1/

nickreese··on Lessons from Building a Static Site Generator (2020)
Good question. Hydration is where Javascript is rendered statically or on the server and the client needs to take over that HTML.

Traditional frameworks like Next.js, Gatsby, Nuxt.js all "fully hydrate" the client.

This means that every bit of HTML that is sent to the is browser is taken over by JS on the client.

This has it's costs but it is done to give interactivity.

Partial hydration is where you are only adding interactivity to the parts of the site that need it... think of it like the good old days of jquery but with a modern front end framework... Svelte.

nickreese··on Lessons from Building a Static Site Generator (2020)
Author of the post. This is really an interesting take on shortcodes. I've been struggling with a format that the svelte compiler likes and can be used in markdown. This may be the answer.

> <embed-youtube id="123asdf4"></embed-youtube>

Thank you.

nickreese··on Lessons from Building a Static Site Generator (2020)
Not arguing that. Updated the article template to keep others from getting infuriated. ;)
nickreese··on Lessons from Building a Static Site Generator (2020)
Hey, author here. I banged this out quickly and didn't update the template to include the date as an oversight. It was written in Nov 2020 as shown on the homepage.
nickreese··on Lessons from Building a Static Site Generator (2020)
Author here. At it's core most static site generators are just fancy "string concatenation" tools.

In my experience playing with several generators before building Elder.js it isn't so much about the output that matters it is about how the static site generator lets you do non-trivial customization. Things that would be hard without a larger framework.

More importantly, when building a major project on a static site generator, it is important to have an upgrade path beyond a static site generator should you require it. Elder.js was built with that use case in mind though I didn't cover that in the article.

Being able to move to SSR should the project require it is a huge plus in my book.

nickreese··on Lessons from Building a Static Site Generator (2020)
Shortcodes as they are implemented in Elder.js (what the article is about) are borrowed from WordPress. Basically they are a placeholder such as [[lastestTweet/]] that let you add dynamic content into otherwise static content.

While Elder.js does allow for full server side rendering making "Javascript the backend" the goal of the static site generator is generate static HTML/CSS/JS that can be hosted from a CDN, S3, or other static host.

That said, one of the biggest pitfalls with building a major site on a static site generator is there is often no upgrade path to server rendering. Elder.js does offer that out of the box.

nickreese··on Lessons from Building a Static Site Generator (2020)
Hey all -- Author here. This was a reflection on building Elder.js.[0]

Happy to answer any questions. I'll be going through and adding context to the questions I see.

[0]: https://elderguide.com/tech/elderjs/

nickreese··on Neeva Announces Public Availability of Its Ads Free, Private Search Engine
The main problem with search today is the lack of organically appearing "curation" found on the early internet.

Today everyone knows the value of a link, so it curation via links doesn't happen organically any more like it used to... yet this is still a major/the primary part of Google's Search results.

Until the "curation problem" is solved I am not hopeful of a search engine producing excellent results like Google did before 2010.

Stoked to try this out, but teaching a machine to curate is hard.

nickreese··on Micro APIs for Everyday Use
Really surprised this is the first I've seen of the idea for an API marketplace that seems to get the developer UX right. Would love to be an investor in this idea.
nickreese··on D3 7.0
This x1000. D3 is such a great tool. Just the scales/coloring/map project libraries would be impressive standalone. D3 is incredible.
nickreese··on Astro: Ship Less JavaScript
Elder.js supports Islands with SSR. It is also MIT. I released it as an SEO experiment as much as anything else.

I’m enjoying the dev process and am committed to facilitating (myself or paying another) it’s maintenance for several years. I can do that because my prior successes can subsidize the cost.

If I had to do it again, I’d probably pick another license. As a first time maintainer of a project that is hitting the pit of success it is amazing the number of for profit companies taking the framework and demanding changes to suit their narrow business cases.

I literally LOL at some of the emails. I very much think the state of OSS isn’t sustainable. It has been an interesting rodeo.

nickreese··on Astro: Ship Less JavaScript
Hey Elder.js author here. Only browsed their docs but here are the things that stand out in very quick read:

- Framework agnostic but uses their own .astro language/filetype. Elder.js is Svelte only.

- Both support partial hydration and they appear to offer similar options as Elder.js

- Elder.js’ target isn’t building a small site but a large one. So data flow and making the data model pluggable via hooks and plugins really makes this possible in a way we haven’t seen other framework approach it. We’ve heavily dogfooded Elder.js for building major SEO assets. Fetch as the main way of getting external data in Astro where Elder.js leaves that up to you and gives you complete control allowing various database or filesystem sources.

- Unclear on their build process.

- Elder.js is express middleware (SSR) and a static site generator. Astro appears to just be a SSG. (Some of our sites are outgrowing SSG so the flexibility matters).

- No shortcode support, hooks, or plugins.

My take is that Astro might be a good fit for simpler use-cases but may stumble when you need more control or go against their model. Elder.js has similar opinions but tries to put you in full control. That comes at a complexity cost which Astro appears to do a good job of simplifying but I’d need to dig in deeper to see what tradeoffs were made in order to make things simpler.

Happy to see more people taking partial hydration seriously.

Edit: formatting

nickreese··on Ask HN: How to cope with the death of a dear person?
Thank you for this. This is the clearest way I’ve seen my approach to grieving spelled out.
nickreese··on Ask HN: What are some tools / libraries you built yourself?
Elder.js, an SEO first, Svelte framework and Static Site Generator. [0]

Lots of SSGs existed but none supported Svelte and I wanted partial hydration when people said it was impossible.

[0]: https://elderguide.com/tech/elderjs/

nickreese··on Elder.js – An Opinionated, SEO Focused, Svelte Framework
In front end JS frameworks there is a tendency to render your site on the server, then also ship JS to the client which then takes over the rendering of the page and adds interactivity.

As you can guess this adds a lot of overhead.

Partial hydration allows the developer to specify which parts of the page have interactivity and only those parts of the page are made interactive.

nickreese··on Elder.js – An Opinionated, SEO Focused, Svelte Framework
Try the latest version pushed today. V1.4.0 moved the dev server into the rollup config and it should be a lot smoother.
nickreese··on Elder.js – An Opinionated, SEO Focused, Svelte Framework
Yep. That’s the story. :)

Lots of Svelte users asked how I built the site so I figured it was worth open sourcing.

nickreese··on Elder.js – An Opinionated, SEO Focused, Svelte Framework
Elder.js is designed to render the entire site at a time. 100 pages should take substantially less than 10s in most CI/CD pipelines.

We refer to what you are looking for as incremental builds and it is honestly a pretty difficult problem as it requires tracking data dependencies. Here is an overview of the complexities. [0]

[0] https://github.com/Elderjs/elderjs/issues/8

nickreese··on Elder.js – An Opinionated, SEO Focused, Svelte Framework
There is a community plugin for i18n: https://github.com/kiuKisas/elderjs-plugin-i18n
nickreese··on Elder.js – An Opinionated, SEO Focused, Svelte Framework
Nope. It generates a fully static site with HTML, CSS, JS that you can deploy with any static host. (s3, netlify, cloudflare workers)
nickreese··on Elder.js – An Opinionated, SEO Focused, Svelte Framework
Hey, it's an SEO framework. :) Decided as an experiment that links should go to the SEO project that spawned the framework.

So far the links from the JS ecosystem seem to be confusing Google's algos, but we'll give it more time to see how it plays out.

nickreese··on Elder.js – An Opinionated, SEO Focused, Svelte Framework
To be honest, I've only briefly played with SvelteKit as it still isn't finalized.

Here are the main parts where Elder.js stands out

pros:

* Purpose built for large sites with SEO in mind.

* Hooks and plugin ecosystem for common issues. Responsive images, sitemaps, critical path css, etc.

* 0kb JS and partial hydration.

* Blazing fast builds.

* Async shortcodes make working with and future proofing static content a breeze.

cons:

* The complex Rollup implementation needed for partial hydration leads to less optimal dev experience. HMR isn't a possibility as it currently stands. Until `esbuild` is stable reloads won't be as fast as with Vite.

* Unfamiliar way of handling routing / no dynamic routing. (PR to simplify this is basically done [0])

* No client side routing.

* Less optimal for "apps" and logged in experiences until this PR is merged. [0] This should happen in the next week.

---

[0] https://github.com/Elderjs/elderjs/pull/130

nickreese··on Elder.js – An Opinionated, SEO Focused, Svelte Framework
To be honest, I'm not familiar with the specifics of the benchmark. I was surprised as well.

Currently I think the biggest limiter for small sites is that we sequentially fork the processes and wait for each to bootstrap.

I'm sure we could eek out a huge gain by rewriting it and optimizing, but at this point it is faster than anything else in the ecosystem and throwing more CPU cores at a problem is cheaper than throwing more development hours at the problem. :)

nickreese··on Elder.js – An Opinionated, SEO Focused, Svelte Framework
I get what you are saying.

In that example most of it was waiting on the remote database. (I’m ans SQL newb).

That said, Elder.js makes it easy to see what is causing performance hits with full perf tracking.

These days that same site is 1 min 22sec.

nickreese··on Elder.js – An Opinionated, SEO Focused, Svelte Framework
Yep. :) Though I often laugh at the thought of seniors using a cutting edge JS framework.
← PreviousPage 3 of 7Next →