Symfony vs UIkIt

Overview

UIkIt

Stacks791

Followers417

Votes262

GitHub Stars18.5K

Forks2.3K

Symfony

Stacks8.5K

Followers6.2K

Votes1.1K

GitHub Stars30.7K

Forks9.7K

Symfony vs UIkIt: What are the differences?

# Symfony vs UIkit

Symfony and UIkit are both popular tools in web development, but they have key differences that distinguish them from each other.

Architecture: Symfony is a PHP framework that follows the MVC (Model-View-Controller) architecture, which separates the application logic from the user interface. On the other hand, UIkit is a front-end framework that focuses on providing a modern and lightweight CSS framework for building responsive and mobile-first websites.
Backend vs Frontend: Symfony primarily focuses on the backend development aspects of web applications, providing robust features for building complex server-side applications. In contrast, UIkit is more geared towards the frontend design and user interface of websites, offering a wide range of customizable CSS and JavaScript components for creating attractive and interactive interfaces.
Server-side Rendering: Symfony is known for its server-side rendering capabilities, where the HTML content is generated on the server and sent to the client for display. UIkit, on the other hand, emphasizes client-side rendering, leveraging JavaScript to manipulate the DOM and dynamically update the content on the user's browser without reloading the entire page.
Community and Support: Symfony has a large and active community of developers, with extensive documentation, tutorials, and third-party bundles available to help developers build and deploy web applications efficiently. UIkit also has a supportive community, but it may not be as extensive as Symfony's, especially when it comes to server-side development resources.
Scalability and Complexity: Symfony is designed for building large-scale applications with complex business logic, offering a robust set of tools and components for handling enterprise requirements. In comparison, UIkit is more suitable for smaller to medium-sized projects that focus on frontend design and user experience without requiring extensive backend functionalities.
Learning Curve: Symfony has a steeper learning curve due to its comprehensive feature set and adherence to best practices in PHP development. UIkit, on the other hand, is relatively easier to learn and implement, making it a suitable choice for front-end developers looking to create modern and responsive websites without delving into backend development complexities.

In Summary, Symfony and UIkit differ in their architecture focus, backend vs frontend orientation, rendering technologies, community support, scalability, and learning curve, making them suitable for distinct web development purposes.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on UIkIt, Symfony

Daniel

Frontend Developer at atSistemas

Jun 10, 2020

Needs adviceon

New Relic

Next.js

React

I'm building, from scratch, a webapp. It's going to be a dashboard to check on our apps in New Relic and update the Apdex from the webapp. I have just chosen Next.js as our framework because we use React already, and after going through the tutorial, I just loved the latest changes they have implemented.

But we have to decide on a CSS framework for the UI. I'm partial to Bulma because I love that it's all about CSS (and you can use SCSS from the start), that it's rather lightweight and that it doesn't come with JavaScript clutter. One of the things I hate about Bootstrap is that you depend on jQuery to use the JavaScript part. My boss loves UIkIt, but when I've used it in the past, I didn't like it.

What do you think we should use? Maybe you have another suggestion?

1.07M views1.07M

Comments

Fabian

May 5, 2020

Needs adviceon

GraphQL

C++

Symfony

I'm about to begin working on an API, for which I plan to add GraphQL connectivity for processing data. The data processed will mainly be audio files being downloaded/uploaded with some user messaging & authentication.

I don't mind the difficulty in any service since I've used C++ (for data structures & algorithms at least) and would also say I am patient and can learn fairly quickly. My main concerns would be their performance, libraries/community, and job marketability.

Why I'm stuck between these three...

Symfony: I've programmed in PHP for back-end in a previous internship and may do so again in a few months.

Node.js: It's newer than PHP, and it's JavaScript where my front-end stack will be React and (likely) React Native.

Golang: It's newer than PHP, I've heard of its good performance, and it would be nice to learn a new (growing) language.

2.4M views2.4M

Comments

Filippo

Aug 27, 2020

Review

In my humble opinion the best available php platform is "API Platform". I have tried a lot of backend frameworks in the last 10 years, and that is one of the best, at least in the PHP ecosystem. It's based on Symfony, it supports plenty of features like Swagger docs, Rest API, GraphQL. You can plugin React Admin to have a full admin in no time. But the best part in my opinion it's how you can easily extend the backend taking advantage of the ORM Doctrine (which is one of the most mature available across all technologies) and all the plugins of Symfony. The fact that the Doctrine entities are in automatic relation and they can be exposed as GraphQL it's a big win if you have a complex database. It is also possible to reverse engineering an existing database and create automatically all the entities, admin, restapi, graphql endpoints ... welcome to the future :)

50 views50

Comments

Detailed Comparison

UIkIt	Symfony
UIkit gives you a comprehensive collection of HTML, CSS, and JS components which is simple to use, easy to customize and extendable.	It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP..
LESS - UIkit is developed in LESS to write well-structured, extendable code which is easy to maintain.;Components - A collection of small, responsive components using consistent and conflict-free naming conventions.;Customizer - UIkit's very basic style can be extended with themes and is easy to customize to create your own look.;Responsive - With the mobile-first approach UIkit provides a consistent experience from phones and tablets to desktops.	-
Statistics
GitHub Stars 18.5K	GitHub Stars 30.7K
GitHub Forks 2.3K	GitHub Forks 9.7K
Stacks 791	Stacks 8.5K
Followers 417	Followers 6.2K
Votes 262	Votes 1.1K
Pros & Cons
Pros 39 Complete GUI 29 Easy modify 27 Practical 24 Functional 24 Easy to learn	Pros 177 Open source 149 Php 130 Community 129 Dependency injection 122 Professional Cons 10 Too many dependency 8 Lot of config files 4 YMAL 3 Feature creep 1 Bloated
Integrations
No integrations available	CakePHP PHP ReactPHP

What are some alternatives to UIkIt, Symfony?

Node.js

Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

Bootstrap

Bootstrap is the most popular HTML, CSS, and JS framework for developing responsive, mobile first projects on the web.

Rails

Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.

Django

Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.

Laravel

It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching.

.NET

.NET is a general purpose development platform. With .NET, you can use multiple languages, editors, and libraries to build native applications for web, mobile, desktop, gaming, and IoT for Windows, macOS, Linux, Android, and more.

ASP.NET Core

A free and open-source web framework, and higher performance than ASP.NET, developed by Microsoft and the community. It is a modular framework that runs on both the full .NET Framework, on Windows, and the cross-platform .NET Core.

Spring

A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments.

Spring Boot

Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration.

Android SDK

Android provides a rich application framework that allows you to build innovative apps and games for mobile devices in a Java language environment.

Related Comparisons

Symfony vs UIkIt: What are the differences?

# Symfony vs UIkit

Symfony and UIkit are both popular tools in web development, but they have key differences that distinguish them from each other.

Architecture: Symfony is a PHP framework that follows the MVC (Model-View-Controller) architecture, which separates the application logic from the user interface. On the other hand, UIkit is a front-end framework that focuses on providing a modern and lightweight CSS framework for building responsive and mobile-first websites.
Backend vs Frontend: Symfony primarily focuses on the backend development aspects of web applications, providing robust features for building complex server-side applications. In contrast, UIkit is more geared towards the frontend design and user interface of websites, offering a wide range of customizable CSS and JavaScript components for creating attractive and interactive interfaces.
Server-side Rendering: Symfony is known for its server-side rendering capabilities, where the HTML content is generated on the server and sent to the client for display. UIkit, on the other hand, emphasizes client-side rendering, leveraging JavaScript to manipulate the DOM and dynamically update the content on the user's browser without reloading the entire page.
Community and Support: Symfony has a large and active community of developers, with extensive documentation, tutorials, and third-party bundles available to help developers build and deploy web applications efficiently. UIkit also has a supportive community, but it may not be as extensive as Symfony's, especially when it comes to server-side development resources.
Scalability and Complexity: Symfony is designed for building large-scale applications with complex business logic, offering a robust set of tools and components for handling enterprise requirements. In comparison, UIkit is more suitable for smaller to medium-sized projects that focus on frontend design and user experience without requiring extensive backend functionalities.
Learning Curve: Symfony has a steeper learning curve due to its comprehensive feature set and adherence to best practices in PHP development. UIkit, on the other hand, is relatively easier to learn and implement, making it a suitable choice for front-end developers looking to create modern and responsive websites without delving into backend development complexities.

Symfony vs UIkIt

Overview