I think Polymer is an interesting framework with terrible docs. The company I'm interning at used Polymer 1.0 to build a complex web app. If you want a framework to replace jQuery, I'd mess with vue-js. It's a progressive JavaScript framework that is easier to learn and as light as jQuery.

I used to configure react js projects manually, but it can get really tedious with the number of dependencies and module loaders you need to remember to install. But the advantage of creating your own environment is that you know how everything works, instead of in a boilerplate project where the folder structure and different technologies used can make it difficult to customize. I personally use an ejected create-react-app as boilerplate now because it's pretty easy to understand, but definitely mess with other boilerplates and see which ones work best for you.

I know that feeling. When I was first learning React, I didn't understand why React developers hated seeing jQuery in React projects. But after getting more into the framework, I've realized that using jQuery isn't necessary because React has ref's and event handlers such as onClick built in to many components, so accessing DOM elements and adding event listeners can be easily done. Also, because React uses a virtual DOM, I believe it's not great for performance to directly manipulate the DOM as is the case in jQuery.

I like the simplicity of mini.css, and it has good documentation. I'll definitely experiment with mini.css on codepen, though because I'm not a very experienced web designer I usually like to stick with full-blown CSS frameworks like Semantic-UI or Materialize in my main projects.

I'm a distance runner, play jazz and soul music on the piano, listen to podcasts, and I like to read funny books.

What features in Exponent do you want to add in the future?

I believe that they're almost the same thing, but hashHistory adds a few extra characters to a route while browserHistory has a clean root. For example, if you had a route to an about page like this: <Route path="/about" component={AboutComponent} /> And you were using hashHistory, then the route in your web browser may look like localhost:8080/#1231/about (or something similar), while with browserHistory, the route in your web browser would look like localhost:8080/about. However, when you're using browserHistory, refreshing the page on one of the routes causes an error, so you have to modify your start script. It should look something like this: "start": "webpack-dev-server --inline --content-base . --history-api-fallback"