zak_mc_kracken

12 ms·

61.
by zak_mc_kracken 11y ago
Allow me to translate: > Twitter is using your app graph to help build a more tailored experience for you on Twitter. The more we can prove to advertisers we deliver targetted content, the more they will pay us. > Improved “who to fo
62.
by zak_mc_kracken 11y ago
Might be worth mentioning that the project has been abandoned for a few years (it ran out of funding) and that Gilad now works on Dart at Google.
63.
by zak_mc_kracken 11y ago
That is some crazy amount of spin. SourceForge started their path down the scummy side a while ago but this is really taking it to a new level. You'd think that if they really cared, they would back pedal on what they did, but no, inst
64.
by zak_mc_kracken 11y ago
I'm puzzled about the asymmetry of the syntax. What's the reason behind map[Point]string as opposed to something more symmetrical?
65.
by zak_mc_kracken 11y ago
Ok, so who is this person you are referring to?
66.
by zak_mc_kracken 11y ago
No, you are confusing people. The person is James Strachan, he created Groovy. Since then, he abandoned Scala and he's now a committer on Kotlin (or was, not sure if he still is, he tends to bounce around projects a lot).
67.
by zak_mc_kracken 11y ago
> There's a legitimate feeling the language tacked on way too much, too soon. A lot of people certainly feel this way, and this feeling has given rise to the first crop of post-Scala languages: Ceylon and Kotlin. I'm sure there
68.
by zak_mc_kracken 11y ago
> If a good team nails the guidelines down before hand on which idioms they plan to use and stick to them, yeah. So, like we used to do with C++? Anyone old enough to remember "C++ is fine as long as you define a well specified subs
69.
by zak_mc_kracken 11y ago
So now, your Scala can be both slow to compile and also slow to run! Seriously though, that's a pretty cool project.
70.
by zak_mc_kracken 11y ago
> Much of the hostility people are seeing in my post history is frustration with the industry Then stop attacking people and get used to the idea that you might be wrong on certain things pertaining to FP.
71.
by zak_mc_kracken 11y ago
You've never been to France or you never paid much attention in school, did you? Probably both.
72.
by zak_mc_kracken 11y ago
"Millions of people on the planet believe in Santa Claus, proving that it's very easy to create cover ups involving crowds across multiple continents". See the fallacy you're committing there?
73.
by zak_mc_kracken 11y ago
True. What makes this model compelling is that our flawed intuitions are very good at describing the world we live in, which is macroscopic and non relativistic. Letting go of these intuitions is a requirement to become a competent physicis
74.
by zak_mc_kracken 11y ago
Again, that says absolutely nothing about the quality of Go compared to other languages. You can write programs that work in Go, big deal. Maybe it would have been easier or harder with another language? Who knows. The valuation has everyth
75.
by zak_mc_kracken 11y ago
> Tell me then why Go is being used to drive so many big projects? False dichotomy. The fact that a language is being used for big projects (or used at all) doesn't mean it has great design. Think of PHP... I also completely fail to
76.
by zak_mc_kracken 11y ago
It's particularly baffling when, in response to: > But I disagree that putting commands in comments at all is a good idea. Just because other languages do it doesn't make it a good idea. It's clearly a hack to get around
77.
by zak_mc_kracken 11y ago
That's both an appeal to wrongful authority and irrelevant. You don't judge a software product by the credentials of who wrote it, you judge it by whether it's a good software product or not.
78.
by zak_mc_kracken 11y ago
You have a very naïve view of the world and an unrealistic conception of what open source is.
79.
by zak_mc_kracken 11y ago
> Just because it is open source does not me (a) that your changes will be mainlined, (b) that your changes will be even considered or (c) that you will logistically be able to maintain an ongoing fork. Or d) that I have any time in my l
80.
by zak_mc_kracken 11y ago
> Our conservatism should be a testament to how much we care about quality. Offering code generation as a solution to code reuse is not caring about quality, it's laziness.
81.
by zak_mc_kracken 11y ago
> We underestimated the passion the consumer had for this The passion of their customers to not put up with bullshit? Yeah, they definitely underestimated that.
82.
by zak_mc_kracken 11y ago
Why reinvent an editor from scratch? This is pretty much a guarantee that you will get zero traction. Your time would be much better spent writing a plug-in for Eclipse or IDEA.
83.
by zak_mc_kracken 11y ago
> it is hard not to see the power that comes from simplicity Actually, it is quite hard for anyone who's not already versed in Lisp and equipped with some reasonable knowledge of basic FP constructs such as folds. It's also im
84.
by zak_mc_kracken 11y ago
"Peek", damn it, "peek". You're not climbing a mountain stealthily, you're allowing people to "peek" into an early version of your product. How hard is it to just use common sense before writing words
85.
by zak_mc_kracken 11y ago
He meant 'viral' as a negative. The GPL is pretty much banned across the entire industry because of the fact that it forces accompanying software to be open sourced as well, which is a deal breaker for most companies.
86.
by zak_mc_kracken 11y ago
This is a pretty standard multithreading problem that has nothing to do with mutability or immutability.
87.
by zak_mc_kracken 11y ago
> "At what point in the frame was this change made?" Some parts of the game may have looked at the original version, while others looked at it after the change. Now magnify the potential for crossed-wires by all of the destruct
88.
by zak_mc_kracken 11y ago
As opposed to Apple and Microsoft?
89.
by zak_mc_kracken 11y ago
It's not his original page because he took it down (probably because he realizes this article makes him look incompetent).
90.
by zak_mc_kracken 11y ago
I always tell recruiters that my current salary is irrelevant. What's relevant is what I want my compensation to be in my next job, and I give them that number. Same thing when I interview: if the company insists on knowing my current

More ›