Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could we get an official update on the status of/roadmap for Tachyons? #645

Closed
j-greig opened this issue Oct 4, 2019 · 4 comments
Closed

Comments

@j-greig
Copy link

j-greig commented Oct 4, 2019

I am hugely grateful for everything that the creators of Tachyons have done on this project, it really has radically changed the way I make websites for the better, as I'm sure it has for a ton of other folk.

It would be great to know if Tachyons is still going to be actively maintained and v5 released, or if you need help with certain things, or if something else is in the pipeline?

I appreciate that as an open-source project and everyone has other things on their plate... it must be a huge commitment to keep Tachyons updated, and for very little reward.

Knowing the roadmap (if any... if not it's totally cool and understandable :) would help us to decide on whether to keep making PRs, FRs etc.

@j-greig j-greig changed the title [FR] Could we get an official update on the status of/roadmap for Tachyons? Could we get an official update on the status of/roadmap for Tachyons? Oct 4, 2019
@dangayle
Copy link
Contributor

dangayle commented Oct 4, 2019 via email

@mrmrs
Copy link
Member

mrmrs commented Oct 11, 2019

Tachyons is a larger project than just this repo. This is one flavor of tachyons. It happens to be the most popular implementation at this point in time, but is not the only one. While the last push to this repo might have been in January there have been contributions in other repos e.g. https://github.com/tachyons-css/tachyons-styled-react as well as some private repos over the past year. Most of the significant differences in v5 will be centered around customization and a GUI version of our current generator https://github.com/tachyons-css/generator with a more comprehensive generated style guide. If you're hankering for v5, it's basically been there for you in the generator for more than a year.

While I know new versions are always exciting - there won't be much difference in the overall codebase and what you'll be able to build. A few small tweaks to how media queries work so the medium doesn't contain a max-width, and the type scale has been flipped for consistency with other scales.

I worked on what would become Tachyons for quite sometime before people used it to any significance. The bulk of the interesting work and breakthroughs in that space has been pressed out already - and the biggest gains that functional css started to chip away at, have been completely leapfrogged by css-in-js. When I originally set out building Tachyons, the current landscape of css-in-js was what I envisioned as an ideal world. I am quite frankly surprised we got here this quickly. The affordance of writing css in a 'traditional' css class based construct while outputting the fastest rendering css with the smallest possible footprint is truly astounding. As I developed Tachyons I viewed it as a stop-gap until that tech was matured on the web.

Currently as before, @johno and I have been iterating and experimenting with a number of things over the last few years. It's the same as before, you're just experiencing it in real time and not noticing where the changes and advances are occurring. For us, this time around, the problems are a bit more vast and take a bit longer to chip away at. The creation of https://components.ai has been a direct result of our initial work on the Tachyons component library and trying to see how far we could push the concept. Originally we set out to build a simple GUI where other people could build components with the Tachyons design system. A number of components already have cut and paste integration with tachyons-styled-react and will eventually be used to generate entire customized Tachyons builds.

As for whether or not to make PRs and FRs, nothing is different now than it always has been for this project. Pull requests and feature requests are more often than not noise. Tachyons is tough project in that regard as it's not the result of listening directly to what people wanted in a css toolkit. While some of the patterns are driven by performance alone - many of the naming patterns and architectural decisions came out of user testing and observing what was sticky and what wasn't with lots of different types of people across multiple projects. I do find the noise well worth the contributions that do make it in though. We've had a lot of awesome contributions from the community that far surpass my technical abilities regardless of the timeline that fit within the overall goals of the project.

If people want to take the time to make feature requests and share their ideas, I always appreciate their time and effort and everything influences my thinking somewhat. Some of the ideas are really good - but unfortunately not aligned with my goals for the project. The percentage of PRs that make it in or feature requests that get built has traditionally been quite low and will likely continue to be. I don't enjoy frustrating people or making them feel like they've wasted time. Everyone is able to host and maintain their own fork with the changes they desire and I do encourage people to do that if they feel their change should exist in the world.

Hope that helps.

@mrmrs mrmrs closed this as completed Oct 11, 2019
@dangayle
Copy link
Contributor

Can you sticky this or add this to the readme so it doesn't get buried?

@jenswittmann
Copy link
Contributor

I use v5 now for my personal projects. Feel free to use it:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants