rain,
@rain@hachyderm.io avatar

Is there a good, well-argued article on why OOP is a good fit for UI code? I've heard this talked about many times, but want to read something meaty from an experienced dev who has seriously considered alternatives to OOP

twipped,
@twipped@twipped.social avatar

@rain @astraluma I would say that React’s switch from class components to functional components is a fairly good case for this. It significantly reduced complexity, thabks to react hooks giving us a better way to manage state

nikitonsky,
@nikitonsky@mastodon.online avatar

@twipped @rain @astraluma yes but it won’t be possible without DOM which is OOP

twipped,
@twipped@twipped.social avatar

@nikitonsky honey, if you’re going to reduce a system to the layer it abstracts, then you need to collapse the entire waveform.

Everything is ISA
@rain @astraluma

nikitonsky,
@nikitonsky@mastodon.online avatar

@twipped @rain @astraluma sorry, I thought we were talking about implementing UI, not using UI

twipped,
@twipped@twipped.social avatar

@nikitonsky my original reply was about react component implementation, which largely required class construction prior to react 16 and was thus entirely OOP. With the introduction of react hooks it became possibly to do the vast majority of components using entirely functional programming. The vast majority of components do not interact directly with the DOM, there is no OOP involved.

What happens below that abstraction isn’t relevant to the discussion.
@rain @astraluma

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • DreamBathrooms
  • mdbf
  • osvaldo12
  • magazineikmin
  • GTA5RPClips
  • rosin
  • thenastyranch
  • Youngstown
  • Durango
  • slotface
  • everett
  • kavyap
  • InstantRegret
  • khanakhh
  • megavids
  • ethstaker
  • tacticalgear
  • cubers
  • normalnudes
  • anitta
  • cisconetworking
  • ngwrru68w68
  • Leos
  • modclub
  • provamag3
  • tester
  • JUstTest
  • lostlight
  • All magazines