JavaScript Jabber

Panel:Aimee KnightCharles Max WoodSpecial Guests: Nick DisabatoIn this episode, Java Script Jabbers talk with Nick Disabato. Nick is a newbie to JavaScript Jabber. Nick is the founder of Draft, an interaction design agency where he does research driven A/B testing of E-commerce business.This is a practical episode for those who are running a business and doing marketing for the products and services. Nick talks about A/B testing for a number scenarios within the company, such as for websites, funnels, and various marketing mechanisms. Nick further goes into how this helps companies strategically increase revenue by changing things such as websites design or building funnels.In particular, we dive pretty deep on:Testing of changes of Copy, Websites, etc.What does it mean of changes, Tools, Framework, Plugins, etcDoes it matter what tools you use? Framework that works within your stackHow do make we company moneyResearching for the next testTesting for conversion rate to decide which design to go implement - VariantResponsibility for the designsFeature and getting pay for the serviceLearn more about the resources and Copy HackersLarge organization or developers, or a QA departmentOptimization teamsUsability tests and coming up with A/B testsExpertiseWhy should be care?And much more!Links:DraftNick Disabato@nickdConversionXLAB Testing ManualWider Funnels Copy HackersPicks:AmieeNodevember CharlesMike Gehard Admin LTENickHotJar.comSpecial Guest: Nick Disabato. Support this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

17 Loka 201742min

Panel:Joe EamesAimee KnightCharles Max WoodCory HouseSpecial Guests: Scott WyattIn this episode, JavaScript Jabbers talk with Scott Wyatt. Scott is the Co-founder, CTO, UEX at Cali StyleTechnologies, and is a Node developer and graphic designer.  Scott is on JavaScript Jabber to talk about Trails.js. and its simplistic build, but many useful functions.Scott mentions that Trails.js was created by Travis Webb. Scott gives us an introduction to the Trails.js framework, as the Jabbers take apart and dive deep into the build, functions, and uses.  Scott goes into what trail packs are, and the similar or related projects. Scott talks about the ease of using trails to build with, and not ending up in frustration.In particular, we dive pretty deep on:Trails.js is Node Framework and lightweight or BlueprintSimilar to Redux?Is it MVC like RailsYou don’t need to understand it, it is all under the hood.Tuple SpaceIs this sole for server-side rendering?Closest projects - SailsAvoid problems like React.Not dealing with corporationsWhy would you want to use trails instead of other projects like Sails, rails, etc.How do you get started - trailjs.ioQuickest way to learn Trails is to build a Trail PackDon’t be afraid to kill you darlingsTestingIt Trails production ready?It is a particular type of app where Trails shines?Linkstrailsjs.ioTravis WebbPicksAmyFull Stack Developers by Brad FrostTracking MacrosJoeThe Behavior GapCharlesProfit First Keto Dietscott-wyatt/GitHub CoryNever write another high Order ComponentScottProxy EngineSpecial Guest: Scott Wyatt. Support this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

10 Loka 201745min

Panel: Aimee KnightAJ O'NealCharles Max Wood Guest: Eric BerryThis week on Ruby Rogues, we interview our very own, Eric Berry, to talk about the sustainability of open-source projects through ethical advertising. The team talks about once open source projects like PhantomJS, Cancan, and many others.The Rogues dive into the many different scenarios that lead open source projects astray. Problems like working on the project without compensation, be overworked, and no interest are many of the reasons these are not sustained in the long run.However, are there solutions like donations or sponsorship to sustain such projects? And how do we go about finding funding or compensation for these open source projects? Eric describes that advertising tactics and strategies for open source. Eric talks about his work with Code Sponsor and how they support the open source community with funding.In particular, we dive pretty deep on:Ruby Rogues talk about burnout on projectsWorking on projects for free and the project falls apartSolutions behind the more popular projects like Ruby on Rails and NPM.Lemonade Stand - Sustaining and bounty sourced projectsSponsorship or company supported projects.Crowdfunding - not sustainable, but helps.Donation buttons, do they work?Who would pay developers for this?Developers taking care of other developersAdvertising, and helping pay for projects to stay alive!Help developers stay funded without a spam haven.and much, much more!Links: CancanPhantomJSCode SponsorTimber RollbarCoreLogicTrackJS CircleCICodeConf. PicksAimeePositive Experience for Women in TechHand Written CardsCharlesKeto Diet - Fat HeadRuby Dev. SummitAJReal Love by Greg BaerEricNate HopkinsOpen CollectiveCarbonAds.Etc.Special Guest: Eric Berry. Support this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

