“Why We Didn’t Use A Framework” (Case Study) – Smashing Magazine


28 bookmarks. First posted by taylorcammack 5 weeks ago.


Really great overview for not using or using a framework
framework  javascript  webdesign 
12 days ago by dogonwhe
“Why We Didn’t Use A Framework” (Case Study) – Smashing Magazine
from twitter
29 days ago by wschenk
Using this approach, we were able to create an incredibly fast and light web application that is also less work to maintain over time. The average page load on MeetSpace has just 1 uncached request and is 2 KB to download, and the page is ready within 200 milliseconds. Let’s take a look at what went into this decision and how we achieved these results.
lastmac  framework 
4 weeks ago by philapple
When we set out to build MeetSpace (a video conferencing app for distributed teams), we had a familiar decision to make: What’s our tech stack going to be? We gathered our requirements, reviewed our team’s skillset and ultimately decided to use vanilla JavaScript and to avoid a front-end framework.
article  framework  javascript 
5 weeks ago by Gwendoux
Find out why the team at MeetSpace decided to build their app without a front-end framework, and what the pros and cons of a frameworkless back end are.
web  javascript  progressiveenhancement 
5 weeks ago by sonniesedge
Advertisement Many companies try to create a great experience for customers. But few are willing to make the changes required to deliver on that promise. In…
from instapaper
5 weeks ago by mledu
“Why We Didn’t Use A Framework” (Case Study) – Smashing Magazine
from twitter
5 weeks ago by iany
Find out why the team at MeetSpace decided to build their app without a front-end framework, and what the pros and cons of a frameworkless back end are.
programming 
5 weeks ago by emerysnyder
“Why We Didn’t Use A Framework” (Case Study) https://t.co/MI2RZ5GHUp

— Chris Heilmann (@codepo8) May 17, 2017
IFTTT  Twitter 
5 weeks ago by abraham
“Why We Didn’t Use A Framework” (Case Study)
from twitter
5 weeks ago by codepo8