-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Features from other pre-processors #2708
Comments
What does "Nest a set of selectors with parent reference below another selector" means? |
That's kind of a hilariously Sass-centric perspective of pre-processors. |
Yep. But since the question is not about this table, but about particular features, here we go:
|
Thanks seven-phases-max, and for last part of my question? I suggest to have a public roadmap to have an idea of what features we could expect for near future, and approved features requests. What do you think about it? |
As for roadmap, roughly: I don't think any fair roadmap is possible currently, at least when it comes to timeline expectations. |
I've started a roadmap, not with timelines but just trying to list a summary of ready-to-implement features, but man, it's hard to get the extra time for organizational stuff like that. Keeping up with Github issues is already a decent chunk of work. |
It's currently private, but I could add anyone (outside of the less org who doesn't already have access) who wants to contribute. Not much there so far. |
Less could seriously use more people devoted to documentation, issue summaries for roadmap, and product evangelism. Along with, of course, JS coders to implement said features / bug fixes. |
@matthew-dean Do you have some ideas about how to do product evangelism? |
transparent mixins please |
I thought this was intended as a feature request board? |
I see someone made the roadmap repo public. Okay, then. @seven-phases-max Roadmap is not for feature requests, nor is meta, really. But yes, this is probably smart to close since there is no one specific feature request. @SomMeri At CSS / web confererences, it seems like there's always someone giving a presentation about Sass, but never about Less. Not sure why that is, but that would be a place to start. Plus, there is a Sass conference but no Less conference. |
Yes. But it's not a good idea to throw multiple requests into the same thread. Each feature needs a separate discussion, separate decision and thus a separate ticket. I gave the links to the corresponding opened threads for the initially mentioned features above. I.e. for each new feature please create a dedicated topic (do not hesitate to read https://github.com/less/less.js/blob/master/CONTRIBUTING.md#feature-requests first). |
I was looking at this page that clearly shows differences between various pre-processors.
I know that certain differences are wanted by design, for example lack of default variables in LESS, due to lazy loading feature, but I would like to know if other missing features are expected in near future or definitely rejected.
I personally think that these features could be very helpful:
Indipendently by actual strategies, I suggest to have a public roadmap that clearly mantain "tuned" users about future of LESS, desired features, etc.
What do you think about it?
The text was updated successfully, but these errors were encountered: