Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

From Gatsby gridlock to Astro bliss: my personal site redesign

jwn.gr

Post reply on HN
Print view View original

61–70 of 91 posts

Re: From Gatsby gridlock to Astro bliss: my personal site redesign

#61

Post by [deleted] »

madeofpalk wrote: post #57
soufianee wrote: post #46

Earlier quoted context omitted.

Remix is backed by Shopify, compared to Next.js being backed by Vercel. Does this influence any decision to take? Today Next.js has a big advantage which is that they have already integrated most of the new React 19 rendering features and apis. I think it will take a while for Remix to catch up to that. Other notable frameworks are community led Waku made by Daishi Kato from Pmdrs and TanStart made by Tanner from Tan…

> Remix is backed by Shopify This makes me distrust it (slightly more than I distrust Next/Vercel). Shopify's core business is not in making javascript frameworks. Remix is always one bad Shopify away from being ejected.

[deleted]

Re: From Gatsby gridlock to Astro bliss: my personal site redesign

#62

Post by com2kid »

swyx wrote: post #43
com2kid wrote: post #38

Earlier quoted context omitted.

> But the bigger lesson is bitterer. Frontend tooling isnt worth that much. This is a modern oddity, as historically front end tooling was worth a lot . During the 80s and 90s, multiple companies made a lot of money off of front end tooling. Even as late as 2009 or so, Silverlight tooling was bringing in money for Microsoft. But think of how popular Flash was and the empire that helped build. Prior to that. Visual Ba…

yes good point. ofc Unity/Unreal Engine today also makes great money. i think those frontends you mention made money because they had defacto monopoly on a certain platform or kind of experience that was unavailable anywhere else. xcode is a piece of absolute crap but i still have to pay $100 a year or whatever for it. perhaps the emergence of web standards - both JS and browser standards - killed frontend. when ever…

> xcode is a piece of absolute crap but i still have to pay $100 a year or whatever for it.

You say xcode is horrible, but have you tried opening a project in Android Studio after 6 months and getting it to compile again?

It was funny, when I was at Microsoft, almost no one used Visual Studio because it wasn't able to handle code on the scale of MS's code bases. (I think things may be different now). That and it didn't support unusual build scenarios (which now it does.)

I wonder if it is the same case at Apple with xcode. Do OS engineers on MacOS actually use xcode to developer MacOS?

Re: From Gatsby gridlock to Astro bliss: my personal site redesign

#63

Post by jwngr »

jama_ wrote: post #60
jwngr wrote: post #55

Earlier quoted context omitted.

Thanks for sharing! I use Fireabse Hosting, which I guess gets grouped in with the other services you mentioned. It's free, has a lightweight devX, and integrates with CI via GitHub actions for preview and production builds [1]. [1] https://github.com/jwngr/jwn.gr/tree/master/.github/workflow...

Right, I didn't consider Google. The 360MB/day of free egress traffic (Spark plan) strike me as very peculiar. But at least it isn't Cloudflare's "unlimited" with secret limits in place, or Netlify's 100GB/month and then enormous costs on everything above. Thanks for reminding me! I'll give Firebase a look. By the way, very minor thing I noticed. Clicking on your photo on the homepage swaps backgrounds, but the timer…

Oh, thanks for letting me know! Looks like I'm not properly clearing the interval. I'll get that fixed.

Re: From Gatsby gridlock to Astro bliss: my personal site redesign

#64

Post by neonsunset »

com2kid wrote: post #54
MikeTheGreat wrote: post #47

Earlier quoted context omitted.

> Even as late as 2009 or so, Silverlight tooling was bringing in money for Microsoft Huh. It always kinda seemed like a "Microsoft's version of , because Microsoft always has to compete with everything, including ". In this case, is "Adobe Flash" I'm curious if people have examples of what it was used for? Looking at the Wikipedia page [1] which says "According to statowl.com, Microsoft Silverlight had a penetration…

Silverlight's real usage was rapid internal corporate app development. Internal tools basically. It is hard to describe exactly how absurdly popular Silverlight was at the time within corporations. Microsoft had a big internal political battle and did the stupidest thing possible and abandoned Silveright, which pissed off a LOT of companies, who then started building internal web apps instead. This lead to a slow mig…

Silverlight legacy lives on in the form of https://opensilver.net. I don't have experience with it, but am going to assume that it's a shadow of the former self.

They do have a pretty cool demo project however: https://xaml.io

