Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Laravel
Laravel

7.3K
4.5K
+ 1
2.8K
Semantic UI
Semantic UI

603
600
+ 1
576
Add tool

Laravel vs Semantic UI: What are the differences?

What is Laravel? A PHP Framework For Web Artisans. Laravel is a web application framework with expressive, elegant syntax. We believe development must be an enjoyable, creative experience to be truly fulfilling. Laravel 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.

What is Semantic UI? A UI Component library implemented using a set of specifications designed around natural language. Semantic empowers designers and developers by creating a shared vocabulary for UI.

Laravel can be classified as a tool in the "Frameworks (Full Stack)" category, while Semantic UI is grouped under "Front-End Frameworks".

"Clean architecture", "Growing community" and "Composer friendly" are the key factors why developers consider Laravel; whereas "Easy to use and looks elegant", "Variety of components" and "Themes" are the primary reasons why Semantic UI is favored.

Laravel and Semantic UI are both open source tools. Laravel with 53.4K GitHub stars and 16.4K forks on GitHub appears to be more popular than Semantic UI with 45.9K GitHub stars and 4.84K GitHub forks.

According to the StackShare community, Laravel has a broader approval, being mentioned in 831 company stacks & 773 developers stacks; compared to Semantic UI, which is listed in 77 company stacks and 55 developer stacks.

What is 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.

What is Semantic UI?

