Exactly. At an investment bank for which I used to work in NYC, they moved their datacenter to be next door to the exchange's datacenter just to reduce latency.
Because in HFT, every fraction of a second can mean the difference between 10s or even 100s of millions of dollars in profit/loss.
You can change jobs on an H1B, if you're planning on working in the US it's probably your best option unless you can quality for an O1. I can tell you most people on an E2, an L1 or comparable visa would give their left arm to be on an H1B if they have any intent to stay in the US.
I realize it's the best option right now, but it's terrible. That's my point. The system is awful.
Theoretically you can change jobs but only to another employer who is in a position to sponsor your H1B. Which really limits your options, and doesn't likely move you into a better scenario because the new employer still has a distinct advantage over you (they are the one allowing you to stay in the country.)
I have the same problem. list-view 2.0 exists as a branch on krisseldens github (https://github.com/krisselden/list-view/network) and there have been other people forking from there. The implementation is _much_ simpler now due to glimmer, no more needing to get funky with ember internals. So it's essentially a re-write.
I haven't tried the 2.0 branch myself, but it _should_ be a drop in replacement.
That is good to know. I figured that ember-list view was likely using some private APIs and fiddling with the ember internals. It makes sense that the Glimmer engine would require a large amount rewrite work for list-view.
I just finished getting this working - if you clone that branch there is an example ember-cli app inside tests that has some examples which are great starting points.
Ember, more strongly than any of the other solutions mentioned, pushes you to a browser application (or SPA) architecture. Usually developers who complain about bloat aren't thinking of web development in that context.
The number of challenges a framework should help a developer manage for a long-lived client-side JavaScript application is not trivial. It is absolutely true that Ember is heavier than other frameworks, but it has a specific style of development in mind. If someone chooses to build their app with an alternative, they often end up with a similar amount of code in other dependencies and application code.
And though we aren't there yet, we're working on ideas for modular loading of application code (via the pods patterns) and of Ember itself via tree shaking. This latter strategy leverages the fact that Ember's code and much app code is written in ES6, and thus we can identify and drop un-referenced code.
Oh look that object extends another class... apparently it uses Mixin to extend these classes maybe the apply function? If it's using prototype inheritance than looking up the prototype chain would be a performance hit IIRC.
I was doing Ember while during beta though. But during that time they were marketing Ember as smaller library and more performance than Angular.
The last bench mark I've seen, Ember library is much bigger and the performance was not that great compare to Angular...
I'm not certain if it's bloated, and if I was building a regular CRUD app I would probably have selected it over Angular. It just implemented some things I had the feeling I would do differently, i.e. I didn't want to pick a framework I would have to fight to get to work the way I wanted it to. Ember is being developed by some very smart guys so I would never dismiss it out of hand.
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...).
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.
