upcarta
  • Sign In
  • Sign Up
  • Explore
  • Search

92: Temple with Mitchell Hanberg

  • Podcast episode
  • Mar 29, 2022
Mitchell Hanberg
@mitchhanberg
(Guest)
open.spotify.com
Listen on Spotify
48 min
1 Recommender
1 Mention
We talk with Mitchell Hanberg and learn about why he created the alternate Phoenix templating language called “Temple”. He explains how Temple works, some of its unique benefits and... Show More

We talk with Mitchell Hanberg and learn about why he created the alternate Phoenix templating language called “Temple”. He explains how Temple works, some of its unique benefits and where he's going with it in the future. Mitchell also took over maintenance of the testing project Wallaby from Chris Keathley. We revisit what Wallaby is and the special place it can have when building automated full system tests for our projects.

Show Notes online - http://podcast.thinkingelixir.com/92

Elixir Community News

- https://twitter.com/josevalim/status/1506248906979659782 – José shared his personal definition of a reduction as "energy".

- https://twitter.com/thibaut_barrere/status/1501909747854942212 – PSA for people whose app fails to start on port 5000 when running on the new macOS.

- https://dashbit.co/blog/rustler-precompiled – Rustler Precompiled project was announced on the Dashbit blog by Philip Sampaio

- https://twitter.com/nervesproject/status/1504821571524964357 – Lots of update Nerves releases on Hex

- https://snyk.io/blog/peacenotwar-malicious-npm-node-ipc-package-vulnerability/ – A popular NPM package was maliciously updated by the maintainer as an act of protest. Impacted Vue.js projects.

Do you have some Elixir news to share? Tell us at @ThinkingElixir or email at show@thinkingelixir.com

Discussion Resources

- https://github.com/mhanberg/temple

- https://github.com/mhanberg/tableau

- https://github.com/mhanberg/blog/tree/mh/tableau

- https://github.com/elixir-wallaby/wallaby

- https://twitter.com/elixir_wallaby

- https://www.selenium.dev/documentation/webdriver/

- https://github.com/markaby/markaby

- https://crystal-lang.org/

- https://luckyframework.org/

- https://laravel.com/

- https://laravel.com/docs/9.x/blade

- https://github.com/elixir-lsp/elixir_sense

- https://surface-ui.org/template_syntax

- https://surface-ui.org/

- https://teamcapybara.github.io/capybara/

- https://hexdocs.pm/hound/readme.html

- https://www.selenium.dev/

- https://keathley.io/blog/concurrent-feature-testing-with-wallaby.html

- https://github.com/elixir-wallaby/wallaby/discussions

- https://github.com/puppeteer/puppeteer

Guest Information

- https://twitter.com/mitchhanberg – on Twitter

- https://github.com/mhanberg/ – on Github

- https://www.mitchellhanberg.com – Blog

Find us online

- Message the show - @ThinkingElixir

- Email the show - show@thinkingelixir.com

- Mark Ericksen - @brainlid

- David Bernheisel - @bernheisel

- Cade Ward - @cadebward

Sponsored By:

- Fly.io: Fly.io is a great place to deploy your next Phoenix application! Check them out!

Show Less
Recommend
Post
Save
Complete
Collect
Mentions
See All
José Valim @JosValim · Apr 5, 2022
  • Post
  • From Twitter
Great episode @mitchhanberg! For Temple, maybe you can invoke the functions in the EEx.Engine directly? This way you can distinguish between text and code and it should solve the issues with line numbers in stack traces! Perhaps this is the bifrost approach? :)
  • upcarta ©2025
  • Home
  • About
  • Terms
  • Privacy
  • Cookies
  • @upcarta