Interesting
I wonder if its seems easy because it’s explained simply or if it really is simple to put in place.
I want to make a clone now, just to try. At least for this inspiration, this article was well worth the read. Thanks !
I've built quite a few projects using almost exactly the same stack over the last 15 years. Almost all are still running, those that aren't are for business reasons not technical.
The problem is, they're not exciting The Next Thing real-time javascript somethings, so a lot of devs won't want to use it.
I’m trying to find old software engineering gems and explain them as simply as possible, so I’m glad you found it simple to understand.
Also, it’s definitely possible to make a clone, but the hard part is getting the users :)
You are probably right. The Instagram Engineering blog [0] points to the Fabric documentation on Read the Docs [1] which is empty.
"Read the docs" links to the GitHub repo [2] but it's 404 and even the GitHub organization zwsyff888 is gone.
[0] https://instagram-engineering.com/what-powers-instagram-hund...
To get traction from users is the real challenge.
Unfortunately yes. Scaling is a problem I would love to have :D.
You've got a company paying off influential people in a space where people are looking for guidance, convincing them that they too have hard problems that cannot settle for simple solutions.
Selling the narrative that developers need to be all in on the most irrelevant aspects of building a product, and ignoring the fact that if you instead focus on building simple, easy to maintain software, the fact your LCP isn't hyper optimized by some newly invented mental model for app development won't matter: Google (or any search engine for that matter) will not ignore the fact people just actually want your content.
They do not care how great your web core vitals are if you waste a bunch of time bending over for some irrelevant bullshit problem instead of talking to users and iterating.
So not only are you wasting your time on all the wrong things, you're also gaining nearly no benefit from it
I'm pretty convinced that all these shiny new hotness tools and frameworks of the past decade are actually just meant to sabotage competition and small companies
They introduced the concept of a "server component": one that is rendered once and cannot update state.
And instead of making that opt-in, they made it the default.
—
That is to say, the default of React is to no longer allow updating state in components.
No value proposition is safe from the forces of financially incentivized thought leaders.
I'm not even going to get into how ridiculous it is that the default config chosen was to break people's builds for a feature that isn't mature enough to have anything more than a single reference implementation from Vercel.