Offler

9 ms·

91.
by Offler 14y ago
Presumably to squeeze out maximum performance from multi-core machines. Current engines are all single thread per page instance.
92.
by Offler 14y ago
Could you not just fix it? Or drop support for IE6/7/8 and only support the newer IE browsers?
93.
by Offler 14y ago
(However, It's also worth mentioning that Discourse is, if anything, even more of a JavaScript project than a Ruby on Rails project. So why not Node.js? Presumably it's down to maturity.
94.
by Offler 14y ago
Where I work we have build a framework which is quite powerful for handling large JavaScript codebases. http://www.caplin.com/developer/component/bladerunner I'm surprised there isn't an equivalent OS one, I think Yeoman is a pale compari
95.
by Offler 14y ago
Of course you can use JavaScript to express OOP patterns. You say it yourself that you need those patterns to develop large apps. Anyone who does otherwise either leaves behind a mess of a code base or is being naive. You can have classes r
96.
by Offler 14y ago
I understand the evented nature of Node.js and I'm not taking that away. In the code example I gave I'm still using the async methods. DirectoryScanner.scanLibraries = function(librariesRoot) { // Asynchronous Function Callback func
97.
by Offler 14y ago
Author here: I like promises and I think they have their uses but I think for most cases simply writing well structured and encapsulated code will make them superfluous. You also have the problem of working with APIs that don't return promi
98.
Callback hell is a design choice.(blog.caplin.com)
7 points by Offler 14y ago|4 comments
99.
by Offler 14y ago
I just don't understand the issue people are having here. Nested callbacks are a design choice, if you do not want nested callbacks stop writing code with them in it. Here is a simple example in some Node.js code I've just written (I've nev
100.
by Offler 14y ago
Yes, it's a conspiracy! They're out to get Webkit.
101.
by Offler 14y ago
Indeed, 'terrible', 'evil' but not 'lazy'. Nothing could cause such pain without a lot of hard work.
102.
by Offler 14y ago
Then I suggest you read the article as he gives a very good explanation.
103.
by Offler 14y ago
I believe they've said never. They don't want just one major rendering engine.
104.
by Offler 14y ago
Could not agree more with the idea that people should write more well designed, OO code. This exact same issue is prevalent in JS land and it leads to people saying JS can't be used for real development, when in fact the problem is that the
105.
by Offler 14y ago
We have a framework more than a library, we basically ship a framework that our clients use to create their own web trading applications. This framework covers many asset classes and many use cases. It's not likely that any client would use
106.
by Offler 14y ago
I think those eras had browsers that weren't capable of delivering on the promise. If you only work with IE9+ (all the other browsers are quite good now) you will be working in a run time environment that is far superior to those available
107.
by Offler 14y ago
I would suggest using a modern browser, it looks fine in FF 18.
108.
by Offler 14y ago
Could you back up your statement with some examples? I have friends with the SII and they are very happy with it.
109.
by Offler 14y ago
Be careful about A/B tests, from what I understand Amazon relies on the extensively and they have helped it produce its Amazon website. Enough said. If you have two choices one bad and another less bad you will chose the less bad, when inst
110.
by Offler 14y ago
The problem may be down to their poor conversations. We have both wide ranging general knowledge and focused technical conversations in my office involving groups of people and I would be sad to lose that. Talk about something that can deli
111.
by Offler 14y ago
I read Justice Breyer as Justin Bieber for a second, I immediately had to double take!
112.
by Offler 14y ago
Not if other platforms grow faster than it i.e. Smartphones or Tablets.
113.
by Offler 14y ago
This looks interesting but the website seems to lack information, could I have just walked up to this place one day and offered my services as a developer to any idea that took my fancy?
114.
by Offler 14y ago
Because it takes time and CPU cycles for them to figure out what is a Type and what is not. They don't know how much memory to allocate to these objects for instance, but now with classes they will know types immediately.
115.
by Offler 14y ago
It's called Type Specialization http://dl.acm.org/citation.cfm?id=1542528
116.
by Offler 14y ago
I'd bet you they will allow browsers to optimize their compilation steps, so they are more then just sugar.
117.
by Offler 14y ago
Why is that not the default way to access preferences? It just seems so much nicer than a dialog box. Death to all dialog boxes.
118.
by Offler 14y ago
We build online trading applications with KO (we use it only for the view, we have our own Presentation Model were we have observers which pretend to be KO observables) and we have found it quite helpful. The components built are FX tiles,
119.
by Offler 14y ago
If Mozilla succeed then there will be a common standard for all developers to code to, there will no longer be any worry about an app not working on Linux/MacOS because the targeted environment is the browser. The browser becomes a VM, in f
120.
by Offler 14y ago
Correct, this looks like a less capable Popcorn.js

More ›