tstusr20190823

It is true for a few components derived from TouchableOpacity like Button, sure. That is NOT true for most other components. You does not have UICollectionView, UINavigationView (only solvable with third-party buggy components), etc.

React allows you to write custom renderer and React Native is a quick and dirty example of that custom renderer. The only reason it does not "feel native" is because Meta does not invest much into it and only subset of the "native" features is implemented in "native way".

React Native constructs only single UIView by default and draw actual UI using poorly man browser engine using JS. This UI does not "feel native" to user, because it has wrong animation timings, scroll speed, border elevation, missing "native" gestures, etc.

"html_elements_cant_self_close" is not a very clear error. Yes, now it is clear what does it mean, and it would be great if other users should not start a new HN-discussion to receive clear explanations when it can be explained directly on "html_elements_cant_self_close" tooltip. We can polish text, decide to mention XHTML or not, but the error message should be more informative.

I got this error first with HTML doctype, so it is a problem in my code which uses self-closing tags with HTML doctype. Instead of very noninformative "html_elements_cant_self_close" message it should explain that HTML spec does not have "self-closing tags", and this code uses deprecated feature from previous (XHTML) specs.

OK, so it should not warn with XHTML doctype? But it does too

My html is: <!DOCTYPE html> <html>

<head> <meta charset="utf-8" /> </head>

</html> Why it warns html_elements_cant_self_close on meta tag?

What is "latest build"? V does not release any stable build and you can get "large error" on any platform right now when trying random "latest build" without any effort to investigate the issue.

V have first-class Windows support, what is your problem?

The former is a human-readable text which allow eye to easy understand and latter is a technical info which is not required to have space on the screen and makes UI "hard to use".

gitweb requires server setup, while Mercurial web ui can quickly start locally without any configuration and that was the one of mercurial selling point until github and other services arrives.

Can you make "sr.ht git services" the blue title of the repo "card" and "~sircmpwn/git.sr.ht" - the subtitle (with dimmed color)? This simple change will improve UI usability in 10x times.

Mercurial users can use their builtin Web UI unlike Git users

Am I the only one who can't find the source of this "open source software"? How they can beat Bitbucket while they hide the code under unusable UI?