Live data from Hacker News

Things I wish I knew before moving 50K lines of code to React Server Components

mux.com

531–540 of 540 posts

Re: Things I wish I knew before moving 50K lines of code to React Server Components

#531

Earlier quoted context omitted.

yeah, i'm not google of facebook or ny times or whatever, i'm a lone dev in montana what other options did i have?

I am not saying HTMX is terrible or anything. What you've built is cool and I've built something with it. The point I was making wasn't made very well. What I meant was good options are often left out of the conversation because of React, Vue and for a while there, Svelte. There are a lot of great libraries and frameworks that nobody talks about, HTMX included. I just feel like HTMX isn't being hyped because it's goo…

yeah, it is a little unfair

i've tried to produce a lot of technical content, arguing for htmx on its merits:

https://htmx.org/essays

https://hypermedia.systems

but the reality is that marketing is what gets people to that content. I tried for years to convince people on pure technical merit alone, and only made halting progress.

i also got very lucky that a few things all came together at once:

* the primeagen & fireship_dev both covered htmx * we released our book * the twitter algorithm changed to boost funny stuff/memes

Re: Things I wish I knew before moving 50K lines of code to React Server Components

#532

Earlier quoted context omitted.

Well, I've yet to see any web project of that scale survive more than 2 years. What do you think would be a better stack with similar frontend interactivity? (Genuine question, not being snarky)

I have Aurelia 1 apps that have been in production since 2015. They don't need to be really touched. But, when they do, they're really easy to modify. I am currently using Aurelia 2 and will have similar scalable apps that will be in production for years to come too.

Hadn't heard of this one, and checked it out just now. Seems interesting. Thanks for sharing!

Re: Things I wish I knew before moving 50K lines of code to React Server Components

#533

Earlier quoted context omitted.

I don't really buy this argument. Raw CSS/HTML is easier to understand. At the end of the day, all frameworks really do is remove `getElementById` and a couple helpers like `element.style.display`. This does make code MUCH cleaner, but the argument is that raw code isn't easier to understand. I have also had a couple of CSS wizards that wrote all the styles by hand - sounds great until someone has to fix it, even a s…

That’s not totally true though. React, used correctly, lets you use and share a mental model where you have clearly defined the minimum complete information required to display any state of the app, and separately you have a set of simple functions which reliably convert pieces of that data to correct html. That’s insanely powerful and massively reduces complexity in highly interactive apps, because it means you no l…

That's a good addition - I was being reductionist by saying it eliminates a couple of functions that identify and modify elements. With that said, I feel it's still pretty close to being "just that" - I understand the details of everything you listed, but at the end of the day it just keeps track of individual displayed items, if they are parts of objects and regardless of how they are passed in (params, state, context, etc).

Re: Things I wish I knew before moving 50K lines of code to React Server Components

#534
post #517

Earlier quoted context omitted.

Unionize already. It's not just about wage, it's about assigning appropriate work to peoples level and having them progress through the most efficient steps to mastery while also completing billable hours

Normally workers unionize to improve their poor conditions vs an abusive employer, and when they have little to no ability to find another job for similar/better terms. Is that the situation for software devs where you’re at?

That may be common circumstances where a union becomes the only viable option for the workers, but unions have additional benefits that something like it would greatly benefit the software industry.

In particular, it's the assignment of work to the union and then the union is responsible for pairing workers with the assignments which enables the union to create a training funnel where different requirements of the same job can be split among different workers of varying seniority such that apprentices are able to work on the easier items even when there are things beyond their skill involved in the overall work assigned to the union.

Typically a union does primarily exist to create CBAs for wages but this is another function of them which I think would be very helpful for SE and future protection.

So maybe not a traditional union is necessary, but I think there are some functions more or less exclusive to unions right now that would be beneficial to apply to SE. Hopefully that makes sense

Re: Things I wish I knew before moving 50K lines of code to React Server Components

#535

Earlier quoted context omitted.

This is why web development (and python, don't get me started on the pain that is python) is not for me.

What do you code in? For any language if you don't have the toolchain set up, obviously it'll seem laborious to install it, it's not a knock on the framework used on top of the toolchain.

Java/Kotlin. You define where to get the dependencies in a simple script, you define the version of the build tools, a wrapper script fetches the build tools (gradle) for you and that's it. Everything is neatly cached system-wide where possible and on a project-level otherwise. No conflicts, no shenanigans.

Re: Things I wish I knew before moving 50K lines of code to React Server Components

#536

Earlier quoted context omitted.

What do you code in? For any language if you don't have the toolchain set up, obviously it'll seem laborious to install it, it's not a knock on the framework used on top of the toolchain.

But python is already installed on most linux systems

Which Python, 2 or 3? How will you handle local versus global dependencies? Will you use pip, conda, virtualenv or something else? How will you package up the code and/or executable?

It's not as simple as shipping code to the user.

Re: Things I wish I knew before moving 50K lines of code to React Server Components

#537

Earlier quoted context omitted.

What do you code in? For any language if you don't have the toolchain set up, obviously it'll seem laborious to install it, it's not a knock on the framework used on top of the toolchain.

Java/Kotlin. You define where to get the dependencies in a simple script, you define the version of the build tools, a wrapper script fetches the build tools (gradle) for you and that's it. Everything is neatly cached system-wide where possible and on a project-level otherwise. No conflicts, no shenanigans.

You still had to set that toolchain up, which is my point.

Re: Things I wish I knew before moving 50K lines of code to React Server Components

#538

Earlier quoted context omitted.

But python is already installed on most linux systems

Which Python, 2 or 3? How will you handle local versus global dependencies? Will you use pip, conda, virtualenv or something else? How will you package up the code and/or executable? It's not as simple as shipping code to the user.

[dead]

Re: Things I wish I knew before moving 50K lines of code to React Server Components

#539

Earlier quoted context omitted.

[flagged]

I did not flag your comment, if that's what you're implying. I can't downvote comments I reply to and I'm pretty sure flagging has no effect either on such comments. But yes, it's still interesting that you haven't responded to those other comments, as I've said.

[flagged]

Re: Things I wish I knew before moving 50K lines of code to React Server Components

#540

Earlier quoted context omitted.

I did not flag your comment, if that's what you're implying. I can't downvote comments I reply to and I'm pretty sure flagging has no effect either on such comments. But yes, it's still interesting that you haven't responded to those other comments, as I've said.

[flagged]

Yikes! You can't post like this to HN and we ban accounts that do.

I don't want to ban you because your account has been around for a while—but when I look through your history I see so many comments breaking the site guidelines (and often quite badly) that I don't think we have much of a choice. However, we also haven't warned you before, so I suppose it would be fair to start with that.

If you'd please review https://news.ycombinator.com/newsguidelines.html and stick to the rules from now on, we'd be grateful. That means no more personal attacks, putdowns, name-calling, or flamebait—at a minimum. We want thoughtful, substantive, curious conversation. I did see at least one comment on the good side: https://news.ycombinator.com/item?id=37235139, which is a nice proof that you can do this. Please stick to this from now on!

Post reply on HN