shivawu

On the other hand, I consider v8 the most extreme optimized runtime in a weird way, in that there’re like 100 people on the planet understand how it works, while the rest of us be like “why my JS not fast”

The other thing is.. installer generally only runs once on a single machine, not sure how useful it is to “show the changes since last run”

Obviously the article is making valid points. But a recent epiphany I had is, things by default are just mediocre but works. Of course the first shot at this problem is not going to be very good, very much like the first version of JavaScript is a shitshow and we’ll take years to pay down the technical debts. In order to force a beautiful creation, significant effort and will power needs to be put in place. So Id say I’m not surprised at all and this is just how the world works, in most cases.

I agree except I think 100 lines is definitely worth a method, whereas 15 lines is obviously not worthy for the most cases and yet we do that a lot.

My principle has always been: “is this part a isolated and intuitive subroutine that I can clearly name and when other people see it they’ll get it at first glance without pausing to think what this does (not to mention reading through the implemention)”. I’m surprised this has not been a common wisdom from many others.

Am I right to say that this is a template on top of cloudflare durable objects, not an actual software of its own?

This is I believe how ziglang works on its asynchronous story

Yeah this is exactly what I ended up doing, like two days ago. It’s quite a pitfall… (and not optimal in terms of performance)

Exactly this. This incident has proven MSFT’s strong hands without a board seat and they don’t really need it if things do/did go off the rails.

How does it work with nodejs? Iirc they don’t support ebpf

Engineers at small startups are generally founder minded. They’re like founders, and are passionate about the product and the problem. That’s how they get to decide/involve in the decision about what to work on

Thanks for replying!

Another question is, what motivated you to start this effort in the first place? And why do you think it's useful. I haven't read the book, so not really sure

Great job! How long did you spend on writing the book?

What you said makes sense, but only to limited set of people.

Not all people are interested/capable of learning how it works underneath. There're like, I don't know, hundreds of thousands of React developers in the world, very few of them understand how React really works underneath.

This is actually one of the goals that React was invented and popularized inside Facebook. It's just sooo easy to pick up and start building.

That being said, for our product, it's not only about React and its basics. We can totally create a workout project for React internals. That depends on what you guys need :) We started with these two projects because it seems a common useful and popular thing, and we're able to do them ourselves.

Pay to get work! That's one way to phrase it, I'll remember that, LOL

The first part makes perfect sense.

> That said I don’t often get asked for source code during interviews these days, so probably the ability to host the minified code for a demo would be enough.

I'm a little bit confused about this piece. Are you suggesting we host the minified code on our site + the demo? Because in the first part, I thought you wouldn't want that because employer should see this as a tutorial thing if they see anything on a third party website other than your own website?