Things said aloud: Stencil is made by the Ionic team and allows you to use "decorators" (which are really annotations) to in turn use TypeScript but serve it to people compiled as JavaScript. HipChat is a ghetto chat client. MUMPS is NoSQL and JSONesque. It is the Vue.js philosophy that a separation of concerns is not a separation of technologies and therefore we have what we have with Vue in which the JS, the HTML, and the CSS are all jammed into one file. A lot of people who did AngularJS who were put off by how different Angular 2 was switched to Vue instead. When should you use the Redux pattern in React or Angular for that matter? When cousins in a tree of components need the same data or when you are passing down data from atop in a tree of components is when. A lot of PowerBuilder devs can only do PowerBuilder. The Lawson ERP was bought out by Infor. Ruby Gems can get pulled into scope in such a way that you cannot tell which ones are being looped in by Ruby on Rails. The slashdotting of a web site entails a better trafficked web site lending links in, giving a bounce in traffic. That's the slashdot effect. The history of architecture was run through from the old school web sites to what you might think of as Web 2.0 with some AJAX (gmail was suggested to be the first example) in the DHTML (Dynamic Hypertext Markup Language) days to modern client-side MV* implementations. OAuth and Auth0 were namedropped as canned ways to do security in modern times to make development quicker. npm is now far and away the largest open source sharing platform approaching nine hundred thousand registered packages which dwarfs Maven in second place with a third of that footprint. There was a whole React versus Angular versus Vue conversation. React is easily the most popular of the three while Angular offers the least decision paralysis. The best ideas in all three spaces get adopted in the other places. It is easy to port a React app to React Native, you just swap out the anchor links (the a tag in HTML makes anchor links to "other pages" and hypertext by definition links topics into text so this is cornerstone to HTML) to something that plays nicely in the mobile space. ParseRoller and Rollup are rivals to Webpack in the packaging space. You may specify nth number of versions of JavaScript back when you compile with Webpack, bringing in polyfills selectively, creating only the fatness you need. Webpack has the concept of loaders and anyone can make a loader to transpile TypeScript to JavaScript or something. The optional chaining proposal, a stage three proposal from TC39, is like the safe navigation operator in C#. There are a series of steps that a proposal goes through to become a part of ECMAScript with the TC39 approach to things. In stage zero, it's just an idea. In stage one it has a backer and an outlined specific way it functions. Babel support comes in stage two and browser support in stage three while stage four is ready to go. Under the hood all modern JavaScript is really a bolt-on extension to JavaScript so this allows TC39 to extend its language incrementally with proposals. There is a Vue CLI like the Angular CLI. Next.JS for React and Nuxt.JS for Vue combine the basic scaffolding of a Hello World app with some basic isomorphic scaffolding server side à la Express and Node. I wrote in my notes that SoundJS for working with audio in JavaScript is killed.
From left to right above, Drew Barette, Colin Smith, and Zach Dahl each alternated in presenting while Graham Francois moderated. All four men work at sdg (Solution Design Group) a consultancy in Golden Valley, Minnesota (i.e. the twin cities) and sdg hosted the event. It wasn't just these four guys standalone however. There was quite a bit of audience participation and much of what is above comes from that. In particular, a white guy with dreadlocks named Jason taught me a great deal in the meet-and-mix before the main theatrics. There was a smorgasbord of sources for input. Colin Smith specifically spoke to trends at the end of the session. The most interesting things he mentioned were JamStack and Svelte. The Jam in JamStack is an acronym for JavaScript APIs and Markup and JamStack as an idea has to do with serving up static content with a JavaScript engine. Gatsby is an implementation of JamStack. Jekyll was referenced as something comparable though not technically JamStack as it does not use JavaScript to do what it does. Svelte will allow you to use web components without Angular, Vue, or React where they are getting trendy. Svelte will spit out a minimized HTML and JavaScript site rendered from your web components orchestrated independent of the larger frameworks and their fatness. Colin also put some emphasis on Headless CMS which as a term seems to be akin to serverless and pointed at a trend in talking to cloud functions such as Azure functions.
No comments:
Post a Comment