Download as pdf or txt
Download as pdf or txt
You are on page 1of 115

http://site.com/something#!

state
https://docs.microsoft.com/en-us/azure/architecture/patterns/index-patterns
http://en.wikipedia.org/wiki/JSONP
http://www.dofactory.com/javascript-
patterns.aspx
http://raganwald.com/2008/05/narcissism-of-small-code-differences.html

https://yinwang0.wordpress.com/2013/11/09/oop-fp/
• Reasons for concerns
• Language familiarity
• OOP style – not class focused
• The DOM (really browsers)
• HTML5 (really browsers)
• Language warts
• Support for programming in large (modules in particular)
http://oscargodson.com/posts/why-i-dont-use-coffeescript.html
asmjs.org
https://github.com/medikoo/modules-webmake
http://browserify.org/

Fundamentally still to be realized properly in any reasonable way


Only solve a problem when Benefit > Cost
Fact: Times and Tech Always Change
Solaris, Novell, Windows MFC, <insert 100s more>
React perception wise has won amongst CS types, but amongst
observed things at scale it’s a jQuery and Vanilla JS world by a
massive factor ~80% vs ~4% in library use and well over half don’t
even use libraries. HTTP Archive
Algorithm feeds me
stuff that is
getting hot

+ * = !?!?

My friend just got a


job using X
jQuery

React
Watch Your Dependencies!
Code you don’t control can rot!
Software Tends to Mirror the Structure of the Organization That Build It
This also includes tech choices and thoughts about solutions
Environmental Weather Patterns
Laws
Unwritten 

Rules
Regulations

Coercive Forces

Licensing

Certification
Mimetic Forces Normalizing Forces
Popularity “Software
Professionalism
Engineering”
Social Acceptability
Accreditation
Career Influences

Moral Values
Into the black hole all here is
sucked in and crushed into a
belief what we do is all about
code?

From the tech industry itself From other industry practices, lore and needs
Respect the Environment
The World

The Broader Industry

Our Context
Situation
Firm
Group
People

The “Software”

Our
Code
Programming as Gardening
That Means Care Over Time and a More Organic Process

So don’t go dig up your garden just because EVERYONE is doing it


http://martinfowler.com/eaaCatalog/modelViewController.
html
http://nobackend.org/solutions.html
http://mustache.github.io/ http://handlebarsjs.com/
PopStateEvent - Web APIs
| MDN (mozilla.org)
http://www.elijahmanor.com/2013/03/angry-birds-of-
javascript-red-bird.html
https://developer.mozilla.org/en-
US/docs/Web/Guide/API/DOM/Events/Creating_and_triggering
_events
http://www.nczonline.net/blog/2010/03/09/custom-events-in-
javascript/

https://developer.mozilla.org/en-
US/docs/Web/Guide/API/DOM/Events/Mutation_events
IIFEs are a great example of idiomatic coding patterns that are time sensitive. Beware of
This and it is likely going to continue.
https://medium.com/better-programming/object-oriented-
programming-the-trillion-dollar-disaster-92a4b666c7c7

https://stackoverflow.blog/2020/09/02/if-everyone-hates-it-why-is-oop-still-
so-widely-spread/

You might also like