stepcut

5 ms·

1. 1.▲
   by stepcut 13y ago

   For me, the biggest downside is lack of solid embedded device support -- arduino (Atmel AVR), android(ARM), iOS (ARM). After using Haskell pretty much full-time for 10 years, writing C and Java code makes me sad. The support for the above m
2. 2.▲
   by stepcut 14y ago

   Well, there is no bad choice when it comes to picking a Haskell web framework. They are more alike than they are different. Anything you could develop in one, you could develop in another. There are certainly no magic bullets in any of the
3. 3.▲
   by stepcut 14y ago

   I think you mean, "Snap is pretty much the same as Happstack", since Happstack came first, and Snap borrowed many ideas from it. I would tell Snap users they should use Happstack because we have a shiny 3D graphic on our homepage. That is b
4. 4.▲
   by stepcut 15y ago

   I think that as far as the end user is concerned, there is not much difference between the warp, Snap, and Happstack backends. Speed-wise, warp is maybe 3 times faster than Snap and Happstack in the pong test. Though, how that plays out in
5. 5.▲
   by stepcut 15y ago

   I am Jeremy.. and I am not sure I would tell you the same thing. The Happstack webserver is pretty darn good. Of course, I think we can do even better. In fact, I think we can do better than warp.
6. 6.▲
   by stepcut 15y ago

   acid-state, http://acid-state.seize.it/ , which was previously known as happstack-state, and before that HAppS-State, has been doing it since 2005 or so. acid-state currently lacks replication/multimaster support, but happstack-state has h
7. 7.▲
   by stepcut 15y ago

   Agreed. Snap circuits is great. The mechanics are easy enough that my three year old can put together simple circuits.