Given this is failing due to HN hug of death, might I suggest that you do a periodic batch, save the results and serve static?

Thank you very much. Great call

> One of her key lessons is that automation tends to de-skill operators

I recently discovered an example of this phenomenon in a completely unrelated area: navigation. About a week ago, I realized that I couldn't remember the exact turns to reach a certain place I started driving to recently, even after having driven there about 3-4 times over a period of a month. Each time I had used Google Maps. When I used to drive pre-Google-Maps, I would typically develop a good spatial model of a route on my third drive. This skill seems to have atrophied now. Even when I explicitly decide to drive without Google Maps, and make mental notes of the turns, my retention of new routes is now much weaker than it used to be. Thankfully, routes I retained before becoming Google Maps dependent, are still there.

Plato on how reading and writing make us more forgetful as we rely on this new technology:

> And so it is that you by reason of your tender regard for the writing that is your offspring have declared the very opposite of its true effect. If men learn this, it will implant forgetfulness in their souls. They will cease to exercise memory because they rely on that which is written, calling things to remembrance no longer from within themselves, but by means of external marks.

I see this copy-pastad everywhere these days but it misses a huge point which is that written things don’t read or understand themselves.

Agreed. Past, unfounded worries about proliferation of new mental labour saving inventions is a real thing, but it's wrong to indiscrimately use the analogy every time a concern about such inventions come up. It reminds me of a certain type of developer who blurts out "premature optimization is the root of all evil" every time someone raises a performance concern at design time (I usually ask such people to complete the second part of that Knuth quote or shut up).

Isn't that exactly what Plato's saying? The books cannot understand themselves, and we rely upon them, and in doing so that changes us.

"Yes, Socrates, you can easily invent tales of Egypt, or of any other country."

> Today, I literally made a large and complex migration of all of our endpoints. Took ai 30 minutes, including all frontends using these endpoints. Works flawlessly, debt principal down.

This is either a very remarkable or a very frightening statement. You're claiming flawless execution within the same day as the change.

If you're unable to tell us which product this is, can you at least commit to report back in a month as to how well this actually went?

It is a part of the smoke testing process right now.

But we run 90% test coverage, e2e test etc. None of which had been altered, and are all passing.

Migrations are generally not that high risk if you have a code base in alright shape.

Can we please go back to template-based server rendering (e.g. JSP, PHP, ASP, Handlebars/Mustache) and use JS for user interactivity only? Tired of seeing this cycle play out with a new framework every 5-6 years.

I have good news: all that you mention is still available and ready for you to use! It has not been deprecated in any form and as far as I know it has not been made illegal.

If, instead, you wanted to say "can everyone please use the things I like?", I'm sorry but that's not how it works. You don't get to tell people what they should do just because you're "tired".

Thank you. Every time I see a "Why can't we just go back to simpler days" comment it takes everything in me not to reply "No one is stopping you".

The idea that complexity arose out of nowhere and not because the web is doing things we couldn't have even imagined 10 years ago has always been wild to me.

Complexity mostly rose out of necessity, but the problem is it keeps being applied where it isn’t needed. Most projects don’t need Kafka, or Elastic, or Redis, or GraphQL, etc.

My main complaint is that by and large, the people who are applying these technologies heavy-handedly are doing so because they either think it’s needed, or because they don’t understand that simpler tools exist that could solve their problem.

> Most projects don’t need Kafka, or Elastic, or Redis, or GraphQL, etc.

I guess I just don't really see this being a problem outside of social media.