Re: From Gatsby gridlock to Astro bliss: my personal site redesign

#65

Post by kcrwfrd_ »

toinewx wrote: post #14

Cannot use React UI lib with Astro such as Mantine. With Gatsby it was possible. Astro is MPA while Gatsby provided SPA-like navigation. That's why Astro is not really a replacement.

You can achieve SPA-like navigation in Astro with their transitions API, but if that’s what you’re after it’s better to use Next.js or Remix IMO.

(I helped build playboy.com/magazine with Astro, which uses the transitions API for this SPA-like behavior… as well as playboy.com/app (nsfw) with Next.js)

Re: From Gatsby gridlock to Astro bliss: my personal site redesign

#66

Post by kelnos »

swyx wrote: post #5

I am still not over the collapse of Gatsby (for reference i nearly joined the company in 2017, was saved only by my own character flaws). They rode the highs - being the default docs tool for React, and building a massive ecosystem of integrations you could install out of the box. But too many abstractions, divided goals between cloud and OSS, and the better stewardship/design of Nextjs brought it down. There were th…

> Frontend tooling isnt worth that much.

Is any tooling worth that much, really? I think the key is that backend tooling lends itself to selling hosted solutions, while frontend tooling is usually stuff you run locally or on CI to build artifacts. Sure, there are exceptions, but most people don't pay for developer-focused software anymore, at least not directly.

Re: From Gatsby gridlock to Astro bliss: my personal site redesign

#67

Post by mmckelvy »

mind-blight wrote: post #35
mmckelvy wrote: post #17

Earlier quoted context omitted.

My bet is on Remix (which will eventually just be React Router). I think it's just the right amount of abstraction over native web functionality with a nice, simple API that doesn't deviate too much from web standards. I also think the full stack approach just makes sense for developing on the web.

I'm a huge remix fan. Remix, Shadcn, postgres, and Prisma have been great for rapid development

Agreed, minus the Primsa.

Re: From Gatsby gridlock to Astro bliss: my personal site redesign

#68

Post by victorhooi »

swyx wrote: post #5

I am still not over the collapse of Gatsby (for reference i nearly joined the company in 2017, was saved only by my own character flaws). They rode the highs - being the default docs tool for React, and building a massive ecosystem of integrations you could install out of the box. But too many abstractions, divided goals between cloud and OSS, and the better stewardship/design of Nextjs brought it down. There were th…

I'm probably a bit out of the loop her - but you referenced Gatsby's collapse?

Did something happen to them, in the community or project?

Googling, I saw that they were acquired by Netlify in early 2023 - but not much concrete beyond that?

Re: From Gatsby gridlock to Astro bliss: my personal site redesign

#69

Post by mmckelvy »

soufianee wrote: post #46
mmckelvy wrote: post #17

Earlier quoted context omitted.

My bet is on Remix (which will eventually just be React Router). I think it's just the right amount of abstraction over native web functionality with a nice, simple API that doesn't deviate too much from web standards. I also think the full stack approach just makes sense for developing on the web.

Remix is backed by Shopify, compared to Next.js being backed by Vercel. Does this influence any decision to take? Today Next.js has a big advantage which is that they have already integrated most of the new React 19 rendering features and apis. I think it will take a while for Remix to catch up to that. Other notable frameworks are community led Waku made by Daishi Kato from Pmdrs and TanStart made by Tanner from Tan…

Shopify "backing it" means less to me than the maintainers themselves. The Remix maintainers are straight shooters and have been maintaining open source consistently for over a decade now.

I also just like their API and design decisions.

Re: From Gatsby gridlock to Astro bliss: my personal site redesign

#70

Post by theflyinghorse »

kelnos wrote: post #66
swyx wrote: post #5

I am still not over the collapse of Gatsby (for reference i nearly joined the company in 2017, was saved only by my own character flaws). They rode the highs - being the default docs tool for React, and building a massive ecosystem of integrations you could install out of the box. But too many abstractions, divided goals between cloud and OSS, and the better stewardship/design of Nextjs brought it down. There were th…

> Frontend tooling isnt worth that much. Is any tooling worth that much, really? I think the key is that backend tooling lends itself to selling hosted solutions, while frontend tooling is usually stuff you run locally or on CI to build artifacts. Sure, there are exceptions, but most people don't pay for developer-focused software anymore, at least not directly.

Sure. There are several companies selling paid JVMs and corpos gladly pay them a lot of money.
Post reply on HN