I'm no fan of Facebook or its social effects but I can't deny the wonderful downstream effect of their open source.

Popular microscopy models like Cellpose[0] have leaned heavily on the cornucopia of open and SOTA power. I have no doubt thousands of biologists have benefitted from the capabilities these models bring. I think it was unthinkable just 5 years ago that a single biologist with just a laptop could do mass-segmentation at this kind of fidelity.

Then there's Napari and it's plugin ecosystem[1] that wouldn't exist without the Chan Zuckerberg Initiative. Again, I'm not trying to glaze them but as someone in the biotech/microscopy space I can't understate how often I use and benefit from their open source.

[0] https://cellpose.readthedocs.io/en/latest/models.html [1] https://chanzuckerberg.com/rfa/napari-plugin-grants/

▲

3 hours ago | parent | next [-]

[deleted]

▲

DaiPlusPlus 4 hours ago | parent | prev | next [-]

> but I can't deny the wonderful downstream effect of their open source.

ReactJS has been a very mixed-bag...

▲

4 hours ago | parent | next [-]

[deleted]

▲

righthand 4 hours ago | parent | prev | next [-]

React is more of a plague than a wonderful downstream effect or mixed bag. It’s essentially cemented Js as the way to build a website even if you don’t need the complexity. It is the leader in brain dead Js evangelism.

▲

DaiPlusPlus 4 hours ago | parent [-]

Credit where credit is due, though: ReactJS became #1 on its merits.

...yes, Redux (not React) deserves to be #1, but Redux isn't a complete, all-under-one-roof framework the way React is; but regardless of that: The Redux/React approach is just fundamentally a better design than what we had before: stateful-controls/widgets and two-way data-binding.

If you'd like to relive how UI devs suffered throughout the 1990s, 2000s, and most of the 2010s I invite you to try making a native Windows 11 desktop UI using WinUI3 using the MVVM (anti-) pattern: nothing but mutable objects of indeterminable state getting caught in infinite-loops or unbound recursion due to INotifyPropertyChanged - and Microsoft is still pretending that's the "right" way to build a UI.

Sorry am ranting on about something I have very little control over; it's just frustating.

▲

nxc18 an hour ago | parent | next [-]

WinUI3 is horrible, but that is an implementation detail. WPF isn’t so bad (of course for business reasons no one should use either).

I still see WPF and AppKit as both being superior UI technologies to web+react, if you ignore the challenges of distribution.

▲

pavlov 2 hours ago | parent | prev | next [-]

I made several large Cocoa (macOS AppKit, Obj-C) apps in 2004-2018 using the classic Smalltalk-inspired MVC patterns and this was never a problem. Sometimes writing the controller boilerplate was boring, but at least there were no observer loops, it was simple to debug where things happened, and undo/redo were reliable to implement through the framework.

Maybe Microsoft just never was very good at these 1990s style GUIs?

▲

andyjohnson0 3 hours ago | parent | prev | next [-]

> nothing but mutable objects of indeterminable state getting caught in infinite-loops or unbound recursion due to INotifyPropertyChanged

Rant on brother/sister. I'm a year into building a large WPF (because reasons) app for my employer and some days its very difficult.

▲

locknitpicker an hour ago | parent | prev [-]

> ...yes, Redux (not React) deserves to be #1,

This is a rather perplexing statement to make.

If anything, Redux only plays a role in adding syntactic sugar over React's support for reactive programming.

More importantly, the general guidelines are that you should only bother with Redux if your SPA is already considerably complex.

	▲	DaiPlusPlus 14 minutes ago \| parent [-]
		> Redux only plays a role in adding syntactic sugar over React's support for reactive programming Redux doesn't have anything to do with any kind of syntactic-sugar for Reac. > the general guidelines are that you should only bother with Redux if your SPA is already considerably complex If one already has an (non-React) SPA which is not already built following Redux then you're stuck with what you've got; it isn't really possible to take an existing SPA of any complexity and deciding to "make it use Redux" because it completely up-ends practically every aspect of SPA application-design, at least as far as how "traditional" (non-React) SPAs do things. If you'll permit me to oversimplify: I tell people that React is a basically an opinionated Redux kernel wrapped around a JSX-based DOM+component/widget system (, which then means you now need a JS build system too); or conversely: Redux is like React, except without JSX components. ...or am I misunderstanding you?

▲

locknitpicker an hour ago | parent | prev [-]

> ReactJS has been a very mixed-bag...

This is a very confused statement to be made, specially after the last decade where React established itself as the de facto way of writing any and every SPA.

Is it yet another example of "there are only two kinds of languages: the ones people complain about and the ones nobody uses."

	▲	nxc18 an hour ago \| parent \| next [-]
		I think the universe of SPAs that should exist is far smaller than the universe of SPAs that does exist, and the hype around react is largely to blame.
	▲	DaiPlusPlus 24 minutes ago \| parent \| prev [-]
		> the ones people complain about and the ones nobody uses The funny thing is that prior to 2015 "the ones nobody uses" were the academically-designed ivory tower FP languages; perpetually relegated to being a minority curiosity because FP is immensely difficult to wrap one's head around at first, especially if all you've-ever-known was imperative C or VB and (compromised) OOP in Java and C#. I remember when Google's overqualified design-team for Angular decided that Angular2+ is too good for Promise-based fetch() - instead everyone should be forced to learn RxJS's way-of-doing-things - cue the agony, wailing and the gnashing of teeth. ...I think being forced to live through that experience did 2 things: 1) It forced an entire generation of front-end web-devs (and VB6 refugees) to get familiar with FP-like concepts. 2) It also made those same front-end web-devs swear-off ever using a Google-maintained SPA framework in future. ...which set the stage for the mass-adoption of ReactJS: 1) It made effective use of FP concepts, which many devs were now accustomed-to after having survived Angular2. 2) It wasn't made by Google.

▲

4 hours ago | parent | prev [-]

[deleted]