Do you feel the JavaScript fatigue? Are you still trying to learn ‘the next big thing’? Does your code seem legacy just after six months because of that ‘next big thing’? Have you ever thought of building a software, even a complex one, without any kind of dependency on your package.json? During the talk we are going to see how to create your own framework and libraries with just standard ECMAScript features and W3C standard APIs.

1. Frameworkless
Frontend
Development

2. Why do we use
frameworks?

3. Not Invented Here (NIH)
syndrome

4. Photo by on UnsplashDakota Corbin

5. By Falk2 (Own work) [ ],CC BY-SA 4.0 via Wikimedia Commons

6. “ Every framework you’ve ever seen is
really just an echo of this statement:
My language sucks!
Robert C. Martin (Uncle Bob)

7. I ❤ JavaScript

8. “ Ehi guys, if I would need to have data
binding without using Angular/React or
whatever, what do you suggest?

10. Demo
https://github.com/e-xtrategy/frontend-frameworkless-
development

13. Scalability

14. Performances

17. You shouldn't go
frameworkless but...

18. "Defend" yourself
from Frameworks

19. What parts of a framework
are really important for
your project?

20. @Component(...)
export class MyComponent implements OnInit {
results: string[];
constructor(private http: HttpClient) {}
ngOnInit(): void {
this.http.get('/api/items').subscribe(data => {
this.results = data['results'];
});
}
}

21. @Component(...)
export class MyComponent implements OnInit {
results: string[];
ngOnInit(): void {
window.fetch('/api/items')
.then(r => r.json())
.(data => {
this.results = data['results'];
});
}
}

22. Frameworkless Full Framework
The Right Mix for your business needs

23. ...but how to understand
our clients business needs?

25. Context is everything

26. Technical debt
Technical investment
Technical debt
Frameworks are...

28. Emergent Design

29. “ ...architectures should be driven by the underlying
technical requirements of the system, rather than
speculative planning for a future that may change.
Thoughtworks Technology Radar

30. The right architecture
should be defined by your
features...

31. Let the need for a
framework to emerge

32. Sometimes you need to
build your own wheels

33. By Falk2 (Own work) [ ],CC BY-SA 4.0 via Wikimedia Commons

34. Photo by paolo candelo
on Unsplash

35. Ego Slide
f.strazzullo@extrategy.net
@TheStrazz86
https://github.com/francesco-strazzullo
https://medium.com/@TheStrazz86
https://slides.com/francescostrazzullo

36. http://www.avanscoperta.it/it/training/frameworkless-
frontend-workshop/
Workshop

37. Thanks!