Krzysztof Modras

Have compiled #WebKit from sources first time Today. Few things to notice: 1. on MacOS there is zero setup required. clone the repo - run build script and it works 2. on latest MacBook (i9) compilation takes less than 20 min 3. Safari is fully open source I'm actualy impresed.

I think I'm doing it wrong: `import React, { useContext, useReducer, ComponentType, useMemo, useImperativeHandle, Ref, forwardRef, useState, useCallback, RefObject } from 'react';`

Final levels in video games have a tendency to be something more than the game they aim to conclude - this in my experience makes them often frustrating as instead of perfecting the subject formula, they try to be something else.

#reactjs is a mass hallucination and one day we will all wake up with a dreadful realization that we have to rewrite half of the web, again.

There are lots of cases when reactive programming is very efficient and elegant. But when you get into one of those situations that a state on a component level would fix all issues you are out of luck as in modern hook driven react, components cannot have methods anymore..

APIs like document.querySelector feel like next level shit when you hit a wall another time by trying to wire simple UI into application state.

On top all weird React ideas like hooks, iteration keys, refs, contexts, reducers etc, make me realize how brittle VDOM approach is. I wish there was a cross platform alternative for #ReactNative rendering layer.

Functional reactive programming (like in #reactjs) limitations are extremely frustrating when you know that Object Oriented alternative are way simpler and a mixed approach would just work.

Fun fact about those privacy stats is that this little piece of UI comes from #ReactNative and it can resize itself freely. It’s probably not very canonical solution to mix Native and RN views like that so you may like to check the code https://github.com/cliqz/user-agent-ios/blob/23b00a9d32636ed71794e5164737d5c723583cb5/ReactNative/Views/PrivacyStatsView.swift …