text
stringlengths
0
1.17k
[4025.20 --> 4029.34] seems like every kind of language that claims to be embeddable is basically more designed to be
[4029.34 --> 4035.22] installed onto a system and then loads its additional modules via extra shared libraries
[4035.22 --> 4041.50] and mruby is really interesting it has its own little build system that compiles all it's split
[4041.50 --> 4047.02] into all of its features are split into what are called mrb gems and then those are all compiled down
[4047.02 --> 4053.50] into one single static linked library that you can then embed into other programs and so man it's
[4053.50 --> 4058.96] really nice and it's actually pretty decent documentation around it uh but like there's not a lot of
[4058.96 --> 4063.68] projects around it so you do have to do kind of your research and tinker around with the code
[4063.68 --> 4070.12] but uh it's really well put together and i think it has huge potential and just uh anywhere you could
[4070.12 --> 4076.16] put lua uh the embeddable language lua you could probably put mruby and do a lot more because you
[4076.16 --> 4084.84] know lua misses it lacks certain things basic things like bitwise operators yeah cool so the last question
[4084.84 --> 4089.84] is uh for a programmer hero or just somebody that's been really influential in your life to this point
[4089.84 --> 4097.78] oh man um so i try to be really anti-hero because anti-hero worship i feel like it really holds people
[4097.78 --> 4102.72] back uh when they're always kind of looking up to someone and instead of some inspiring to you know
[4102.72 --> 4108.46] improve themselves and challenge themselves but i definitely have to say like uh as as far as like
[4108.46 --> 4114.06] programmer wisdom goes i feel like uh dan cubb who worked on the data mapper project uh
[4114.06 --> 4124.68] uh uh piat solnick and then also uh marcus i'm gonna mispronounce his name marcus shriept mbj uh he he
[4124.68 --> 4131.08] wrote mutants yeah and uh those people are kind of like the most interesting discussions about like
[4131.08 --> 4137.24] design and you know when when principles are taken too far uh when they're not applied like pretty much
[4137.24 --> 4142.82] anything solnick writes is like i pretty much agree with it so those are kind of like they're
[4142.82 --> 4150.10] they're they're hip cats they know what's up yeah for sure awesome well i wanted to say thanks a lot
[4150.10 --> 4156.72] for coming on this show i think that this is a uh i don't know you kind of get the sense with with
[4156.72 --> 4162.80] ruby switchers and just with the this world that um we've we've almost gotten as simple as we can get
[4162.80 --> 4168.10] but at the same time it feels like we've got a far a long way to go right i mean your call to arms kind
[4168.10 --> 4175.06] of sums it up right and that like the goal would ultimately be to not really need these things and
[4175.06 --> 4180.48] uh so you know i think that we've got a long way to go here but but i like the uh the simplicity that
[4180.48 --> 4184.74] you're aiming for so once again i just want to say thanks a bunch for joining us today it was post
[4184.74 --> 4191.98] modern um his uh real name has been redacted and uh no just kidding um but yeah no for sure we will uh
[4191.98 --> 4197.42] we'll uh be back next week um so make sure you listen we are going to start doing this weekly
[4197.42 --> 4203.68] again um now that everything has started to settle down so back to live too i think we're gonna be uh
[4203.68 --> 4209.16] if you're listening to this obviously you are because you're hearing me say this but uh our uh our new date
[4209.16 --> 4216.80] is friday live at 10 a.m central standard time um if for some reason we don't have a guest we're just
[4216.80 --> 4221.54] gonna get on there anyways and just talk about awesome open source so we're we're aiming for weekly
[4221.54 --> 4228.58] live um should be a fun time and a postmodern we've we've uh been playing some email tag for a bit
[4228.58 --> 4233.56] too trying to get you on the show and just echo andrew's thoughts too just static static to have you
[4233.56 --> 4238.46] on the show uh love the work you're doing in open source and just want to do as much as we can to
[4238.46 --> 4243.66] encourage you to keep doing the awesome work that you're doing thanks man it was a fun time being
[4243.66 --> 4247.70] on the show and hope to hear more awesome episodes of you guys absolutely go ahead andrew
[4247.70 --> 4254.04] uh yeah that's it so until next time we'll just say goodbye bye-bye adios
[4254.04 --> 4256.70] you
[4256.70 --> 4258.70] you
[4258.70 --> 4272.70] you
[4272.70 --> 4283.70] you
[4283.70 --> 4285.70] you
[4285.70 --> 4287.70] you
• Tim Caswell discusses his background and experience in open source and web development
• He explains how he enables other programmers and loves inventing things
• Tim shares his advice on open source for newer developers, citing the ease of access to information and the importance of community involvement
• He discusses how open source can be intimidating, but notes that it's a great way to give back to the community and that volunteering time and passion can lead to success
• Tim reflects on his own journey and how he overcame his own doubts and lack of confidence to contribute to the open source community
• He emphasizes the importance of finding one's own voice and contributing to the community, regardless of skill level or experience
• Starting programming at age 7 and high school web startup failure
• Experience with Asperger's and social struggles in high school
• Overcoming stage fright and public speaking through small groups and conferences
• Language progression: Basic to JavaScript, and the challenges of finding information and building confidence in the early days of programming
• The importance of experiencing challenges and finding ways to overcome them, as opposed to relying on easily accessible information today
• The desire to push the boundaries of what's been done before, and the ongoing discovery of new frontiers in programming.
• Goal to make programming accessible to people with restricted devices by creating a full professional developer environment
• Implementing git in javascript as a key part of the project
• Kickstarter campaign to fund the project, initially aiming for $12,000 but hitting the minimum goal overnight
• Struggling to reach stretch goals and eventually seeking help from Bounty Source, which found additional funding from corporations
• Reflection on the experience, including the difficulty of fundraising and the importance of setting realistic goals
• The initial Kickstarter campaign for JS Git exceeded its $12,000 goal, receiving around $20,000 in funding.
• The goal of JS Git was to create a platform for JavaScript that runs anywhere, but the JavaScript module ecosystem is fragmented, making this goal challenging.
• The main hurdle in developing JS Git was abstracting away the differences between various systems and finding a way to work with them.
• The developer had to invent their own module system and dependency injection, as existing solutions like browserify were not suitable for the project's requirements.
• T Edit was not funded through crowdfunding, but the JS Git campaign was successful, which might be due to the companies' reluctance to fund open-source projects without a contract and exclusive ownership.
• The developer learned that crowdfunding can help get an idea off the ground and test its feasibility, but it's not a sustainable long-term funding method.
• Generational gap in understanding the benefits of open-source projects
• Importance of having the right person to champion a project
• Mozilla's donation to the project and their goals for the open web
• Difficulty in selling open-source projects to companies that don't understand their benefits
• JS-Kit and its use in the project
• Challenges faced by the developer, including lack of funding and having to abandon some features
• The developer's current work on the project, including a chrome app version
• Overview of the T-Edit project, including its goals and features
• Improved user experience through a different way of working directly on the Git database
• Addressing issues with submodules, such as lack of UX in traditional Git clients
• T Edit's approach to submodules, mapping them as virtual file systems and using a back end to handle remote data storage
• Offline functionality, including queuing up changes and handling temporary commits
• Multiple backends available for JSGit, including GitHub, index db, Web SQL, local storage, and others.
• Key-value store as a core component for Git storage
• Implementing push, pull, merge, and diff functionality in T Edit
• Funding and sustainability of the T Edit project
• Exploring alternative funding models, such as consulting and hosting services
• Goals for T Edit, including making infrastructure code open source and available for free
• Building a development environment with T Edit, including a package manager and build system
• T Edit build system's unique rule files and arbitrary programs written by users
• Potential charging for services like hosting, but not charging for infrastructure code
• Creating an app cache that automatically updates when dependencies change
• Building a JavaScript compiler for cross-platform development
• Using a minimal AMD loader to load JavaScript modules on demand
• Adding automatic concatenation and minification features
• Integrating with the app cache to ensure the latest code is loaded
• Using a Chrome app as a development environment due to its limitations compared to a web page
• Running a local HTTP server and hosting web apps within the Chrome app
• Implementation of app cache for offline access to the game
• Mounting a GitHub repository using a token for easier access
• Use of Ace Editor and its customization for syntax highlighting and color schemes
• Accessibility features, including keyboard shortcuts for font size and color scheme changes
• Current state of the project, with missing pieces including network, diff, and merge functionality