I think property based testing becomes a lot easier when you can just use normal asserts like this: https://github.com/unexpectedjs/unchecked

Not to be too critical but coming from Java/C# I‘m not not so hot they are writing their own tests: https://github.com/unexpectedjs/unchecked/blob/master/test/i...

Maybe just a matter of familiarity?

Really interesting to see Preact adopt this kind of model.

I have been working on a similar programming model for a while, where this kind of state management is the only approach:

https://github.com/sunesimonsen/dependable-view https://github.com/sunesimonsen/dependable-state

The library has other kinds of agendas like being able to run without a build step, being really small and allow multiple versions in the page.

Examples: https://github.com/sunesimonsen/dependable-example-hackernew... https://github.com/sunesimonsen/dependable-example-todomvc

You are actually right - I should update the readme with unpkg information:

import { css, classes } from "https://unpkg.com/stylewars@1.6.0/dist/bundle.esm.min.js";

Here we go https://github.com/sunesimonsen/stylewars#unpkgcom

An alternative that is much easier to adopt, is to use unexpected-check http://unexpected.js.org/unexpected-check/

It actually works similar enough that I switch between Vim and Evil daily without getting annoyed. I usually use Vim from the terminal. The follow things you asked about are all working:

  Macros
  Repeat
  :'<,'>s/foo/bar/gi
  :%s/foo\(bar\)/bar\1/

It is very actively developed and quite stable. There are of cause Vim features that are not implemented yet, but the core seams to be very well covered.

Interesting, maybe I'll give it a try. Do you feel any kind of impedance mismatch from using emacs w/o the native emacs bindings?

No, Emacs should be configured to your liking. The default Emacs keybindings (especially the more complex ones for common things) suck.

That said, you're still using Vim keybindings within Emacs and for some operations that Vim has no equivalent for you will need some Emacs knowledge. Also, some thing that Vim does have an equivalent for are easier to do in Emacs.

You cannot step into Emacs + evil-mode thinking you will never need to know anything else. You would be well advised to learn some Emacs basics and then help functionality.

For day-to-day operations like buffer editing you'll be able to use you Vim muscle memory.

Does Textmate users never learn? - "Yay let's use another proprietary editor as our most important tool" :-/

I don't care. And neither should any other programmer. If ST2 is going to be abandonware a few years down the line like Textmate is right now, that doesn't matter at all to me. $60 for a piece of software that I spend 1500+ hours a year working from is a steal. If it gives me a 5% performance boost, I'll gladly take the afternoon and convert to it, whether it's open source or proprietary.

I currently use vim & MacVim for all my programming needs, because I'm at my peak of programming performance while using them. With the very quick turn-around on ST2's builds, and tons of features coming out every month, I'm strongly reconsidering a switch. Knowing vim is still invaluable knowledge for general sysops, but like I said, I'd gladly give it up in daily usage for something better.