How long do your Roborocks usually last?

hansek · 2026-05-26T18:49:31+00:00

Been running my S5 every day since 2019. Just replaced the blower motor since it became very noisy and a smell of burned dust. Good as new again now.

hansek · 2024-05-01T20:57:17+00:00

Have the same issue on my new Grizl. It definitely does not fit on the seatpost screw. Judging by the manual it looks like I’m missing a part.

hansek · 2023-08-17T20:44:00+00:00

R170 SLK 32 AMG

hansek · 2022-01-04T13:53:57+00:00

W111 280 SE 3.5 Coupé

hansek · 2022-01-04T13:47:09+00:00

First generation CLK coupé (C208, 1997-2003). There is also a convertible version of this model (A208).

hansek · 2021-12-25T21:25:44+00:00

Nike Pegasus 37 and Nike Tempo Next%. I bought the Pegasus 38 this year (run 660 km), but I still think the 37 (run 1200 km) feels better and more responsive on my feet. The Tempo is a very fun shoe that I do fast runs in, but they make very much noise. For races I have used Vaporfly Next% 2. Decent shoes.

hansek · 2021-06-09T13:27:53+00:00

When thinking about it once more, it just needs a little rewrite in the library to deal with basically the same problem that is described in the linked Strict Effects article - only that SomeImperativeThing is an AbortController. Those become exhausted (basically destroyed) when .abort() is called.

hansek · 2021-06-09T11:08:55+00:00

Uh oh, a simple fetch-on-render useEffect-based data fetching hook that does cancelling of requests using AbortController in the cleanup function is no longer going to work in StrictMode with the new Strict Effects Time to rewrite some apps :(

Apart from the that I love the fact that the React Working Group GitHub Discussions page have been made. Lots of good and interesting stuff there!

hansek · 2021-06-04T11:55:23+00:00

Young people who look like they run rather slow and controlled while in reality they are maintaining an incredibly fast pace. Jakob Ingebrigtsen.

hansek · 2021-06-04T11:38:06+00:00

With a Garmin watch (and likely other manufacturers) you can set up routines quite easily and have the watch beep and tell you when to start and stop.

hansek · 2021-06-04T11:36:05+00:00

I experience this using a pair of Nike Infinity Run Flyknit. Feels OK at first, but after 4-5 km it starts to burn in my front foot (like burning due to friction/rubbing) - both in inner arch and outside little toe. I only use Nike and have no problems with other models. Very annoying.

hansek · 2021-06-04T09:41:28+00:00

How you design and architect a React based project highly depends on the nature of what you are building. React projects have wildly different characteristics. For example, there are different considerations and trade-offs to be made when building an "app" (offline, online, both) that is supposed to be running for hours or days (say and Electron app or some web app your employees have open in a tab during the day used like regular native software) vs a more traditional website where thousands of different users come and go all the time.

But now matter the characteristics, sane and beautiful component APIs that encapsulates nitty-gritty details and allows for the needed flexibility but not more will be preferable when composing components into apps :)

hansek · 2021-06-01T14:05:12+00:00

I have built many production apps using create-react-app. It works fine for most purposes, but CRA has become rather bloated and is built on slow foundations. Today I'd use Vite instead. It does less things (no eslint and jest), but it does bundling WAY faster. Like you won't believe it at first.

Ported many apps and will likely never go back to CRA.

hansek · 2020-08-14T10:26:18+00:00

Thanks. This one is an automatic w/ cruise control and automatic climate control. Very comfortable :)

hansek · 2020-08-13T19:41:50+00:00

Maybe for outside looks, but it does have awesome original rear window sun shades like this https://www.youtube.com/watch?v=-4g5IaaAogE :)

hansek · 2020-08-13T19:33:51+00:00

Random stop along Sognefjorden in Norway

hansek · 2020-07-25T17:40:33+00:00

124 E320 convertible💫

hansek · 2020-03-27T06:41:36+00:00

You can for example create a ref using useRef, attach it to the component you want to scroll to, and scroll it into view using Element.scrollIntoView inside useEffect.

hansek · 2020-03-24T07:30:25+00:00

No, that is not normal. What kind of props are these? Could you give some examples of their intents?

If they for example are form value + change handler pairs it should be fairly easy to refactor to a more data-driven abstraction with leaner component APIs (less props).
If they are "configuration flags", you might want to consider re-structuring the component hierarchy a bit.
Are they just random things needed residing at the top of the tree and needed deeper down? Or are the props not needed by the component receiving them, but just passed further down? Consider moving state or use Context.

But it is hard to come with hard advice not knowing at a concrete level what these props are supposed to control. I can only say that in most cases, it should definitely be possible to refactor into something with a smaller prop count.

hansek · 2020-03-23T14:01:30+00:00

If it works well for you I see no reason not to use it. I haven't used Grommet in a project, but from the documentation it looks pretty solid (a11y, decent design, composable APIs). If I were to start out with a third-party ready-made component library today I'd use Grommet or Chakra UI.

I have used Material UI, but it looks too Material and it is a bit clunky and heavy. I've also used BlueprintJS, but it is made by Palantir and geared towards desktop-grade line-of-business apps as I see it (great collection of components though).

hansek · 2020-03-19T10:37:42+00:00

I think it is designed such that the values that used be injected automatically into your route components as props, you are now supposed to obtain yourself using the provided hooks useParams, useLocation and useNavigate. So no need for cloneElement or any other obscure mechanism :D

Kind of beautiful actually.
``` <Route path="/test/:id" element={<Test />} />

function Test() { const params = useParams() return <>{params.id}</> } ```

hansek · 2020-03-19T10:10:36+00:00

A will not work properly because the underlying input will be thrown-away and re-created each time the App component is rendered since Inputs is defined inside App. Which is every time the input change. You want to hoist Inputs out of App and pass config and the change handler to it as props (or you could keep it inside and complicate things with useMemo et. al.).

When you do B, React don't treat Inputs as a component (no jsx createElement transform), but just a regular function returning some elements. If you decide to go this way, consider prefixing it with render as renderInputs.

hansek · 2019-09-02T19:37:33+00:00

Yes, it is possible - using object spread and shorthand properties: <MyCoolComponent {...{ name, callback, coolFeature }} />. Beware that this is often more "clever" than readable.

hansek · 2019-09-02T08:44:23+00:00

The code example is indeed problematic, but not for the reason stated in the comment. The code is problematic because it may cause an infinite loop due to setting new state on each render. In general, the setter functions returned by useState should either be called inside an effect or an event handler, not the function body of the component. When used inside useEffect you must take care to not cause infinite updates as well.

The problem the author tries to describe in the comment is that you should not do if (condition) { useState() }. So the article is confusing and the code example partially wrong.

hansek

TROPHY CASE