<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Blog on Mevisys</title>
		<link>https://mevisys.net/posts/</link>
		<description>Recent content in Blog on Mevisys</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Thu, 08 Oct 2026 15:33:00 +0000</lastBuildDate>
		
			<atom:link href="https://mevisys.net/posts/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Backend - Rust</title>
				<link>https://mevisys.net/posts/backend-rust/</link>
				<pubDate>Thu, 08 Oct 2026 15:33:00 +0000</pubDate>
				<guid>https://mevisys.net/posts/backend-rust/</guid>
				<description>&lt;p&gt;When building the site with a full-stack framework like Nuxt, I realized that developing with JavaScript or TypeScript just wasn&amp;rsquo;t the right fit for me. Consequently, I started looking for a solution that would give me greater confidence.&lt;/p&gt;&#xA;&lt;p&gt;Backend solutions can be divided into those built on scripting (interpreted) languages and those that leverage traditional compiled languages.&lt;/p&gt;&#xA;&lt;p&gt;Python is another interpreted language on this list. It’s part of my regular toolkit, and I actually used it within the MEVISYS platform to build the MeSca project (you can check it out under the Projects tab). While Python could certainly do the job, it inherently shares a very similar set of characteristics with JavaScript and TypeScript. Because of this, Python is out of the question for building a high-speed, reliable application.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Frontend</title>
				<link>https://mevisys.net/posts/frontend/</link>
				<pubDate>Mon, 05 Oct 2026 12:49:00 +0000</pubDate>
				<guid>https://mevisys.net/posts/frontend/</guid>
				<description>&lt;p&gt;Currently, the most widely adopted frontend solutions are:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;React&lt;/li&gt;&#xA;&lt;li&gt;Angular&lt;/li&gt;&#xA;&lt;li&gt;Vue&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;React is by far the most widely adopted solution. It debuted back in 2013, with Meta (Facebook and others) serving as its primary developer. It is a complex ecosystem, and mastering it comes with a fairly steep learning curve.&lt;/p&gt;&#xA;&lt;p&gt;Angular debuted in 2016 and is the most complex and difficult framework to learn among those listed. Developed primarily by Google, it is the most robust option available and is typically reserved for the most demanding enterprise applications.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Full-stack</title>
				<link>https://mevisys.net/posts/full-stack/</link>
				<pubDate>Sun, 04 Oct 2026 11:23:00 +0000</pubDate>
				<guid>https://mevisys.net/posts/full-stack/</guid>
				<description>&lt;p&gt;Our initial thought was to build the entire web solution — both frontend and backend — using a single full-stack framework. It’s an enticing idea, especially considering the size of the team behind the project.&lt;/p&gt;&#xA;&lt;p&gt;Our research into current technologies revealed that the most widely used solutions today are:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Next.js&lt;/li&gt;&#xA;&lt;li&gt;Astro&lt;/li&gt;&#xA;&lt;li&gt;Nuxt&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Their common denominator is that they are all programmed using JavaScript (or TypeScript). Beyond that, however, they differ quite significantly.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Current Status</title>
				<link>https://mevisys.net/posts/actual-state/</link>
				<pubDate>Sat, 03 Oct 2026 09:15:00 +0000</pubDate>
				<guid>https://mevisys.net/posts/actual-state/</guid>
				<description>&lt;p&gt;Toward the end of 2024, we got back to working on the MEVISYS platform. Having moved on from the Embedded Linux architecture, we shifted our focus to a new technical solution that has much stronger economic potential and, more importantly, is simple enough for our small team to realistically bring to life.&lt;/p&gt;&#xA;&lt;p&gt;We also began focusing much more intensely on the security of the entire solution. These considerations led to a major shift in our architectural logic. Now, all core business logic lives on the server. At the installation site, we deployed a relatively simple — and therefore cheaper — hardware unit. There is no longer any need to program the device; instead the logic lives on the server.&lt;/p&gt;</description>
			</item>
			<item>
				<title>The Initial Idea</title>
				<link>https://mevisys.net/posts/first-idea/</link>
				<pubDate>Thu, 01 Oct 2026 20:35:00 +0000</pubDate>
				<guid>https://mevisys.net/posts/first-idea/</guid>
				<description>&lt;p&gt;Our work on the MEVISYS platform began back in 2018. While developing a complex Embedded Linux device, we realized that Embedded Linux could actually have great potential as a cost-effective solution for data acquisition and measurement applications.&lt;/p&gt;&#xA;&lt;p&gt;We aimed for a modular, brick-style system featuring a central unit and several additional I/O units, all designed to mount onto a standard DIN rail. With this in mind, we chose compact, space-efficient enclosures from Phoenix Contact, which take up minimal space on a DIN rail (just 25 mm). Our goal was to engineer an Embedded Linux module that would fit perfectly inside.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