2 Loka 20171h 1min

Panel:Joe AimeeCharles  Special Guests: Eric Simmons Albert PaiIn this episode, JavaScript Jabbers talk to Eric Simmons and Albert Pai, the co-founder of thinkster.io, where their team teaches the bleeding edge of javascript technology’s various frameworks and backend. Also, with the recent creation of Stalkblitz, which is the center topic of today discussion. Stackblitz it an online VS Code IDE for Angular, React, and a few more others are supported. This is designed to run web pack and vs code inside your browser at blazing fast speeds. Eric and Albert dive into the many different advantages and services available by StackBlitz and thinker.io. In particular, we dive pretty deep on:Similarities  and differences to Heroku System JS Stacklets  Testing and creating an in-browser system file systemCreating a type of VS Code experience, Working Off Line Updating of the StackletsDeployment tools or exporting Hot ReloadingIntegrated terminalsMonacoLanguage Services How do you architect this implementation The innovation of browsersGuy Bedford Financing vs. Chipotle Burritos Will this product in the future cost moneyLinksthinkster.iohttps://medium.com/@ericsimons/stackblitz-online-vs-code-ide-for-angular-react-7d09348497f4@stackblitz stackblitz.com PicksAimeePromises Series by Andrew Del PreteCrossfit JoeWholesome MemeSara CooperCharlesPivotal Tracker MatterMost asana.comZapierEric realworld.io David East Albert thinkster.ioThing ExplainerSpecial Guests: Albert Pai and Eric Simons . Support this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

26 Syys 201751min

Tweet this EpisodeJohn-David Dalton is probably best known for the Lodash library. He's currently working at Microsoft on the Edge team. He makes sure that libraries and frameworks work well in Edge.The JavaScript Jabber panel discusses the ECMAScript module system port to Node.js. John wanted to ship the ES module system to Node.js for Lodash to increase speed and decrease the disk space that it takes up. This approach allows you to gzip the library and get it down to 90 kb.This episode dives in detail into:ES Modules, what they are and how they workThe Node.js and NPM package delivery ecosystemModule loaders in Node.jsBabel (and other compilers) versus ES Module Loaderand much, much more...Links:LodashES Module Loader for NodeNodeCommonJSBabelTypeScriptFlowTypeMicrosoftESM Blog PostMeteorReifyESM SpecPhantomJSzlib module in NodeAWS LambdaNPMWebpackRollupJohn-David Dalton on TwitterPicks:Cory:Trending Developer SkillsThe Devops HandbookAimee:NodevemberES Modules in Node Today (blog post)Dating is DeadAaron:Ready Player One trailer breakdownJim Jefferies  ShowI Can't Make This Up by Kevin HartWork with Aaron at SaltStackChuck:Angular Dev SummitZohoCRMWorking on Cars - Therapeutic working with your hands doing physical workJohn:TC39 Proposal for Optional ChainingToyBox 3D PrinterSpecial Guest: John-David Dalton. Support this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

19 Syys 201757min

Tweet this EpisodeTyler Renelle is a contractor and developer who has worked in various web technologies like Node, Angular, Rails, and much more. He's also build machine learning backends in Python (Flask), Tensorflow, and Neural Networks.The JavaScript Jabber panel dives into Machine Learning with Tyler Renelle. Specifically, they go into what is emerging in machine learning and artificial intelligence and what that means for programmers and programming jobs.This episode dives into:Whether machine learning will replace programming jobsEconomic automationWhich platforms and languages to use to get into machine learningand much, much more...Links:Raspberry PiArduinoHacker NewsNeural Networks (wikipedia)Deep MindShallow AlgorithmsGenetic AlgorithmsCrisper gene editingWixthegrid.ioCodeschoolCodecademyTensorflowKerasMachine Learning GuideAndrew Ng Coursera CoursePythonRJavaTorchPyTorchCaffeScikit learnTensorfireDeepLearn.jsThe Singularity is Near by Ray KurzweilTensorforceSuper Intelligence by Nick BostromPicks:AimeeInclude mediaNodevemberPhone casesAJData SkepticReady Player OneJoeEverybody LiesTylerEx MachinaPhilosophy of Mind: Brains, Consciousness, and Thinking MachinesSpecial Guest: Tyler Renelle. Support this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

12 Syys 201748min

Tweet this episodeJSJ BONUS: Web Apps on Linux with Jeremy Likness and Michael CrumpIn this episode Aimee Knight and Charles Max Wood discuss Microsoft's Web Apps on Linux offering with Jeremy Likness and Michael Crump.[00:37] Michael Crump IntroductionMichael is on the developer experience team for Azure.[00:52] Jeremy Likness IntroductionJeremy is on the cloud developer advocacy team. Their mission is to remove friction and support developers and work with teams to build a positive experience.The NodeJS team is headed up by John Papa. They have teams around the world and involved in many open source communities.They're focused on building documentation and creating great experiences[02:54] What is it about Azure that people should be getting excited about?Azure is a huge platform. It can be overwhelming. They're trying to help you start with your problem and then see the solution as it exists on Azure.Azure is growing to embrace the needs of developers as they solve these problems.The experience is intended to be open and easy to use for any developer in any language on any platform. It allows you to work in whatever environment you want.Standing up applications in production is tough. Azure provides services and facilities (and interfaces) that make it easy to manage infrastructure.You don't have to be an operations expert.Chuck mentions this messaging as he heard it at Microsoft Connect() last year.It's not about bringing you to .NET. It's about making it easy where you're at.Aimee adds that as a new-ish person in the community and Azure excites her because the portal and tutorials are easy to follow for many new programmers.A lot of these features are available across command lines, tools, and much more.The documentation is great. See our interview with Dan Fernandez on the Microsoft Docs. [12:04] Web Apps on LinuxWeb application as a service offering from Microsoft. I don't need to worry about the platform, just what's different about my application.Web Apps has traditionally been on Windows. Web Apps on Linux is in preview.You can choose the size of your infrastructure. You only get billed for what you use and can scale up.Setting up multiple servers, managing synchronization and load balancing is a pain. Web Apps gives you a clean interface that makes this management easy.You can also scale across multiple datacenters around the world.[15:06] Why Linux? What's hard about Windows?Node was originally created on Linux and many tools run nicely on Linux. It was later ported to Windows.The toolchains and IDE's and build processes is in an ecosystem that is targeted more toward Linux than Windows.This allows people to work in an environment that operates how they expect instead of trying to map to an underlying Windows kernel.Aimee gives the example of trying to set up ImageMagick on Windows.Web Apps on Linux also allows you to build integrations with your tools that let you build, test, and deploy your application automatically.[19:12] Supported RuntimesWeb Apps on Linux supports Node, PHP, Ruby, and .NET Core.You can run a docker container with Node up to 6.x. If you want Node 7.x and 8.x you can create your own Docker container.Web Apps on Linux is build on Docker.The containers also have SSH, so developers can log into the docker container and troubleshoot problems on the container.If you can build a container, you can also run it on this service.At certain levels, there's automatic scaling.[22:06] Consistency between containers? Shared ownership of state or assetsIt depends on how you build your app. The Docker containers have a shared storage where all the containers have access to the same data and state.There's a system called kudu that makes this really simple.You can also pull logs across all systems.You can also use SSH in the browser[25:23] What's painful about Linux and containers?How is the application built and how does it manage state so that you can isolate issues.If you have 20 containers, can you connect to the right one.It's up to you to manage correlation between containers so you can find the information you need.Knowing your traffic and understanding what to do to prepare for it with scaling and automation is sometimes more art than science.[28:28] How should you manage state?A lot of these systems lend themselves to running stateless, but you don't want to run mongodb on each container versus running one mongodb instance that everything attaches. You want a common place to store data for the entire app for shared state.[30:34] CosmosDB (was DocumentDB)It's an API equivalent to MongoDB. It's a database as a service and you can connect your containers to the CosmosDB in Azure using your portal to make it super easy.You may need to open up some firewall rules, but it should be pretty straightforward.[34:14] Third Party Logging Management AppsAzure has a service that provides metrics (Application Insights) and a logging service. Many other companies use elasticsearch based solutions that solve some of these problems as well.[36:06] How do people use Web Apps on Linux?Companies building new applications many times want to run without managing any infrastructure. So, they use Azure Functions, and other services on Azure.Lift and shift: Take a virtual machine and change it into a web app container that they can run in the cloud. They also move from SQL Server on a server to SQL Server on the cloud. Moving from hosted MongoDB to CosmosDB.You can also use any images on DockerHub.[40:06] Continuous Integration and Continuous DeploymentWhether you're using a private registry or cloud registry. When you publish a new image, it'll use a webhook to pull the custom image and deploy it. Or to run it through Continuous Integration and then deploy it without any human interaction.Chuck mentions the case when you haven't logged into a server for a while, there's a huge backlog of system updates. Updating your container definitions makes upkeep automatic.[42:02] Process files and workers with PM2 formatYou can set up instances to run across cores with the PM2 definitions. You can also make it run various types of workers on different containers.Why did you use PM2? What other uses are there for this kind of setup?You can tell it which processes to start up on boot. You can also have it restart processes when a file is changed, for example, with a config file you can have it restart the processes that run off that config file.[45:38] How to get startedGetting started with Nodedocs.microsoft.comTrial account with a few hundred dollars in Azure credit.Michael's Linksmichaelcrump.net@mbcrumpgithub.com/mbcrumpJeremy's Linksbit.ly/coderblog@jeremyliknessgithub/jeremyliknessPicksAimeeHaving a little bit of mindfulness while waiting on code and tests to run.JoeOzark on NetflixStar Wars: Rogue OneChuckTravelers on NetflixJeremyOzark filming in Woodstock, GAAutonomous Smart DeskLED light stripsMichaelConference Call BingoLife (Movie)Get Out (Movie)Special Guests: Jeremy Likness and Michael Crump. Support this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

