Live data from Hacker News

Why I Don't Use React Router

jkk.github.io

61–70 of 79 posts

Re: Why I Don't Use React Router

#61
post #3

It's great to someone express this point. Though it's hard to beat the convenience of dropping someone else's library into your codebase, each new dependency adds more security surface area and bloat to your application. I wish people considered this balance more carefully. In general I think a littlw NIH is a good thing. Even if there exists a library that does what you want, it might also include much more that you…

An idea of open source is that it's very likely that your own implementation is buggier, slower, and more poorly specified than the existing state of the art open source implementation. https://en.wikipedia.org/wiki/Wisdom_of_the_crowd https://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect

Yes, but if my version only has the features I need. Then it's lighter and most probably faster. Since OS tends to support a smorgasbord of usecases it's more often than not bloated and unnecessarily complex when used.

Re: Why I Don't Use React Router

#62
post #49

Earlier quoted context omitted.

What if there is a breaking change in lib3 and only lib2 upgrades? Does that mean lib1 can just never be used again because of something lib3 did?

If a new version of lib2 moves to a half-baked version of lib3, I want to stay on the old version of lib2 (and lib3) until the community agrees that the lib3 change is good and everyone has migrated to it. Having two different versions of lib3 in process is begging for bewildering bugs, and it was a serious mistake for npm to let that happen (much less by default!)

While I'm not defending running multiple versions of a library, I've never seen it cause bewildering bugs, or any bugs at all. The deeply nested style of npm may have issues, but it makes it really easy to avoid thinking about dependency problems.

Re: Why I Don't Use React Router

#64

I really need to get my blog up and running so that I can write about things like this. My view is that dependencies are someone else's solution to my problem of technical debt. I'd be a straight-up liar if I claimed to be proud of every line of code I've written, either for an employer or for myself. Sometimes you just have to hammer a square peg into a round hole and be done with it because deadlines. Or lazy. Or b…

[deleted]

Re: Why I Don't Use React Router

#65
post #58

Earlier quoted context omitted.

I didn't get my blog up and running until I a) started keeping a journal on 750words.com and b) started writing in a spiral-bound notebook every spare half-hour. Those two habits and https://blot.im made blogging nigh-effortless. Like dandruff, I get it for free.

Oh my problem isn't that at all. I have no problem writing endless amounts of crap that no one will ever read. It's just that I really care about my writing, and I want it to have a perfect home. So I'm constantly writing and rewriting blog engines. In this case, the perfect is the enemy of no one. A blog engine is the one side-project that I don't just hack. It's my one and only place for writing pure, elegant code.…

I was(am?) in the same boat as you. I don't like using other platforms because they don't do exactly what I want. I go through the same decision points while trying to maintain a todo list. I guess that is the drawback of being a developer, you know you can do better(for your usecase) job of developing a great application and eventually, writing a blog or maintaining a todo list becomes an excercise in yak shaving (http://www.dailymotion.com/video/x2est2c_yak-shaving_fun ).

I am trying to get over this habit. Any advice/suggestions would be appreciated.

Re: Why I Don't Use React Router

#66

I really need to get my blog up and running so that I can write about things like this. My view is that dependencies are someone else's solution to my problem of technical debt. I'd be a straight-up liar if I claimed to be proud of every line of code I've written, either for an employer or for myself. Sometimes you just have to hammer a square peg into a round hole and be done with it because deadlines. Or lazy. Or b…

haha, yes.

Got an React project running for a year now. Hundred of deps. I just don't know anymore...

Last year Flummox got deprecated and we had to replace it with Redux, good times...

Re: Why I Don't Use React Router

#67
post #58

I really need to get my blog up and running so that I can write about things like this. My view is that dependencies are someone else's solution to my problem of technical debt. I'd be a straight-up liar if I claimed to be proud of every line of code I've written, either for an employer or for myself. Sometimes you just have to hammer a square peg into a round hole and be done with it because deadlines. Or lazy. Or b…

I didn't get my blog up and running until I a) started keeping a journal on 750words.com and b) started writing in a spiral-bound notebook every spare half-hour. Those two habits and https://blot.im made blogging nigh-effortless. Like dandruff, I get it for free.

Thanks for sharing this and introducing me to 750words, I just finished my first entry! The analysis provided after just a single writing session is awesome - I can't wait to see how this affects my writing, focus, and ability to communicate with myself and others. Did you see a shift in sentiment, focus or elsewhere in your analysis as you prepared to make your writings public? For instance, I notice a pretty even distribution of Emotion and Mindset which I imagine will become way more focused as I work towards writing in public.

Re: Why I Don't Use React Router

#68
That's why they call it angular 2. It's finally out and ready to be used. Works really well with routers. Although you don't get the constant updating but you do get codeless directives that are really easy to understand.

Re: Why I Don't Use React Router

#69
I might be missing something (after reading the article twice) but the author says nothing about why he doesn't use React Router...

The only mention I can find is "But the API smelled funny to me, and had not settled, so I continued to wait" that hints that the API is changing and looks weird. But other than that, there is no constructive criticism here.

I'm all for being able to write freely about software we find bad, but without any concrete examples or even pointers to what is bad, I don't think this article have any merit (except that it's good to make sure you understand the dependencies you have).

Re: Why I Don't Use React Router

#70
post #69

I might be missing something (after reading the article twice) but the author says nothing about why he doesn't use React Router... The only mention I can find is "But the API smelled funny to me, and had not settled, so I continued to wait" that hints that the API is changing and looks weird. But other than that, there is no constructive criticism here. I'm all for being able to write freely about software we find b…

It looked like a risky dependency, simple as that. Despite the HN title, the point of the article was not to talk about React Router.

EDIT: Additionally, I'm not saying React Router is bad per se, just that it's not fully baked. I'm glad to see people working on the problem. I look forward to leveraging the fruits of their labor in the future (in fact, I already do - I use the history library on which RR is built).

Post reply on HN