inglor

102 ms·

961.
by inglor 12y ago
Python is a bad example since it has declarative data manipulation syntax. You'd use a comprehension and not a for loop which is practically the same thing in my opinion.
962.
by inglor 12y ago
In particular - the Microsoft .NET JIT will gladly make them as fast as loops in most cases - there might be overhead involving closures but that's mostly taken care of.
963.
by inglor 12y ago
Super useful. Debugging Select/Where is now as easy as debugging for loops. Also remember that the pain point for debugging is the laziness and not the declarative syntax and you can just use `.ToList()` to get rid of it.
964.
by inglor 12y ago
I humbly disagree - in the C# code I can pass an IQueryable and reuse the same code to make an SQL query, or a RavenDB query, or an XML query and it works just the same - there is a unified way to access data in the language. As for your qu
965.
by inglor 12y ago
I don't get why someone would rather write a for loop than use declarative data syntax. If I want to get the names of all administrators doing `users.Where(user => user.isAdmin()).Select(user => user.Name)` is so much nicer than
966.
What are the actual use cases of WeakMaps in JavaScript?(stackoverflow.com)
2 points by inglor 12y ago|0 comments
967.
by inglor 12y ago
Slow for me too - i7 3770k, 16gb ram, win 8
968.
by inglor 12y ago
This is a termionology issue based on what "theory" actually means in science. Theory in science means a foundation of how we think things work. For example people are perfectly fine with the "Theory of Gravity" being a
969.
by inglor 12y ago
Exactly! If you have a sane build process everything is always synchronized anyway.
970.
by inglor 12y ago
Why though? The whole point of git is that it's distributed source control - you _always_ have a local copy of the source and the history. That's one of the biggest wins in using git and not a centralised source control in the fir
971.
by inglor 12y ago
Start at slide 44 http://www.cs.huji.ac.il/~shais/Lectures2014/lecture11.pdf
972.
by inglor 12y ago
Any plans to make deployment of io.js easier to Azure websites? Also - any way we might get "break on exception" like with C#? Also - any plans to support debugging promises better?
973.
by inglor 12y ago
Why aren't they just using compressed sensing instead of PCA in the first place? PCA is good because it guarantees perfect recovery wen the set of examples is contained in an n dimentional subspace. Compressed sensing guarantees recove
974.
by inglor 12y ago
From the actual article (and not the news article): "The results show that students’ change in programming patterns is only weakly predictive of course performance" Not as "juicy" as the website - but then again, it&#x27
975.
by inglor 12y ago
I meant Linear Discriminent Analysis - good answer! I've experienced similar results with PCA vs other methods.
976.
From Bytecode to JavaScript: the Js_of_ocaml Compiler [pdf](pps.univ-paris-diderot.fr)
19 points by inglor 12y ago|2 comments
977.
by inglor 12y ago
Can anyone explain to a newbie why LDA and embedding through neural networks were not included as a dimensionality reduction techniques?
978.
Handling resources with JavaScript Promises(stackoverflow.com)
1 points by inglor 12y ago|0 comments
979.
by inglor 12y ago
"“hey, the >8=3 operator in this obscure paper on ouroboromorphic sapphotriplets could save me 10 lines of code, I’d better include it. My coworkers won’t have trouble understanding it as the meaning is clearly expressed in the type
980.
Io.js 1.5 released – with Buffer#indexOf and various enhancements(github.com)
4 points by inglor 12y ago|1 comments
981.
by inglor 12y ago
I'm just wondering - where does PostgreSQL stand with those numbers vs MySQL? Did someone perform similar benchmarks comparing the two in such workloads? Searching finds surprisingly outdated information.. Lots of articles say things l
982.
Super cool hack for adding infix operators in C++(stackoverflow.com)
1 points by inglor 12y ago|1 comments
983.
by inglor 12y ago
Ok. Here are some issues from joyent/node that have not gotten any comments in over a month: https://github.com/joyent/node/issues/9022 https://github.com/joyent/node/issues&#x2
984.
by inglor 12y ago
It still does have a way old version of v8 that's unsupported by Google. For the record.
985.
by inglor 12y ago
I didn't notice that - but 42 minutes later I think the comment still stands :) Check out the other top 5 issues - it's mainly a bunch of people talking to themselves. Anyhow - I genuinely wanted to link to both - not trying to po
986.
by inglor 12y ago
Similar thread on NodeJS's GitHub. Booming with comments and interesting discussion as usual ;) https://github.com/joyent/node/issues/9295
987.
by inglor 12y ago
Why? io is more stable and fixes get backported to node when it's possible to backport them. io.js can certainly benefit from these fixes but I don't think it'll be a "shitshow".
988.
Io.js and Node.js reconciliation proposal(github.com)
225 points by inglor 12y ago|77 comments
989.
by inglor 12y ago
Yes, it's possible this indeed will be the default behavior at some later point. Some people don't like this since `unhandledRejection`s can be handled later on at some point (for example, after a week of not adding a catch handle
990.
by inglor 12y ago
There is a short regression for https://github.com/iojs/io.js/issues/932#issuecomment-760226...

More ›