<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>The Computer Whizz</title><link>https://kostek.uk/computer-whizz/</link><description>Recent content on The Computer Whizz</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><lastBuildDate>Wed, 26 Aug 2026 19:27:49 +0100</lastBuildDate><atom:link href="https://kostek.uk/computer-whizz/index.xml" rel="self" type="application/rss+xml"/><item><title>How I'm learning Rust with UI programming</title><link>https://kostek.uk/computer-whizz/posts/how-im-learning-rust-with-ui/</link><pubDate>Wed, 26 Aug 2026 19:27:49 +0100</pubDate><guid>https://kostek.uk/computer-whizz/posts/how-im-learning-rust-with-ui/</guid><description>&lt;hr&gt;
&lt;p&gt;tags:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;projects/on-going&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;p&gt;Rust has quickly become a major player in the low-level programming sector, adapting to use cases once thought impossible. Learning a new language effectively is a skill that&amp;rsquo;s as valued as gold.&lt;/p&gt;
&lt;h1 id="ui-in-rust"&gt;UI in Rust&lt;/h1&gt;
&lt;p&gt;Rust&amp;rsquo;s UI libraries are still relatively immature, but this is actually an advantage. They don&amp;rsquo;t carry the baggage of GTK&amp;rsquo;s or Qt&amp;rsquo;s aged architecture, nor React&amp;rsquo;s complexity. They can be engineered from the ground up to be maintainable.&lt;/p&gt;</description></item><item><title>React pt. 2: More on components</title><link>https://kostek.uk/computer-whizz/posts/react-pt2/</link><pubDate>Wed, 19 Aug 2026 09:30:22 +0100</pubDate><guid>https://kostek.uk/computer-whizz/posts/react-pt2/</guid><description>&lt;p&gt;&lt;a href="https://themindpalace.bearblog.dev/react-pt1-the-footwork/"&gt;&amp;lt;&amp;ndash; Previous Post&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Hello again! In this part, we will take a closer look at components and how to pass props down the component hierarchy.&lt;/p&gt;
&lt;p&gt;But first, let us get a better grip on how components work. Let&amp;rsquo;s create a simple colour card. It will include the colour name and the colour itself. This exercise is to solidify our understanding of how props and components work. The HTML code will always stay the same, so I will only include the JavaScript:&lt;/p&gt;</description></item><item><title>React pt. 1: The Footwork</title><link>https://kostek.uk/computer-whizz/posts/react-pt1/</link><pubDate>Tue, 11 Aug 2026 09:26:15 +0100</pubDate><guid>https://kostek.uk/computer-whizz/posts/react-pt1/</guid><description>&lt;p&gt;&lt;a href="https://themindpalace.bearblog.dev/react-pt2-more-on-components/"&gt;Next Post &amp;ndash;&amp;gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I have to say straight away that i absolutely hate React, Vue, and Angular. There has to be a better solution for responsive UI/UX design than cramming everything into javascript. Javascript in itself is a mess with library updates every 3 minutes, and so. many. security issues.&lt;br&gt;
That said, React is the de-facto standard in website design , so it is useful to master it. And that is what i am planning to do as i read through the book &lt;a href="https://www.amazon.co.uk/Learning-React-Kirupa-Chinnathambi/dp/0134546318"&gt;Learning React&lt;/a&gt; and make a full guide for you.&lt;br&gt;
My last computer science post is a massive monolithic creature, so let us jump straight in.&lt;/p&gt;</description></item></channel></rss>