Someone just forwarded this to me. It's absolutely a true story and it changed the course of my career as well as starting Netflix OSS. I'm forever grateful to Yuri and Ruslan Meshenberg for their support.
Has anyone found a similar vulnerability with the BlueJeans local server? I tried sending a few test URLs and they don't seem to do anything so I'm not sure what the protocol is. If BlueJeans can't cause a webpage to launch it's app like Zoom does then I'm less concerned.
I'm old enough to remember programming for the original Macintosh which used handles and relocatable memory. It was a nightmare. Constantly locking, unlocking handles was a chore and error prone. I also remember early Windows APIs that had opaque handle-based memory allocations. Sometimes in life it's useful to check your history books and understand why some things were consigned to history.
I've been working remotely for more than 4 years and never accept cost of living pay. Of course, I don't make Silicon Valley salary but I'm paid a reasonable rate based on my experience not where I live.
I've always felt the problem was the moderators have too much control. A bad or dictatorial moderator can ruin an SO board. Hanlon seems to imply moderator changes but doesn't say anything specifically. So, I'm dubious until this is directly addressed.
If only life were that logical. Under the rules as they are today, there are many scenarios where illiquid options/stock have a taxable event. People's finances have been ruined by this. I had a friend lose a house when he sold his company for stock.
So true. Implicit parameter explosion is one the worst aspects of maintaining Scala code. In larger projects trying to comprehend how to import and understand which implicit parameters are used/needed can be maddening.
Are you implying they have a choice about where they live? As it happens, I've learned many things about the DPRK and what life is like there. So, I'm confident in saying that there are millions who'd love to get out of that hell-hole if they could.
To not mention it is conspicuous. Last year, an American tourist was tortured to death for taking a poster from his hotel room. I have a lot of trouble believing that the graphic designers in the DPRK aren't under similar threats. This piece smacks of context dropping. Not to mention that the author of that book promotes DPRK tourism. One might consider that American and think twice about going there.
The lack of any mention that the DPRK is a murderous dictatorship that is starving its people to death is disturbing. This piece makes it seem like the DPRK is just another country with a quirky culture.
What isn't mentioned is the tooling. The Scala compiler and sbt are atrocious. If you move to Scala you'd better get the most massive machine you can find and be prepared to deal with the monstrosity that is sbt.
You're right of course. I'm the main author of Apache Curator. While it does have a mirror on Github it's mostly consumed via its Maven Central repo. The Maven Central repo is most likely a better source of open source project usage.
It's important to remember how simple Java was in 1999. 10-15 years from now it's likely Go will have all the features that people have been asking for. The earlier these features are added the better. As a project gets larger it gets much harder to make large changes. Do it now and while they're at it they should fix the lack of good exception handling and a few other things that they will most likely have to address eventually.