jonpress

9 ms·

31.
by jonpress 12y ago
This guy has everything. Why is it that people feel an urge to praise him right to his face? His ego is going to start leaking out of his eyeballs.
32.
by jonpress 12y ago
Also, I think it takes a long time before you can judge if an engineer is really good - Many months, sometimes it takes years before you see any payoffs! Also some engineers might not be great, but they are good at picking the right tools f
33.
by jonpress 12y ago
I have worked with a lot of people in a number of different companies (including a few startups) and I can think of a couple of engineers who really stood out. When discussing engineering problems with these individuals, I never had to expl
34.
by jonpress 12y ago
The problem is that as requirements grow, class structures are often kept the same but the 'glue logic' which operates on these structures becomes increasingly complex (you have to handle a growing number of edge cases). There is
35.
by jonpress 12y ago
This makes sense for backwards compatibility reasons since it fits in with the existing REST API. An alternative if starting from scratch would be to design an event-based realtime API that uses WebSocket with long polling fallback.
36.
Show HN: LoadBalancer.js – A sticky TCP load balancer for realtime apps(github.com)
3 points by jonpress 12y ago|0 comments
37.
by jonpress 12y ago
I usually bookmark the page then later when I have the time I will read the parts that could be useful for my project.
38.
by jonpress 12y ago
Meteor is monolithic in that it forces your app to be structured in a particular way - It dictates how you should handle your data and how your scripts get loaded/bundled into your app. That said, I think it's much more flexible (
39.
by jonpress 12y ago
I have experienced this personally in a couple of companies I worked for - Just like mentioned in the article, they had high staff turnover. What happens is that nobody truly understands the codebase and it requires many more employees to m
40.
by jonpress 12y ago
A lot of wisdom there. I had similar experiences with SocketCluster. It used to be a full-stack framework (with a heavy, opinionated client-side part) but I was the only one working on it and when Meteor, SailsJS etc came along, I understoo
41.
by jonpress 12y ago
Another alternative is to use process-based concurrency with SocketCluster http://socketcluster.io/ - It runs on top of plain Node.js (or io.js) - It's just a module.
42.
SocketCluster v1.0 – An open source alternative to Pusher, PubNub and Firebase?(socketcluster.io)
4 points by jonpress 12y ago|0 comments
43.
by jonpress 12y ago
I don't think people should be given special treatment because they belong to a particular group. It's not a HR problem - It's a problem with society itself. Certain groups will inevitably lag behind (in terms of number of ca
44.
What I learned from my bosses' mistakes (startups)(fincrunch.wordpress.com)
3 points by jonpress 12y ago|0 comments
45.
Full stack pub/sub with SocketCluster(ncombo.wordpress.com)
1 points by jonpress 12y ago|0 comments
46.
SocketCluster – Full stack Pub/Sub – All the way to the browser(github.com)
1 points by jonpress 12y ago|0 comments
47.
Thread-based vs. Process-based concurrency – Node.js(ncombo.wordpress.com)
3 points by jonpress 12y ago|0 comments
48.
by jonpress 12y ago
I agree with all your arguments. I even have a project to back you up (it's Node.js multi-process based): https://github.com/topcloud/socketcluster - It scales linearly. I just ran a benchmark on a 16-core machine
49.
SocketCluster WebSocket engine benchmark – 42000 concurrent clients(github.com)
1 points by jonpress 12y ago|0 comments
50.
Why HTML5 is superior to native for mobile apps(fincrunch.wordpress.com)
14 points by jonpress 12y ago|18 comments
51.
Show HN: nData – In-memory data store which uses JavaScript as a query language(github.com)
6 points by jonpress 12y ago|0 comments
52.
by jonpress 12y ago
I wrote SocketCluster. I haven't tried that yet, it would definitely be interesting to test.
53.
by jonpress 12y ago
They don't. You can have fewer stores than workers. In the benchmark, we could in fact do with very few stores because they are not really used. I'm sure you could fiddle with the worker, load balancer and store count to get bette
54.
Show HN: SocketCluster – Node.js WebSockets that scale to unlimited CPU cores(github.com)
1 points by jonpress 13y ago|0 comments
55.
NData – A flexible deep key-value store server and client pair(github.com)
2 points by jonpress 13y ago|0 comments
56.
Nombo – Highly scalable and resilient realtime app framework for Node.js(nombo.io)
1 points by jonpress 13y ago|0 comments
57.
A powerful, dynamic caching engine for Node.js(github.com)
2 points by jonpress 13y ago|0 comments