<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nifs on Scholion</title><link>https://scholion.thluiz.com/tags/nifs/</link><description>Recent content in Nifs on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Wed, 18 Nov 2026 13:08:13 +0000</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/nifs/index.xml" rel="self" type="application/rss+xml"/><item><title>Elixir, NIFs, Xbox Kinect, and LiveView</title><link>https://scholion.thluiz.com/notes/elixir-nifs-xbox-kinect-and-liveview-dockyard/</link><pubDate>Tue, 12 May 2020 10:30:37 +0000</pubDate><guid>https://scholion.thluiz.com/notes/elixir-nifs-xbox-kinect-and-liveview-dockyard/</guid><description>The post traces how Kinext was built to connect an Xbox Kinect to Elixir through Erlang NIFs, then expose it in a simple Phoenix LiveView demo app.</description></item><item><title>Elixir Native Interoperability – Ports vs. NIFs</title><link>https://scholion.thluiz.com/notes/elixir-native-interoperability-ports-vs-nifs/</link><pubDate>Thu, 07 May 2015 13:16:59 -0300</pubDate><guid>https://scholion.thluiz.com/notes/elixir-native-interoperability-ports-vs-nifs/</guid><description>The page compares two Elixir/Erlang interoperability mechanisms for serial device access. NIFs are faster and simpler but can crash the VM; ports are safer and more flexible but use awkward STDIN/STDOUT messaging.</description></item></channel></rss>