292 karma · joined November 5, 2014
as an example,i want to build a web crawler. ive worked with akka actors, and that seems like a good fit because the messaging logic for scraping is simple and it gives me remote distribution for free.. but then i see all these other models and wonder - what is the difference in doing it with Rx or futures etc? is there any difference besides choice of programming model in terms of how these things actually map to low level primitives?
However, programming may be lambda calculus at a theoretical level, but execution is a turing machine. All these little real world things that can be abstracted away in abstractions(!!), have to be unabstracted to meet a bunch of very real NAND gates somewhere, limited memory, resources etc.
Thats one reason it "sucks", but thats why its engineering and not math. Maybe one day computers will just be so powerful that we can afford to treat memory as infinite, runtime as infinitesimal, and build all the abstractions we want for free - then programming will be done :)
In this fun world, when i want to build something ill just draw a bunch of squiggly boxes and describe an alarmingly underspecified thingy i want done. Then the program will automatically figure out all possible inputs, quickly perform a "32 questions" kind of thing and resolve any ambiguity, then produce code. Managers will once again be confused why "adding this textbox is so hard", but this time they will be right - i will just tell lambda to go make a textbox.
from the paper:
The purpose of homomorphic encryption is to allow computation on encrypted
data. Thus data can remain confidential while it is processed, enabling useful
tasks to be accomplished with data residing in untrusted environments. In a
world of distributed computation and heterogeneous networking this is a hugely
valuable capability.Wow, i had no idea the prevailing wage was that high. Does this mean literally everyone on an H1B in the bay area is making at least $100k/year?! I should have negotiated harder...
"git stash branch <branchname>"
like "git stash" it stashes away all the untracked modifications you have, but it puts them onto another branch. i often end up making partial progress on things that should be conceptually in different branches at once - this way, you can stash unrelated changes into different branches, and then merge each branch as you finish.
This is another thing that makes stereotypes tricky - it takes a little bit of statistical insight to see how they can be both right in some sense but completely wrong in the other, but statistics is very unintuitive, and math doesn't grab headlines. So that kind of argument is difficult to use with non-nerds, but ultimately i think its the only accurate one.
That brings up another good point in that its really a perfect opportunity for media outlets that like to turn controversy into clicks. Its very controversial and very broadly applicable.
You can't tackle a problem you aren't even willing to talk straight about. The current system is something like attempting to make an ostrich walk while its head is forced in the sand.
But the official, carefully constructed non-offensive party line reasoning behind it in the US seems to be something like "all people of all types ever are the same", which is just not true. Any one deviating from the party line is automatically labelled bigot, and anyone defending these people is lumped into the same bucket.
Its NOT wrong to make generalizations about people. Our brains are pattern finding machines - we generalize all the time. It IS wrong to use them as justification to treat certain people differently - because a statistic computed on a population of millions doesn't really tell you anything about a specific person. So it makes sense to discard the generalization prior - i.e be unbiased and not view someone through stereotypes.
Its a hard problem - tolerating honesty but not bigotry, someones right to be offended vs. the offenders right to speak their mind etc etc. But right now US culture is very biased towards not being offensive, at the cost of truth - at the least, this kind of attitude does not belong in research. Research needs to be about truth.
Before - use chef/puppet to manage dependencies, distribute config files. run processes. maybe use something like upstart to restart on failure.
After - use Dockerfiles to manage dependencies (same thing, bunch of install commands). now you have a container for the web app, one for another service, etc. so everything is isolated.. great. what do you gain over running 2 separate processes? thats pretty damn isolated too.. except for the same disk, they each have own virtual memory, state, config files etc..
I'm not a (modern) ops expert at all, but i know my way around the command line. What do you gain from Docker or say launching a mongo instance on the cloud instead of just renting a server and launching the process? I really want to know. Atleast on a small scale, say if you're managing say 10-20 servers, i don't see the point.
Cat < Animal < Thing
So if the function takes any animal, of course it can take a cat (so its covariant in argument). And because all animals are things, we can say the output type of f is Thing.. its just less accurate than Animal but still correct - that is the contravariance in the result.
Cat extends Animal means "Cat can do everything Animal can, plus maybe more stuff". So all cats are animals, but not all animals are cats. So Cat is a subtype of Animal.
For the second question,
"an instance of subclass can replace an instance of superclass" is the right one.
Really it makes a lot of sense intuitively. e.g say Int is a subclass of Number (a simpler way to read is just "Int is a Number") . then anything you can do with numbers, you can do with ints too so we can put an int in place of a number.
It would be really cool if this was powerful enough to work for any video.
https://github.com/lampepfl/dotty/issues/818
I think the talk was pretty influential, but atleast the community is responding. I don't think it spells doom for Scala.
As a young dev, I really want to learn how to do this. I'm a newcomer to the Scala party, but I can definitely see it becoming a huge player and there are so many reasons - Odersky has basically a team of PhDs at EPFL constantly making awesome stuff for the language and they have made some incredible stuff - TASTY + scala-meta is one of the latest, Scala.JS is another, and really the list goes on and on.
But I'm only beginning to clue in on this now. Would've been great if I had jumped in earlier. If you don't mind me asking, how do you learn to pick the right horse? What were the signals for Scala? my guess now is the fact that Odersky was a major contributor to Java and built both a strong technical team and corporate backing, but thats hindsight ofcourse :)
The renewed push for accepting women in the workplace is simply one instance where a (reasonable) position has been chosen (women should have all the same opportunities as men in the workplace), but anyone who speaks against this position (even if just to improve it, or learn more) is labeled a old-fashioned,bigoted, and much worse.
The answer is to take a position without instantly shaming anyone who disagrees. So we can have an open discussion. The way controversial issues are treated here reminds me of medieval times - if you don't believe, you will be "excommunicated" from society. Debates aren't football games where you watch and cheer for your team to win. Right now, everyone is cheering for the womens side. Dont get me wrong, I am too, but that doesn't mean the other side is wrong/evil.
I guess it ultimately comes down to a persons belief systems and emotions at that point, far beyond the reach of mere logical arguments. We are animals first, thinking human beings second (this is the topic of one my favorite songs, Apeman- https://www.youtube.com/watch?v=aRHqs8SffDo)
Nothing in this world is stable. Your boss will fire you if you cant perform. Your friends may move away or change. Some will try to use you, but even the best ones will never care about you the way your partner will. Its an anchor in the storm of life.
There are probably many many authors who can wax poetic about this stuff better than me though, so I'll stop now.