midway

45 ms·

1.
by midway 8y ago
> 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
2.
by midway 8y ago
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
3.
by midway 8y ago
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 t
4.
by midway 8y ago
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 l
5.
by midway 8y ago
Turn-key ready http2 which is significantly faster.
6.
by midway 8y ago
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 healt
7.
by midway 8y ago
Interesting read from Dec 2018 [1] about Next.js: SSR throughput of your server is significantly less than CSR throughput. For react in particular, the throughput impact is extremely large. ReactDOMServer.renderToString is a synchronous CP
8.
by midway 8y ago
> 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.
9.
by midway 8y ago
> 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.
10.
by midway 8y ago
> 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 back
11.
by midway 8y ago
> 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. Y
12.
by midway 8y ago
> 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
13.
by midway 8y ago
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
14.
by midway 8y ago
Sorry but I disagree. Just take any of your a bit bigger React projects and transform them to Next or the way around. In. One. Hour. And production-ready please. Good luck, man (this is vendor lock-in).
15.
by midway 8y ago
> prefetching Prefetching is a questionable and a lot discussed feature, do you want to prefetch all the 50 links on my page? Even if you think this a great feature, I am sure the user using your page doesn't like that you abuse his
16.
by midway 8y ago
Then why don't you just use the automatic code splitting of CRA?? And it's not generic, if you ever worked on a years old code base you are happy if complexity is low. Do you know if all the page transition libs will play well wit
17.
by midway 8y ago
This is the wrong question. I use React for SPA use cases and then initial loading time is secondary but I tell you something, my stock React SPA with tons of js and assets has following loading times: DOMContentLoad: 1.08sec, Load: 2.2
18.
by midway 8y ago
Pls check my other comment, anything you add to your code adds complexity and a natural lock-in. Maintainable code is not about adding every lib which crosses your way.
19.
by midway 8y ago
Of course there is a lock-in. Every lib you use locks you in. You don't know how many libs don't play well together. The more code and libs you add to your app the more complexity. It's not hard to write code, it's hard
20.
by midway 8y ago
> Next.js [...] loads a little faster IDK, my dockerized express site loads much faster. At 20ms without network time (and this w/o caching). My real React SPA give you instant (0ms) page loads. Nextjs.org initial load is at 580ms a
21.
by midway 8y ago
Still don't get it. Next.js gives you a vendor lock-in and its features are easily avail w/o Next (eg. automatic code-splitting, this is standard stuff in CRA, why the fuss?). If your business is about SEO then React is the wrong
22.
by midway 8y ago
What I don't get: Either you go full SPA or SSR. And If you go for latter then you can choose any stack, e.g. Rails, express with pug, Django, PHP, etc. Why do people take React's constraints to the backend? No bashing, really w
23.
by midway 8y ago
Man, Moonscript looks amazing, reminiscent of pug/Jade. Anyone experienced Moonscript? How is it, how is the ecosystem, is it fun?
24.
by midway 8y ago
Don't forget that there are also folks writing bad reviews and often not just one. Sometimes they are toxic and got fired for a good reason. We know all these borderliners where everybody wonders how they passed the interviews. So, the