Randgalt

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.

Anyone know what port the Bluejeans server is running on and/or how to kill it in a manner similar to the Zoom workaround?

Wow - the amount of material that YouTube will demonetize has expanded massively.

Touche :D

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.

Dropwizard on the server. Vue on the browser.

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.

To compare the DPRK to first world nations such as the USA is beyond the pale. I can't even comprehend this.

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.

Yeah that's true. Think of the npm ecosystem, the burgeoning Go ecosystem, etc. All full worlds with their own repos, etc.

Maybe not - but some tool that you use probably gets it artifacts from it. http://search.maven.org - https://www.quora.com/What-is-the-Maven-central-repository

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.

A while back I wrote an Olive Garden dish name generator. http://jordanzimmerman.com/olivegarden.html

Like Taco Town :D Run Javascript in the JVM in Javascript

Exactly - I'm a hobbyist musician and have all my music there. But, the last year or so they've been focusing on podcasting, etc. and, as you say, it's not good at any of that. For people like me, they haven't offered any new features in a long time.

author here - I'd appreciate feedback on this. Is it useful? I think it is but wonder what others think. If there's interest I can push this to Maven Central.

Unlike many iTunes hate pieces this one offers constructive solutions. Yes. It's time to break this monolith up.

Very interesting article. In my experience writing Scala for the past year or so this article does indeed hit on many warts. But, there are many more warts not mentioned. The biggest two are the tooling (sbt for example) and the nearly incomprehensible standard library.

I'm good at writing code, developing libraries, architecture, etc. I'm not very good at operations - mostly because I don't enjoy it and haven't spent much time applying it.

Not everyone is the pitcher, the catcher, the first baseman, etc. We specialize because that's how humans work best together. Everyone should not need to know how to do everything.

Developers must work with operations - of course. The way and the what developers build must be able to be deployed in an agile manner. But, that does not mean that developers must become operations engineers as well. Leave that to the specialists in that role.

zookeeper always lacked ttl

ZooKeeper 3.5.3 supports TTLs

I did some quick testing with Apache Curator (note: I'm the main author of Curator) and it looks like zetcd isn't implementing the create2 opcode and several others. If the goal is to really be ZK compatible it has a long way to go. I'm not sure who the target of this is. But, I'll keep following and try to get the Curator tests to run when it's further along.

32G for my birthday in October, please. Thanks!

So then I assume you support prohibitions on drug use, the draft, etc.

Besides, what are you going to do with your <fill in the blank>? It'll be gone sooner or later

So, other's needs trump my desires?