Fellshard

44 ms·

721.
by Fellshard 8y ago
You'd need shared protocols for data, of some sort. Probably similar to the original dream for XML schemata.
722.
by Fellshard 8y ago
A key insight is less that all Indian devs are bad, and more that they tend to be called in by companies who are incapable of knowing whether they are doing good or bad. So when a competent team comes in and sees an Indian team that has op
723.
by Fellshard 8y ago
It is reasonable to assume overreach by governing bodies will occur; this is no less true for the EU than for any national government. The EU is no less likely to misuse that hammer, intentionally or not.
724.
by Fellshard 8y ago
Doubly so when they're apparently talking about a now-useless open fuse.
725.
by Fellshard 9y ago
This is a rough one, because the intent is genuinely good, but - as usual - the implementation is very poor. That always makes it extremely difficult to talk about reasonably with most people.
726.
by Fellshard 9y ago
A point I believe the author has missed: Goroutines aren't simply forked functions, but are abstracted as independent, autonomous processes. Now, that doesn't mean 'go' is a sufficient tool to reason about goroutines, b
727.
by Fellshard 9y ago
Precisely this. Reich's other works do a much better job, in my opinion, of accomplishing his goals, engaging you intellectually without boring your ears, either. 'The Desert Music' is also very good composition, as well, mo
728.
by Fellshard 9y ago
I'm reading through Joe Armstrong's thesis on Erlang, and one of his main points is that concurrency programming shouldn't need to care about locality, at least in terms of correctness. Processes can run locally, or on separ
729.
by Fellshard 9y ago
This distinctly worries me if it becomes considered a viable option. This is engineering 'not built here' ignorance. "Managed copy-paste"? This will lead to lack of ownership, fragmentation, amorphous components, broke