<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ferit Enes Güzel on Medium]]></title>
        <description><![CDATA[Stories by Ferit Enes Güzel on Medium]]></description>
        <link>https://medium.com/@fenesguzel?source=rss-eb75647301c0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*SXKuaimniaR6gk0u.</url>
            <title>Stories by Ferit Enes Güzel on Medium</title>
            <link>https://medium.com/@fenesguzel?source=rss-eb75647301c0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 09:19:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@fenesguzel/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Next.js vs Qwik]]></title>
            <link>https://medium.com/@fenesguzel/next-js-vs-qwik-6658c7f33453?source=rss-eb75647301c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/6658c7f33453</guid>
            <category><![CDATA[nextjs]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[qwik]]></category>
            <dc:creator><![CDATA[Ferit Enes Güzel]]></dc:creator>
            <pubDate>Mon, 08 May 2023 00:03:16 GMT</pubDate>
            <atom:updated>2023-05-08T00:03:16.327Z</atom:updated>
            <content:encoded><![CDATA[<p>There are many JavaScript-based frameworks and tools available to create modern web applications, and two of them, Qwik and Next.js, stand out as fast, scalable, and modern options. However, they take different approaches to achieve their goals. In this article, we will explore the main differences between Qwik and Next.js.</p><figure><img alt="Laptop with code and plant in coffee shop" src="https://cdn-images-1.medium.com/max/1024/1*JGvrVsp3nYmj4Uu92Oxpng.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@jstrippa?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">James Harrison</a> on <a href="https://unsplash.com/photos/vpOeXr5wmR4?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4><strong>Server-Side Processing Approach</strong></h4><p>The most significant difference between Qwik and Next.js is their server-side processing approach. Next.js is a React-based framework that relies on server-side rendering (SSR) to provide server-side non-SPA (Single Page Application) support. SSR involves performing full page refresh on the server side for each request, so each request gets processed on the server side. This requires application developers to write a separate API layer on the server side.</p><p>Qwik, on the other hand, utilizes techniques such as preloading to speed up the application instead of relying on server-side processing. Qwik can serve pages statically and only reprocesses the parts that are changing. This eliminates the need for application developers to perform any processing on the server side.</p><h4><strong>Performance and Loading Time</strong></h4><p>Another difference between Qwik and Next.js is their performance and loading time. Next.js performs full page refresh on the server side, so each request goes to the server. This can slow down the application and increase loading times, making it less suitable for high-performance applications.</p><p>Qwik, however, is optimized for startup time, efficiency, and speed. Qwik reprocesses only the changing parts of the web application and serves the rest statically, eliminating the need to reload pages. This ensures that users perceive the application to be faster.</p><h4>Features and Structure</h4><p>Qwik and Next.js both offer data binding, component-based design, and easy testability, among other features. However, they have different structures. Next.js is a React-based framework that is used to create React applications. This provides an easy transition for developers who are already familiar with React. Additionally, Next.js is compatible with popular tools such as TypeScript and Sass.</p><p>Qwik, on the other hand, is an Angular-based framework used to create modern Angular applications. Unlike AngularJS (AngularJS 1), Qwik supports modern Angular applications and also supports features such as TypeScript, Sass, PWA (Progressive Web App), and SEO (Search Engine Optimization).</p><p>In conclusion, Qwik and Next.js take different approaches to creating modern web applications. Next.js requires additional API layers to achieve efficiency by performing full page refresh on the server side. Qwik, on the other hand, increases the speed of the application by using preloading techniques instead of relying on server-side processing. They both offer different approaches in terms of performance, features, and structure. The choice may vary depending on the needs of the application and the preferences of the developer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6658c7f33453" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Next.js vs Remix.js]]></title>
            <link>https://medium.com/@fenesguzel/next-js-vs-remix-js-6189c46aa1d?source=rss-eb75647301c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/6189c46aa1d</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[remixjs]]></category>
            <category><![CDATA[nextjs]]></category>
            <dc:creator><![CDATA[Ferit Enes Güzel]]></dc:creator>
            <pubDate>Sun, 16 Apr 2023 23:12:14 GMT</pubDate>
            <atom:updated>2023-04-16T23:12:14.976Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Next.js</strong> and <strong>Remix.js</strong> are two powerful JavaScript frameworks that have gained popularity in recent years for building modern web applications. While both frameworks are based on React, they differ in their approach to development and the features they provide. In this blog post, we will explore the key differences between Next.js and Remix.js to help you decide which framework is best suited for your project. Let’s dive in!</p><figure><img alt="react.js code on black screen" src="https://cdn-images-1.medium.com/max/1024/1*slZR4US7-L7TkkIUB9cY9Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@flowforfrank?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Ferenc Almasi</a> on <a href="https://unsplash.com/photos/tvHtIGbbjMo?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Here are some differences between Next.js and Remix.js:</p><ul><li><strong>Routing System</strong>: Next.js has a file-based routing system, where each page corresponds to a file on the server. In contrast, Remix.js has a data-driven routing system, allowing you to map data sources to components.</li><li><strong>Data Fetching</strong>: While Next.js provides some data fetching capabilities, Remix.js emphasizes data-driven development and has a built-in data fetching API to retrieve data from various sources and render pages.</li><li><strong>Developer Experience:</strong> Next.js prioritizes a smooth developer experience, providing features such as automatic code splitting and optimized rendering. Remix.js prioritizes a more flexible approach to building web applications, allowing developers to customize more aspects of the application.</li><li><strong>Built-in Features</strong>: Next.js comes with many built-in features, such as CSS modules, hot reloading, and automatic routing. Remix.js has fewer built-in features but provides a more customizable approach to building web applications.</li><li><strong>Popularity</strong>: Next.js has been around for longer and is widely adopted by the development community. Remix.js is a newer framework but is gaining popularity due to its unique approach to building web applications.</li></ul><p>Ultimately, the choice between Next.js and Remix.js depends on your specific needs and preferences. If you’re looking for a framework with many built-in features and a smooth developer experience, Next.js is a great choice. If you’re looking for a more data-driven approach and a more flexible application development process, Remix.js might be the better fit.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6189c46aa1d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Accessibility: Ensuring All Users Can Access Your Website]]></title>
            <link>https://medium.com/@fenesguzel/web-accessibility-ensuring-all-users-can-access-your-website-e3b657927c30?source=rss-eb75647301c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3b657927c30</guid>
            <category><![CDATA[wcag]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[digital-accessibility]]></category>
            <category><![CDATA[web]]></category>
            <category><![CDATA[web-accessibility]]></category>
            <dc:creator><![CDATA[Ferit Enes Güzel]]></dc:creator>
            <pubDate>Tue, 04 Apr 2023 06:54:18 GMT</pubDate>
            <atom:updated>2023-04-04T06:57:00.792Z</atom:updated>
            <content:encoded><![CDATA[<h4>If you’re involved in website design or development, it’s essential to consider web accessibility as a key part of your process.</h4><h4>Let’s discuss the important topic of web accessibility.</h4><p>It’s important to make sure your website is accessible to everyone, not just for moral reasons, but because it’s often required by law. Web accessibility means designing your site in a way that makes it usable for people with disabilities.</p><figure><img alt="A computer with a refreshable braille display." src="https://cdn-images-1.medium.com/max/1024/1*n8_XeXeDXboofI9GRhJhhw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@elizabeth_woolner?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Elizabeth Woolner</a> on <a href="https://unsplash.com/photos/9xxNZCJZ8bA?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>There are many types of disabilities that can impact a user’s ability to navigate and interact with websites. These include visual, auditory, physical, and cognitive disabilities. For example, some users may have difficulty reading small fonts, others may rely on screen readers or keyboard navigation, and some may have difficulty with complex visual layouts.</p><p>To ensure that your website is accessible to everyone, it’s important to follow the four key principles of web accessibility:</p><p><strong>Perceivable</strong>: Your website should be designed in a way that allows users to perceive and understand the content. This includes using alternative text for images, captions and transcripts for videos, and ensuring that color is not the only way to convey information.</p><p><strong>Operable</strong>: Users should be able to operate your website, regardless of their abilities. This means providing keyboard navigation, allowing users to pause or stop moving content, and giving users enough time to complete tasks.</p><p><strong>Understandable</strong>: Your website should be easy to understand and use. This includes using clear and concise language, organizing content in a logical way, and providing instructions and feedback to users.</p><p><strong>Robust</strong>: Your website should be able to handle a variety of user agents, including assistive technologies. This means using clean and valid code, avoiding proprietary technologies, and providing fallbacks for unsupported features.</p><p>By implementing accessibility features, you can create a more inclusive and usable website that benefits all users. Not only is it the right thing to do, but it can also improve your site’s search engine optimization (SEO) and user experience for everyone.</p><p>There are many tools and resources available to help you ensure that your website is accessible. For example, you can use screen reader simulators to test how your site is perceived by users with visual impairments, or use automated accessibility testing tools to identify issues with your site’s code.</p><p>In addition to these technical considerations, it’s also important to consider the content of your website. This includes using inclusive language, avoiding offensive or discriminatory content, and ensuring that your website is culturally sensitive.</p><p>By keeping web accessibility in mind when designing and developing your website, you can create a more welcoming and inclusive online space for everyone. So, remember to follow the key principles of web accessibility, and use the available tools and resources to ensure that your website is accessible to all users.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3b657927c30" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>