These are chat archives for ractivejs/ractive

28th
Jul 2017
Bob Schellink
@sabob
Jul 28 2017 11:24
I created a small and simple SPA with Ractive to demo ES6 modules to some collegues. Being ostly backend devs so we are a couple of years behind the curb ;-) For some reason unknown this exercise ended up as a modified router based on https://github.com/Rich-Harris/roadtrip. The examples can be found here: https://journey-js.github.io/journey-examples/
Target audience are newbies though.
Joseph
@fskreuz
Jul 28 2017 12:05
Nice!
kouts
@kouts
Jul 28 2017 12:09
That looks good! Seems that 0.9.3 was released also :fireworks:
kouts
@kouts
Jul 28 2017 13:23
@sabob I have an app that currently uses Ractive+page.js , I will try to convert it to journey!
I recently convert it it from gobble+ractive components to webpack+ractive-bin-loader
since I'm new to webpack+ES6 I find your guide very useful! Thanks for sharing!
Bob Schellink
@sabob
Jul 28 2017 15:28
If it is production code I wouldn't necessarily convert. Journey was just a way to "show and tell" colleagues about es6. Don't even know if it runs on anything but Chrome.
I got burned by gulp/grunt in the past and raw node have worked out well for me. But I hear good things about webpack, so perhaps that is the future? ;-)
kouts
@kouts
Jul 28 2017 15:32
Ah ok thanks, looks neat though, it's something that Ractive is missing.
Chris Reeves
@evs-chris
Jul 28 2017 17:24
@sabob that's pretty slick!
I was just playing with a stateful router based on roadtrip a day or two ago
Bob Schellink
@sabob
Jul 28 2017 18:50
If one needs nested routing this is probably a good choice: https://github.com/tildeio/router.js/
Martin Kolárik
@MartinKolarik
Jul 28 2017 19:10
There's also https://github.com/MartinKolarik/ractive-route which is similar to page.js feature-wise, but can sync state between ractive and the url, ractive and the History API, and also between indivudal routes.
Chris Reeves
@evs-chris
Jul 28 2017 19:20
nice!
it's kinda hard to keep track of where all you should look for plugins and components for various js things
Joseph
@fskreuz
Jul 28 2017 19:21
is it time to monorepo? :D
Chris Reeves
@evs-chris
Jul 28 2017 19:22
I guess npm is the default, but deduping names is problematic
monorepo might solve part of it for ractive
but not all and not for other stuff
there's a ractive org
Joseph
@fskreuz
Jul 28 2017 19:23
We could start adopting unofficial plugins as official plugins. That way, they reside under @ractive on npm, and the ractive repo for bower things. Deduping names however...
Naming is still hard in computer science... still a fact.
Chris Reeves
@evs-chris
Jul 28 2017 19:24
number 1 problem
I've been gradually working on a material-ish component suite
Martin Kolárik
@MartinKolarik
Jul 28 2017 19:26
it would work if we were able to pick one "best" package for one job that would become official... currently you'll easily find four ractive browserify plugins
Chris Reeves
@evs-chris
Jul 28 2017 19:26
I've no idea what to name things, and I'm conflicted on making the components completely independent, use shared lib code, or just build on each other as composites for the more complex components
that's a good use-case for the ractive npm org
Juan C. Andreu
@andreujuanc
Jul 28 2017 19:27
I used crossroads with ractive and works really good
(On that routing chat from before )
Joseph
@fskreuz
Jul 28 2017 19:28
We could ask the authors of the plugins to deprecate and we adopt one with the most uses/flexible/more options/bells and whistles. But then... https://xkcd.com/927/
Juan C. Andreu
@andreujuanc
Jul 28 2017 19:28
xD kek
Chris Reeves
@evs-chris
Jul 28 2017 19:29
should gradually get better, though
I'd imagine npm install @ractivejs/tabs and npm install @ractivejs/browserify are pretty conclusively "the standard"
for maintenance purposes, it's also not nearly as painful to grant users npm admin rights with an org
regular packages... I'm still not sure what npm, inc was thinking by not allowing a regular package to be controlled by an org - or at least something along those lines
Martin Kolárik
@MartinKolarik
Jul 28 2017 19:34
yep npm org sounds very suitable for this kind of thing
@fskreuz in this case there would still be 14 since we'd just promote one of the existing ones :stuck_out_tongue:
Joseph
@fskreuz
Jul 28 2017 19:35
:D
Joseph
@fskreuz
Jul 28 2017 20:26
What are the long numbers?
Martin Kolárik
@MartinKolarik
Jul 28 2017 20:26
timestamps
it's hits per day
Joseph
@fskreuz
Jul 28 2017 20:28
Looking at it, everyone skipped 0.8 and most people don't use legacy? :D
Martin Kolárik
@MartinKolarik
Jul 28 2017 20:30
yep, seems like it
Joseph
@fskreuz
Jul 28 2017 20:31
I would think percentage uses across major versions, minor versions, file (builds). Something similar to browser stats or this site http://gs.statcounter.com/
That way, there's a 10k ft view of the playing field.
And could drive development decisions like which versions or features to drop, include, why people still use it, etc.
Martin Kolárik
@MartinKolarik
Jul 28 2017 20:35
so maybe add a total field for each version and each file? and percentage would be easy to compute based on that
Joseph
@fskreuz
Jul 28 2017 20:39
Hmm... I could just total the days returned tho... :grin:
ones that have hits?
Martin Kolárik
@MartinKolarik
Jul 28 2017 20:40
yes
it doesn't have all the data yet
so some might be missing
Joseph
@fskreuz
Jul 28 2017 20:41
Hmm... I can't think of anything else. Looks good to me. :D
oh wait...
time cards?
what times people download
Martin Kolárik
@MartinKolarik
Jul 28 2017 20:42
that won't be possible for now
it's too much data even when stored per day
Joseph
@fskreuz
Jul 28 2017 20:43
:D
Martin Kolárik
@MartinKolarik
Jul 28 2017 20:43
not per-package that is
we might have something like that for hits in total per network
Joseph
@fskreuz
Jul 28 2017 20:48
the /npm/ means it was downloaded via the npm proxy while without it, it's downloaded another way?
Martin Kolárik
@MartinKolarik
Jul 28 2017 20:49
yes, we have stats for /npm/ and /gh/ proxies
Joseph
@fskreuz
Jul 28 2017 20:49
awesome
(speechless)
Martin Kolárik
@MartinKolarik
Jul 28 2017 20:50
and /combine/ of course :D
Chris Reeves
@evs-chris
Jul 28 2017 21:46
It'sa nice! 👌
Chris Reeves
@evs-chris
Jul 28 2017 21:57
@MartinKolarik are there more abstract endpoints, like 'the last year', 'the last month', 'the last week'?
Martin Kolárik
@MartinKolarik
Jul 28 2017 21:58
no, the default is last 30 days and it's fully customizable by from and to parameters
except changing those right now doesn't seem to work because of issues with the database 😅
Martin Kolárik
@MartinKolarik
Jul 28 2017 22:04
but I was thinking about adding such endpoints too, maybe https://data.jsdelivr.com/v1/package/npm/ractive/stats/{day,week,month,year} ?
Chris Reeves
@evs-chris
Jul 28 2017 22:09
That'd make badging super simple 😁
Martin Kolárik
@MartinKolarik
Jul 28 2017 22:11
yep it'd be great for cases when you need a static link that's always up-to-date... think I'm going to add it
Chris Reeves
@evs-chris
Jul 28 2017 22:40
I wonder who's using 0.4?
Martin Kolárik
@MartinKolarik
Jul 28 2017 22:41
almost nobody :D
Martin Kolárik
@MartinKolarik
Jul 28 2017 22:48
looks like the DB is back alive and so is this: https://data.jsdelivr.com/v1/package/npm/ractive/stats/day
Chris Reeves
@evs-chris
Jul 28 2017 22:53
nice!
0.4 has about half the usage of 0.9.1 😊
Martin Kolárik
@MartinKolarik
Jul 28 2017 22:56
btw we also count the old non-npm links, so 0.4.0 is most likely just some old website... it doesn't mean someone decided to use it recently