12 Syys 201759min

JSJ 277: Dojo 2 with Dylan Schiemann and Kitson KellyThis episode of JavaScript Jabber features panelists Aimee Knight, Cory House, and Charles Max Wood. They talk with Dylan Schiemann and Kitson Kelly about Dojo 2.[00:02:03] Introduction to Dylan SchiemannDylan is the CEO at Sitepen and co-founder of the Dojo Toolkit.[00:02:22] Introduction to Kitson Kitson is the CTO at Sitepen and project lead for Dojo 2.[00:02:43] Elevator Pitch for DojoDojo 1 has been around forever. Started back in 2004 as a way to solve the challenge of "I want to build something cool in a browser." Promises and web components were inspired by or created by Dojo. It's been a huge influence on the web development community.Dojo 2 is a ground up re-write with ES 2015, TypeScript and modern API's. It's a modernized framework for Enterprise applications.[00:04:29] How is Dojo different from other frameworks?There's a spectrum: small libraries like React with an ecosystem and community of things you add to it to Angular which is closer to the MV* framework with bi-directional data binding. Vue lands somewhere in the middle. Dojo 2 is also somewhere in the middle as well. It's written in TypeScript and has embraced the TypeScript experience.[00:06:00] Did the Angular 2 move influence the Dojo 2 development and vice-versa?Dojo 2 had moved to TypeScript and 2 days later Angular announced that they were going to TypeScript. Angular also moved very quickly through their BETA phase, which caused some challenges for the Angular community.With Dojo 2, they didn't start the public discussion and BETA until they knew much better what was and wasn't going to change. They've also been talking about Dojo 2 for 6 or 7 years.The update was held up by adoption of ES6 and other technologies.Dojo 1 was also responsible for a lot of the low-level underpinning that Angular didn't have to innovate on. Dojo 2 was built around a mature understanding of how web applications are built now.People doing Enterprise need a little more help and assistance from their framework. Dojo provides a much more feature rich set of capabilities.Angular could have pushed much more of TypeScript's power through to the developer experience. Dojo much more fully adopts it.It's also easier if all of your packages have the same version number.Call out to Angular 4 vs Angular 2.[00:12:44] AMD ModulesWhy use AMD instead of ES6 modules?You can use both. Dojo 2 was involved in the creation of UMD. James Burke created UMD while working on Dojo.ES6 modules and module loading systems weren't entirely baked when Dojo 2 started to reach maturity, so they went with UMD. It's only been a few months since Safari implemented the ES6 module system. Firefox and friends are still playing catchup.The Dojo CLI build tool uses webpack, so it's mostly invisible at this point.So, at this point, should I be using UMD modules? or ES6? Is there an advantage to using AMD?With TypeScript you'd use ES6 modules, but UMD modules can be loaded on the fly.[00:16:00] Are you using Grunt?Internally, for tasks we use Grunt. But for users, we have a CLI tool that wraps around Webpack.For package builds and CI, Grunt is used.[00:18:30] What is the focus on Enterprise all about?There are a lot of different challenges and complexities to building Enterprise apps. Dojo was the first framework with internationalization, large data grids, SVG charts, etc. Dojo has spend a long time getting this right. Many other systems don't handle all the edge cases.Internationalization in Angular 2 or 4 seems unfinished.Most Dojo users are building for enterprises like banks and using the features that handle large amounts of data and handle those use cases better.[00:21:05] If most application frameworks have the features you listed, is there a set of problems it excels at?The Dojo team had a hard look at whether there was a need for their framework since many frameworks allow you to build great applications. Do we want to invest into something like this?React has internationalization libraries. But you'll spend a lot of time deciding which library to use and how well it'll integrate with everything else. A tradeoff in decision fatigue.In the Enterprise, development isn't sexy. It's necessary and wants to use boring but reliable technology. They like to throw bodies at a problem and that requires reliable frameworks with easily understood decision points.Producing code right is a strong case for TypeScript and they pull that through to the end user.Many frameworks start solving a small set of problems, become popular, and then bolt on what they need to solve everything else...Dojo tried to make sure it had the entire package in a clear, easy to use way.You can build great apps with most of the big frameworks out there. Dojo has been doing this for long enough that they know where to optimize for maintainability and performance.[00:29:00] Where is Dojo's sweet spot? https://www.sitepen.com/blog/2017/06/13/if-we-chose-our-javascript-framework-like-we-chose-our-music/The biggest reason for using Dojo over the years is the data grid component.They also claim to have the best TypeScript web development experience.You may also want a component based system with the composition hassles of React.The composability of components where one team may write components that another uses is a big thing in Dojo where one person doesn't know the entire app you're working on.Theming systems is another selling point for Dojo.[00:34:10] Ending the framework warsTry Dojo out and try out the grid component and then export it to your Angular or React app.There are a lot of frameworks out there that do a great job for the people who use them. The focus is on how to build applications better, rather than beating out the competition.Sitepen has build apps with Dojo 2, Angular, React, Dojo + Redux, etc.[00:39:01] The Virtual DOM used by Dojo2 years ago or so they were looking for a Virtual DOM library that was small and written in TypeScript. They settled on http://maquettejs.org/.The more you deal with the DOM directly, the more complex your components and libraries become.Makes things simpler for cases like server side rendering getting fleshed out in BETA 3.It also allows you to move toward something like React Native and WebVR components that aren't coupled to the DOM.They moved away from RxJS because they only wanted observables and shimmed in (or polyfilled) the ES-Next implementation instead of getting the rest of the RxJS  that they're not using.[00:46:40] What's coming next?They're finishing Dojo 2. They're polishing the system for build UI components and architecture and structuring the app. They plan to release before the end of the year.They're also wrapping up development on the Data Grid, which only renders what shows on the screen plus a little instead of millions of rows.[00:49:08] TestingThey've gothttp://theintern.io.It pulls together unit testing, functional testing, continuous integration hooks, accessibility testing, etc.It's rewritten in TypeScript to take advantage of modern JavaScript.The Dojo CLI uses intern as the default test framework.Kitson build the https://github.com/dojo/test-extras library to help with Dojo testing with intern.Dojo Links- http://dojo.io- http://github.com/dojo/meta- http://sitepen.com/blog- https://gitter.im/dojo/dojo2- http://github.com/dylans- http://twitter.com/dylans- http://twitter.com/sitepen- http://twitter.com/dojo- http://github.com/kitsonk- http://twitter.com/kitsonkPicksCory- https://www.farnamstreetblog.com/2017/08/amateurs-professionalsAimee- https://www.eventbrite.com/e/devfest-florida-2017-tickets-31833188925?discount=JSJABBER (use code 'jsjabber')Chuck- Taking some time off- http://amzn.to/2j8VKRJ- https://www.youtube.com/watch?v=vVsXO9brK7MDylan- https://www.zenhub.com/- http://halfstackconf.com- https://www.sitepen.com/blog/2017/06/13/if-we-chose-our-javascript-framework-like-we-chose-our-music/Kitson- https://en.wikipedia.org/wiki/Dunbar%27s_number Special Guests: Dylan Schiemann and Kitson Kelly. Support this podcast at —Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

6 Syys 20171h 3min