Alternatives to tachyons logo

Alternatives to tachyons

Bootstrap, Apache Ignite, Bulma, styled-components, and BEM are the most popular alternatives and competitors to tachyons.
46
78
+ 1
0

What is tachyons and what are its top alternatives?

Create fast loading, highly readable, and 100% responsive interfaces with as little CSS as possible.
tachyons is a tool in the Front-End Frameworks category of a tech stack.
tachyons is an open source tool with 11.3K GitHub stars and 684 GitHub forks. Here’s a link to tachyons's open source repository on GitHub

Top Alternatives to tachyons

  • Bootstrap
    Bootstrap

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

  • Apache Ignite
    Apache Ignite

    It is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads delivering in-memory speeds at petabyte scale ...

  • Bulma
    Bulma

    Bulma is a CSS framework based on Flexbox and built with Sass

  • styled-components
    styled-components

    Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅 ...

  • BEM
    BEM

    This methodology was developed at Yandex with the goals in mind that Fast development and long-lasting results for standard projects,A project involves many people,Scalable teams,Code reuse. ...

  • Basscss
    Basscss

    It is a lightweight collection of base element styles and immutable utilities designed for speed, clarity, performance, and scalability. ...

  • Tailwind CSS
    Tailwind CSS

    Tailwind is different from frameworks like Bootstrap, Foundation, or Bulma in that it's not a UI kit. It doesn't have a default theme, and there are no build-in UI components. It comes with a menu of predesigned widgets to build your site with, but doesn't impose design decisions that are difficult to undo. ...

  • Material-UI
    Material-UI

    Material UI is a library of React UI components that implements Google's Material Design. ...

tachyons alternatives & related posts

Bootstrap logo

Bootstrap

54.8K
12.6K
7.7K
Simple and flexible HTML, CSS, and JS for popular UI components and interactions
54.8K
12.6K
+ 1
7.7K
PROS OF BOOTSTRAP
  • 1.6K
    Responsiveness
  • 1.2K
    UI components
  • 944
    Consistent
  • 779
    Great docs
  • 678
    Flexible
  • 472
    HTML, CSS, and JS framework
  • 411
    Open source
  • 374
    Widely used
  • 367
    Customizable
  • 242
    HTML framework
  • 77
    Mobile first
  • 77
    Easy setup
  • 77
    Popular
  • 58
    Great grid system
  • 52
    Great community
  • 38
    Future compatibility
  • 34
    Integration
  • 28
    Very powerful foundational front-end framework
  • 24
    Standard
  • 23
    Javascript plugins
  • 19
    Build faster prototypes
  • 18
    Preprocessors
  • 14
    Grids
  • 9
    Good for a person who hates CSS
  • 8
    Clean
  • 4
    Easy to setup and learn
  • 4
    Love it
  • 4
    Rapid development
  • 3
    Great and easy to use
  • 2
    Community
  • 2
    Provide angular wrapper
  • 2
    Great and easy
  • 2
    Boostrap
  • 2
    Powerful grid system, Rapid development, Customization
  • 2
    Great customer support
  • 2
    Popularity
  • 2
    Clean and quick frontend development
  • 2
    Great and easy to make a responsive website
  • 2
    Sprzedam opla
  • 2
    Easy to use
  • 1
    Responsive design
  • 1
    Geo
  • 1
    Painless front end development
  • 1
    Design Agnostic
  • 1
    So clean and simple
  • 1
    Numerous components
  • 1
    Recognizable
  • 1
    Intuitive
  • 1
    Material-ui
  • 1
    Love the classes?
  • 1
    Pre-Defined components
  • 1
    It's fast
  • 1
    Felxible, comfortable, user-friendly
  • 1
    The fame
  • 1
    Easy setup2
  • 1
    Not tied to jQuery
CONS OF BOOTSTRAP
  • 25
    Javascript is tied to jquery
  • 16
    Every site uses the defaults
  • 15
    Grid system break points aren't ideal
  • 14
    Too much heavy decoration in default look
  • 8
    Verbose styles
  • 1
    Super heavy

related Bootstrap posts

Ganesa Vijayakumar
Full Stack Coder | Technical Lead · | 19 upvotes · 3.2M views

I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

As per my work experience and knowledge, I have chosen the followings stacks to this mission.

UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

Happy Coding! Suggestions are welcome! :)

Thanks, Ganesa

See more
Francisco Quintero
Tech Lead at Dev As Pros · | 13 upvotes · 1M views

For Etom, a side project. We wanted to test an idea for a future and bigger project.

What Etom does is searching places. Right now, it leverages the Google Maps API. For that, we found a React component that makes this integration easy because using Google Maps API is not possible via normal API requests.

