2 ms·
Whenever I see someone describe how small something they've written as a replacement for a big library is, I wonder what they've discarded in order to get it so
by lexicality 4y ago
Whenever I see someone describe how small something they've written as a replacement for a big library is, I wonder what they've discarded in order to get it so small.
Normally it's backwards compatibility, but in this case it appears to be "everything".
- jrvarela56 4y agoYeah huh? It's like 'I'm selling the cheapest bag of chips ever' and it's just cuz you're putting less chips inside lol These short libs are apples to oranges unless we have a test suite or set of acceptance criteria. Something like https://todomvc.com/ https://todomvc.com/ and https://eugenkiss.github.io/7guis/tasks https://eugenkiss.github.io/7guis/tasks helps keep reqs constant.
- ReactNative22 4y agoI don't get it...this is a simple library that people can use without bringing in external dependencies. Of course it won't be as functional as React-Router - that goes without saying!!
- lexicality 4y agoI would say that a router that doesn't support url patterns, query parameters or state is basically useless for anything other than small static sites that in my personal opinion shouldn't have clientside routing. This is a nice demonstration of how routers can work for people that are curious, but I would have a lot of concerns about it as production-worthy, especially because you're manually firing browser native events during periods that people generally wouldn't expect them to fire. I'm saying this as someone that had to write a full clientside routing system for a bespoke web app - routing is very hard and full of edge cases.
- delaaxe 4y agoYou're trying to argue with a code golfing exercise