a-kojeve

5 ms·

1.
by a-kojeve 9y ago
I agree. I like functional programming, but at some point, you're going to have some type of encapsulation, whether at the closure, module, actor, or network boundary. It's always important to think about what API you're expo
2.
by a-kojeve 9y ago
There's an important distinction, however, between redistribution that seeks to create a more free and just society and retribution that seeks to prevent a society without consumers. Most tech people in favor of redistributive schemes
3.
by a-kojeve 9y ago
What if I have an application that needs to be deployed internally and externally in separate instances. Identical application, but different security contexts. Using Nginx to handle these concerns is easy.
4.
by a-kojeve 9y ago
Yeah, but nobody relies on the execution order of disparate callbacks to achieve their results in JS. You're going to get burned in like two seconds if you try to do anything you listed. Lower level concurrency primitives in other lang
5.
by a-kojeve 9y ago
Definitely not the norm and probably not enforceable. I hope you find a new job!
6.
by a-kojeve 10y ago
I think the distinction is that a breaking API change breaks some of your code, a backward incompatible change breaks your entire codebase -- i.e., fix a few method signatures vs refactor your entire codebase.
7.
by a-kojeve 10y ago
Obviously the shareholders want the business to focus on whats the most profitable. iPhone seems basically to be a license to print money for Apple. Still, I think there are two arguments: They are sitting on so much cash. There is obviou