You kind of need a map to work as a proxy between the software and Google Maps API.

We hate configuration(coming from Rails world) so also decided to use Create React App because setting up a React app, with all the toys, it's a hard job.

Thanks to all the people behind Create React App it's easier to start any React application.

We also chose a module called Reactstrap which is Bootstrap UI in React components.

An important thing in this side project(and in the bigger project plan) is to measure visitor through out the app. For that we researched and found that Keen was a good choice(very good free tier limits) and also it is very simple to setup and real simple to send data to

Slack and Trello are our defaults tools to comunicate ideas and discuss topics, so, no brainer using them as well for this project.

See more
Apache Ignite logo

Apache Ignite

83
146
31
An open-source distributed database, caching and processing platform
83
146
+ 1
31
PROS OF APACHE IGNITE
  • 4
    Free
  • 4
    Written in java. runs on jvm
  • 3
    Load balancing
  • 3
    High Avaliability
  • 3
    Multiple client language support
  • 3
    Sql query support in cluster wide
  • 3
    Rest interface
  • 2
    Easy to use
  • 2
    Better Documentation
  • 1
    Distributed Locking
  • 1
    gtj
  • 1
    Distributed compute
  • 1
    Benfica
CONS OF APACHE IGNITE
    Be the first to leave a con

    related Apache Ignite posts

    Bulma logo

    Bulma

    653
    821
    37
    Free, open source, & modern CSS framework based on Flexbox
    653
    821
    + 1
    37
    PROS OF BULMA
    • 11
      Easy setup
    • 6
      Easy-to-customize the sass build
    • 6
      Community-created themes
    • 5
      Responsive
    • 5
      Great docs
    • 4
      Easy to learn and use
    CONS OF BULMA
    • 2
      Not yet supporting Vue 3

    related Bulma posts

    Daniel Hernández Alcojor
    Frontend Developer at atSistemas · | 8 upvotes · 779K views

    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?

    See more
    styled-components logo

    styled-components

    1.6K
    561
    11
    Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps...
    1.6K
    561
    + 1
    11
    PROS OF STYLED-COMPONENTS
    • 11
      Very easy to use and integrate
    CONS OF STYLED-COMPONENTS
      Be the first to leave a con

      related styled-components posts

      Johnny Bell

      For Stack Decisions I needed to add Markdown in the decision composer to give our users access to some general styling when writing their decisions. We used React & GraphQL on the #Frontend and Ruby & GraphQL on the backend.

      Instead of using Showdown or another tool, We decided to parse the Markdown on the backend so we had more control over what we wanted to render in Markdown because we didn't want to enable all Markdown options, we also wanted to limit any malicious code or images to be embedded into the decisions and Markdown was a fairly large to import into our component so it was going to add a lot of kilobytes that we didn't need.

      We also needed to style how the markdown looked, we are currently using Glamorous so I used that but we are planning to update this to Emotion at some stage as it has a fairly easy upgrade path rather than switching over to styled-components or one of the other cssInJs alternatives.

      Also we used React-Mentions for tagging tools and topics in the decisions. Typing @ will let you tag a tool, and typing # will allow you to tag a topic.

      The Markdown options that we chose to support are tags: a, code, u, b, em, pre, ul, ol, li.

      If there are anymore tags you'd love to see added in the composer leave me a comment below and we will look into adding them.

      #StackDecisionsLaunch

      See more

      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
      BEM logo

      BEM

      113
      91
      0
      It is a methodology, that helps you to achieve reusable components and code sharing in the front-end
      113
      91
      + 1
      0
      PROS OF BEM
        Be the first to leave a pro
        CONS OF BEM
          Be the first to leave a con

          related BEM posts

          Basscss logo

          Basscss

          6
          13
          0
          Low-level CSS toolkit
          6
          13
          + 1
          0
          PROS OF BASSCSS
            Be the first to leave a pro
            CONS OF BASSCSS
              Be the first to leave a con

              related Basscss posts

              Tailwind CSS logo

              Tailwind CSS

              1.9K
              2.2K
              240
              A utility-first CSS framework for rapid UI development
              1.9K
              2.2K
              + 1
              240
              PROS OF TAILWIND CSS
              • 42
                Highly customizable
              • 31
                Quick setup
              • 29
                Utility first styles, its amazing
              • 24
                Versatile
              • 22
                Great docs
              • 16
                Customizable
              • 16
                Fast
              • 15
                Consistent
              • 11
                Very light
              • 11
                Semantic
              • 11
                Open source
              • 9
                Responsive
              • 1
                Jnn
              • 1
                Sex
              • 1
                Easy Tree shaking with Tailwind CLI
              CONS OF TAILWIND CSS
              • 14
                Priced
              • 5
                Cluttered html structure

              related Tailwind CSS posts

              James Bender
              Lead Application Architect at TekPartners · | 10 upvotes · 34.1K views
              Shared insights
              on
              Tailwind CSSTailwind CSSBootstrapBootstrap

              Bootstrap is a great idea until your designer wants something that doesn't fit neatly into a 12 column paradigm. Then things start to get difficult. We've had to add customizations and tweaks to Bootstrap-ed HTML that by the time we were done, we would have been better off just going straight CSS. Bootstrap helps with responsiveness, but again, it's an "80/20" solution at best. And that 20 percent can be a nightmare. Plus, most clients have this odd belief that you just drop Bootstrap into an app, and abracadabra, your site is totally responsive over every type of screen and form factor in existence. This is not the case. We have had MUCH better and faster results with Tailwind CSS. Our designers are happy we're not trying to force them into a Bootstrap-friendly design, and even with responsive sites, development has been easier and faster.

              See more
              Giordanna De Gregoriis
              Jr Fullstack Developer at Stefanini Inspiring · | 8 upvotes · 258.6K views

              TL;DR: Shall I keep developing with Nuxt.js 2 and wait for a migration guide to Nuxt 3? Or start developing with Vue.js 3 using Vite, and then migrate to Nuxt 3 when it comes out?

              Long version: We have an old web application running on AngularJS and Bootstrap for frontend. It is mostly a user interface to easily read and post data to our engine.

              We want to redo this web application. Started from scratch using the newest version of Angular 2+ and Material Design for frontend. We haven't even finished rewriting half of the application and it is becoming dreadful to work on.

              • The cold start takes too much time
              • Every little change reload the whole page. Seconds to minutes of development lost looking at a loading blank page just changing css
              • Code maintainability is getting worse... again... as the application grows, since we must create everytime 5 files for a new page (html, component.ts, module.ts, scss, routing.ts)

              I'm currently trying to code a Proof of Concept using Nuxt.js and Tailwind CSS. But the thing is, Vue.js 3 is out and has interesting features such as the composition API, teleport and fragments. Also we wish to use the Vite frontend tooling, to improve our time developing regardless of our application size. It feels like a better alternative to Webpack, which is what Nuxt 2 uses.

              I'm already trying Nuxt.js with the nuxt-vite experimental module, but many nuxt modules are still incompatible from the time I'm posting this. It is also becoming cumbersome not being able to use teleport or fragments, but that can be circumvented with good components.

              What I'm asking is, what should be the wisest decision: keep developing with Nuxt 2 and wait for a migration guide to Nuxt 3? Or start developing with Vue.js 3 using Vite, and then migrate to Nuxt 3 when it comes out?

              See more
              Material-UI logo

              Material-UI

              2K
              3.4K
              407
              Material UI is a library of React UI components that implements Google's Material Design.
              2K
              3.4K
              + 1
              407
              PROS OF MATERIAL-UI
              • 132
                React
              • 81
                Material Design
              • 57
                Ui components
              • 28
                CSS framework
              • 22
                Component
              • 13
                Looks great
              • 10
                Responsive
              • 10
                Good documentation
              • 9
                LESS
              • 7
                Open source
              • 6
                Ui component
              • 6
                Code examples
              • 5
                Flexible
              • 4
                JSS
              • 3
                Angular
              • 3
                Very accessible
              • 3
                Fun
              • 3
                Supports old browsers out of the box
              • 2
                Interface
              • 2
                Designed for Server Side Rendering
              • 1
                Easy to work with
              CONS OF MATERIAL-UI
              • 31
                Hard to learn. Bad documentation
              • 25
                Hard to customize
              • 19
                Hard to understand Docs
              • 6
                Extra library needed for date/time pickers
              • 6
                Bad performance
              • 5
                For editable table component need to use material-table

              related Material-UI posts

              Adebayo Akinlaja
              Engineering Manager at Andela · | 29 upvotes · 1.5M views

              I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen—since I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

              A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

              In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

              If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

              See more

              My React website is a simple 5-pager that attaches to a database to store and display registrations and other data. The user (small user base) can change any form elements, but I don't need theme-ing, though that would be fun for the user. reactstrap/react-bootstrap built on Bootstrap 4 sounds dated. I am familiar with reactstrap, but a friend said to try Material-UI. The thought of learning it is interesting, but somehow I think it might be overkill. So... reactstrap, react-bootstrap, or Material UI, which should I use?

              See more