chrisweekly

> "SpaceX has the vertical integration to be able to plonk down datacenters and get them powered with literal jet/rocket engines/turbines that they make from scratch"

Is that really a viable path? (Honest question)

Yeah, that's what I figured too. Sadly, that shallow / kneejerk response leads to unearned mindshare advantage for problematic incumbents like Next.js, and risks stifling meaningful improvement.

TanStack Start absolutely merits a closer look. It's not a flash in the pan or "the new shiny". It's the robust, coherent, independent and logical evolution of battle-hardened wisdom and brilliant design and implementation from first principles. See TanStack Router and TanStack Query for more evidence and background context. I've been around the block (25+ years in webdev) and gained a deep appreciation for Tanner's way of thinking. No affiliation, just a grateful user trying to help others notice by amplifying the signal in the noise.

P.S. Yes I wrote ~"it's not X, it's Y". No I didn't use genAI to write here (nor anywhere, ever).

I'd be grateful if whoever downvoted my comment could explain what they found objectionable.

+1 for TanStack Router (and TanStack Start if your needs evolve to merit a metaframework).

I recommend ditching Next.js in favor of Tanstack Start^1, an alternative metaframework that gives you more freedom, better DX, and better defaults. Stick w the best aspects of SPAs and introduce SSR selectively if and when it makes sense.

1. https://tanstack.com/blog/tanstack-start-1-0

FWIW, the original Hitster game is really fun, highly recommended.

mitmproxy is an amazing cli powertool I first discovered over a decade ago (around the same time as lnav). highly recommended.

The idea that "most users" won't notice the absence of 2 slices of bread per day strikes me as unlikely.

That's not quite right. jQuery was exactly the right tool for those of us who knew what we were doing. Browser inconsistencies in the early days were practically insurmountable without jQuery to provide a consistent API surface.

Relying on an LLM's baked-in syntax knowledge is suboptimal, compared to leveraging reasonable context affordances (skills, examples, tool calls, MCP servers, search) to ensure adherence to precise APIs and language specs. Don't get me wrong; a model specifically trained on your desired framework is obviously preferable for more consistent generation of idiomatic code -- but relying on that in a large general-purpose model is a questionable proposition IMHO.

good for you, I hope it lasts another decade+

just sharing my lived experience

you're not necessarily wrong, but science is likely also to continue saving a lot of lives while the endless search for our collective ass continues

into the modern era... ... or back into the dark ages

Synology NAS - an ugly doorstop with data loss resulting from its half-baked post-purchase attempts to enforce hardware vendor lock-in. (Was working fine w/ a Western Digital drive, the next day, boom.)

no doubt (tho I see it as a "yes and")

(meta commentary) really gnarly word choice: "drop" in "they're going to drop the real prices in your lab"?

I took your meaning as "they're gonna drop [a bad surprise on you by raising] the real prices"... so at least it's not quite as tortured as the ambiguous "support for version N dropped today" (where you often can't even infer the direction from context).

this isn't just a tangent, I'm having trouble understanding the point you're trying to make, which hinges entirely on deciding if you meant "drop" literally

I will not stop using good words like those. (We really do need a direct replacement for "trump" in card games, though.)

Thank you for this gem of a comment.

I'm no expert (let alone compared to others weighing in here on HN), but this strikes me as incisive -- and it clearly articulates a logical case (beyond my previously merely instinctual aversion) against such "safety filters" / "nanny" processes. It also resonates with ancient (e.g. Buddhist) ideas about the futility of trying to exert control, such efforts most often being counter-productive.

Yikes.

And right on about disabling auto-correction.

Indeed nothing. Of course the English language is rife with logical inconsistencies; you're attempting to double down on a strawman argument.

Reread my comment and you may notice that "logic and precision" referred to capabilities of the people in the HN community, not characteristics of the English language. Of course (as demonstrated in this very thread), that capability is not evenly distributed.

No, "gonna, wanna, kinda, sorta, coulda" don't count.

Sorry everyone, I didn't mean to feed the trolls.

Wrong.

Thanks for your response. You raise an interesting point, but I take a different view. Contractions _always_ use an apostrophe, while possessives only sometimes do [they're / their, you're / your, he's / his, she's / her, it's / its, ...]. For "it", the apostrophe alone serves to distinguish between the two words.

it's (it is) -> its (belongs to it)

I'm not trying to be pedantic, but they're different words, and (esp. considering how capable our community is when it comes to logic and precision with programming languages) I find it strange how often this "it's / its" error is repeated. Calling it out in hopes of helping others get it right.

In the US, 911 is treated as a generic "emergency" dispatcher. I don't have stats handy but am pretty sure 911 calls are at least as likely to result in an ambulance as a cop (or fire truck).

Node has a bright future. See e.g. Platformatic's "Watt" server^1 for an example of pushing it forward.

1. https://platformatic.dev/ and https://github.com/platformatic#-watt--the-nodejs-applicatio...

This being a motorized vehicle on a pedestrian sidewalk, that "widely understood to be constitutional[ly protected]" is a stretch.

"ACAB" - "All Cops Are Bastards"

(Not endorsing this view, just spelling it out bc I had to look it up.)

Related tangent: earlier today I discovered https://disco.cloud, which may speak to the same audience while focusing more on "self-hosted" PaaS (ie, any VPS) vs scaffolding for AWS/GCP/Azure.

> "understand the debate between spaces vs tabs"

The reason spaces won is that it's not (spaces) vs (tabs), it's (spaces) vs (tabs AND spaces).