sunesimonsen

6 ms·

1.
by sunesimonsen 2y ago
I think property based testing becomes a lot easier when you can just use normal asserts like this: https://github.com/unexpectedjs/unchecked
2.
by sunesimonsen 4y ago
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/depend
3.
by sunesimonsen 6y ago
Here we go https://github.com/sunesimonsen/stylewars#unpkgcom
4.
by sunesimonsen 6y ago
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";
5.
Show HN: A 1KB CSS-in-JS library with all the bells and whistles(github.com)
6 points by sunesimonsen 6y ago|6 comments
6.
Beating Levenshtein with Ukkonen's algorithm(github.com)
2 points by sunesimonsen 9y ago|0 comments
7.
Test Full Virtual DOM – Unexpected-React(survivejs.com)
1 points by sunesimonsen 9y ago|0 comments
8.
by sunesimonsen 9y ago
An alternative that is much easier to adopt, is to use unexpected-check http://unexpected.js.org/unexpected-check/
9.
React testing: enzyme vs. unexpected-react(medium.com)
7 points by sunesimonsen 9y ago|0 comments
10.
by sunesimonsen 13y ago
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/fo
11.
First batch of videos from the Øredev conference 2011(oredev.org)
1 points by sunesimonsen 15y ago|0 comments
12.
by sunesimonsen 15y ago
Does Textmate users never learn? - "Yay let's use another proprietary editor as our most important tool" :-/