purplerabbit

Posted on another thread and haven’t heard an answer, so I’ll post it here too… Serious question: how do you refactor code when using nesting? In my experience it makes styles impossible to audit.

Serious question: how do you refactor code when using nesting? In my experience it makes styles impossible to audit.

These are all valid. However, if only nuclear can get us past "bottleneck events" (e.g., oil supply chains falling apart due to deglobalization or the world's oil running out, either of which would (or possibly will) cause catastrophic effects), then that supersedes #2 and #3, and probably #1 as well in most analyses.

I'm not well-versed enough in hard evidence to assert that we absolutely need nuclear to make it through bottleneck events. But it's plausible that we do. And so we shouldn't rule it out unless there is high-certainty evidence we don't need it.

In other words: I think the burden of proving that nuclear is unnecessary is on the anti-nuclear crowd. I've heard plenty of arguments that wind/solar will be enough, but haven't seen an analysis that seems to prove it based on numbers. (If you know of any such analysis, please share!)

Seamless runtime checks are fully supported via zod.

https://github.com/colinhacks/zod

You’re welcome.

(I use this library every day. It has changed my life.)

You’re right on the first (although classes are out of fashion, so this is low impact)

On the second, doesn’t this work?: ‘function foo({ bar = 3 }: { bar?: number })’

There were two official music videos for this song. This is the one I prefer :)

This piece reminded me of this music video: https://www.youtube.com/watch?v=WjNssEVlB6M (it's a bit slow but the visuals are great)

The overmedicalization of death is a giant ethical problem that we haven’t developed the culture to healthily deal with.

If you haven’t read the book “Being Mortal”, I would highly recommend it. It addresses how to approach death from a perspective that combines existential and medical issues. It’s one of a very small set of books that should probably be required reading for all of humanity

Probably both in advising Apple, and in sculpting the thoughts of many people replying to this story

In the end, the heat death of the universe is the only story that matters

Yes.

Only tangentially related: does anyone else have the sense that GraphQL is fancy, modern SOAP?

Realtime is undoubtedly the dream... What restrictions or limitations are present for live queries?

Cognitive overload. Storing 3-4 succinct variable names in your head takes the same energy as storing 1-2 verbose variable names in your head.

Leveraging massive libraries is not "from scratch".

Another thought: You are on HN, so you probably prefer Unix to Windows. Why do you think that is?

It's worth gluing together 1) so everything is explicit, 2) you don't have to write all of the schrodinger's cat "if executing on client, x, else, y" logic inherent in SSR frameworks, and 3) you can avoid Next.js's slowness

You're right on the tone. I've edited it to make it less negative.

Both popular SSR frameworks (Next.js + Remix) break the Unix philosophy, and Next.js + Blitz.js is the opposite of the Unix philosophy. (You might think that this is worth it, and you may even be right, but it's something to consider.)

Want a better React stack? Try React + tRPC + Express + Prisma. Each component can be easily swapped out and understood independently (sorry Next.js / Remix), all routing is explicit (sorry Next.js / Remix), development startup time is fast (sorry Next.js), and you still get e2e type safety + minimal boilerplate. I like to call this stack the "NF" stack: "No Framework".

The fanboys will complain. "What about SSR?", they will say. Well, here's the solution: quit fretting about SSR. Your signed-in customers will gladly take 0.05 seconds extra render time for the extra features your devs will be able to deliver after you ditch your complicated SSR framework. Want to do SEO? Make a WordPress site and "SSR" it with Simply Static[0]. Your site will achieve the theoretical minimum Time To First Whatever, your marketing team will be free to actually do their job rather than spending 2/3 of their time trying to get devs to update the landing page, and your devs can move on to something more useful (like creating useful features. Isn't that supposed to be the goal?)

/rant

[0] https://wordpress.org/plugins/simply-static/

(edited to remove some unnecessary negativity)

Terrifying. Please link the story if you can find it!

Two ideas: 1. If you can borrow at 2 or 3%, it might be worth it to keep cash-on-hand so you can jump on unexpected opportunities that may arrive in the future. 2. Paying dividends makes stock price go down. So it's basically equivalent to deciding to sell a small percentage of shares on behalf of each of your investors. Which is why fewer companies are worrying about dividends

Same.

Yes, it was also a hallucination, as other commenters have pointed out. But if you allow yourself to be affected by ideas, or art (i.e., synthetic visual or audio experiences), shouldn't you be open to being affected by a unique positive experience generated by your own specific mental architecture? Almost definitionally, it's possible that such an experience could impart you with something more meaningful than something generated externally.

Also, to other commenters: such an experience is obviously very difficult to communicate about effectively. It was formulated by and for your own brain, and so will be hard to translate effectively to a different architecture.

I don't understand why everyone in this thread is being so pedantic, accusing Hetzner of "lying", etc.

If you are subscribing to something and the subscription price changes, that's not "lying", that's one party renegotiating. Furthermore, Hetzner's legal agreement allows them to do this.

Sure, Hetzner could publish "up to X TB / month" (and it sounds like it should considering their apparent audience). But let's have a little empathy here, sheesh.

Why would you assume that conservatives are the ones spooked about unattended children?

This is an opinion that’s risky to have because at a superficial level it’s not oriented enough around “save the children”. But there’s some good evidence for it. There’s some great analysis in “The Future of Capitalism” by Paul Collier if anyone is interested in a deeper look

I've experienced with this with racquetball strangely enough, and my brother tells me that he regularly experiences this with playing the piano.

(This makes me terrified of the degree to which programming has affected my way of thinking, considering I've spent 100x as much time doing that as playing racquetball.)

No affiliation. Haven't investigated much yet, but I'm blown away by the prospect of "standing queries" that you can subscribe to.

It looks like this could provide many of the benefits of Flink/Spark/ksqlDB with much less complexity.

Great insight. Without this approach, A/B testing could be used to generate an infinite stream of meaningless work

I don’t. Because it’s not worth the hassle, as explained in my comment.

If I did want to avoid it I could send html for a generic loading state in my base html template, which does not require ssr.

If you’re using Wordpress or static site generators for your public facing pages you won’t have the flash, and if your user is invested enough to have made it past the landing page the flash will be a non issue anywhere else.

I'm sorry people are downvoting, because you are correct.

SSR (by which I mean Next.js) is the most over-invested in JS tech of all time. It introduces a bunch of crummy DX which never pays for itself from a business standpoint.

SSR is only potentially useful for landing pages. In which case you should be using Wordpress or something like Wordpress so you aren't wasting dev resources on something a marketing team should be doing. (If your argument is that SSR is necessary for speed, I'm pretty sure exporting your Wordpress site to static HTML + CSS and using Cloudflare could more than make up for the difference.)

The one asterisk I'll add to this is that SSR in the form of the Remix framework may justify its own existence as it removes the need for an explicit API layer, which lets you skip a ton of boilerplate code. This is a big win. The fact that Remix uses SSR is just an implementation detail -- it's the DX that's actually valuable (although SSR fetishists will probably still like it, too.)

There’s definitely some fairness to your callout. To make a long story short, I was once quite invested in the genre of literary fiction, and eventually became disillusioned when I realized I had been sucked into a prestige game. My old bitterness comes out in my comment

Social media posts may be bad for you brain, but my personal opinion of Gravity’s Rainbow is that ~everyone who “enjoys” that painful slog does so because of the “literary” status “enjoying” Gravity’s Rainbow affords them