Alternatives to tachyons logo

Alternatives to tachyons

Bootstrap, Apache Ignite, Bulma, styled-components, and BEM are the most popular alternatives and competitors to tachyons.
28
61
+ 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 10.2K GitHub stars and 630 GitHub forks. Here鈥檚 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

    It is a comprehensive guide for visual, motion, and interaction design across platforms and devices. ...

tachyons alternatives & related posts

related Bootstrap posts

Hello, I hope everyone is doing good and safe. I need advice on what to learn more, I have started learning HTML, CSS, Bootstrap, JavaScript, Node.js, ExpressJS, React. eventually will learn MongoDB too. I would like to be a Front End developer or full-stack developer. What else would be the suggestion to get a job and what things I need to focus more on as a fresher to make my skills better. Do I have to be good in Algorithms and Dynamic Programming to find a job for entry-level? Looking forward to hearing from you guys for suggestions.聽

See more
Ganesa Vijayakumar
Full Stack Coder | Module Lead | 18 upvotes 路 1.9M 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
Apache Ignite logo

Apache Ignite

46
81
14
An open-source distributed database, caching and processing platform
46
81
+ 1
14

related Apache Ignite posts

Bulma logo

Bulma

461
526
20
Free, open source, & modern CSS framework based on Flexbox
461
526
+ 1
20

related Bulma posts

Daniel Hern谩ndez Alcojor
Frontend Developer at atSistemas | 8 upvotes 路 160.1K 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

641
344
6
Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps...
641
344
+ 1
6
PROS OF STYLED-COMPONENTS
CONS OF STYLED-COMPONENTS
    No cons available

    related styled-components posts

    Johnny Bell
    Software Engineer at Weedmaps | 14 upvotes 路 437.4K views

    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

    82
    60
    0
    It is a methodology, that helps you to achieve reusable components and code sharing in the front-end
    82
    60
    + 1
    0
    PROS OF BEM
      No pros available
      CONS OF BEM
        No cons available

        related BEM posts

        Basscss logo

        Basscss

        2
        12
        0
        Low-level CSS toolkit
        2
        12
        + 1
        0
        PROS OF BASSCSS
          No pros available
          CONS OF BASSCSS
            No cons available

            related Basscss posts

            Tailwind CSS logo

            Tailwind CSS

            497
            804
            138
            A utility-first CSS framework for rapid UI development
            497
            804
            + 1
            138

            related Tailwind CSS posts

            Shared insights
            on
            Tailwind CSS
            Bootstrap

            I am planning to redesign my entire application, which is currently in Bootstrap. I heard about Tailwind CSS, and I think its really cool to work with. Is it okay if I use Bootstrap and Tailwind together? I can't remove Bootstrap altogether, as my application is using the js dependencies of Bootstrap, which I don't want to disturb.

            See more
            Babak Khademi
            Frontend Developer at Freelance | 2 upvotes 路 18.5K views

            What is the best and fastest developing UI CSS Framework to couple with Angular Material ? Mostly for making responsive components and writing less sass. I have Bootstrap and Tailwind CSS in mind.

            See more

            related Material-UI posts

            Adebayo Akinlaja
            Engineering Manager at Andela | 14 upvotes 路 336.1K 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鈥攕ince 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