What Fortis Is Not: Limitations and Constraints

Fortis is a versatile and powerful JavaScript library for building web applications with a JSX-based approach. However, like any technology, Fortis has its own set of limitations and constraints. In this article, we will explore what Fortis is not, helping you understand its boundaries and areas where it may not be the best fit for your project.

1. No Server-Side Rendering

Fortis is primarily designed for client-side rendering, meaning it relies on the browser's Document Object Model (DOM) to create and manipulate user interfaces. As a result, Fortis does not offer built-in support for server-side rendering (SSR). If you require server-side rendering for SEO optimization or other reasons, Fortis may not be the best choice, and you might want to consider alternative solutions that specialize in SSR.

2. No Reactive Framework

Fortis is not a reactive framework in the traditional sense. While it does support class components, which can rebuild when their attributes change, this approach has limitations. The reactivity in Fortis class components is not as performant as dedicated reactive frameworks like React or Vue. If you require a highly reactive and real-time data-binding framework, Fortis may not provide the level of reactivity you need.

Furthermore, class components in Fortis rely on the attributeChanged standard web hook for attribute changes. This approach, while functional, might not offer the same level of reactivity and ease of use as a full-fledged reactive framework.

3. No Fragments

In Fortis, there is no native support for fragments, which are a feature in some other JSX-based libraries. Fragments allow you to group multiple elements without introducing an extra parent element in the DOM structure. Fortis does not have a direct equivalent to fragments. However, it does handle fragments in a unique way.

In Fortis, fragments are treated as if they were a custom component with the name fortis-fragment. While this approach allows you to group elements, it does introduce an additional custom element in the DOM structure. This may not be ideal for situations where you need to keep the DOM structure as clean and minimal as possible.

Conclusion

Understanding the limitations of Fortis is crucial for making informed decisions about whether it is the right choice for your web development project. While Fortis excels in many areas, such as its seamless integration of JSX and native DOM manipulation, it may not be the best fit for projects that require server-side rendering, a highly reactive framework, or minimal DOM pollution with fragments.

As with any technology, it's essential to evaluate your project's specific requirements and constraints and choose the right tools accordingly. Fortis can be a valuable addition to your toolkit, but it's essential to be aware of its limitations and use it in situations where it aligns with your project's needs.