Skip to main content

The Power Paradigm: Metaverse edition

     This blog post will be slightly off the kilter of my usual writing. Not that I don't want it to be funny or engaging, but I'm not writing it with the same lighthearted intention that I've written about other, less-consequential topics like how to create tally marks or what I made my first website about. This post is also meant to be less results-oriented; there's no final product I want to show off or "behind the scenes" descriptor I'm writing. Instead, I want to use this entry as a jumping off point for discussing an issue that seems to be plaguing every aspect of society nowadays: the rise and dominance and social destruction as a result of: Facebook.
    But, in particular, I've been curious: what role has their software-baby, ReactJS, played in this power struggle? It's been a hard question to answer definitively. For one, news coverage seems very intently focused on "one side" or "the other":
    -It's very easy to find tech sites singing the praises of ReactJS, describing its history, and without judgmental tone, mentioning that Facebook introduced it in 2013.
    -It's also very easy to find news coverage, from a myriad of political perspectives, decrying the role Facebook has been allowed to play in our society, usually with some blame placed at the feet of the politicians who haven't-yet reacted.
    It occurred to me then, as I started thinking about this story, that I would have to be the one to draw the connections I was looking for.


I know, Mark. I know. Responsibility is hard.

    Fortunately, connections aren't that hard to come by. Sure, maybe some part of me is indeed disappointed that there's no "smoking gun" - no on the record ad executive instructing the software department to create new software that will 'really reel them in...'. But what is there?
    Well, for one there's the timeline: Facebook introduced ReactJS in 2013. While that may seem like "forever ago," the company had already existed for nearly a decade1, and already financially settled in 2009 as recompense for their advertising strategies that involved selling your profile data wholesale, while encouraging their users to "consent" to this data harvesting by allowing "everyone" to see their profile/data2. 2013 was also good timing for the internet to receive a framework that was lighter weight and allowed client-side rendering(, etc), as smartphone usage in the US had just crossed the 50% threshold the year before3, allowing more users to access these apps - and access them in a way more integrated within their whole day - than could have just from their home computer. As the popularity of the site grew, popularity for this new language also grew, as more and more developers grew to appreciate its simple, reusable component structure, and blend of HTML/Javascript (called "JSX")4. At this point, then, the growth of one really is directly connected to the growth of the other. Facebook at this time really recognized the growth potential of their new language and began to invest heavily in it4.
        React was then made fully open-source (under the common "MIT License") in 2017. While it's too cynical to say that move/presentation of the code as a "gift" was itself covering up for something, it was not how the code was initially released. Initially it was released under Facebook's own custom "BSD+Patents" license. That licensing wound up drawing scrutiny by developers (some of whom walked away from Facebook-compatible projects) for legally preventing developers from taking action against Facebook in the event the developers' own patents were infringed on by the company5.
    The closest thing to a "smoking gun" came in 2019 when some lawmakers began targeting Facebook not for its reputation but as part of a tirade against social media in general - and its code in particular. Famously, Missouri Senator Josh Hawley introduced legislation that would literally-outlaw some of what he viewed as the most sinister, and habit-forming, features of social media in general6.
    In particular? He took aim at "infinite scroll" - a feature that allow Facebook and Instagram to continue to feed you more and more data through more and more page loads - without your ever needing to click a single link. As a developer in training, I can intuitively understand the basic idea behind it - and how might greatly benefit such a feature: being able to re-render a basic component (the screen, itself a list of smaller "post" components), without having to navigate away from the page or refresh the page as a whole, would be simple to implement in react. A quick online search reveals that there are indeed multiple GitHub repositories and even some from-scratch walk-through tutorials allowing users to implement it on their own apps7. Here is a case where, agree or not with his motivations - Senator Hawley took aim not only at the effect of Facebook on society, but on the code that got it there. 

