fsnarskiy

7 ms·

1.
by fsnarskiy 8y ago
Again you are saying the "inner functions should only be allocated once", there is no rule or book in CS that states that as the absolute truth. It is however a concept that would be taught in a typical OO programming class. Idk w
2.
by fsnarskiy 8y ago
Also to clarify something, it technically wouldn't be a closure since - A closure is an inner scope that has a references to its outer scope. It happens any time a function is created (technically, even global). That actually even goes
3.
by fsnarskiy 8y ago
what i was demonstrating by showing that design pattern is that there is already an easier and clean way to do private variables and scopes. BUT if you want to talk about its speed and efficiency here we go: It very intentionally trades me
4.
by fsnarskiy 8y ago
Please for the love of god learn functional programming. this is a primary example of being stuck thinking there is a RIGHT way to do things according to Object oriented design practices. Firstly objects in JavaScript are not classes, they
5.
by fsnarskiy 8y ago
Why? I feel like the person who proposed this is relatively young and newer to coding. The reason why i say this is the functionality he is proposing can already be done using one of the myriad of JavaScript design patterns - https:/&
6.
by fsnarskiy 8y ago
This is actually very interesting. Low-grade inflammation is often linked to aging and cancer developments, it is however often unclear whether its cause/effect or correlation - https://academic.oup.com/biomedgerontolo
7.
by fsnarskiy 8y ago
A much better article that talks about the same problem today - https://thetechsolo.wordpress.com/2016/02/29/scalable-io-eve...
8.
by fsnarskiy 8y ago
OK threads aren't "BAD" or "GOOD", threads are a tool to be used correctly. Threads are like a data super-highway and all the incorrect uses of them arise from using them for way to little data. Akin to building a 5