midway

> It is possible that an admin changed the title

Still strange. Why should an admin change the submission of a random user if it doesn't breach any of HN's rules?

Maybe because it's not a random submission by a random user?

Guess I must be wrong but would love to hear what that admin who did the change has to say.

While I agree with most what you wrote, I still think that setting up a legal entity is a good first step. Most wannabes struggle with starting. They wait for the perfect idea, the perfect team and so on. They never start. Even if you start with a crappy idea. Ideas will evolve, get pivoted, whatever. My message is about to start and not wasting your time with inactivity like reading random Google Docs by random dudes.

Interesting: The title was changed ('57-Page' was removed) while the comment which classified the prior title as close to click-bait was downvoted.

I didn't know that users could change the title of their submission. How is this possible or is this actually a post by YC?

If latter, a hint would be great that this might be YC promoted content and not actual user content.

Catchy title with strong words ('57-page', 'YC'), no real click-bait but close.

I skimmed the first pages and most of the advice is neither wrong or bad. Still, reading a lenghty 57-note in order to learn is wrong.

You learn by doing. If you want to start something stop procrastinating on HN and execute the first step: found the legal entity for your endeavor. This will keep you busy for the next days, and you learn.

Btw, you don't need to have a good or any idea or co-founder now. This will all come. Just start, make mistakes, stop reading random advice.

Edit: Don't downvote if you disagree, downvote if a comment doesn't add anything to the discussion.

Turn-key ready http2 which is significantly faster.

Not commenting about the transfer but the urge from some to move this to the koajs organization (which is silly request):

Great about koa is that it's not a monoculture like express. express has all batteries included and lacks a healthy ecosystem. Yes, there is a lot stuff out but everything in and around express feels broken. Yes, you can use it and it's ok but you not really happy.

This paired with the same maintainers who also are on connect, express-generator, etc. They do all together a great job maintaining express but you feel the lacking pace in all these project. express still lacks hhtp2 (not turn-key-ready), express-generator is full of strange edge-cases nobody needs (in the www file) polluting your code. express docs got better but still.

But we as a community need healthy competition and if koa-router moved to koajs you'd start the next monoculture and new contenders wouldn't have any chance to establish because there is a default router.

The key to be successful is to build a minimal/barebone product and let others create additions and not swallowing everything into a slow org.

And tbh, I like koa-router but simple stuff like a regex path matching is not included where I need my own middleware (I mean it's a few lines but still).

Everyone who don't like this move, fine, fork koa-router and make it better and we will see if koa-router's new maintainer is a real maintainer who will push the product. Or just write your own router, it's not that hard.

Forking and improving is open source not complaining in dozen threads and pressuring people to hand out a repo (this reminds me of office politics and blackmailing" 'give us the repo or we destroy your and the new maintainer's reputation online'). I think it's more about getting the SEO-relevant Github and npm name 'koa-router'.

So guys, just stop it, welcome the new guy and/or fork, I am happy to yarn add your fork.

> they are only adding static types.

The parent says something different and if it were just about adding types then you need just to add a file to DefinitelyTyped which I guess happened already.

> Next.js is also going to help you with [...] routing

I respect your experience and knowledge but people in this thread say exactly the opposite: Next.js' routing is actually not helping you.

> they started to rewrite the core of Next.js

This is such an important piece of information. Imagine you opt for Next and have to rewrite your app soon. I know, APIs can be backwards compatible and Next's next version will be backwards compatible but there is always something which doesn't work, sending you down the rabbit hole...

> How can that be possible? The DNS lookup takes longer than that and you still haven't even gotten to your site.

Me too. But if you ever did marketing landing pages for products you might know that one landing page is not enough. You need thousands which match to Ad Word campaigns or which are optimized to different SEO fields, domains and whatever. While you still could manage this with Next and nice components, Next's subpar routing might be an obstacle.

> How can that be possible? The DNS lookup takes longer than that and you still haven't even gotten to your site.

I wrote without networking time which includes DNS lookup

Next.js is some over-engineered thing without a proper use case.

If Next.js was good in SEO, nextjs.org would rank well on the search query 'react ssr' but you know what, it couldn't even rank within the top 10. There's nothing, no nextjs dot org, just a Medium article below the fold. Just want to see your face after you convinced your management and your entire team to move to Next and facing how your organic search volume is nosediving...

This whole thing is pure content marketing paired with forum spamming to get people converted to Zeit's products. I am bit surprised that not more 'real users' defend Next.js here, seems like just some maintainers/contributors could show up worshipping Next. This is all too obvious and maybe young devs fall into your trap.

Btw, I know what JSX is capable of and I prefer it over many things but it's not about JSX or pug or whatever. Next.js is abusing a powerful lib/framework for SSR and templating. SSR is much more, e.g. proper routing, read the thread, Next doesn't get routing (the #1 req of SSR) right and wants to do SSR? Sure.