I hope they use the money to improve all the issues people have arised over the years. It can be a really good platform, if they're open to change. Otherwise, it might be dead in the future.

No faith on a piece of software of the author of the now abandoned Pixelfed, a software that is not finished and still very buggy.

Pixelfed released an updated app on TestFlight on January 13 (12 days ago). Not sure where you are getting abandoned from.

Buggy, sure. It’s new.

Abandoned? I don’t think that’s accurate at all.

Pure Bluesky endorsement from a MIT blog.

ActivityPub, Pleroma and Mastodon existed before this, and they just work.

> 1) A Twitter clone without the political baggage and chaos of the current Twitter ownership.

Not the current, but the previous one when Dorsey owned Twitter. And I don't know what's worse, honestly.

Cool. Now, in Europe, please.

> It seems very cool that you can roll back in the case of a catastrophic upgrade failure, but has that every happened to you? Not me.

It did, and thanks to that rollback feature, my system was working in a few minutes.

It's not. Open Source has its own definition.

You can define however you want, but it's not Open Source. What you mean is "source available".

For the love of God, stop putting "Native" in web frameworks. No, React will never be native.

What does this mean? There are plenty of big, native apps using React.

It's "native" in that the wrapper is a native binary, but it's still a webpage.

React Native actually constructs a view hierarchy in the platform's UI toolkit, so I'm curious what you mean by "still a webpage"?

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.

That is certainly true of Flutter, which has its own rendering pipeline. React native, if you create a Button then on iOS you'll get an actual UIButton instance constructed, etc.

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.

With respect, literally the exact opposite is true. I think you're mistaking it with something else.

But everything in that view hierarchy is still drawn using HTML and CSS, and all the logic is implemented in JS, no? If that's the case, then that's not "native".

No, it renders native views.

React is a web framework. You can put Native behind React, it'll never be.

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".

Hiding another AI post... This is getting _so_ tiresome...