Hacker Newsnew | comments | ask | jobs | submit | jonnii's commentslogin

If they can convince Zibetto on 6th Ave to sign up I'll immediately give them $45/month. It'll save me a fortune!

reply


I write a lot of ember.

It can, occasionally, be frustrating (for example run loop craziness), but in my opinion it's no more frustrating than working with any other stateful front end framework (WPF, backbone etc...).

-----

kaonashi 80 days ago | link

I've done quite a bit of Ember as well, and lately I'm kind of liking React's approach much better. It composes well with many routing/model solutions, and keeps the 'run loop' isolated in the view layer.

-----


There are some really good cheap prosumer level EEG devices on the market now, for example the Avatar EEG (http://avatareeg.com/) and a few of the Emotiv devices.

I've been working on a side project (https://octopusmetrics.com) that allows you to connect these devices to your computer to record, visualize and analyze your EEG data in the browser. I think it's great that there are people out there thinking about how to do this more cheaply as it'll bring _real_ EEG devices into the price range where it'll be more available to hobbyists.

-----


I believe volume licenses apply after 100 users, but even so there is a rather large price difference.

-----


There's a lot of things wrong with ClickOnce. IIRC chrome's installer only uses clickonce as a bootstrapping mechanism for the _actual_ installer.

Problems:

* Can't choose installation path * No offline installation * Hard (impossible?) to use with a CDN.

Here's an example of how to turn a directory of precompiled binaries into a click once package using powershell:

https://gist.github.com/jonnii/2628150

My powershell isn't _great_, so forgive any powershell oddities, but notice how much you have to massage the output of the mage tools to actually get it to do what you want.

-----


Or maybe try Shimmer?

https://github.com/github/Shimmer

-----


Quickly, everyone convert their C to javascript!

-----


I'm using this and it works great. We even managed to get it deploy to heroku, which was pretty magic.

-----

benmanns 214 days ago | link

How do you handle when Heroku sends a SIGTERM to kill your process? I couldn't find a way to preempt running workers, so everything running on Heroku has to finish within 10 seconds or you can lose it.

-----

jrallison 214 days ago | link

Hey Ben,

Author of go-workers here. On SIGTERM, I stop accepting new work, and wait for all running workers to finish before halting.

If workers take longer than the 10 seconds Heroku gives you, go-workers uses reliable queueing (using http://redis.io/commands/brpoplpush) so the job will run again next time you start up the process.

-----

benmanns 214 days ago | link

Okay, cool. I do the same thing on the polling side, but don't use reliable queueing yet. I think that is probably the best way to handle the failures.

-----

jonnii 214 days ago | link

I'm not sure tbh, we haven't had that problem yet.

-----

jonnii 229 days ago | link | parent | on: Ember.js 1.0 Released

And Emu:

* https://github.com/charlieridley/emu/

-----


Everything is in this pull request, including the guides/samples.

-----

More

Lists | RSS | Bookmarklet | Guidelines | FAQ | DMCA | News News | Feature Requests | Bugs | Y Combinator | Apply | Library

Search: