jwhitlark

26 ms·

91.
by jwhitlark 8y ago
There's a moral liability to do your due diligence when using upstream software, too. Otherwise it's just whining about "the untrustworthy system I built upon is untrustworthy".
92.
by jwhitlark 8y ago
How cool. I only know of him from these courses, but it was a fantastic intro and overview of distributed systems.
93.
by jwhitlark 8y ago
P2P isn't a single thing. But if you know more about what you want to do, you can usually find libraries to do it with. I recommend Indy's courses for getting the map of the territory: https://www.coursera.org/inst
94.
by jwhitlark 8y ago
Yea, I saw several instances of people who milked it for all it was worth, then retired and left everyone else to clean up the mess.
95.
by jwhitlark 8y ago
There were people who were fucked, but there were also people that were explicitly taking advantage. I know of two cases were individuals bought lots of property, borrowed to the hilt, took the money out of the country, refused to pay the
96.
by jwhitlark 8y ago
It's not shady at all. He wasn't suggesting breaking the contract, just enforcing it. Good luck winning a court case, although you might be able scare some landlords off with court costs. Many would just fight it out on principl
97.
by jwhitlark 8y ago
My gut feeling is the problem matters more than the language. I'm hopeful with the push to microservices we'll be able to mix and match these things where we think they'll work best.
98.
by jwhitlark 8y ago
There's a reason why we teach math in kindergarten and proofs in college. There's lots of things that are useful to do without the rigors of rigorous proof.
99.
by jwhitlark 8y ago
Well, there are certainly classes of problems that I'd use static typing for, but in my experience, static typing != software that gets the job done. That doesn't mean that it holds things back, though. Many static typing argumen
100.
by jwhitlark 8y ago
After my time with Scala, I think that if I need a heavy type system, I'd look to Haskell. And there are certainly classes of problems that I would choose a type system, but the general case isn't nearly as strong as I though it
101.
by jwhitlark 8y ago
At its core, spec lets you ask "Do I have what I need to do my job?", and if you have more, spec doesn't care. Type systems answer the question "Do I have exactly the machine primitives I expected, no less and no more
102.
by jwhitlark 8y ago
I think of spec like seasoning; if you put lots on everything, you ruin the dish.
103.
by jwhitlark 8y ago
In my experience, static typing was somewhat helpful in monolithic projects, but when I saw it used in heterogeneous distributed systems, it seemed to lose much of its benefit and impose new costs. I'm curious if we're going to se
104.
by jwhitlark 8y ago
I think there needs to be something like the Apache foundation for Clojure libraries, not handling major dev work, but maintaining working libraries over time.
105.
by jwhitlark 8y ago
If you can, I'd suggest use spec to improve your understanding and verify behavior. I certainly do know that Clojure can get very dense if you're not careful. http://blog.cognitect.com/blog/2017/6/1
106.
by jwhitlark 8y ago
I think this is a valid point. We talk about the right tool for the job, but forget that the evaluation needs to include the people using the tool, the people paying for the job to be done, and other elements of the environment.
107.
by jwhitlark 8y ago
I think some of that is due to the nature of the people it attracts, namely, grumpy, older, I've been burned before, programmers. I use Clojure constantly and have for 10 years, but I've never felt a strong need to proselytize.
108.
by jwhitlark 8y ago
Well, I would assume the receiving node would verify that each entry was actually needed.
109.
by jwhitlark 8y ago
It's easy to roll back capital costs if you make a mistake. That is far harder to do with people.
110.
by jwhitlark 8y ago
Well, at least that's dangerous.
111.
by jwhitlark 8y ago
Encryption + lose the key policies seem to satisfy the GDPR. So you don't have to actually delete an event, you can just give up your ability to read its payload.
112.
by jwhitlark 8y ago
As a 40+, the first time someone mentioned "the tyranny of the random number generator" it had immediate resonance. It was in a gaming context, but is a useful life metaphor.
113.
by jwhitlark 8y ago
A thorough explanation for a 0.1 project seems a high bar. I'd like to see an example or two where it loses data in the manner he speaks of, though.
114.
by jwhitlark 8y ago
I wonder sometimes if legal = moral is just a labor saving device for most of the population.
115.
by jwhitlark 8y ago
I became much more forgiving about political structures since I started working with distributed system. The ways things go wrong in distributed systems even before you inject free will is staggering. The link has worthwhile content, and wa
116.
by jwhitlark 8y ago
Wasted perhaps in immediate strategic outcomes. But don't discount blooding troops, burning in systems and building institutional knowledge, which are strategic assets. One can certainly argue if it was worth it, though.
117.
by jwhitlark 8y ago
You might be right. I do think that by being intentionally hosted, it avoids a number of traditional lisp problems. If it was a stand alone implementation, I wouldn't be nearly as bullish on it.
118.
by jwhitlark 8y ago
As my brother likes to say, "good enough is, otherwise they wouldn't call it that."
119.
by jwhitlark 8y ago
I think part of the point of clojure is a hosted, small core, programmable programming language can't really die, it would just be dormant and could spring back whenever someone needed it. It's weird to me when people claim clojur
120.
by jwhitlark 8y ago
This is in line with what I was thinking. The constitution is not a suicide pact, and at some point we're going to say you can't distribute certain knowledge. (How to destroy the world in one easy step). Give that, there's g

More ›