Conclusion/Further Reading:

    Facebook's impact on both technology and the social sphere as a whole can't be understated, especially with the inclusion of Instagram and What'sApp. But how much does React have to do with that?


    As this chart8 shows...probably not a whole lot. Whatever the reason, engagement with the company and its platform(s) has grown nonstop since the website's inception in 2004. The creation of a brand new, lighter-weight, more-dynamic framework for JavaScript really should, in this author's opinion, be seen not as a tool that enabled that transformation, but one that came about as part of that same transformation. Without their early success, Facebook would not have had the resources to invest in something as groundbreaking as this new programming tool. Without their new programming tool, Facebook would not have had the dynamic capabilities to continue to stay as relevant and successful as they have. They feed into each other; they're part of a continuous loop.
    So, where to next? However they got there, Facebook as a company is now worth one trillion dollars. Will Facebook and/or React stay that relevant, and retain that level of market dominance forever? Even for the rest of this generation? Maybe not? Will our democracy and society survive this assault on our sense of reality and community? Hopefully.
    But, in the meantime, as Redditor capuccinolizard helpfully laid out: "Take this tool they have given you and use it for good."9 Using one does not necessarily have to mean you endorse the other. Even with all the problems this Pandora's Box of social media has unleashed, there is still a wide world to code in. And, React can make that kind of fun.

Sources:

  1. https://www.nytimes.com/2021/11/12/opinion/facebook-privacy.html
  2. https://www.theguardian.com/technology/blog/2009/sep/21/facebook-privacy
  3. https://www.washingtonpost.com/national/health-science/teenage-depression-and-suicide-are-way-up--and-so-is-smartphone-use/2017/11/17/624641ea-ca13-11e7-8321-481fd63f174d_story.html 
  4. https://softwareengineeringdaily.com/2020/12/11/facebook-react-with-dan-abramov-repeat/
  5. https://www.freecodecamp.org/news/facebook-just-changed-the-license-on-react-heres-a-2-minute-explanation-why-5878478913b2/ 
  6. https://www.pluralsight.com/guides/how-to-implement-infinite-scrolling-with-reactjs
  7. https://www.npr.org/2019/08/14/750585438/senator-pushes-bill-to-curb-exploitative-and-addictive-social-media-practices 
  8. https://www.statista.com/chart/10047/facebooks-monthly-active-users/
  9. https://www.reddit.com/r/reactjs/comments/j3slql/ethics_of_using_react/

Comments

Post a Comment

Popular posts from this blog

Don't Touch That Dial

    This article was inspired by a technical error I can't replicate through writing, nor refer to in official documentation (unless I missed something ). The overhead digital projector in one of the classrooms I attend, in between displaying its computer signal and a neutral, soothing blue screen displayed something curiously familiar: tv static. you may be familiar...     For a brief instant, the "snow" felt oddly comforting. It made me think of old movies in the basements of old houses. It reminded me that  Hunter Thompson liked to fall asleep to white noise  (white noise, side note, actually having some  therapeutic benefit? ). It made me wonder if my teacher needed to climb on the roof and adjust the antenna.      Then it hit me: what the heck? Technically speaking/as this  helpful reddit page  explains, tv static was originally the cause of an internal mechanism within the television: the amplifier, normally in charge of boosting whatever signal it received (from th
Post a Comment
Read more

Introducing: Tales from the Other Side

      Hello to my loyal fans. I hope you all have been having an excellent autumn/summer/spring/2022 since you last stopped by, hoping to find what was instead a mysteriously (and no doubt, frustratingly) absent fresh article from me. Apologies for keeping you waiting. But here it is!     Still, I hear you. "What", you might be asking, "could be so important that it would be worth pausing on committing to record these written anecdotes that so many of us have come to enjoy?". Well, I'll tell you what - I got a job! I got a job! I got a job!     Well, sort of. I got an internship. For several months this summer-through-fall I worked as a member of the Frontend Web Team at the Meal Kit delivery company Blue Apron . I was pretty excited for the opportunity. Not only would it be my first job in tech, but the food industry in general is something I've been an enthusiastic part of for most of my professional life. Not only was I excited to retain some semblance of
Post a Comment
Read more

Tales From the Other Side: e.stopPropagation();

 Hello Readers,      Greetings from a chilly November day in New York. The kind of day that forces you to forget that Fall is after Summer, and to remember that Fall is before Winter. The kind of day that makes one glad they spent several years in Vermont and now have several tricks up their sleeve. Namely: warm socks and vigorous walking . But I digress.     The first 'tale from the other side' that I wanted to share is actually the one I was most excited about (in real time!) when I learned about it. Spoiler alert from the title: it's the event.stopPropagation() javascript method. So...what the heck is it?     Well, here's a few things about it: It's a native Javascript method, so there's no extra libraries, packages, components, syntaxes, etc to import. It's in the same 'family' as event.preventDefault() , so those familiar with other common event handlers may already have a sense of where it can be called. Think about all the ways you could wa
Post a Comment
Read more