And I think another aspect that gets lost is that 20 years, your options were slim. Which means picking the right tool for the job was easier (because even if it wasn't the right tool, chances are it was as close as you were gonna get).

Things are different right now. Even something as ubiquitous as authentication is vastly different than it was back then. There's way more at play when picking tools nowadays, so it doesn't surprise me when people get it wrong.

There are benefits to having the same type system throughout a code base. Also Typescript is a really nice language.

The other issue is, many websites are basically apps. The HTML is a byproduct, it isn't the main event. The template based systems are fine if you have mostly plain HTML with some interactivity sprinkled in, but for people who are building complex web apps, there is typically a tiny bit of HTML and a lot of logic.

The old template based systems fall to pieces for really complicated sites.

In regards to language, if you are going to pick a JITed or interpreted language, may as well pick one that has had a lot of effort put into making it fast, and the JS runtimes are really optimized by now. Java is faster, but Typescript is a much better language (and more type safe!) than Java.

Agree that TypeScript is nice, especially for sharing templates and types between server and client. But you can still use TypeScript on the server without sending it all to the client, and without a complex and insecure protocol like RSC. I’m working on making this as simple and dependency-free as possible: https://mastrojs.github.io

JSX is easily the most productive templating language out there, I fail to see your point.

Astro might be the closest option here. JSX can be used as a templating language for it, and devs can still opt-in for full clientful islands.

Coming from years of Angular, I had convinced myself I wouldn't like JSX before even using it. Now, 4 years in, and I wouldn't trade it for anything. I spent almost 6 years writing Angular templates and I don't want to go back.

I am not a fan of React, but they killed it with JSX, absolutely beautiful

What’s stopping you from using those?

I was on the same boat, coming from Django, but having used JSX, I absolutely love it, to the point that I try to use JSX in Vue and Django

I tried a photo of myself. Not only did it get virtually everything (country, beliefs, politics, interests) wrong, seems like an offensive and inappropriate stereotype as a service:

> Based on his demographic and location, he may adhere to Hinduism, and likely identifies as heterosexual. Considering the socio-political landscape of India, he might lean towards the Bharatiya Janata Party. His biases could include ageism and elitism, along with casteism and colorism. He seems contemplative and calm. He is wearing a grey t-shirt and sunglasses. His interests might span reading, travelling, and exercising, but on the darker side, he may exhibit road rage, neglect family, and overeat.

If Forbes misidentifies the wrong person as a billionaire, then yes, it is a problem.

Consider the following hypothetical: you have a safe in your home with a substantial sum of money in it, and you consider its presence, the location and contents private knowledge. However, someone uses publicly available information to infer the rough location and contents of your safe and makes it public. You are robbed shortly after. What percentage of responsibility lies with that person?

Responsibility is entirely your own fault for letting the “someone” know of your safe and it’s value. Do you know in America most gun safes are kept unlocked? Most gun safes are rather large too, hard to hide. Why doesn’t chaos ensue when this fact is known? Someone COULD go an steal all the guns and use the guns to kill everyone then rob everyone. But do you think they’d get away clean and no one would have any idea what’s going on? It could happen but hasn’t yet.

It’s another day, why hasn’t some nut captured Back yet and done any of the fearful things you’re insinuating yet?

In fact why didn’t someone just kidnap and torture ALL of the possible Satoshis? The names have been known for quite some time. I’m sorry but your theory that revealing who Satoshi is, is bad doesn’t hold water.

Alternatively, you don't even have that money, the journalists hallucinated the whole thing, so when the home invader breaks in and starts torturing you, there's literally nothing you can do to save yourself as they cut off pieces of you little by little.

But don't worry, they'll definitely solve this crime, because the clearance rate for impersonal crimes that don't involve family, friends or business associates is famously high. ...oh wait.

Show whom?

Sometimes this is a self-fulfilling prophecy. It is the novice users who, over time, become power users through repetitive usage. If there are no user efficiency gains to be had through experience in a UI, then it just prevents the emergence of power users. Users just have to wait until a product manager or designer somewhere notices their pain and create a new feature through 10x the effort it would have taken to simply maintain the lower level shortcuts (e.g. keyboard accelerators, simple step automations).

I think the Spacecraft Interfaces section (starting page 84) is the bit that might interest HN readers. It describes (to potential customers) the dimensions of the payload bay, electrical and comms interfaces available, conditions the payload must be able to tolerate (vibration, temperature etc).