text stringlengths 0 1.17k |
|---|
[3485.12 --> 3491.54] i wrote or how i wrote it uh you know i wanted just like you know you know that that uh uh that image |
[3491.54 --> 3496.72] where it's like you know lie down and ball try not to cry cry uncontrollably like i like it's really |
[3496.72 --> 3507.60] uh hit my ego hard but the reason he he was uh uh so so so i guess why it hurt me so much |
[3507.60 --> 3513.46] was because it's so true and his his feedback was so crisp and so grounded in just so much expertise |
[3513.46 --> 3517.66] and so much wisdom that he he'd you know he didn't get that wisdom because he was older and he'd been |
[3517.66 --> 3521.72] programming a long time he got that wisdom because he was incredibly thoughtful and introspective |
[3521.72 --> 3527.94] and careful and he managed to have both that aspect which i which uh you know i try to pride |
[3527.94 --> 3534.04] myself on but also this ability to very gracefully meet people where they are and get inside of their |
[3534.04 --> 3540.56] heads and um that's something that that i think that all of us could you know do a better job with |
[3540.56 --> 3545.08] and it just makes me really sad we're not going to be running into him at all the conferences |
[3545.08 --> 3553.92] throughout ohio from now on yeah absolutely man uh speaking of jim the ruby rogues did a a great |
[3553.92 --> 3557.64] tribute episode i don't know if you heard that or not episode 151 look it up while you're talking there |
[3557.64 --> 3562.72] uh the ruby rogues talk about jim and all the impact he had on them he had such a dramatic impact on |
[3562.72 --> 3567.36] so many it's just amazing how many people even though it's a small community that he specifically |
[3567.36 --> 3574.84] touched a huge loss to the ruby community well justin i think that's a good place to wrap |
[3574.84 --> 3579.28] appreciate you coming on we're excited about lyman and what you're doing there i've used it a little |
[3579.28 --> 3584.72] bit i'm excited to use it on some more projects and uh thanks for coming on and talking to us right |
[3584.72 --> 3589.18] on thank you guys i really appreciate being here and if anyone has any questions at all feel free to |
[3589.18 --> 3594.30] reach out to me on twitter or i'm justin at testdouble.com and specifically with lyman like |
[3594.30 --> 3598.74] we don't have an irc or anything so if you have a question or something's confusing just open a github |
[3598.74 --> 3603.16] issue it's not just about this code doesn't work we just want to have the conversation uh in in one |
[3603.16 --> 3609.38] place and help help everyone out awesome well we'll be back next week and let's all say goodbye |
[3609.38 --> 3612.18] bye so long |
[3612.18 --> 3627.78] like |
[3627.78 --> 3630.88] you |
[3630.88 --> 3632.88] you |
[3632.88 --> 3662.86] Thank you. |
• Mean.js is a full-stack JavaScript boilerplate |
• It's an opinionated framework using MongoDB, Express, AngularJS, and Node.js |
• It was created to help developers from a Java/PHP background transition to Node.js web applications |
• Mean.js aims to make it easier to get started with the stack by addressing the interface between the different parts |
• The framework is open-source and was released in response to a common trend in Node.js development |
• It was born out of a blog post on the MongoDB blog about the "Mean" stack |
• The creators, Amos Aviv and Roe Schwaber Cohen, used it in their own projects and recognized its potential |
• Mean.js is intended to be a better organized and more efficient way to build Node.js applications |
• Developing a REST API for Angular JS using Mean Stack (MongoDB, Express, Angular, Node) |
• Importance of proper organization and structure in a web application |
• Using popular and well-documented components to simplify development |
• Trade-off between simplicity and control over individual components |
• Discussion of Mean Stack's modularity and ease of use |
• The problem of forks and different flavors of Mean Stack |
• Encouragement of variety and choice of tools, rather than a "one true way" |
• Juggling multiple databases as an obfuscation layer for different databases |
• Using Angular and letting users choose their own web framework (e.g. Amber, Backbone, Knockout) |
• Full stack JavaScript as a vision and starting point, not a goal |
• Performance gain and benefits of using a full stack JavaScript boilerplate |
• Starting a project (JSFS) to contain different flavors of full stack JavaScript |
• Implementing own flavor of stack and taking the discussion about JavaScript to a new level |
• Collaboration across the ecosystem and package management for front-end and back-end |
• Introduction of Rackspace as a sponsor and provider of developer discount and free cloud services |
• Editor wars and discussion about the best editor to use with MEAN developers |
• Difficulty in juggling multiple tools and editors when maintaining a full stack application |
• Learning and adapting to new environment in node land and MEAN framework |
• Experimentation and understanding of JavaScript core and asynchronous programming |
• The Mean JS project aims to simplify web development with a popular stack that includes MongoDB, Express, AngularJS, and Node.js. |
• The project's documentation is designed to point developers to the documentation of the individual components, rather than duplicating information. |
• The project's community support is built-in due to the popularity of the stack, and updates are handled by the community. |
• The team tries to make updates modular to avoid breaking projects. |
• The team is aware of the challenges of maintaining backward compatibility and supporting dependencies. |
• The team uses package managers like npm and Bower to manage dependencies. |
• The project's complexity makes it hard to predict breaking changes, but the team is doing their best to handle them. |
• The team chose popular and well-supported tools like Express and AngularJS for the project. |
• The project is designed to be flexible and allow developers to choose their own tools and frameworks. |
• Discussing the decision to choose between supported packages and maintaining backwards compatibility |
• Introducing JSFS (Javascript Full Stack) as a concept to address larger issues in full stack javascript development |
• Mentioning the goal of JSFS to create a level playing field for different flavours of javascript stacks |
• Describing the process of managing file systems, deployment, and development cycles in JSFS |
• Discussing the concept of modules in JSFS, with examples such as the Mean SEO module |
• Explaining the features of JSFS modules, including cross-stack compatibility and improved loading and compressing of scripts |
• Mentioning the focus on creating features that make stacks work properly, rather than building something opinionated towards a specific stack |
• Discussing the sponsorship of the changelog by Harry's, a shaving supplies company |
• Discussion of Harry's shaving kit, its quality, and the company's product design. |
• Switching from Jade to Swig as a templating engine in the Mean framework. |
• The need for a generator to support different view engines and alleviate community concerns. |
• Getting started with Mean: recommended steps for new users, including documentation and examples. |
• Importance of community engagement and support for open-source projects. |
• Mean JS community support and involvement |
• Documentation improvements |
• Accepting forks and community contributions |
• Limiting scope to JavaScript for now |
• Real-world use cases for Mean JS |
• Building a "built with" section on the Mean JS website |
• Call to action for community involvement |
• Ways to provide feedback and suggestions (github issues, twitter, etc.) |
• Hosts' personal interests and hobbies (surfing, music) |
• Discussion of a new project or initiative with significant movement |
• Promotion of the Mean JS organization (meanjs.org) on various platforms (Facebook, GitHub) |
• Request to have the @MeanJS Twitter handle (currently abandoned) |
[0.00 --> 14.40] welcome back everyone this is the changelog where members support a blog podcast and weekly |
[14.40 --> 21.02] email covering what's fresh and what's new in open source check out the blog at the changelog.com |
[21.02 --> 27.20] our past shows at five by five dot tv slash changelog you're listening to episode 119 and |
[27.20 --> 34.28] talk to the fellows behind mean js amos aviv and rowie cohen mean js is a full stack javascript |
[34.28 --> 43.10] solution using mongo db express anguli js and node great show today it's sponsored by codeship |
[43.10 --> 48.52] rackspace and harry's we'll tell you a bit more about rackspace and harry's later on the show but |
[48.52 --> 54.54] our good friends over at codeship also a partner of the changelog they're a hosted continuous |
[54.54 --> 60.36] deployment service that just works easily set up continuous integration for your application today |
[60.36 --> 66.26] in just a few steps and automatically deploy when all your tests pass that's the way to do it |
[66.26 --> 71.66] codeship has great support for lots of languages test frameworks as well as notification services |
[71.66 --> 77.52] they easily integrate with github bitbucket and can deploy to cloud services like heroku |
[77.52 --> 85.02] aws nojitsu google app engine or even your own servers get started today with their free plan |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.