💾 Archived View for lufte.net › en › index.xml captured on 2024-05-10 at 10:36:24.
⬅️ Previous capture (2024-03-21)
-=-=-=-=-=-=-
<?xml version='1.0' encoding='UTF-8'?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>lufte.net</title>
<link>gemini://lufte.net/en/</link>
<description>Recent content from lufte.net</description>
<lastBuildDate>Sun, 14 Apr 2024 20:55:56 -0300</lastBuildDate>
<atom:link href="gemini://lufte.net/en/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Introducing Vimini: a desktop browser for Gemini</title>
<link>gemini://lufte.net/en/post/introducing-vimini/</link>
<guid>gemini://lufte.net/en/post/introducing-vimini/</guid>
<pubDate>Sat, 10 Sep 2022 00:00:00 -0300</pubDate>
<description>I've been working for a few months on Vimini, a desktop browser for Gemini (and Gopher, in the future) based on what's been my favorite web browser for a few years: qutebrowser. It's written in Rust and has been tested in Linux and Windows. A very modest 0.1.0 version, which barely opens Gemini capsules, can be downloaded from its repository at sourcehut and run with "cargo run": …</description>
</item>
<item>
<title>The triple relation problem</title>
<link>gemini://lufte.net/en/post/the-triple-relation-problem/</link>
<guid>gemini://lufte.net/en/post/the-triple-relation-problem/</guid>
<pubDate>Sun, 25 Apr 2021 00:00:00 -0300</pubDate>
<description>In my years working as a software developer I've had to design data models for a variety of web applications. I consider data and referential integrity fundamental to developing reliable systems. If a particular combination of input data should be treated as invalid in my application, I prefer to have that validation in the database. Clearly, we want these same validations in the application server and/or the web frontend for usability, but I have found that bad data will find its way to your app if you don't validate it in your database. I can usually cover our needs with the tools provided by modern RDBM systems (PostgreSQL in most cases) like foreign keys, (partial) unique constraints, and check constraints. I try to avoid triggers if I can, but they're there as a last resort. …</description>
</item>
<item>
<title>The chronicles of "Lona", my little game for Firefox OS</title>
<link>gemini://lufte.net/en/post/lona-chronicles/</link>
<guid>gemini://lufte.net/en/post/lona-chronicles/</guid>
<pubDate>Thu, 30 Apr 2020 00:00:00 -0300</pubDate>
<description>In 2013 Mozilla released Firefox OS[1], an operating system for mobile phones that was based on their rendering engine Gecko. The premise for this new OS was that all apps would be written using open web technologies, basically HTML5 and JavaScript. …</description>
</item>
<item>
<title>Conway's Game of Life in SHENZHEN I/O</title>
<link>gemini://lufte.net/en/post/game-of-life-shenzhen-io/</link>
<guid>gemini://lufte.net/en/post/game-of-life-shenzhen-io/</guid>
<pubDate>Fri, 24 Apr 2020 00:00:00 -0300</pubDate>
<description>In this post I'm going to (show off) explain my implementation of Conway's Game of Life inside SHENZHEN I/O[1]. This[2] video shows it in action with an "oscillator"[3]. …</description>
</item>
</channel>
</rss>