Kodsnack 607 - Emberisms, with Balint Erdi
Kodsnack · Kristoffer, Fredrik, Tobias
Audio is streamed directly from the publisher (traffic.libsyn.com) as published in their RSS feed. Play Podcasts does not host this file. Rights-holders can request removal through the copyright & takedown page.
Show Notes
Fredrik talks to Balint Erdi about the web framework Ember. Where did Ember come from, what stands out about it today, how do new features get into the framework, and how is development being made more sustainable?
Plus: Balint's experiences organizing Emberfest, and quite a bit of appreciation for the Ruby and Ember communities in general.
The episode is sponsored by Cursed code - a half-day conference with a halloween mood taking place on October 31st, in central Gothenburg.
Thank you Cloudnet for sponsoring our VPS!
Comments, questions or tips? We a re @kodsnack, @tobiashieta, @oferlundand @bjoreman on Twitter, have a page on Facebook and can be emailed at [email protected] if you want to write longer. We read everything we receive.
If you enjoy Kodsnack we would love a review in iTunes! You can also support the podcast by buying us a coffee (or two!) through Ko-fi.
Links- Balint
- JSP - Java server pages
- ZODB - Python object database
- Ruby
- Ruby on rails
- Convention over configuration
- ORM
- Active record
- Ember
- Angular
- Yehuda Katz
- Emberfest
- Balint's (first!) book - Rock & roll with Ember.js
- Ember data
- Support us on Ko-fi!
- Classes in Javascript
- Internet explorer 6
- Handlebars
- Glimmer
- Controllers in Ember
- Ember addons
- Ember RFC:s
- Codemods
- React native
- Tree shaking
- Webpack
- Embroider
- Vite
- Cursed code - sponsor of the episode
- Poppels
- cursedcode.se - to read more and buy tickets
- The Embroider initiative
- The Ember initiative
- Ember CLI
- Ember core teams
- Emberconf
- devjournal.balinterdi.com
- Ember community links
- Ember guides
- Ember checkup - Balint's productized consulting service
- These two decades
- I'm a web guy
- Just one thing
- It'a always useful
- Rails carried me over
- Ember was in flux
- Javascript didn't have classes
- Emberisms
- Nowadays I like explicitness more
- Everything needs to be imported
- A change they would like to see in the framework
- (The) Emberfesting
- Fellow emberino
- We don't do drama