POPULARITY
Travelling to JSConf EU from another country? You probably had to pay an arm and a leg for a data roaming package on your phone. But there's a better way! What if I told you that you could stay connected to the internet with a phone that can only send and receive text messages? In this talk we'll build our own browser that makes all requests over SMS, so that next time you can forget about that fancy data package.
Machine Learning is a powerful tool that offers unique opportunities for JavaScript developers. This is why we created TensorFlow.js, a library for training and deploying ML models in the browser and in Node.js. In this talk, you will learn about the TensorFlow.js ecosystem: how to bring an existing ML model into your JS app and re-train the model using your data. We'll also go over our efforts beyond the browser to bring ML to platforms such as React Native, Raspberry Pi, and Electron, and we'll do a live demo of some of our favorite and unique applications!
As usage of ad blocking software has risen over the years, an entire micro-industry has popped up catering to publishers - promising to get around the ad blocker and show ads to users of ad blocking software. Some of these techniques rely on browser bugs, or limitations of browser extensions and some are just extremely creative ways to get around ad-blockers. This has forced ad blockers to come up with their own ingenious ways to counter and block the circumvented ads. In this talk, we'll go over some of the techniques used in this cat and mouse game between ad blocking extensions and the people who want to circumvent them. It's a fascinating peek into a world very few people seem to know.
With CSS animations and web animations moving elements became possible in the browser. But how one moves an object in such a way that it appears “correct” for the human eye? How does a motion feel natural? These and similar questions confronted the artists who brought cartoons to life as early as 1906. Let's take a look behind the scenes and see how drawings learned to walk and what we can learn from it for animations in the browser.
Offline capable web apps have come a long way in just a few years. Tools like service workers, PouchDB & CouchDB gave answers to the first questions of “can we do this, where do we begin?”, pushing new possibilities to the browser. But taking the medical supply system online & offline for Africa's most populous country asked us a whole new set of questions. How do you model distributed data and scalable code for 30,000 clinics? What about that growth is easy to mess up, and how do we plan for it?
Wer sein Studium abbricht, um ins Denoland zu gehen, hat sicher eine interessante Geschichte zu erzählen. Aus diesem Grund haben wir in dieser Folge Luca Casonato zu Gast, der uns von Deno erzählt, einer Laufzeitumgebung für JavaScript und TypeScript. Deno wurde 2018 von Ryan Dahl, dem Schöpfer von Node.js, auf der JSConf EU vorgestellt (hier geht's zur Aufzeichnung des Talks). Er beschreibt darin fundamentale Schwächen von Node, die er bereut und nun mit Deno lösen möchte. Unser Gast Luca arbeitet als eine der wenigen Personen hauptsächlich am Projekt und spricht mit uns über die größten Unterschiede zwischen den beiden Varianten. In dieser Folge streifen wir das Dependency-Management von Deno, seine Eigenschaften als opinionated Runtime und seine hohe Sicherheit gegenüber Node. Hier kommt ihr zu Lucas Webseite und seinem Twitter-Profil. Auf der Webseite von Deno könnt ihr euch noch mehr Infos einholen. Picks of the Day Luca: Die Deno-Extension für Visual Studio Code mit cooler Autocompletion. Fabi: JSConf Vortrag von Philip Roberts: What the Heck is the Event Loop anyway. Ein Must-Watch für alle Javascript-EntwicklerInnen. Ihr habt euch schon immer gefragt, was die Event Loop ist bzw. wie sie funktioniert? Dann ist das Video genau richtig. Ansonsten ist es aber auch nochmal die perfekte, unterhaltsame Auffrischung, um die Event Loop komprimiert in 25 Minuten erklärt zu bekommen. Schreibt uns! Schickt uns eure Themenwünsche und euer Feedback. podcast@programmier.bar Folgt uns! Bleibt auf dem Laufenden über zukünftige Folgen und virtuelle Meetups und beteiligt euch an Community-Diskussionen. Twitter Instagram Facebook Meetup YouTube Musik: Hanimo
Since its creation in 2016, Yarn continuously pushed for better standards in the JavaScript ecosystem in particular. Dependency locking, built-in monorepos, zero-network modes, Plug'n'Play resolution, we've been on all fronts. Let's discuss what we have in store for the future, and what it means for our ecosystem!
Most people connected to the Web are carrying JavaScript in their pocket without even knowing it, and those of us making tools for building with it are either unaware of or blissfully ignoring that population. While JavaScript's pervasiveness grows, so is the gap in its literacy, and this is a gap we need to solve if we're ever going to survive self-driving cars on the blockchain. Let's talk about JavaScript, the tool, as opposed to JavaScript, the Oracle-run Twitter account.
In September of 2008, Google's Chromium Project released V8, a JavaScript engine, as part of a browser optimization wave that heralded the era of JavaScript browser applications that we both love, and love to hate. Less than a year later, in 2009, Ryan Dahl announced (at this very conference!) a way to run the V8 browser environment outside of the browser- Node.js, a platform that held the promise of unifying web application development, where both client and server side development could happen in the same language - JavaScript. A decade later, V8, JavaScript, and its new buddy WebAssembly, have expanded to lands charted only a few years after Node.js debuted- known (confusingly) as the “Edge”. In this talk, we'll introduce what the “Edge” is and why we are excited for it to revolutionize computation on the web. We'll explore how this adventurous JavaScript engine, V8, is so well suited to tasks previously limited to Virtual Machines, Containers, or even simply Operating Systems. Finally, we'll talk about security, Spectre, and ask ourselves the age old question, “You can do it, but should you?”.
After so many years sitting with the computer you can take your old scratched Les Paul or Stratocaster from the case and fill all the space around with warm riffs. I'm going to show how to transform the code into Kirk Hammett's wah-wah, Stevie Ray Vaughan's overdrive and Kurt Cobain's distortion. You'll learn how to parse audio input in real-time using JavaScript and the Web Audio API. I'll be jamming live on stage with my guitar to demo every code example and we'll also use WebRTC to jam with friends across the world! After this talk, you will be familiar with the principles behind pedal sound effects and how to create them in code. Let's rock the Web!
From its friendly developer experience to its performance benefits, a lot has been said about GraphQL. Underlying it all is the GraphQL query language, made possible by GraphQL schema language. These surprisingly versatile features have the potential to provide a single interface for all modern web app development concerns. We will start with a case study on how we use GraphQL queries as an universal interface to resolve data over a variety of datasources ranging from remote HTTP requests, to local CSV files, and in-memory data stores. Next we will explore these ideas further, using GraphQL queries as an interface over the DOM and various other web APIs.
Podcast Description Kim is taking some much needed time off, so enjoy this presentation from the 2018 JSConf EU conference. Additional Resources Presentation SlidesPresentation Video Transcription 00:31 Hello, everyone. [Shouts] Hello, everyone! [Audience cheers]. Alright! If you don't follow me on Twitter, you should know, ask somebody, it's not going to be a quiet room. Welcome to "Unintended Consequences: How to Reduce Exclusionary Practices in Organizations and Communities". I am Kim Crayton. Yes!You can use the hashtag #causeascene, you can find me @KimCrayton1. I have a website hashtagcauseascene.com as well as kimcrayton.com. After this slide, I usually would put my credentials in there but you know what, I'm causing such a scene I don't care if you don't trust what I have to say. I know what I'm talking about. So there it is. Also, there it is.So let's define some terms. I am an educator by trade. I only entered tech four years ago, and I like to start everybody on the same page so that when I get into my talk, people aren't saying, "Yeah, I don't know what that means." So we just start off everybody the same place.01:46Privilege is about access. When I talk about privilege, I don't just talk about race and gender and all these things. I talk about access. That means that there's a group of people who have more access to resources, connections than other groups. That's what privilege is, it's that simple. It's about access. And so I use this picture because people have seen these lil' monkeys in Japan, they think, "Oh, that's so cute." But right there is an example of access, because there's a family of female, family group, that is, they're the only ones who get in the water. The other monkeys on the outside, they gotta fend for themselves. If they freeze to death, they freeze to death. So it's only, a family of monkeys that can get in. So this family has access to this pool of this hot water where others don't.Underrepresented is about numbers. So that's all that is. In tech, white women are underrepresented.Marginalized is about treatment. In tech, many white women are not marginalized, so I like to make that distinction because when people say they want diversity, adding a white woman to your team or to your panel is not diversity.03:09 Diversity is about variety. I know I'm from the 'States, and we have Crayola crayons. When you get that big box—I was an only child so I got a 64 box of crayons, I had a lot of variety—that's what diversity is about.To me, inclusion is the holy grail. It is about experience. It is about everyone having the experience they expect when they come in contact with your business, your community or your event. Inclusion is not about equity, because if you, white man, and I, Black woman from the south of the United States, start the race at the same time, you're still gonna be ahead of me. I need you to stop, sit down for a second, and let me catch up—and past you. Inclusion is not about quotas. That's underrepresentation. Inclusion is about people's experiences with your companies, your communities, and your events.All right, so we gonna talk about some businesses here, and these are some of the things that I find that get individuals in trouble or get them in places they don't want to be with these unintended consequences is because many people think they have a business when in fact they have a product or a service. A product or a service is not a business. A business requires processes, policies, and procedures that allow you to grow, to scale, to recover. But just for the fact that you have created a product or service, you do not necessarily have a business. That's why a VC can come in and take over your company, because they bring in those skills to help you grow and everything else. And I blame the lean canvas model for this because that is about iterating a product or service and not about a business.05:04Also,
The year is 1972 and GUI applications like no one has seen before are being built in Smalltalk: bitmaps graphics, draggable elements, drop-down menus, collapsable windows
“We all know and love framework-like features such as hot module replacement, reactive properties, templating, CSS-in-JS, lazy-loaded bundling, etc. Stencil is a new approach, a build-time abstraction with framework-level productivity, that generates hand-optimized components using future-proof web APIs. We'll discuss the architecture of Stencil and the innovations a compiler can introduce to your apps and design systems!
“Falling sand games” were a beloved childhood curiosity, but when I set out to write my own in Javascript, performance got in the way of the scale and granularity I wanted. Could WebAssembly be the tool to build the sand simulation of my dreams, or is it still just for blog posts? I'll share with you the history and beauty of falling sand games, what I learned building mine to leverage the power of modern browsers, and show you how WebAssembly can cooperate productively with the JS ecosystem to enable awesome web experiences.
npm has more data than anyone about who JavaScript developers are and what we're up to. Using registry stats and the results of our 2019 ecosystem survey of over 30,000 developers, I break down the current state of JavaScript and where trends look like they're headed, so you can make more informed technical choices.
With nearly 1,000,000 packages, the npm ecosystem is the largest out there, by far – but the ecosystem and its package manager were created in more humble times, for small projects and packages centered around the Node.js ecosystem itself. It's about time we redefined package management for modern web development, and that redefinition is tink: a package unwinder for JavaScript brought to you by npm itself. With tink, you'll find unprecedented speeds, deep compatibility with everything from Node.js to bundlers, and a UX workflow optimized for the modern web developer. Come join us for the official unveiling and find out what the future of all package management will look like for years to come.
Web APIs developed and standardized by the browsers have been serving client-side JavaScript applications with a wide selection of features out of the box, while Node.js have been developing another set of APIs that are today the de-facto standards for server-side JavaScript runtimes. There is now a conscious effort to bring the two worlds closer together, in particular by introducing more Web APIs into Node.js core, but it's not an easy ride - not every Web API, designed for the browsers, makes sense for Node.js. In this talk, we are going to take a look at the story of Web APIs in Node.js core - what Node.js have implemented, what are being discussed, what are blocking more APIs from being implemented, and what we can do to improve the developer experience of the JavaScript ecosystem.
Currently only ‘fs' and ‘dns' have an experimental promise api in Node core. People LOL at node.js core modules for still using the callback pattern. I could launch into a bunch of puns here but instead I'll just say the current status is sad but fixable. Where are we? What do we need to do? How can you help?
It's almost here! Houdini — the future of CSS! This spec allows developers to write web worklets with JavaScript syntax and access the CSS Object Model for the very first time. Everything will change! In this talk, we'll will walk through some of the visual magic we can create by using Houdini and its various upcoming browser APIs, and go through a live demo of how we can get started with implementation. Learn about how to use Houdini and what it means for the future of web application styling.
PWAs are now installable on every mobile and desktop OSs, but there is a lot of new things since last year we need to do to create a successful experience. We will start understanding the App Lifecycle on every OS including new APIs, the limitations on iOS and how to deal with them, and how WebAPK works on Android. We will mention challenges on desktop PWAs, including multi-window management and we will finally cover distribution channels, including new DOM events to improve analytics, how to create a custom Install experience, and how to distribute the app in the store.
Thankfully, every year ECMAScript gives us new shinies to advance how we code JavaScript. I've found myself digging into features & proposals ever since my curiosity of ES2017's SharedArrayBuffer took me down a fascinating rabbit hole. Let's delve into some of the features & proposals we get to look forward to in 2019.
This presentation is about server performance, which means that no time in the world would be enough to cover it all. Hopefully, I can share with you the top #10 things I've learned while putting JavaScript on the top of the server side benchmarks. You will learn about runtimes and engines, how some are more capable than others, and sometimes the obvious choice is not always the right one… This talk is about thinking outside of the box, being creative and don't take anything for granted. We will debunk myths about native code vs script or RAM usage, it's going to be fast! I promise!
Very few developers have the need to write super optimized code. In application development we tend to favor readability over optimization. But that's not the case with frameworks. Developers who use frameworks expect them to run as fast as possible. In fact, speed is often a defining characteristic when choosing a framework. There are techniques that make code run faster. You've probably heard about linked lists, monomorphism and bitmasks, right? Maybe you've even used some. Well, you can find all these and a bunch of other interesting approaches in the sources of most popular JS frameworks. Over the past year I've seen a lot while reverse-engineering Angular and React. In this talk I want to share my findings with you. Some of you may end up applying them at work. And others, who knows, may even end up writing the next big framework.
Have you wondered how JS engines work? This past year I built an engine from scratch in Rust. It was fun, weird, exciting and sometimes exhausting. I will share my experience as well as what it is like to work on the specification, collaborate with TC39, and lessons from engines in use today.
To build inclusive websites, developers have to consider accessibility, performance and user flows. Crafted source code forms the foundation for thought-through UIs, but it's not only about the code. Let's have a look at HTTP, and to be specific, its headers that can have a direct impact on user experience.
The JS package commons is in the hands of a for-profit entity. We trust npm with our shared code, but we have no way to hold npm accountable for its behavior. A trust-based system cannot function without accountability, but somebody still has to pay for the servers. How did we get here, and what should JavaScript do now?
Ionic Core team member Manu joins the podcast to talk about his JSConf EU talk and why bringing a compiler to the web is good for everyone
Podcast Description “Where are our biases? What do we have to do to get more people of color into our team and feel safe in our team. And then maybe feeling safe enough to tell us: we are feeling harm, please help us in this case. I think this is the biggest failure that they didn’t feel safe enough to tell us that they need our help. Or to trust us that we want to help or could help in this situation.” Simone Haas is CEO of The Neighbourhoodie Software GmbH. After studying history and working in the publishing industry she moved to Berlin in 2015 and became a member of the CSSconf EU and JSConf EU team. Since 2018 she is curator of JSConf EU. Being a non-programming person in tech she is challenging the status quo by managing the operative business behind the code. Additional Resources BIPoCiT Space: What Happens When You Disrupt White TechLinkedIn Twitter Simone Haas Become a #causeascene Community Sponsor because disruption and innovation are products of individuals who take bold steps in order to shift the collective and challenge the status quo.Learn more >All music for the #causeascene podcast is composed and produced by Chaos, Chao Pack, and Listen on SoundCloud Listen to more great #causeascene podcasts full podcast list >
Deler av panelet har vært på tur til Berlin for den (foreløpig) siste utgaven av JSConfEU. En konferanse som har mye historiske høydepunkter i JavaScript-verden. Dette året var ikke uten unntak om du skal tro panelet. På slutten av dag en ble det som noen omtaler som et potensielt vendepunkt for JS-økosystemet lansert i form av et nytt federert desentralisert pakkeregister og verktøy. Ment som en mulig erstatter for et potensielt belastet VC-finansiert npm, inc. Hør dagens episode for refleksjoner og reaksjoner av det som beveger seg i bransjen. Shownotes: https://bartjs.io/37-jsconfeu-entropic/
Cassidy and Marie share some of the fun things CodePen community members are doing around the web including newsletters, Pass the Pen, JSConfEU, and Zdog. The post #224: Community Roundup appeared first on CodePen Blog.
GUEST BIO: My guest on today’s show is a front end developer who has been writing code since he was 8 years old. He enjoys people, code and talking to people about code. He now travels around the world encouraging, educating and empowering developers in the web development community. EPISODE DESCRIPTION: Phil’s guest on his show today is Tejas Kumar. He is a front-end developer who has been coding since the age of 8. Tejas has worked with a long list of front-end frameworks, programs and languages, including JavaScript, TypeScript, React, and the Babel webpack. He is also a conference speaker who is working towards his goal of speaking at every JSConf, across the word. Tejas wants to educate and empower developers, in every corner of the globe. KEY TAKEAWAYS: (1.10) – I would like to start by asking about your work traveling the world speaking to developers and empowering them. Tejas explains that he started doing this, June of last year, when he spoke at JSconf EU. His talk was well received and he really enjoyed it. So, he decided that he would like to speak at each of the JSconf events that are held worldwide. Tejas structures his talks as dialogue. He enjoys the conversation he has with his audience. Afterward he gets to carry that conversation on and talk to some really interesting people, from all walks of life. Everyone from web architects to traditional architects who design buildings. (2.25) - So in terms of the numbers of conferences, talks you've done, how many of you clocked up now? Last year, Tejas did 7 conferences in 6months. But, that is nothing compared to his friend Sarah Vieira who spoke at 47, last year alone. His aim is to do an average of one a month, so he can maintain a reasonable work-life balance. (3.10) – Have you got any conferences coming up? There is one that had not yet been announced, at the time this recording was made. But, he also due to speak in September, at JSconf Budapest. (4.15) – Can you please share a unique career tip with the I.T. career audience? Tejas says it is important to remember that IT professionals are working in an industry where feigning knowledge is the norm. He has noticed that in technical meetings, everyone, including himself, will just nod their heads and pretend that they fully understand what is going on. Tejas finds this sad. He points out that a culture in which people feel an overwhelming need to be right and are disinclined to ask questions is not a healthy one. There are also a few people who feel an overwhelming urge to constantly correct everyone. Often, these people publically pick others up about silly, unimportant things simply because they want to appear to be cleverer. They tend to think they are always right. People like that can end up putting those who are new to the industry. (7.54) – Can you tell us about your worst career moment? And what you learned from that experience. Unfortunately, at the start of his career Tejas was thrown in at the deep end. He was being asked to do a mid-level job despite the fact he had very little experience. Worse, his team leader was constantly critical of him. Despite this, Tejas toughed things out and became good at the job. So, much so that other companies were headhunting him. But, when he asked for a raise his CTO just laughed at him and said he was not worth it and nobody would pay him that sort of money. Naturally, he quit. Before asking for the raise he had been looking around to see what was available. So, he knew what he was asking for was reasonable and that he could get a job elsewhere. In other words he had leverage. So, when they said no, he was comfortable with just quitting and moving on. In fact, he had already been offered a job by a company he liked the look of. But, he was not sure he was qualified and experienced enough. So much so, that he wrote back and explained this to them. Fortunately, they were really positive. Their attitude was that he knew more than he thought and if he did not they were sure he could quickly fill any gaps in his knowledge. Even before the hiring was official his new boss demonstrated that he believed in Tejas. After working for a boss that constantly tore him down working for someone who built him up was very refreshing for Tejas. Quitting his previous post was the best thing Tejas has ever done. (10.35) – What has been your career highlight? Tejas responds by saying that he is actually currently living his career highlight. Every day feels like a new best day at his job. He works with a brilliant team, has a lot of freedom, can more or less choose what technology he works with and works on interesting projects. Tejas especially appreciates the fact that his team works smart. For example, they budgeted 2 days to build a feature. With the help of his team, he was able to build it in 15 minutes. Phil jokes that if he was Tejas’ boss he would probably be challenging his estimation process. This joke encourages him to share another career highlight. Tejas always has a good time at conferences and meets interesting people. But, being asked to speak at React Finland was extra special. It is non-profit, everyone stays in the same hotel and the atmosphere is great. (12.17) – Can you tell us what excites you about the future of the IT industry and careers? The fact that the web is an on-exhaustible resource really excites Tejas. He grew up in Qatar, a country that is built on oil, which, unfortunately, is running out. So, Tejas appreciates working in an industry where there will always be work. Tejas is particularly pleased to see the serverless way of working coming to the fore. It is a simple way of working that means that things like IoT are now a reality. He is also to see the industry become more inclusive. People from every corner of the globe are getting involved and succeeding in the tech industry. They are many people from these countries becoming leaders in their field. People of color, women and non-binary people are all enjoying successful IT careers. (14.11) – What drew you to a career in IT? Tejas has a rare, dangerous and life-threatening illness. Even doing something relatively simple like climbing the stairs or lifting a backpack could kill him. He has ended up in the emergency room several times after doing something relatively minor. So, for Tejas sitting at a screen and writing is his only viable option. Fortunately, at the age of 8, Tejs discovered that he liked coding. He could not go to school or play outside, so he spent many hours playing around with HTML and coding. So, naturally, he got quite good at it. His mother did not expect him to live past 10th grade. So, it feels great to have achieved as much as he has. Tejas is understandably proud of what he has been able to do with his friend, especially the conference speaking. His message to the IT Energizer audience is – if I can do it, so can you. (16.08) – What is the best career advice you have ever received? Someone once warned Tejas not to believe the hype. The same people that are talking you up today may not do so tomorrow. It is very important not to base your identity on what people say about you. If you do that, you are basing your view of yourself on a very shaky foundation. (17.22) - Conversely, what is the worst career advice you've ever received? Someone once told Tejas to quit IT. They literally said you suck at IT, quit. Kill yourself. He knows that some of it must have been a joke. But, at the time, it did not feel that way. Naturally, he was very upset by this and thought maybe I do suck; maybe I will never be anything. It was a real low point for Tejas. (17.38) – If you were to begin your IT career again, right now, what would you do? Tejas thinks he would not actually do anything different. He would still start by learning and working with JavaScript. It is a really forgiving language, which makes it ideal for beginners. (18.15) – What are you currently focusing on in your IT career? Tejas is challenging himself to learn the operations side of things. For example, Kubernetes, he is also interested in learning more about back end development. (19.06) – What is the number one non-technical skill that has helped you the most in your IT career? Tejas says it is his ability to communicate and the fact that he enjoys public speaking. But, these skills have taken a lot of time and hard work to learn. As a child, he was badly bullied. Because he could not go to school or play outside it was hard to connect with people, he became socially awkward. He hated the fact that people did not like him. So, decided to do something about it. He went online and googled “how to make people like you” and read tons of books on the subject. It helped. Bit by bit Tejas learned how to put people at their ease and be good company. Today, being charming, considerate and a good communicator are all 2nd nature to him. (20.44) - What do you do to keep your own IT career energized? His job keeps him energized. He really loves the culture his company has, the team and the work he does. He can’t wait to go to work every day. Tejas gets head-hunted quite a lot, but he is so happy with his current company that he is not tempted by any of the offers. He feels energized every single day by the work he is currently doing. (21.57) - What do you do in your spare time away from technology? Tejas loves music, in particular, playing music. He has an album due out soon. Plus, right now, Tejas is busy planning his wedding. (22.25) – Phil asks Tejas to share a final piece of career advice with the audience. People matter more than code. He would even make the case that soft skills matter more than the hard ones do. BEST MOMENTS: (6.32) TEJAS – "CHECK TO SEE WHO SAID IT" (9.15) TEJAS – “I normally do not negotiate salary unless I have leverage." (10.00) TEJAS – "Developer jobs are in demand. The harvest is plentiful, but the workers are few." (12.42) TEJAS – "The web is a non-exhaustible resource” (16.07) TEJAS – "There's nothing that can ultimately hold you back, if that’s your path." () TEJAS – "" CONTACT TEJAS: Twitter: https://twitter.com/tejaskumar_ Github: https://github.com/tejasq Website: https://www.tejaskumar.com/
Panel: Aimee Knight AJ O’Neal Charles Max Wood Special Guest: PJ Evans In this episode, the panel talks with PJ Evans who is a course developer and an instructor through Manning’s course titled, “Node.js in Motion.” This course is great to learn the fundamentals of Node, which you can check out here! The panel and PJ talk about this course, his background, and current projects that PJ is working on. Check out today’s episode to hear more! Show Topics: 0:00 – Advertisement: KENDO UI 0:36 – Chuck: Welcome and our panel consists of Aimee, AJ, myself, and our special guest is PJ Evans. Tell us about yourself and your video course! NODE JS in Motion is the title of the course. Can you tell us more? 1:29 – PJ: It’s a fantastic course. 2:25 – Chuck: You built this course and there is a lot to talk about. 2:36 – Aimee: Let’s talk about Node and the current state. 2:50 – Chuck: Here’s the latest features, but let’s talk about where do you start with this course? How do you get going with Node? What do people need to know with Node? 3:20 – Aimee. 3:24 – PJ talks about Node and his course! 4:02 – PJ: The biggest headache with Node is the... 4:13 – Chuck. 4:19 – PJ: I am sure a lot of the listeners are familiar with callback hell. 4:50 – Aimee: Let’s talk about the complexities of module support in Node! 5:10 – PJ: It’s a horrible mess. 5:17 – Aimee: Maybe not the tech details but let’s talk about WHAT the problem is? 5:31 – PJ: You are talking about Proper Native ES6 right? They are arguing about how to implement it. 6:11 – PJ: My advice is (if you are a professional) is to stick with the LT6 program. No matter how tensing those new features are! 6:46 – Aimee: It could be outdated but they had to come back and say that there were tons of complexities and we have to figure out how to get there. 7:06 – PJ: They haven’t found an elegant way to do it. 7:15 – Panel: If it’s a standard why talk about it? Seriously – if this is a standard why not implement THE standard? 7:38 – PJ. 8:11 – Panel. 8:17 – Aimee: I would love to talk about this, though! 8:24 – Chuck: I want to talk about the course, please. 8:30 – PJ. 8:54 – Chuck: We will keep an eye on it. 9:05 – PJ. 9:16 – PJ: How is it on the browser-side? 9:33 – Aimee: I don’t want to misspeak. 9:41 – Chuck: I don’t know how complete the forms are. 9:49 – Aimee: I don’t want to misspeak. 9:56 – PJ: I just found the page that I wanted and they are calling it the .MJS or aka the Michael Jackson Script. You can do an import from... Some people think it’s FINE and others think that it’s a TERRIBLE idea. 10:42 – Chuck: “It sounds like it’s a real THRILLER!” 10:52 – Panel. 11:25 – Panel: When you start calling things the Michael Jackson Solution you know things aren’t well. 11:44 – Aimee: Just to clarify for users... 11:57 – Chuck: I want to point us towards the course: NODE.JS. Chuck asks two questions. 12:34 – PJ: The concepts aren’t changing, but the information is changing incredibly fast. The fundamentals are fairly settled. 13:22 – Chuck: What are those things? 13:28 – PJ talks about how he structured the course and he talks about the specifics. 15:33 – Chuck: Most of my backend stuff is done in Ruby. Aimee and AJ do more Java then I do. 15:55 – Panel: I think there is something to understanding how different Node is. I think that Node is a very fast moving train. Node has a safe place and that it’s good for people to know about this space. 16:34 – Aimee: Not everyone learns this way, but for me I like to understand WHY I would want to use Node and not another tool. For me, this talk in the show notes really helped me a lot. That’s the core and the nature of NODE. 17:21 – PJ: Yes, absolutely. Understanding the event loop and that’s aimed more towards people from other back ends. Right from the beginning we go over that detail: Here is how it works, we give them examples, and more. 18:08 – Aimee: You can do more than just create APIs. Aimee mentions Vanilla Node. 18:50 – PJ: To get into frameworks we do a 3-line server. We cover express, and also Sequelize ORM. 19:45 – Advertisement – Sentry.io 20:43 – Chuck: I never used Pug. 20:45 – PJ: PUG used to be called JADE. 20:56 – Aimee. 21:14 – PJ: Express does that for you and I agree with you. I advocate a non-scripted approach, I like when frameworks have a light touch. 22:05 – Aimee: That’s what I liked about it. No offense, Chuck, but for me I didn’t like NOT knowing a lot of what was not happening under the hood. I didn’t want to reinvent the wheel, but I wanted to build at a lower level. 22:40 – PJ: I had the same experience. I wanted to figure out why something wasn’t working. 23:24 – Panel: I had a friend who used Rails...he was cautious to make a switch. This past year he was blown away with how much simpler it was and how fast things were. 24:05 – Aimee: I feel like if you want to learn JavaScript then Node might be easier on the frontend. 24:21 – Chuck: No pun intended. No, but I agree. I like about Rails is that you had well-understood patterns. But the flipside is that you have abstractions... To a certain degree: what did I do wrong? And you didn’t follow the pattern properly. 25:57 – Panel: With Node you get a little bit of both. To me it’s a more simple approach, but the downside is that you have 100’s of 1,000’s of modules that almost identical things. When you start reaching out to NPM that... 26:29 – PJ: Yes the module system of NPM is the best/worst thing about NODE. I don’t have an answer, honestly. There is a great article written that made me turn white. Here is the article! 28:12 – Panel: The same thing happened with the ESLint. That was the very problem that he was describing in the article. 28:50 – PJ: Yep, I put that in the chat there – go ahead and read it! It’s not a problem that’s specific to Node, there are others. It’s the way we do things now. 29:23 – Chuck: We have the NODE Security project. A lot of stuff go into NPM everyday. 29:43 – PJ: We cover those things in the course. 29:53 – Chuck: It’s the reality. Is there a place that people get stuck? 30:00 – PJ answers the question. 30:23 – Aimee. 30:55 – PJ: I am coding very similar to my PHP days. 31:20 – Aimee. 32:02 – PJ: To finish off my point, I hope people don’t loose sight. 32:18 – Aimee. 32:20 – PJ: I am working on a project that has thousands of requests for... 32:53 – Chuck: Anything you WANTED to put into the course, but didn’t have time to? 33:05 – PJ: You can get pretty technical. It’s not an advanced course, and it won’t turn you into a rock star. This is all about confidence building. It’s to understand the fundamentals. It’s a runtime of 6 hours and 40 minutes – you aren’t just watching a video. You have a transcript, too, running off on the side. You can sit there and type it out w/o leaving – so it’s a very interactive course. 34:26 – Chuck: You get people over the hump. What do you think people need to know to be successful with Node? 34:38 – PJ answers the question. PJ: I think it’s a lot of practice and the student to go off and be curious on their own terms. 35:13 – Chuck: You talked about callbacks – I am thinking that one is there to manage the other? 35:31 – PJ answers the question. PJ: You do what works for you – pick your style – do it as long as people can follow you. Take the analogy of building a bridge. 36:53 – Chuck: What are you working on now? 37:00 – PJ: Educational tool called SCHOOL PLANNER launched in Ireland, so teachers can do their lesson planning for the year and being built with Express. Google Classroom and Google Calendar. 39:01 – PJ talks about Pi and 4wd. See links below. 40:09 – Node can be used all over the place! 40:16 - Chuck: Yes, the same can be said for other languages. Yes, Node is in the same space. 40:31 – PJ: Yep! 40:33 – Chuck: If people want to find you online where can they find you? 40:45 – PJ: Twitter! Blog! 41:04 – Picks! 41:05 – Advertisement – eBook: Get a coder job! Links: JavaScript jQuery React Elixir Elm Vue ESLint Node.js Node Security Project Node Security Project - Medium Manning Publications: Course by PJ Evans PUG JSConf EU – talk with Philip Roberts Medium Article by David Gilbertson Hackster.io – Pi Car Pi Moroni Holding a Program in One’s Head PJ Evans’ Twitter Sponsors: Kendo UI Sentry Cache Fly Get a Coder Job Picks: Aimee Paul Graham - Blog AJ Rust Charles Tweet Mash-up The Diabetes Code PJ Music - Max Richter
Panel: Aimee Knight AJ O’Neal Charles Max Wood Special Guest: PJ Evans In this episode, the panel talks with PJ Evans who is a course developer and an instructor through Manning’s course titled, “Node.js in Motion.” This course is great to learn the fundamentals of Node, which you can check out here! The panel and PJ talk about this course, his background, and current projects that PJ is working on. Check out today’s episode to hear more! Show Topics: 0:00 – Advertisement: KENDO UI 0:36 – Chuck: Welcome and our panel consists of Aimee, AJ, myself, and our special guest is PJ Evans. Tell us about yourself and your video course! NODE JS in Motion is the title of the course. Can you tell us more? 1:29 – PJ: It’s a fantastic course. 2:25 – Chuck: You built this course and there is a lot to talk about. 2:36 – Aimee: Let’s talk about Node and the current state. 2:50 – Chuck: Here’s the latest features, but let’s talk about where do you start with this course? How do you get going with Node? What do people need to know with Node? 3:20 – Aimee. 3:24 – PJ talks about Node and his course! 4:02 – PJ: The biggest headache with Node is the... 4:13 – Chuck. 4:19 – PJ: I am sure a lot of the listeners are familiar with callback hell. 4:50 – Aimee: Let’s talk about the complexities of module support in Node! 5:10 – PJ: It’s a horrible mess. 5:17 – Aimee: Maybe not the tech details but let’s talk about WHAT the problem is? 5:31 – PJ: You are talking about Proper Native ES6 right? They are arguing about how to implement it. 6:11 – PJ: My advice is (if you are a professional) is to stick with the LT6 program. No matter how tensing those new features are! 6:46 – Aimee: It could be outdated but they had to come back and say that there were tons of complexities and we have to figure out how to get there. 7:06 – PJ: They haven’t found an elegant way to do it. 7:15 – Panel: If it’s a standard why talk about it? Seriously – if this is a standard why not implement THE standard? 7:38 – PJ. 8:11 – Panel. 8:17 – Aimee: I would love to talk about this, though! 8:24 – Chuck: I want to talk about the course, please. 8:30 – PJ. 8:54 – Chuck: We will keep an eye on it. 9:05 – PJ. 9:16 – PJ: How is it on the browser-side? 9:33 – Aimee: I don’t want to misspeak. 9:41 – Chuck: I don’t know how complete the forms are. 9:49 – Aimee: I don’t want to misspeak. 9:56 – PJ: I just found the page that I wanted and they are calling it the .MJS or aka the Michael Jackson Script. You can do an import from... Some people think it’s FINE and others think that it’s a TERRIBLE idea. 10:42 – Chuck: “It sounds like it’s a real THRILLER!” 10:52 – Panel. 11:25 – Panel: When you start calling things the Michael Jackson Solution you know things aren’t well. 11:44 – Aimee: Just to clarify for users... 11:57 – Chuck: I want to point us towards the course: NODE.JS. Chuck asks two questions. 12:34 – PJ: The concepts aren’t changing, but the information is changing incredibly fast. The fundamentals are fairly settled. 13:22 – Chuck: What are those things? 13:28 – PJ talks about how he structured the course and he talks about the specifics. 15:33 – Chuck: Most of my backend stuff is done in Ruby. Aimee and AJ do more Java then I do. 15:55 – Panel: I think there is something to understanding how different Node is. I think that Node is a very fast moving train. Node has a safe place and that it’s good for people to know about this space. 16:34 – Aimee: Not everyone learns this way, but for me I like to understand WHY I would want to use Node and not another tool. For me, this talk in the show notes really helped me a lot. That’s the core and the nature of NODE. 17:21 – PJ: Yes, absolutely. Understanding the event loop and that’s aimed more towards people from other back ends. Right from the beginning we go over that detail: Here is how it works, we give them examples, and more. 18:08 – Aimee: You can do more than just create APIs. Aimee mentions Vanilla Node. 18:50 – PJ: To get into frameworks we do a 3-line server. We cover express, and also Sequelize ORM. 19:45 – Advertisement – Sentry.io 20:43 – Chuck: I never used Pug. 20:45 – PJ: PUG used to be called JADE. 20:56 – Aimee. 21:14 – PJ: Express does that for you and I agree with you. I advocate a non-scripted approach, I like when frameworks have a light touch. 22:05 – Aimee: That’s what I liked about it. No offense, Chuck, but for me I didn’t like NOT knowing a lot of what was not happening under the hood. I didn’t want to reinvent the wheel, but I wanted to build at a lower level. 22:40 – PJ: I had the same experience. I wanted to figure out why something wasn’t working. 23:24 – Panel: I had a friend who used Rails...he was cautious to make a switch. This past year he was blown away with how much simpler it was and how fast things were. 24:05 – Aimee: I feel like if you want to learn JavaScript then Node might be easier on the frontend. 24:21 – Chuck: No pun intended. No, but I agree. I like about Rails is that you had well-understood patterns. But the flipside is that you have abstractions... To a certain degree: what did I do wrong? And you didn’t follow the pattern properly. 25:57 – Panel: With Node you get a little bit of both. To me it’s a more simple approach, but the downside is that you have 100’s of 1,000’s of modules that almost identical things. When you start reaching out to NPM that... 26:29 – PJ: Yes the module system of NPM is the best/worst thing about NODE. I don’t have an answer, honestly. There is a great article written that made me turn white. Here is the article! 28:12 – Panel: The same thing happened with the ESLint. That was the very problem that he was describing in the article. 28:50 – PJ: Yep, I put that in the chat there – go ahead and read it! It’s not a problem that’s specific to Node, there are others. It’s the way we do things now. 29:23 – Chuck: We have the NODE Security project. A lot of stuff go into NPM everyday. 29:43 – PJ: We cover those things in the course. 29:53 – Chuck: It’s the reality. Is there a place that people get stuck? 30:00 – PJ answers the question. 30:23 – Aimee. 30:55 – PJ: I am coding very similar to my PHP days. 31:20 – Aimee. 32:02 – PJ: To finish off my point, I hope people don’t loose sight. 32:18 – Aimee. 32:20 – PJ: I am working on a project that has thousands of requests for... 32:53 – Chuck: Anything you WANTED to put into the course, but didn’t have time to? 33:05 – PJ: You can get pretty technical. It’s not an advanced course, and it won’t turn you into a rock star. This is all about confidence building. It’s to understand the fundamentals. It’s a runtime of 6 hours and 40 minutes – you aren’t just watching a video. You have a transcript, too, running off on the side. You can sit there and type it out w/o leaving – so it’s a very interactive course. 34:26 – Chuck: You get people over the hump. What do you think people need to know to be successful with Node? 34:38 – PJ answers the question. PJ: I think it’s a lot of practice and the student to go off and be curious on their own terms. 35:13 – Chuck: You talked about callbacks – I am thinking that one is there to manage the other? 35:31 – PJ answers the question. PJ: You do what works for you – pick your style – do it as long as people can follow you. Take the analogy of building a bridge. 36:53 – Chuck: What are you working on now? 37:00 – PJ: Educational tool called SCHOOL PLANNER launched in Ireland, so teachers can do their lesson planning for the year and being built with Express. Google Classroom and Google Calendar. 39:01 – PJ talks about Pi and 4wd. See links below. 40:09 – Node can be used all over the place! 40:16 - Chuck: Yes, the same can be said for other languages. Yes, Node is in the same space. 40:31 – PJ: Yep! 40:33 – Chuck: If people want to find you online where can they find you? 40:45 – PJ: Twitter! Blog! 41:04 – Picks! 41:05 – Advertisement – eBook: Get a coder job! Links: JavaScript jQuery React Elixir Elm Vue ESLint Node.js Node Security Project Node Security Project - Medium Manning Publications: Course by PJ Evans PUG JSConf EU – talk with Philip Roberts Medium Article by David Gilbertson Hackster.io – Pi Car Pi Moroni Holding a Program in One’s Head PJ Evans’ Twitter Sponsors: Kendo UI Sentry Cache Fly Get a Coder Job Picks: Aimee Paul Graham - Blog AJ Rust Charles Tweet Mash-up The Diabetes Code PJ Music - Max Richter
Panel: Aimee Knight AJ O’Neal Charles Max Wood Special Guest: PJ Evans In this episode, the panel talks with PJ Evans who is a course developer and an instructor through Manning’s course titled, “Node.js in Motion.” This course is great to learn the fundamentals of Node, which you can check out here! The panel and PJ talk about this course, his background, and current projects that PJ is working on. Check out today’s episode to hear more! Show Topics: 0:00 – Advertisement: KENDO UI 0:36 – Chuck: Welcome and our panel consists of Aimee, AJ, myself, and our special guest is PJ Evans. Tell us about yourself and your video course! NODE JS in Motion is the title of the course. Can you tell us more? 1:29 – PJ: It’s a fantastic course. 2:25 – Chuck: You built this course and there is a lot to talk about. 2:36 – Aimee: Let’s talk about Node and the current state. 2:50 – Chuck: Here’s the latest features, but let’s talk about where do you start with this course? How do you get going with Node? What do people need to know with Node? 3:20 – Aimee. 3:24 – PJ talks about Node and his course! 4:02 – PJ: The biggest headache with Node is the... 4:13 – Chuck. 4:19 – PJ: I am sure a lot of the listeners are familiar with callback hell. 4:50 – Aimee: Let’s talk about the complexities of module support in Node! 5:10 – PJ: It’s a horrible mess. 5:17 – Aimee: Maybe not the tech details but let’s talk about WHAT the problem is? 5:31 – PJ: You are talking about Proper Native ES6 right? They are arguing about how to implement it. 6:11 – PJ: My advice is (if you are a professional) is to stick with the LT6 program. No matter how tensing those new features are! 6:46 – Aimee: It could be outdated but they had to come back and say that there were tons of complexities and we have to figure out how to get there. 7:06 – PJ: They haven’t found an elegant way to do it. 7:15 – Panel: If it’s a standard why talk about it? Seriously – if this is a standard why not implement THE standard? 7:38 – PJ. 8:11 – Panel. 8:17 – Aimee: I would love to talk about this, though! 8:24 – Chuck: I want to talk about the course, please. 8:30 – PJ. 8:54 – Chuck: We will keep an eye on it. 9:05 – PJ. 9:16 – PJ: How is it on the browser-side? 9:33 – Aimee: I don’t want to misspeak. 9:41 – Chuck: I don’t know how complete the forms are. 9:49 – Aimee: I don’t want to misspeak. 9:56 – PJ: I just found the page that I wanted and they are calling it the .MJS or aka the Michael Jackson Script. You can do an import from... Some people think it’s FINE and others think that it’s a TERRIBLE idea. 10:42 – Chuck: “It sounds like it’s a real THRILLER!” 10:52 – Panel. 11:25 – Panel: When you start calling things the Michael Jackson Solution you know things aren’t well. 11:44 – Aimee: Just to clarify for users... 11:57 – Chuck: I want to point us towards the course: NODE.JS. Chuck asks two questions. 12:34 – PJ: The concepts aren’t changing, but the information is changing incredibly fast. The fundamentals are fairly settled. 13:22 – Chuck: What are those things? 13:28 – PJ talks about how he structured the course and he talks about the specifics. 15:33 – Chuck: Most of my backend stuff is done in Ruby. Aimee and AJ do more Java then I do. 15:55 – Panel: I think there is something to understanding how different Node is. I think that Node is a very fast moving train. Node has a safe place and that it’s good for people to know about this space. 16:34 – Aimee: Not everyone learns this way, but for me I like to understand WHY I would want to use Node and not another tool. For me, this talk in the show notes really helped me a lot. That’s the core and the nature of NODE. 17:21 – PJ: Yes, absolutely. Understanding the event loop and that’s aimed more towards people from other back ends. Right from the beginning we go over that detail: Here is how it works, we give them examples, and more. 18:08 – Aimee: You can do more than just create APIs. Aimee mentions Vanilla Node. 18:50 – PJ: To get into frameworks we do a 3-line server. We cover express, and also Sequelize ORM. 19:45 – Advertisement – Sentry.io 20:43 – Chuck: I never used Pug. 20:45 – PJ: PUG used to be called JADE. 20:56 – Aimee. 21:14 – PJ: Express does that for you and I agree with you. I advocate a non-scripted approach, I like when frameworks have a light touch. 22:05 – Aimee: That’s what I liked about it. No offense, Chuck, but for me I didn’t like NOT knowing a lot of what was not happening under the hood. I didn’t want to reinvent the wheel, but I wanted to build at a lower level. 22:40 – PJ: I had the same experience. I wanted to figure out why something wasn’t working. 23:24 – Panel: I had a friend who used Rails...he was cautious to make a switch. This past year he was blown away with how much simpler it was and how fast things were. 24:05 – Aimee: I feel like if you want to learn JavaScript then Node might be easier on the frontend. 24:21 – Chuck: No pun intended. No, but I agree. I like about Rails is that you had well-understood patterns. But the flipside is that you have abstractions... To a certain degree: what did I do wrong? And you didn’t follow the pattern properly. 25:57 – Panel: With Node you get a little bit of both. To me it’s a more simple approach, but the downside is that you have 100’s of 1,000’s of modules that almost identical things. When you start reaching out to NPM that... 26:29 – PJ: Yes the module system of NPM is the best/worst thing about NODE. I don’t have an answer, honestly. There is a great article written that made me turn white. Here is the article! 28:12 – Panel: The same thing happened with the ESLint. That was the very problem that he was describing in the article. 28:50 – PJ: Yep, I put that in the chat there – go ahead and read it! It’s not a problem that’s specific to Node, there are others. It’s the way we do things now. 29:23 – Chuck: We have the NODE Security project. A lot of stuff go into NPM everyday. 29:43 – PJ: We cover those things in the course. 29:53 – Chuck: It’s the reality. Is there a place that people get stuck? 30:00 – PJ answers the question. 30:23 – Aimee. 30:55 – PJ: I am coding very similar to my PHP days. 31:20 – Aimee. 32:02 – PJ: To finish off my point, I hope people don’t loose sight. 32:18 – Aimee. 32:20 – PJ: I am working on a project that has thousands of requests for... 32:53 – Chuck: Anything you WANTED to put into the course, but didn’t have time to? 33:05 – PJ: You can get pretty technical. It’s not an advanced course, and it won’t turn you into a rock star. This is all about confidence building. It’s to understand the fundamentals. It’s a runtime of 6 hours and 40 minutes – you aren’t just watching a video. You have a transcript, too, running off on the side. You can sit there and type it out w/o leaving – so it’s a very interactive course. 34:26 – Chuck: You get people over the hump. What do you think people need to know to be successful with Node? 34:38 – PJ answers the question. PJ: I think it’s a lot of practice and the student to go off and be curious on their own terms. 35:13 – Chuck: You talked about callbacks – I am thinking that one is there to manage the other? 35:31 – PJ answers the question. PJ: You do what works for you – pick your style – do it as long as people can follow you. Take the analogy of building a bridge. 36:53 – Chuck: What are you working on now? 37:00 – PJ: Educational tool called SCHOOL PLANNER launched in Ireland, so teachers can do their lesson planning for the year and being built with Express. Google Classroom and Google Calendar. 39:01 – PJ talks about Pi and 4wd. See links below. 40:09 – Node can be used all over the place! 40:16 - Chuck: Yes, the same can be said for other languages. Yes, Node is in the same space. 40:31 – PJ: Yep! 40:33 – Chuck: If people want to find you online where can they find you? 40:45 – PJ: Twitter! Blog! 41:04 – Picks! 41:05 – Advertisement – eBook: Get a coder job! Links: JavaScript jQuery React Elixir Elm Vue ESLint Node.js Node Security Project Node Security Project - Medium Manning Publications: Course by PJ Evans PUG JSConf EU – talk with Philip Roberts Medium Article by David Gilbertson Hackster.io – Pi Car Pi Moroni Holding a Program in One’s Head PJ Evans’ Twitter Sponsors: Kendo UI Sentry Cache Fly Get a Coder Job Picks: Aimee Paul Graham - Blog AJ Rust Charles Tweet Mash-up The Diabetes Code PJ Music - Max Richter
Panel Brendan Eich Joe Eames Aaron Frost AJ ONeal Jamison Dance Tim Caswell Charles Max Wood Discussion 01:57 – Brendan Eich Introduction JavaScript [Wiki] Brendan Eich [Wiki] 02:14 – Origin of JavaScript Java Netscape Jim Clark Marc Andreesen NCSA Mosaic NCSA HTTPd Lynx (Web Browser) Lou Montulli Silicon Graphics Kernel Tom Paquin Kipp Hickman MicroUnity Sun Microsystems Andreas Bechtolsheim Bill Joy Sun-1 Scheme Programming Language Structure and Interpretation of Computer Programs – 2nd Edition (MIT Electrical Engineering and Computer Science) by Harold Abelson, Gerald Jay Sussman & Julie Sussman Guy Steele Gerald Sussman SPDY Rob McCool Mike McCool Apache Mocha Peninsula Creamery, Palo Alto, CA Main () and Other Methods (C# vs Java) Static in Java, Static Variables, Static Methods, Static Classes 10:38 – Other Languages for Programmers Visual Basic Chrome Blacklist Firefox 12:38 – Naming JavaScript and Writing VMs Canvas Andrew Myers 16:14 – Envisioning JavaScript’s Platform Web 2.0 AJAX Hidaho Design Opera Mozilla Logo Smalltalk Self HyperTalk Bill Atkinson HyperCard Star Wars Trench Run 2.0 David Ungar Craig Chambers Lars Bak Strongtalk TypeScript HotSpot V8 Dart Jamie Zawinski 24:42 – Working with ECMA Bill Gates Blackbird Spyglass Carl Cargill Jan van den Beld Philips Mike Cowlishaw Borland David M. Gay ECMAScript Lisp Richard Gabriel 31:26 – Naming Mozilla Jamie Zawinski Godzilla 31:57 – Time-Outs 32:53 – Functions Clojure John Rose Oracle Scala Async.io 38:37 – XHR and Microsoft Flash Hadoop Ricardo Jenez Ken Smith Brent Noorda Ray Noorda .NET Shon Katzenberger Anders Hejlsberg NCSA File Formats 45:54 – SpiderMonkey Chris Houck Brendan Eich and Douglas Crockford – TXJS 2010 Douglas Crockford JavaScript: The Good Parts by Douglas Crockford TXJS.com ActionScript Flex Adobe E4X BEA Systems John Schneider Rhino JScript roku Waldemar Horwat Harvard Putnam Math Competition Chris Wilson Silverlight Allen Wirfs-Brock NDC Oslo 2014 JSConf Brendan JSConf Talks 59:58 – JavaScript and Mozilla GIP SSLeay Eric A. Young Tim Hudson Digital Styles Raptor Gecko ICQ and AIM PowerPlant CodeWarrior Camino David Hyatt Lotus Mitch Kapor Ted Leonsis Mitchell Baker David Baren Phoenix Tinderbox Harmony 1:14:37 – Surprises with Evolution of JavaScript Ryan Dahl node.js Haskell Elm Swift Unity Games Angular Ember.js Dojo jQuery react ClojureScript JavaScript Jabber Episode #107: ClojureScript & Om with David Nolen MVC 01:19:43 – Angular’s HTML Customization Sweet.js JavaScript Jabber Episode #039: Sweet.js with Tim Disney TC39 Rick Waldron 01:22:27 – Applications with JavaScript SPA’s Shumway Project IronRuby 01:25:45 – Future of Web and Frameworks LLVM Chris Lattner Blog Epic Games Emscripten Autodesk PortableApps WebGL 01:29:39 – ASM.js Dart.js John McCutchen Monster Madness Anders Hejlsberg, Steve Lucco, Luke Hoban: TypeScript 0.9 – Generics and More (Channel 9, 2013) Legacy 01:32:58 – Brendan’s Future with JavaScript Picks hapi.js (Aaron) JavaScript Disabled: Should I Care? (Aaron) Aaron’s Frontend Masters Course on ES6 (Aaron) Brendan’s “Cool Story Bro” (AJ) [YouTube] Queen – Don't Stop Me Now (AJ) Trending.fm (AJ) WE ARE DOOMED soundtrack EP by Robby Duguay (Jamison) Hohokum Soundtrack (Jamison) Nashville Outlaws: A Tribute to Mötley Crüe (Joe) Audible (Joe) Stripe (Chuck) Guardians of the Galaxy (Brendan)
Panel Brendan Eich Joe Eames Aaron Frost AJ ONeal Jamison Dance Tim Caswell Charles Max Wood Discussion 01:57 – Brendan Eich Introduction JavaScript [Wiki] Brendan Eich [Wiki] 02:14 – Origin of JavaScript Java Netscape Jim Clark Marc Andreesen NCSA Mosaic NCSA HTTPd Lynx (Web Browser) Lou Montulli Silicon Graphics Kernel Tom Paquin Kipp Hickman MicroUnity Sun Microsystems Andreas Bechtolsheim Bill Joy Sun-1 Scheme Programming Language Structure and Interpretation of Computer Programs – 2nd Edition (MIT Electrical Engineering and Computer Science) by Harold Abelson, Gerald Jay Sussman & Julie Sussman Guy Steele Gerald Sussman SPDY Rob McCool Mike McCool Apache Mocha Peninsula Creamery, Palo Alto, CA Main () and Other Methods (C# vs Java) Static in Java, Static Variables, Static Methods, Static Classes 10:38 – Other Languages for Programmers Visual Basic Chrome Blacklist Firefox 12:38 – Naming JavaScript and Writing VMs Canvas Andrew Myers 16:14 – Envisioning JavaScript’s Platform Web 2.0 AJAX Hidaho Design Opera Mozilla Logo Smalltalk Self HyperTalk Bill Atkinson HyperCard Star Wars Trench Run 2.0 David Ungar Craig Chambers Lars Bak Strongtalk TypeScript HotSpot V8 Dart Jamie Zawinski 24:42 – Working with ECMA Bill Gates Blackbird Spyglass Carl Cargill Jan van den Beld Philips Mike Cowlishaw Borland David M. Gay ECMAScript Lisp Richard Gabriel 31:26 – Naming Mozilla Jamie Zawinski Godzilla 31:57 – Time-Outs 32:53 – Functions Clojure John Rose Oracle Scala Async.io 38:37 – XHR and Microsoft Flash Hadoop Ricardo Jenez Ken Smith Brent Noorda Ray Noorda .NET Shon Katzenberger Anders Hejlsberg NCSA File Formats 45:54 – SpiderMonkey Chris Houck Brendan Eich and Douglas Crockford – TXJS 2010 Douglas Crockford JavaScript: The Good Parts by Douglas Crockford TXJS.com ActionScript Flex Adobe E4X BEA Systems John Schneider Rhino JScript roku Waldemar Horwat Harvard Putnam Math Competition Chris Wilson Silverlight Allen Wirfs-Brock NDC Oslo 2014 JSConf Brendan JSConf Talks 59:58 – JavaScript and Mozilla GIP SSLeay Eric A. Young Tim Hudson Digital Styles Raptor Gecko ICQ and AIM PowerPlant CodeWarrior Camino David Hyatt Lotus Mitch Kapor Ted Leonsis Mitchell Baker David Baren Phoenix Tinderbox Harmony 1:14:37 – Surprises with Evolution of JavaScript Ryan Dahl node.js Haskell Elm Swift Unity Games Angular Ember.js Dojo jQuery react ClojureScript JavaScript Jabber Episode #107: ClojureScript & Om with David Nolen MVC 01:19:43 – Angular’s HTML Customization Sweet.js JavaScript Jabber Episode #039: Sweet.js with Tim Disney TC39 Rick Waldron 01:22:27 – Applications with JavaScript SPA’s Shumway Project IronRuby 01:25:45 – Future of Web and Frameworks LLVM Chris Lattner Blog Epic Games Emscripten Autodesk PortableApps WebGL 01:29:39 – ASM.js Dart.js John McCutchen Monster Madness Anders Hejlsberg, Steve Lucco, Luke Hoban: TypeScript 0.9 – Generics and More (Channel 9, 2013) Legacy 01:32:58 – Brendan’s Future with JavaScript Picks hapi.js (Aaron) JavaScript Disabled: Should I Care? (Aaron) Aaron’s Frontend Masters Course on ES6 (Aaron) Brendan’s “Cool Story Bro” (AJ) [YouTube] Queen – Don't Stop Me Now (AJ) Trending.fm (AJ) WE ARE DOOMED soundtrack EP by Robby Duguay (Jamison) Hohokum Soundtrack (Jamison) Nashville Outlaws: A Tribute to Mötley Crüe (Joe) Audible (Joe) Stripe (Chuck) Guardians of the Galaxy (Brendan)
Panel Brendan Eich Joe Eames Aaron Frost AJ ONeal Jamison Dance Tim Caswell Charles Max Wood Discussion 01:57 – Brendan Eich Introduction JavaScript [Wiki] Brendan Eich [Wiki] 02:14 – Origin of JavaScript Java Netscape Jim Clark Marc Andreesen NCSA Mosaic NCSA HTTPd Lynx (Web Browser) Lou Montulli Silicon Graphics Kernel Tom Paquin Kipp Hickman MicroUnity Sun Microsystems Andreas Bechtolsheim Bill Joy Sun-1 Scheme Programming Language Structure and Interpretation of Computer Programs – 2nd Edition (MIT Electrical Engineering and Computer Science) by Harold Abelson, Gerald Jay Sussman & Julie Sussman Guy Steele Gerald Sussman SPDY Rob McCool Mike McCool Apache Mocha Peninsula Creamery, Palo Alto, CA Main () and Other Methods (C# vs Java) Static in Java, Static Variables, Static Methods, Static Classes 10:38 – Other Languages for Programmers Visual Basic Chrome Blacklist Firefox 12:38 – Naming JavaScript and Writing VMs Canvas Andrew Myers 16:14 – Envisioning JavaScript’s Platform Web 2.0 AJAX Hidaho Design Opera Mozilla Logo Smalltalk Self HyperTalk Bill Atkinson HyperCard Star Wars Trench Run 2.0 David Ungar Craig Chambers Lars Bak Strongtalk TypeScript HotSpot V8 Dart Jamie Zawinski 24:42 – Working with ECMA Bill Gates Blackbird Spyglass Carl Cargill Jan van den Beld Philips Mike Cowlishaw Borland David M. Gay ECMAScript Lisp Richard Gabriel 31:26 – Naming Mozilla Jamie Zawinski Godzilla 31:57 – Time-Outs 32:53 – Functions Clojure John Rose Oracle Scala Async.io 38:37 – XHR and Microsoft Flash Hadoop Ricardo Jenez Ken Smith Brent Noorda Ray Noorda .NET Shon Katzenberger Anders Hejlsberg NCSA File Formats 45:54 – SpiderMonkey Chris Houck Brendan Eich and Douglas Crockford – TXJS 2010 Douglas Crockford JavaScript: The Good Parts by Douglas Crockford TXJS.com ActionScript Flex Adobe E4X BEA Systems John Schneider Rhino JScript roku Waldemar Horwat Harvard Putnam Math Competition Chris Wilson Silverlight Allen Wirfs-Brock NDC Oslo 2014 JSConf Brendan JSConf Talks 59:58 – JavaScript and Mozilla GIP SSLeay Eric A. Young Tim Hudson Digital Styles Raptor Gecko ICQ and AIM PowerPlant CodeWarrior Camino David Hyatt Lotus Mitch Kapor Ted Leonsis Mitchell Baker David Baren Phoenix Tinderbox Harmony 1:14:37 – Surprises with Evolution of JavaScript Ryan Dahl node.js Haskell Elm Swift Unity Games Angular Ember.js Dojo jQuery react ClojureScript JavaScript Jabber Episode #107: ClojureScript & Om with David Nolen MVC 01:19:43 – Angular’s HTML Customization Sweet.js JavaScript Jabber Episode #039: Sweet.js with Tim Disney TC39 Rick Waldron 01:22:27 – Applications with JavaScript SPA’s Shumway Project IronRuby 01:25:45 – Future of Web and Frameworks LLVM Chris Lattner Blog Epic Games Emscripten Autodesk PortableApps WebGL 01:29:39 – ASM.js Dart.js John McCutchen Monster Madness Anders Hejlsberg, Steve Lucco, Luke Hoban: TypeScript 0.9 – Generics and More (Channel 9, 2013) Legacy 01:32:58 – Brendan’s Future with JavaScript Picks hapi.js (Aaron) JavaScript Disabled: Should I Care? (Aaron) Aaron’s Frontend Masters Course on ES6 (Aaron) Brendan’s “Cool Story Bro” (AJ) [YouTube] Queen – Don't Stop Me Now (AJ) Trending.fm (AJ) WE ARE DOOMED soundtrack EP by Robby Duguay (Jamison) Hohokum Soundtrack (Jamison) Nashville Outlaws: A Tribute to Mötley Crüe (Joe) Audible (Joe) Stripe (Chuck) Guardians of the Galaxy (Brendan)
Mariko Kosaka さんをゲストに迎えて、JSConf EU, TC39, オープンソースとサステナビリティ、Coinhive などについて話しました。 Show Notes JSConf EU 2018 Eyeo Festival 25 de Abril Bridge User-Agent 家系図 SafariのUA文字列が固定されて固定されなくなったおはなし Twitter ‘smytes’ customers 10 Things I Regret About Node.js - Ryan Dahl - JSConf EU 2018 ry/deno: A secure TypeScript runtime on V8 propelml/propel: Differential Programming in JavaScript. TensorFlow.js Rollup Computer, build me an app - Rich Harris - JSConf EU 2018 Svelte • The magical disappearing UI framework webpack To push, or not to push?! - The future of HTTP/2 server push - Patrick Hamann - JSConf EU 2018 Rebuild: 154: Chinese Menu Selection (kazuho) Towards ever faster websites with early hints and priority hints HTTP2 Early Hints Living on the Edge with Fastly's Tyler McMullen スラスラ読める JavaScriptふりがなプログラミング Rebuild.fmの宮川氏がRubyまつもと氏に聞いた、Ruby開発の10の論点 SmooshGate FAQ Summary for the 64th meeting of Ecma TC39 Open source sustainability Between the Wires: An interview with Vue.js creator Evan You OpenCollective The Varnish Moral License — PHKs Bikeshed 矢文案件 Gratipay Pointer Events Coinhive設置で家宅捜索受けたデザイナー、経緯をブログ公開 Using Web Workers 警察庁 サイバー犯罪対策 Government Digital Service The HTTPS-Only Standard JSConf US 2018
Thomas Lobinger ist Software Development Manager bei Amazon Web Services in Berlin. In unserem Interview mit ihm sprechen wir ein wenig über seinen Werdegang, über Design Systeme, wie bei Amazon Web Services Teams funktionieren und was er für Erfahrungen in den letzten Jahren in einem ständig wachsenden Unternehmen gemacht hat. Unser Team kümmert sich um das Design System, Tools und Automating … um das Leben von Frontend-Entwicklern und Designern besser zu machen und deren Produktivität zu erhöhen. —Thomas Lobinger Das Design System ist über eine längere Phase entstanden. Die Genesis des AWS Design Systems liegt darin begründet, dass das zentrale Frontend-Entwicklungsteam der großen Menge an Projekten nicht nachkommen konnte. Alleine 2016 sind 1017 Features und Services gelauncht worden, um dies mal in einen Kontext zu setzen. Deshalb ist das durch ein Team auch nicht machbar gewesen. —Thomas Lobinger Wir sprechen über Granularität und Feinteilgkeit in Designsystemen und was die Basis für Komponenten ist: Was ist der richtige Grad an Vorschriften vs. Einschränkung der Kreativität? Für uns sind HTML-Tags/Webstandards diese Basis. Wir haben uns dann auf web components fokussiert, haben deren API aktuell noch über Klassen abstrahiert, können diese dann aber (wenn web components native verfügbar sind) ablösen. —Thomas Lobinger Standardisierung ist für das Team um Thomas bei AWS auf allen Ebenen und in allen Gewerken Thema: Wir haben einen Prozess angestoßen, der nicht nur im Frontend standardisiert ist sondern auch im Design. Wir stecken z.B. Research in solche Standards, denn wenn wir standardisieren dann auch richtig. —Thomas Lobinger Open Source für Design Systeme ist Thema für uns und Thomas sagt dazu: Wir glauben, dass es ein Benefit ist für die Community (unser Design System open source zu stellen), … um zu sehen wie es gelöst worden ist. —Thomas Lobinger Uns am Ende noch ein Aufruf: Sucht Euch eine Firma wo ihr das (Design Systeme/UIengineering) umsetzen könnt. Seid nicht der frustrierte Einzelkämpfer. Lasst Euch nicht aufhalten! —Thomas Lobinger Das Interview wurde am 15.09.2017 per Skype aufgenommen. Shownotes & Links Working backwards (Blogpost) Working Backwards (Video) Olga Madejska: Breaking Bad - Web Components in production, what worked for us | JSConf EU 2015 (Web?) Components in production Draft of the Unity (Single File Web Component) Specification
Some of the latest news from the Preact world: the mobile version of Uber website uses Preact as well as the new Transformers promo site, and the author of Preact gave a great talk called "Preact: Into the void 0" at JSConf EU 2017. I will also share my impressions of an egghead.io course and take a look at preact-cli, a tool for quick PWA app creation. - https://preactjs.com/ - https://eng.uber.com/m-uber/ - http://www.transformersmovie.com/ - https://youtu.be/LY6y3HbDVmg - https://egghead.io/courses/up-and-running-with-preact - https://github.com/developit/preact-cli 5 minutes of React - podcast about React hot topics and JavaScript ecosystem. https://5minreact.audio
Сергей Попов, frontend-разработчик в Setka, основатель MoscowCSS и куратор образовательных программ в Moscow Coding School, в гостях у Андрея Смирнова и Артема Цацина из Frontend Weekend. - Как организовывается MoscowCSS? 0:36 - Откуда появилась идея сделать meetup? 4:20 - Как появился логотип и когда ждать обновления сайта? 7:36 - Как подбираются площадки для проведения? 11:11 - В чем различия между аудиторией MoscowJS и MoscowCSS? 16:56 - Есть ли смысл делать платный вход? 19:22 - Вкладывают ли организаторы собственные средства? 28:52 - Увеличивается ли аудитория от митапа к митапу? 36:23 - Каков рецепт идеального frontend-доклада? 41:30 - В чем причина казуса с аплодисментами на MoscowCSS №2? 53:50 - Как Сергей пришел в Moscow Coding School? 55:38 - Что входит в абстрактный курс? 1:01:09 - Какого уровня люди приходят обучаться и в чем их цель? 1:06:50 - Гордится ли Сергей своими выпускниками? 1:10:16 - Прибыльно ли заниматься обучением? 1:12:15 - Почему Сергей перестал заниматься фрилансом? 1:16:05 - Готовим вместе с frontend-разработчиком 1:20:42 Пики 1:23:30 - Visual Studio Code https://code.visualstudio.com - Записи докладов с JSConf EU 2017 https://www.youtube.com/playlist?list=PL37ZVnwpeshFmAPr65sU2O5WMs7_CGjs_ - FONTend Optimization http://telegra.ph/fontend-optimization-05-16 MoscowCSS https://vk.com/css_moscow https://twitter.com/css_moscow
Сергей Попов, frontend-разработчик в Setka, основатель MoscowCSS и куратор образовательных программ в Moscow Coding School, в гостях у Андрея Смирнова и Артема Цацина из Frontend Weekend. - Как организовывается MoscowCSS? 0:36 - Откуда появилась идея сделать meetup? 4:20 - Как появился логотип и когда ждать обновления сайта? 7:36 - Как подбираются площадки для проведения? 11:11 - В чем различия между аудиторией MoscowJS и MoscowCSS? 16:56 - Есть ли смысл делать платный вход? 19:22 - Вкладывают ли организаторы собственные средства? 28:52 - Увеличивается ли аудитория от митапа к митапу? 36:23 - Каков рецепт идеального frontend-доклада? 41:30 - В чем причина казуса с аплодисментами на MoscowCSS №2? 53:50 - Как Сергей пришел в Moscow Coding School? 55:38 - Что входит в абстрактный курс? 1:01:09 - Какого уровня люди приходят обучаться и в чем их цель? 1:06:50 - Гордится ли Сергей своими выпускниками? 1:10:16 - Прибыльно ли заниматься обучением? 1:12:15 - Почему Сергей перестал заниматься фрилансом? 1:16:05 - Готовим вместе с frontend-разработчиком 1:20:42 Пики 1:23:30 - Visual Studio Code https://code.visualstudio.com - Записи докладов с JSConf EU 2017 https://www.youtube.com/playlist?list=PL37ZVnwpeshFmAPr65sU2O5WMs7_CGjs_ - FONTend Optimization http://telegra.ph/fontend-optimization-05-16 MoscowCSS https://vk.com/css_moscow https://twitter.com/css_moscow
Henning is out battling EvilHenning once again. Snail facts! JSConf EU happened and Kahlil did stuff there. Rockbot will be at WebRebels. npm@5 is coming. Merry
Why is it so hard to write and maintain UI code? How can we make it easier? On one hand, we've talked with people who design UI APIs we all use. On the other, we've interviewed those who try to reinvent UI development. Discussion: https://discuss.codepodcast.com/t/episode-6-dont-make-me-write-ui/44 Episode produced by: Andrey Salomatin https://twitter.com/flpvsk Michael Beschastnov michael@codepodcast.com Guests: Steven Tomlinson https://www.linkedin.com/in/bowler-hat/ Casey Muratori https://twitter.com/cmuratori Rik Arends https://twitter.com/rikarends Domenic Denicola https://twitter.com/domenic Yegor Jbanov https://twitter.com/yegorjbanov ## Links: Casey ImGui introduction video https://mollyrocket.com/861 "IMGUI Yay or Nay" http://gamedev.stackexchange.com/questions/24103/immediate-gui-yae-or-nay dear imgui https://github.com/ocornut/imgui React https://facebook.github.io/react/ ## Links: Rik Makepad https://makepad.github.io/makepad Cloud 9 https://c9.io/ "Rik Arends: Beyond HTML and CSS: Fusing Javascript and shaders | JSConf EU 2014" https://www.youtube.com/watch?v=X8xxz-YeWtk ## Links: Domenic "The Extensible Web" article by Domenic https://blog.domenic.me/the-extensible-web/ "How to Win Friends and Influence Standards Bodies" talk by Domenic https://www.slideshare.net/domenicdenicola/how-to-win-friends-and-influence-standards-bodies ## Links: Yegor https://flutter.io https://flutter.io/design-principles https://flutter.io/testing ## Music Mid-Air! @mid_air
All together again - finally! The election happened and we cannot help but vent. Raquel is going on some exciting trips. JSConf EU was announced. How to teach programming to kids. Next.js is pretty cool and butterfly feet.
Fredrik talks to Pete Hunt about monoliths, breaking them up and when not to. And of course React, how it came about and how the introduction to the world looked from the inside. How to handle releases of software and working with communication around it. What happens when you go from underdog to being the safe choice? This episode was recorded during the developer conference Øredev 2015, where Pete gave presentations on monolith-first apps with Node and building React backends. Thank you Cloudnet for sponsoring our VPS! Comments, questions or tips? We are @kodsnack, @tobiashieta, @oferlund och @bjoreman on Twitter, have a page on Facebook and can be emailed on info@kodsnack.se if you want to write something longer. We read everything you send. If you like Kodsnack we would love a review in iTunes! Links Pete Hunt Kubernetes Lee Byron and his talk on Graphql The Graphql introduction talk from React Europe 2015 Smyte - where Pete currently works Pete’s talk from JSconf EU - Rethinking best practises The future of Javascript MVC frameworks React-motion Titles Everyone has a monolith Follow the hype train HTML in my Javascript! It’s let me leave work earlier
Fredrik talks to Pete Hunt about monoliths, breaking them up and when not to. And of course some React, how it came about and how the introduction to the world looked from the inside. How to handle releases of software and building communication around it. And what happens when you go from underdog to being the safe choice. This episode was recorded during the developer conference Øredev 2015, where Pete gave presentations on monolith-first apps with Node and building React backends. Thank you Cloudnet for sponsoring our VPS! Comments, questions or tips? We are @kodsnack, @tobiashieta, @isallmaroon och @bjoreman on Twitter, have a page on Facebook and can be emailed on info@kodsnack.se if you want to write something longer. We read everything you send. If you like Kodsnack we would love a review in iTunes! Links Pete Hunt Kubernetes Lee Byron and his talk on Graphql The Graphql introduction talk from React Europe 2015 Smyte - where Pete currently works Pete’s talk from JSconf EU - Rethinking best practises The future of Javascript MVC frameworks React-motion Titles Everyone has a monolith Follow the hype train HTML in my Javascript! It’s let me leave work earlier
Happy New Year! Resolutions, or not. Fix your electronic devices instead of tossing them. Will Twitter change its character limit? No JSConfEU/CSSConfEU in 2016. Raquel will keynote at ScotlandJS. If you need help with a CFP just ask @rockbot. Using Slack to manage your ToDos. The Hypercard cliffhanger.
Stefan und Schepp haben heute Martin Schuhfuß eingeladen, der bei den diesjährigen Events der JSConfEU und der OTSConf mit seinen kreativen Entwicklungen für Aufsehen gesorgt hat. Schaunotizen [00:00:12] Creative Coding Martin erzählt uns von seinem „Werdegang“ als Creative Coder, und wie er da grundsätzlich an neue Projekte rangeht. Schepp ergänzt durch seine Erfahrungen beim letztjährigen […]
Turns out Kahlil is not only a JavaScript developer, but also a vocalist!!! Kahlil’s musical history and the making of "Nested Loops". Raquel gave an inspiring talk at Strange Loop about JavaScript and Robots. A new initiative for more enjoyable consumption of mobile content - Accelerated Mobile Pages. We are going to introduce a Code of Conduct for our Slack channel. Product Hunt now supports podcasts. Henning needs an audio version of our Slack bot.
A little over a year ago at JSConf EU, Angelina tried to inspire developers to take an interest in Web Components, which includes Shadow Dom, HTML Templates, HTML Imports, and Custom Elements. In this talk we'll take a look at how far we've come in a year: what has been implemented, what hasn't, the current state of the relevant specifications, and discuss various frameworks and libraries that have emerged either with patterns similar to web components or embracing the technology completely. We will take a look at these changes, and also dive into some code for a comprehensive overview of 'the state of things' - spoiler: it's still always changing. More info at: https://fronteers.nl/congres/2013/sessions/web-components
A little over a year ago at JSConf EU, Angelina tried to inspire developers to take an interest in Web Components, which includes Shadow Dom, HTML Templates, HTML Imports, and Custom Elements. In this talk we'll take a look at how far we've come in a year: what has been implemented, what hasn't, the current state of the relevant specifications, and discuss various frameworks and libraries that have emerged either with patterns similar to web components or embracing the technology completely. We will take a look at these changes, and also dive into some code for a comprehensive overview of 'the state of things' - spoiler: it's still always changing. More info at: https://fronteers.nl/congres/2013/sessions/web-components
Twenty-one. Like blackjack. Like the gun salute. For those about to rock. We recorded this episode just a few days after #20, because we were able to get Elizabeth Naramore as a super-special secret guest! She talks to us about Codeconnexx, an open source tech and life skills conference in Indianapolis Nov 8-9. We also talked a lot about getting women to submit talks to conferences, including the success that Jan Lehnardt has had in this area with JSConfEU. We then get into Chris’s experiments with JS testing, and what we think of App.net from a developer perspective. If you’re support the inalienable rights of all humans, you’ll do these things: Check out our sponsors, Engine Yard and WonderNetwork Follow us on Twitter here. Rate us on iTunes here Listen Download now (MP3, 28.5MB, 1:06:42) Links and Notes Codeconnexx True North PHP Øredev 2012 How We Got 25% Women Speakers for JSConf EU 2012 Elizabeth Naramore’s Blog Qunit Jasmine Chai Mocha Sinon App.net Post photo by Liene Verzemnieks/@li3n3