I use animated SVG favicons in a Firefox extension I've been building. They actually work a treat

> The observer pattern is mentioned in the Gang of Four Book[1], published in 1994. JavaScript first appeared in 1995. Observers predate Redux. You don't need Redux to use observers, and in fact there's nothing about React that is incompatible with RxJS.

Yes, and before I was using React+Redux+Redux-Observable I was using Cycle.JS and everything was RxJS and/or Xstream (an RxJS-like) observable-based patterns.

As I said, this stack is a useful "oreo" for my needs right now. I understand if "oreo" isn't your cookie of choice.

> at the very least I think we can agree that "Doing one thing well" in UNIX means not creating a bunch of new problems that you need other tools to solve.

Again, I think the problem here is that we are disagreeing on what the problems even are. Again, I don't think these tools "create problems", I believe they solve very specific problems, and yes very "unix" in that way of solving as specific a problem as they can and no larger, and leave other problems that already existed untouched, whether or not they were in play, because again that's the philosophy here. React is "just" a view layer with a bare modicum of state responsibility. Redux is "just" a state layer. Redux-observable is "just" a tool for handling state side-effects. They don't need to solve every development problem, this isn't Angular. Similarly, they aren't the only tools for the job. There are several alternatives to each part of that stack (as others in this thread keep pointing out), this is just the one I've chosen for my projects right now.

Again. From my game dev days, the people that really lose (over and over) are the artists. Millions of hours have been sunk into laying out vector graphics with the Flash IDE. Code I understand should eventually be tossed away, but, not art. I guess staring at millions of beautiful vector timelined illustrations changed my opinion - but it is art to me. And like books, I think its a sin to toss. I hope the artists convert their .fla files over and save what they can.

I wish tabs/windows worked more like persistent "workspaces".

For example, say I'm booking a trip. I always open a bunch of sites (Kayak, Booking.com, lots of hotels, Google Maps, places to visit, etc.) in a single window. In pre-computer times it would be like covering a desk with a ton of papers, books and notes. Gradually I will figure out stuff, book the trip, etc. but the tabs can stay for quite a while.

I feel like many "dozens of tabs" windows are little projects like this. For example, doing development I typically have a bunch of documentation tabs open. We keep these windows open because there's no way to stash them into a drawer while they're not actively being worked on.

What browsers lack is a good way to treat these tabs as "persistent workspaces". I'd like to be able to close a window and be able to return to it later. Rather like an IDE which remembers your open files. So I wish I could "save" a window (as a "workspace") under a name, after which every action would automatically update the saved workspace. Close the window, workspace stays saved. Open the workspace, everything is restored.

There are some browser extensions that allow saving groups of tabs, but there aren't any that behave like I described above.

And this is why you only ever use credit cards from reputable providers with a proven customer satisfaction track record. I had uber pulling all sorts of shenanigans against my Amex a few months ago, and instead of dealing with Uber's BS I just had Amex cancel the charges. Done. Zero risk to my personal accounts with actual real money on them.

Never use debit cards when credit cards are accepted, is my general tip.