andrejewski
Joined 14 years ago
Karma
17
Submissions
54
Member since
Mar 1
Recent submissions
Comment · 5 years ago
This is really cool! I made a very similar game a couple years ago: https://jew.ski/prime-time/
It's interesting to compare the game play and design. My game is written in Elm and open source if anyone is interested. This website has keyboard inputs (y or n) which is a good idea. My game only does click/touch inputs.
Comment · 8 years ago
Some feedback on the API design and README:
- Having a global registry of machines does not scale. Anyone building an app won't want to deal with the name conflicts. Having a `displayName` for debugging is fine but that's all. Having people pass the Machine instance to transitions directly is much more reliable/scalable.
- This [...rest] for event handlers is not good. Put those in a dedicated object because if you don't any new prop you add has the potential to break users. It's also bad because it looks like memory gets merged with those methods, making it likely the keys will conflict in view().
- Find a better name for T, it's confusing with Transition. Since it looks like a simple struct, maybe just have people pass {name, to} as plain data.
- You don't provide a rejected Promise example. I am interested how that works since it is something people tend to overlook.
- How the heck do I test my machines?
- A micro-framework that doesn't mention byte-size? Probably worth adding that statistic. My idea of a micro-framework is one that fits in a tweet.
- Write up how you expect this to be used. I don't think you could use this to build a real app because there's no way compose machines, only switch between them. You'd end up with huge machines because UIs are trees.
Happy to discuss more.
Comment · 8 years ago
If anyone wants the Elm architecture in JavaScript there is Raj: https://jew.ski/raj/
I spent over a year building the framework and a set of libraries around it so that the architecture feels natural to JavaScript developers.
There's only a few of us building apps with it right now, but the stories for doing most anything are covered and as of 2 months ago the framework hit 1.0. It is a safe foundation to build on as I don't plan to ever change it.
Comment · 11 years ago
Last winter I built an application called Subtweet that built on top of Twitter's Direct Message service, using Twitter's API as much as I could to reduce overhead. It is bittersweet that Twitter is improving DM as it makes Subtweet more and more unnecessary to users, but I am so happy to have all of these features built right in. I saw this shift coming when Twitter added multi-user DMing so I had already written the post mortem if anyone is interested.
http://subtweet.co/ http://chrisandrejewski.com/2015/02/07/subtweet-postmortem.h...
Comment · 12 years ago
If anyone is interested in just scrapping links between webpages with JavaScript, I made Slinky (https://github.com/andrejewski/slinky). The API is simple and easily overridable.
Comment · 12 years ago
Yes, the guarantees provided by true immutability are not met by "const". I wrote the note loosely using the author's expectations and advantages of immutability, not the exact definition. But thank you for letting me clarify.
Also I just noticed with Go's Unicode support we can write `const π = 3.14..` if we really wanted.
Comment · 12 years ago
I am completely in support of Haskell and functional languages in general. There are some gaps in Go and definitely some glaring problems. But this comparison also only lists the bad. Go is good for what it was intended for which is concurrent programming and server/web application.
Just a note: I don't think it is fair to say Go has absolutely no immutability as it was defined, it does have "const". See http://golang.org/ref/spec#Constant_expressions
website: http://chrisandrejewski.com/
email: [email protected]
github: https://github.com/andrejewski/
twitter: https://twitter.com/compooter