Current Tagline
"A React-like, 3.5KB user interface library"
Thoughts:
Suggestions:
Avoiding cliched keywords like efficient, modern, tiny, framework, which lose its meaning over time.
"A small tool for building user interfaces."
The term "user interfaces" is rock solid. It has sustained for the past 40 years :)
"A small tool for building user interfaces for the web and mobile" if your planning to do something like reapp
I think the current tag-line carries a lot of important information. As a react user needing something more light weight for smaller tasks it said exactly what I needed to know. I realise 3.5kb may change over time, but I'd have been sold it if it had said < 5kb.
"A small tool for building user interfaces"
Could just as easily be describing backbone. small is very vague.
+1 for keeping something similar to currently line.
I can also go with the current tag line. It was a careful decision to use the word "React" since many people will immediately know what is this all about.
I guess we can keep it for one year or so before React is history :)
Thanks @crisward
I agree that small is very vague, and that's why I thought of compact, which also have some positive feel, meaning well-organized, packed and all.
Shall we change size (3.5KB) as it is not true anymore? I gzipped riot.min.js and got close to 5KB (4948 bytes).
Let us keep the current tagline otherwise.
Should it be then "A React-like user interface library" or "A React-like user interface library under 5KB"
By the way, React tagline reads "A JavaScript library for building user interfaces"
I think we should remove the size from the tag line. Seems to bring more troubles than benefits.
The size is a BIG selling point. Event if it said <10kb it's still 12x smaller the react. With riot I can write a basic application and still be smaller than most frameworks - that's very cool.
Of course. Small codebase is one of the main driving factors on Riot development.
But could it be taken out from the tagline? The constantly changing size doesn't look pretty. Perhaps use a good adjective there and move the comparison tables upfront on the front page.
I started with Riot, then went to React, and I found it a bit too much for me. So I returned to Riot. There is some inherent beauty and simplicity in working with Riot.
Personally, I do not count speed or size of individual library/framework since it is the whole app or even ecosystem that matters. I use Rails at the backend. On the front-end Riot is coupled with Semantic UI, which is not light-weight, but it works for me.
In highlighting Riot, that beauty or simplicity has to come out to attract developers.
@pyros2097 we are not planning to do anything close to "reapp". Riot is just the "Platform" part on that stack. I hope reapp will switch from React to Riot though as a competitive advantage :)
Size and speed are really important.
But as a developer the first thing I did was open dev tools and check the tag line!
I agree removing a size reference in the tag line would cause less questions. But size is big selling factor.
Maybe something like:
"A React-like (but ~12x smaller) user interface library"
Call me crazy but I still like the word micro even though it's cliche.
Clowns _need_ be crazy!
"A React-like user interface microlibrary"
Works for me too.
"A React-like user interface micro-library"

What about:
"The Isomorphic User Interface Micro Library"
Custom tags • Tiny footprint • Virtual DOM • Full stack • IE8
Like it, but drop ie8. Is that actually a selling point.
IMO IE8 support is not a selling point and we should help the world move forward. But that's me, and most likely a separate discussion!
How about this?
"The Isomorphic User Interface Micro Library"
Custom tags • Virtual DOM • Full stack • Tiny footprint
Maybe replace Full Stack with React-Like, since we are planning to take the router out of the library.
Isomorphic User Interface Micro Library
React-like • Custom tags • Virtual DOM • Tiny footprint
Ah, I was thinking full stack as server to client. Suppose it is a bit ambiguous.
Personally I'd like to remove the React reference (and free advertising!) since I think Riot is plenty good enough without it but understand the identity by comparison point.
Either way I'm happy with above! :-)
"A React-like user interface micro-library"
Custom tags • Virtual DOM • Isomorphic • Below 10k
Perhaps you need to make a poll somewhere on riotjs to figure out why people are choosing it lol.
if you start putting file size anywhere, you contributors are going to constantly be fighting to keep that codebase small which is not the most important part of riotjs imo. Everybody has their own reasons for choosing riotjs but I liked the simplicity of learning and using it, not that the codebase was under 3.5k. It was attractive no doubt, but definitely not the most important thing. Having a vague term like micro allows you all to keep the goal of keeping it small and simple while not having to worry about exceeding a certain file size.
I liked the simplicity of learning and using it
That is definitily the most important selling point and no tagline can be good enough to explain it but your docs can! Most of my time I'm a PHP backend dev but for my own project I needed a smart JS lib to create a multipage UI served by a PHP backend. I worked with backbone and ember in the past and also looked at angular but no framework really convinced me because when you don't work with them every day you need to read the docs again and again to remember what's going on.
Riot on the other side is so simple (but powerful) that reading the docs once is enough forever.
Btw. I tend to agree with @gregorypratt that "React-like" should be removed. Sounds like yet another react copy ... But it isn't. It's better! I looked at React because of this tagline, but fortunately closed the tab in my browser after 1 min to continue read the Riot docs : -)
I love riot.mount. It enabled me to write my own compiler in PHP to prerender riot tags with PHP and inject data, constants etc. server side.
Just my two cent.
I'm enjoying this thread!!
How about:

+1 to the simplicity aspects being a key selling point.
I actually do think IE8 is a good point to mention. Showing the breadth of support shows that the project seems stable and isn't going to just drop support and encourage fragmentation at a whim. It also discourages from eventually breaking IE8 support though. Plus if no one else is, it makes Riot stand out even more.
@gregorypratt your wishes are now fulfilled: https://muut.com/riotjs/
I purposely left out IE8 since I have a feeling the support is going to be dropped. It's just so hard.
Oh cool thats excellent! that'll make me smile every time I go read the docs!
@geordee Did you happen to have nice hello world example for Riot+Semantic UI? :)
ok succes in integrating semantic-ui and riot. j's. I need help to translate query function to javascript. It's just the line of code that in it some element Li the tabs. ¿someone have already solved this?
@geordee Did you happen to have nice hello world example for Riot+Semantic UI? :)
It's been a while since I used both together. Here is a snippet from my old code.
package.json
"devDependencies": {
...
"jquery": "^2.2.1",
...
}
In component:
<script type="es6">
let initialize = () => {
$('.ui.dropdown').dropdown({ on: 'hover' })
}
this.on('mount', initialize)
</script>
Again, not sure whether this will work with Riot today...