Semantic empowers designers and developers by creating a shared vocabulary for UI.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Laravel?
Why do developers choose Semantic UI?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con

    Sign up to add, upvote and see more consMake informed product decisions

    What companies use Laravel?
    What companies use Semantic UI?

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Laravel?
    What tools integrate with Semantic UI?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    What are some alternatives to Laravel and Semantic UI?
    Symfony
    Symfony is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP. Symfony can be used to develop all kind of websites, from your personal blog to high traffic ones like Dailymotion or Yahoo! Answers.
    CodeIgniter
    CodeIgniter is a proven, agile & open PHP web application framework with a small footprint. It is powering the next generation of web apps.
    Django
    Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
    CakePHP
    CakePHP makes building web applications simpler, faster, while requiring less code. A modern PHP 7 framework offering a flexible database access layer and a powerful scaffolding system.
    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.
    See all alternatives
    Decisions about Laravel and Semantic UI
    Koa
    Koa
    React Router
    React Router
    Foundation
    Foundation
    Semantic UI
    Semantic UI
    Bootstrap
    Bootstrap
    PostCSS
    PostCSS
    Less
    Less
    Sass
    Sass
    styled-components
    styled-components
    React Helmet
    React Helmet
    Webpack
    Webpack
    TypeScript
    TypeScript
    JavaScript
    JavaScript
    Apollo
    Apollo
    GraphQL
    GraphQL
    React
    React
    #JSX
    #React.
    #Css
    #StyledComponents.
    #Async
    #HTML
    #GraphQL
    #Apollo

    ReactQL is a React + GraphQL front-end starter kit. #JSX is a natural way to think about building UI, and it renders to pure #HTML in the browser and on the server, making it trivial to build server-rendered Single Page Apps. GraphQL via Apollo was chosen for the data layer; #GraphQL makes it simple to request just the data your app needs, and #Apollo takes care of communicating with your API (written in any language; doesn't have to be JavaScript!), caching, and rendering to #React.

    ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.

    React Helmet was chosen to handle <head> content, because it works universally, making it easy to throw back the correct <title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.

    styled-components, Sass, Less and PostCSS were added to give developers a choice of whether to build styles purely in React / JavaScript, or whether to defer to a #css #preprocessor. This is especially useful for interop with UI frameworks like Bootstrap, Semantic UI, Foundation, etc - ReactQL lets you mix and match #css and renders to both a static .css file during bundling as well as generates per-page <style> tags when using #StyledComponents.

    React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.

    Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.

    See more
    Antonio Sanchez
    Antonio Sanchez
    CEO at Kokoen GmbH | 10 upvotes 71K views
    atKokoen GmbHKokoen GmbH
    ExpressJS
    ExpressJS
    Node.js
    Node.js
    JavaScript
    JavaScript
    MongoDB
    MongoDB
    Go
    Go
    MySQL
    MySQL
    Laravel
    Laravel
    PHP
    PHP

    Back at the start of 2017, we decided to create a web-based tool for the SEO OnPage analysis of our clients' websites. We had over 2.000 websites to analyze, so we had to perform thousands of requests to get every single page from those websites, process the information and save the big amounts of data somewhere.

    Very soon we realized that the initial chosen script language and database, PHP, Laravel and MySQL, was not going to be able to cope efficiently with such a task.

    By that time, we were doing some experiments for other projects with a language we had recently get to know, Go , so we decided to get a try and code the crawler using it. It was fantastic, we could process much more data with way less CPU power and in less time. By using the concurrency abilites that the language has to offers, we could also do more Http requests in less time.

    Unfortunately, I have no comparison numbers to show about the performance differences between Go and PHP since the difference was so clear from the beginning and that we didn't feel the need to do further comparison tests nor document it. We just switched fully to Go.

    There was still a problem: despite the big amount of Data we were generating, MySQL was performing very well, but as we were adding more and more features to the software and with those features more and more different type of data to save, it was a nightmare for the database architects to structure everything correctly on the database, so it was clear what we had to do next: switch to a NoSQL database. So we switched to MongoDB, and it was also fantastic: we were expending almost zero time in thinking how to structure the Database and the performance also seemed to be better, but again, I have no comparison numbers to show due to the lack of time.

    We also decided to switch the website from PHP and Laravel to JavaScript and Node.js and ExpressJS since working with the JSON Data that we were saving now in the Database would be easier.

    As of now, we don't only use the tool intern but we also opened it for everyone to use for free: https://tool-seo.com

    See more
    Laravel
    Laravel

    I use Laravel because it has integrated unit testing that making TDD a breeze. Having a View (Blade engine) making me easier to work without too many efforts in front-end.

    I do recommend going into the root of programming once getting stable on any framework. Go beyond Symfony, go beyond PHP, go into the roots to the mother of programming; c++, c, smalltalk, erlang OTP. Understand the fundamental principle of abstraction.

    A framework is just a framework, it helps in getting feedback quickly; like practicing dancing in front of a mirror. Getting fundamentals right is the one true key in doing it right. Programming is not hard, but abstract-programming is extremely hard.

    See more
    David Block
    David Block
    Owner/Developer | 4 upvotes 480 views
    atNorth Creek Consulting, Inc.North Creek Consulting, Inc.
    Laravel
    Laravel

    I use Laravel because once a client asked me to use it, I recognized that as a solo programmer, I could go from idea to basic website in under an hour. Add one of the app builder templates and the basic design is done for me as well (I use AdminLTE). Lead management means a simple database and some basic workflow - that is where you should be spending your effort. Laravel is well-enough designed that you can plug in a few basic web pages, a simple set of object models, and some Controllers that hold your business logic - and then you iterate on the pages (the UI) and the business logic until your requirements are met. If you are a stickler or have corporate CSS standards, they can be implemented easily enough. And the community is huge and friendly.

    See more
    David Block
    David Block
    Owner/Developer | 8 upvotes 10.8K views
    atNorth Creek Consulting, Inc.North Creek Consulting, Inc.
    Laravel
    Laravel

    I use Laravel because once a client asked me to use it, I recognized that as a solo programmer, I could go from idea to basic website in under an hour. Add one of the app builder templates and the basic design is done for me as well (I use AdminLTE). Lead management means a simple database and some basic workflow - that is where you should be spending your effort. Laravel is well-enough designed that you can plug in a few basic web pages, a simple set of object models, and some Controllers that hold your business logic - and then you iterate on the pages (the UI) and the business logic until your requirements are met. If you are a stickler or have corporate CSS standards, they can be implemented easily enough. And the community is huge and friendly.

    See more
    Jason Martin
    Jason Martin
    Senior PHP Developer at Orange | 14 upvotes 28.5K views
    Debian
    Debian
    MySQL
    MySQL
    Laravel
    Laravel

    For your purposes, I recommend @Laravel, or even @Symfony or @Yii, or whatever. In your use case, a framework is 100% indicated, because it will cut your boilerplate in half or more, and you'll have a pre-fab organization for files, classes and so on. Personally, I am not a fan of Frameworks, because they tend to take over your project like cancer and trap you. But for an internal app to manage stuff, it's probably the best idea to use one (preferably one you like).

    When doing internal apps, your best bet is to stick the essentials and basics, try Laravel with MySQL on a nice Debian virtual machine. Can't go wrong.

    See more
    Tanner Naeher
    Tanner Naeher
    owner, designer, developer at Coyote6 GraphX | 3 upvotes 352 views
    Laravel
    Laravel

    If you are going to build from scratch use Laravel, because it is a little easier to learn than Symfony. They have a bunch of great videos to help you along the way. If you know Drupal 8 already, that is built on Symfony and you can harness the backend, but it is going to have a steeper learning curve. On the plus side you can take advantage of all its features. I wouldn't recommend building without a type of framework. Thousands of man hours have gone into those things for a reason. I started learning Symfony w/o Drupal but lost interest once I found out how much easier Laravel was. They both have their advantages and disadvantages, laravel actually uses part of symfony in its code. I like the blade template system better than twig is a big factor in deciding as well. They are both very similar, but blade is closer to native PHP which makes it a little easier to learn.

    See more
    Ahmet Ertem
    Ahmet Ertem
    Full Stack Developer | 5 upvotes 504 views
    Laravel
    Laravel

    I use Laravel because right now it's really hard to find someone using native PHP without a framework. Also learning a framework easier than native for newcomers. Also; I was not supporting frameworks before but after start developing a core with one I saw i can find many new people for the projects.

    See more
    Jigar Dhulla
    Jigar Dhulla
    Senior Application Developer at Endurance International Group | 2 upvotes 259 views
    Laravel
    Laravel

    I use Laravel because you don't have to re-invent the wheel when compared to core PHP. We can focus directly on business logic. And the little learning curve for Laravel is worth it. Can't really compare with Laravel with Symfony as I haven't worked with Symfony yet. My suggestion would be to pick one and stick to it. If at all you have to move to other, it should be easy. Last thing I would like to add is that there are more people around who knows Laravel compared to PHP, may be that's why I started with Laravel.

    See more
    Interest over time
    Reviews of Laravel and Semantic UI
    Review ofLaravelLaravel

    I moved from .NET and Rails to Laravel, and since then never thought to go back. I feel Laravel framework has the capability to overcome all modern frameworks.

    At Soft Pyramid we are developing rich business applications using Laravel Framework, and never feel any limitation even for complex reporting.We have written REST apis, complex ERP solutions and found awsome in all areas.

    How developers use Laravel and Semantic UI
    Avatar of BrightMachine
    BrightMachine uses LaravelLaravel

    The best PHP framework right now, intuitive and growing up quickly.

    We use Laravel in the outer layer of our Clean Architecture codebases, whereby the domain model does not rely on the framework as a whole.

    Avatar of Kent Steiner
    Kent Steiner uses LaravelLaravel

    See "PHP", I don't really choose to use it, but I can step in and operate in Laravel when necessary. Same goes for quite a few other PHP frameworks, including my own full-featured proprietary stack.

    Avatar of Nicholas Alexander
    Nicholas Alexander uses LaravelLaravel

    An excellent PHP framework employing SOLID principles to rapidly develop web-site systems and connect them to databases. Custom development of admin screens for website management.

    Avatar of Doug Bromley
    Doug Bromley uses LaravelLaravel

    A clean, easy to understand, well documented framework with excellent tools and a great community providing every imaginable extension to add functionality to your project.

    Avatar of Jake Taylor
    Jake Taylor uses LaravelLaravel

    Laravel is the PHP framework we use. It speeds up development and simplifies a lot of PHP. Complicated at first but saves time once you're comfortable with it.

    Avatar of osu! Ripple
    osu! Ripple uses Semantic UISemantic UI

    We use Semantic UI for our frotend. A heavily customised version of it, but still Semantic UI under the hood.

    Avatar of Ralic Lo
    Ralic Lo uses Semantic UISemantic UI

    Used Semantic UI + Angular2 together with Spring or Node/Express for full stack web application development.

    Avatar of Giftstarter
    Giftstarter uses Semantic UISemantic UI

    We haven't yet, but we would like to integrate into our Web App.

    Avatar of Eliana Abraham
    Eliana Abraham uses Semantic UISemantic UI

    It's pretty. Used it once for MDST.

    Avatar of Wellzesta
    Wellzesta uses Semantic UISemantic UI

    Grid, widgets, theming.

    How much does Laravel cost?
    How much does Semantic UI cost?
    Pricing unavailable
    Pricing unavailable
    News about Semantic UI
    More news