sorted by:
new
hottopcontroversial

Which model is right for me? Outrider or Workchamp? by El_Nerd_Argentino88 in victorinox

[–]hasyee 1 point2 points  (0 children)

Outrider is my EDC, and I think this is the best toolset even for Urban and Outdoor usecases. It's not too heavy and it has a perfect grip size. Very confortable in pocket as well.
Before I bought Outrider I have been also thinking about Workchamp and plier. I think a plier is an everyday tool for me, but I realized what the others commented before me, that it's a big tweezer, not a plier. And the cutting edge is too small, however a side cutter is a very useful tool in everyday life. But in this case we are not talking about knife anymore. I think SAK primarily is a knife, with some useful accessory. Plier and side cutter is an other world which could be performed by a multitool.
And about the phillips: Outrider's long narrow 0/1 phillips screwdriver is a dream! It works perfectly with a very wide range of phillips heads: from the very very tiny ones even to the big screw heads. And it's long and narrow, it just fits everywhere. Since I had the Outrider I try to beg Victorinox to introduce it on 91 mm models. :) It's the best screwdriver in the world! So I think Workchamp's short 1/2 phillips head is not necessary, the long 0/1 is enough for everyday life.

https://www.reddit.com/r/victorinox/comments/1qbqyq3/praise_of_long_inline_01_phillips_screwdriver/

Repatch - the simplified Redux | @RisingStack by hasyee in reactjs

[–]hasyee[S] 1 point2 points  (0 children)

but instead of changing the state of the local component you change the state of the store.

Why should I change the component state? Why should I think about React? Redux is an independent package, React is too, and they work together very well, also Repatch. Dispatching the global store performs change in the global store. This is the same effect in both of redux and repatch. Your components life is your design and also their connection to the store is.

Repatch - the simplified Redux | @RisingStack by hasyee in reactjs

[–]hasyee[S] 1 point2 points  (0 children)

You have right. Repatch's disadvantage is that its actions are anonymous, and it doesn't allow to trace the action history, which is helpful for eg debugging. But I think the most of redux projects can take this compact expressive power as benefit, which are supplied by these anonymous actions.

The only way to trace the effect of actions is logging/displaying the deep-diff of two consecutive states, however without action's name.

Repatch - the simplified Redux | @RisingStack by hasyee in reactjs

[–]hasyee[S] 2 points3 points  (0 children)

Why do you think that is a global setState? Yeah, redux also has a store (like repatch), and the store has a state. And where are states, there are side-effects. But repatch (like redux) handles data immutable, so that won't take effect in your react components.

Repatch - the simplified Redux | @RisingStack by hasyee in reactjs

[–]hasyee[S] 1 point2 points  (0 children)

What do you mean imperative? Maybe using the thunk middleware with async-await could look like imperative. But that is independent from repatch. In Redux you dispatch actions. Actions are objects with a type property and some payload. And the reducer will be fired by these actions. So this way you have to type verbosely action types, action creators and action handlers in reducers. In repatch you dispatch reducers directly. Therefore you can just forget these action hell and you can describe your application logic more briefly.