The "Why" Behind Javascript Frameworks, and so much more

We'll keep the open source goodness rolling in February by focusing on a topic we've had our eye on for a while now - Javascript frameworks.

There are 100+ frameworks being used today, and seemingly a new one every few days, and choosing one has become increasingly important and frankly, a little confusing. However, as our speaker Peter Elbaum will explain, understanding the underlying "why" will make the process of choosing and learning a framework much easier and more intuitive.

Topic: The "Why" behind Javascript Frameworks (and How to Learn Them)

Abstract:
There are countless blog posts and tweets given to the topic of whether to choose Vue, React or Angular. We spend a lot of time debating the difference between the frameworks, but we often overlook the reasons that front-end frameworks were created in the first place. This talk will address how front-end development was done before frameworks existed and discuss the main problem that frameworks solve. Through grasping the reason for frameworks, attendees of this talk will be able to accelerate the process of learning a new front-end framework. Specifically, this talk with address component-based architecture, application state management, and component interaction. We'll cover what to look for when learning a new framework and strategies for internalizing the nuances of the various framework ecosystems. Seeing the commonalities among these frameworks allows for grasping the bigger picture.

Speaker: Peter Elbaum, Software Engineer at Praxent and frequent public speaker

Bio: Peter Elbaum is a Software Engineer at Praxent. Peter loves JavaScript, problem solving, and full stack development. Prior to his current position, Peter worked as a developer in the public sector, for a medical data startup and for a local agency. When he's not coding, you can find Peter trying out a new Raleigh restaurant (and reviewing it on his podcast), going on walks with his dog and wife, or talking entrepreneurship. Find him on Twitter at @pjelbaum.

An additional speaker/topic will be added soon as well, so stay tuned for the announcements.

*Note this meeting will be back at the IBM campus location. The address is:
IBM Software Group
Building 500, Room G[masked] S Miami Blvd
Durham, NC 27703
*Questions regarding venue can be directed to Sahdev directly at[masked].

Directions:
We will not have access to the visitor parking lot (as we have in the past), so we'll have to use the employee lot. Attendees can enter through building 502 entrance (instead of 500) from the parking lot.
1). Enter campus from Miami Boulevard and Cornwallis Road,
2). Take first left (Kitty Hawk Drive), then take first right. The parking lot will be right in front of you,
3). Park and enter building door. Someone will be there to escort you.

Doors "open" at 6:00 pm ET (arrive earlier if you like) and programming begins at 6:30 pm sharp with community announcements.

Food and beverages will be served, as always, thanks to our sponsors Mattermost (https://mattermost.com/) and Aiven (https://aiven.io)