kn8

This is easy to dismiss with the wide spread use of digital tools, but something about doing this seems to be deeply beneficial. And the bullet journaling technique specifically is surprisingly flexible and effective. I think some of it’s features could be transferred into our digital tools.

That is very true. That's why I said cut out "most" of the middlemen. But fair point.

This platform is kind of "on the side" and not in the middle though. It's not meant to affect how people listen to the music, how else they contribute to the bands (buying records, tickets, merch). This would just be a way of supporting the bands extra. I think Patreon is good, overall. This is similar but based on your "usage" and leveraging your Spotify account, and it's nice to bypass Spotify to support the band directly. I mean, Spotify gets enough money to run their service, but the bands don't.

I've been thinking of doing something similar for a while! A service that continuously keeps track of what you're listening to and suggests donating to the bands. And if you could allow bands to claim the money via some kind of Brave BAT style mechanic, you could perhaps also cut out most of the middlemen.

The main reason I haven't explored this further is – would enough people care enough to make this worthwhile?

Author here. I started working on jetpack ~2 years ago after several of my colleagues at the time asked – “how do I create a simple web app to display some data from an API I’ve built?”.

At first i was like, well... you could put it all in an index.html file, but realised that it’s not good enough because you can’t use npm packages, and its tricky to connect to the api and deploy such an app.

Then I was like, ok it’s easy, you just need – webpack, babel (for jsx or async/await), babel plugins, webpack config, css loaders, express and nodemon… yeah, that’s a bit much. Assembling an SPA didn’t seem beginner friendly, but also I myself didn’t enjoy wiring all of those things up from scratch.

Then I suggested Next.js, but wrapping your head around SSR has it’s own challenges.

After feeling a bit frustrated that it wasn’t easy to spin up an SPA backed by an API I started working on jetpack.

Since then, I’ve used jetpack to launch a couple internal tools and I am now using jetpack in building my next product.

Its not much, just a thin webpack wrapper with preconfigured defaults. But it’s nice to have this good, simple reference of how to assemble all these different plugins and loaders to create a good foundation for an SPA.

One feature that sets jetpack apart from similar tools is that you don’t need to install it locally into your project. You can point it to any JavaScript file on your machine and it will serve it up in your browser. Useful for testing out libraries or ideas.

Achieving Jetpack’s vision – making it easy for beginners and pros to spin up an SPA – is still work in progress. But that’s mainly due to a lack of good examples or tutorials, I’m pretty happy with the tool overall at this point.

There isn't really any server, it's based on p2p / device to device log syncing.

Tiny Atom integrates with Redux devtools https://qubitproducts.github.io/tiny-atom/devtools and allows jumping back to any state. It also:

* uses the new React.createContext

* is [highly optimised](https://medium.com/@kidkarolis/tiny-atom-3-0-0-e65a50de7f4a)

* provides `<Provider>`, `<Connect>` and `connect()` for both react and preact

* can be plugged in with immer

* explores how to improve over Redux API by combining dispatching and mutations in actions

* is small

I quite like this approach, but haven't had a chance to try it in production yet. It seems to be performant and convenient, the biggest cost being extra bytes.

In general, immer plugs in nicely to a lot of contexts, such as redux. Here's another example of how it works with tiny-atom: https://qubitproducts.github.io/tiny-atom/using-with-immer (disclaimer: yet another state management lib, which I wrote).

An alternative approach to immer I've been using in production is http://zaphod.surge.sh/, which is more like an immutable lodash.

I share this sentiment. I always felt like Redux had the right idea (single store modified via actions), but the API was just making things unnecessarily complicated causing people to either write lots of boilerplate or come up with complicated workarounds.

Here's yet another similar approach, also in 100 LOC https://qubitproducts.github.io/tiny-atom/. Been using it for a year in a few projects.

Interesting that there's no mention of UC Browser in this thread. I actually only learned about this browser myself today, but seems to be gaining a lot of marketshare: https://www.statista.com/statistics/268254/market-share-of-i...

It's generated on the server in Node, so no different than what PHP does in case of Wordpress in this aspect.

SEO is fine. More info here http://www.metacotta.com/ghost-seo/

Normally, when you're logged into multiple Google accounts - Google Bridge in Persona lets you pick which Google account you want to use. This error you're seeing seems like some sort of bug/UX issue (?) in Persona -> Google flow where if you're already signed into multiple Google accounts, but not the extra one you're trying to use - things don't work as smoothly..

Hm, interesting. I see your point.

What about Facebook/Google/Twitter Sign In buttons - do you think Persona is an improvement over those?

Use 2 factor auth to mitigate that? To me that seems safer than having 100s of different accounts with no support for 2 auth.

http://momentjs.com/ is a much better library than datejs. It's maintained, tested, smaller?, deals much better with internationalization/custom date formats. I'd recommend it to anyone looking for a JS date library.

Could this be due to the background image?

What previous attempts are you referring to?

This looks very promising!

JavaScript badly needs a package manager and the community badly needs to agree on a module format (AMD). Do you think that will happen? How can we make that happen?

Every other language has package managers.. ruby has gems and bundler, node has npm, java has maven. That makes it so easy to develop any application or library that can be used by any other application or library. ClientSide JavaScript finally has an amazing way to manage dependencies and build modular applications (AMD). All it needs now is a good package manager for being able to split large applications into individual components and manage external library dependencies. I want to be able to configure jQuery, Backbone, jQuery plugins, Backbone plugins, any other JS library, my own subcomponents as dependencies, use them via AMD's require and optimize in a smart way when building (e.g. only build in a single copy of the given library and warn if multiple versions are required).

I'm really hoping Volo (https://github.com/volojs/volo) or Jam (or both if they become interoperable) will become the solution for this stuff.