ffk

Freenode is still heavily used and is worth frequenting to both meet people with similar interests and get help on a specific project.

I agree. I am not arguing that Comcast should be allowed to go unregulated either. I strongly support net neutrality and do not want to see it thrown under the bus.

Assuming it wasn't harmed is also speculation and we should definitely be concerned about the deal and what it means for net neutrality.

Comcast will likely get better customer retention, less service calls for higher quality netflix streams, a direct line to Netflix's core networking team to resolve problems, and a transfer of cash for the initial peering.

Comcast will also likely work with Netflix to estimate traffic growth and make sure their infrastructure scales before they have problems.

Again, we don't know the details of the deal. Assuming net neutrality was not damaged is also speculation. We need more information to know what is going on.

The deal was a paid-peering deal, which would likely drive down Netflix costs. We don't have any information on whether net neutrality was harmed. Hopefully netflix will provide information on this.

Peering is a practice where two sides agree to maintain their side of the infrastructure and not charge for metered bandwidth.

https://en.wikipedia.org/wiki/Peering

This might not be an anti-net neutrality deal. Here are the details we know at this point:

1. Netflix is currently using Cogent

2. Comcast offered them a direct connection to their network via paid-peering.

3. Netflix agreed and will move over.

4. Nothing about net neutrality was mentioned in the article.

This deal is being referred to as paid-peering. Peering is a practice performed at ISPs where two ISPs hook up infrastructure and agree to maintain their sides without charging for bandwidth. Peering is a common practice among the industry, and content-providers are always looking for ways to peer with more ISPs because it drives down their overall cost of operations.

The article says nothing about net neutrality. We don't have enough information to say whether net neutrality was harmed in this deal. We can only speculate at this time. Hopefully we will hear more from Netflix on this.

[edit to fix list formatting]

This reminds me about how many people don't use domain names at all anymore. Many people probably type the name of their bank into the search bar and visit the first result. I've seen people literally pull up google to search for yahoo mail or ebay.

Domain names are still useful, for a start they provide some level of authentication when mixed with cryptography. (If you visit https://news.ycombinator.com, you can be relatively sure there is no MITM with certain conditions present).

It would be interesting to see how this system can be adapted to work with our current Internet infrastructure.

I'm familiar with this, which is the reason I mentioned "PAE and other expensive workarounds" which allows you to break the 4GB limit.

It was badly worded on my part, I was in a hurry. :)

"But now Apple can also claim an advantage in raw horsepower. The new 64-bit A7 chip is the smartphone equivalent of a big V12 engine."

Except these performance gains most likely would of been seen on a 32 bit version of the chip.

It's interesting to see how much marketing is put around 32 vs 64 bit chips and the effect it has on how people market. The biggest benefit is the ability to access more than 4GB of memory. For reference, the iPhone 5S has 1GB of memory. Eliminating the need for PAE and other expensive workarounds is definitely a bug plus. i64 and cheap doubles are certainly a bonus too.

I suspect the primary reason for moving to 64 bit is not for performance gains now, but for future compatibility. Eventually, the iPhone 5S will be the oldest supported iPhone and running a 64 bit processor will reduce maintenance costs of needing to maintain a 32 and 64 bit line of software.

I think this would be a much more informative article if the author had interviewed a few experts to discuss the benefits of 64 bits over 32 bits rather than just say they go faster which at this point is debatable.

Except it isn't just auto complete he is describing. It is also code generation. The example he gave would come with an auto import. Other examples would include class and method generation, exception handling, parenthesis matching and test stubs.

Using null instead of None means you are more at risk of hitting a NPE.

Here are a couple examples:

myVar match {

  case Some(val) => doSomething(val)

  case None => handleNone()

}

myVar.getOrElse("else")

In both of these cases, we eliminated the possibility of a NPE through the use of a language feature. :)

(edited for formatting)

This was quite a while ago, but Square announced they would not do a FFVII remake until another FF outsells it. FFVII had around 10 million sales. The closest was FFVIII with 8.15 million sales.

Sales data: http://vgsales.wikia.com/wiki/Best_selling_Square-Enix_games

The wording of the article suggests it has never been played to an audience until this year. I suspect it was never built until now.

Sorry for the miscommunication, I specifically meant the tools created by his company such as Mathematica and Alpha.

If scientists can build computational models and test ideas in a significantly easier way, then this is definitely an important project.

Wolfram has a large following in the academic world and improvements to his product line can turn into real results.

I think this is the wrong question to ask. It's clearly enterprise ready considering enterprises are actively using it in their critical infrastructure. A better question is "Will scala ever have major release backwards compatibility as a feature."

This isn't to discredit the author's viewpoint. I strongly agree with many of the assertions he makes. Backwards compatibility is a major problem.

Back to backwards compatibility (wee, puns), I think a major part of it is not due to ABI changes. The JVM has very well defined entry and exit points to deal with this. The problem seems to stem more with the libraries. As long as the libraries keep changing at a fast rate, the scala cmomunity will never achieve backwards compatibility at the level this author wants to achieve. Until typesafe makes a strong commitment to put APIs through a sunsetting lifecycle with deprecation, it will continue to be a problem.

Fortunately, they have made a commitment to not make breaking changes in minor releases. E.g. 2.10.0 compiled applications should continue to work with all release 2.10.* runtimes.

Skype moved away from peer to peer for supernodes. Here's the article: http://arstechnica.com/business/2012/05/skype-replaces-p2p-s...

All I can find on their developer webpage that they appear to support is Skype URIs. It's basically HTML tags that register the skype: service to send commands to skype. The functionality appears to be completely one way. The app sends a message to skype and skype takes over from there.

Skype API appears to be the same things as Skype Desktop API which is the ops focus.

SkypeKit which allowed developers to create a headless skype client is no longer accepting new developer registrations. https://support.skype.com/en/faq/FA12322/what-is-skypekit

I can't see anything at all about hardware that supports skype. This is probably through some enterprise BD channel. Hopefully they aren't being abandoned too.

Yea, that definitely sounds more useful than what the post alludes to. Any chance you can post a screen shot?

This most likely was not the author's intention, but it reads like an ad. We can pay them money to auto translate our own website. The learning stage appears to come from the manual corrections that come after that, and having a friend "grade" his corrections.

A cheaper approach would be to translate from native to non native language using google (or whatever other free tool you want), and performing the same translation step w/friend to assess your progress.

If I am missing something, please speak up so or modify your blog so that we can make use of your technique.

Attack surface. When you increase the number of parties capable of decrypting your data, you increase the risk of an exposure.

I second this suggestion. It doesn't just slurp and serialize data, it also is capable of filtering, transforming, aggregating (+ stats) and pretty printing streams of json records.

For comparison, Google's logo also has a bevel and the first letter englarged extending below the baseline.

They most likely do test for security vulnerabilities. However, the attack surface and overall complexity is so large that things will slip by even with the most rigorous testing.

For now, the best you can hope for is a layered defense and rigorous dev and ops practices to help minimize the attack surface and reduce the overall damage a single successful attack can achieve.

This is most useful when you are renting or borrowing a car. If you don't check before you hop into the car, you need to physically exit the car and move it if you guessed incorrectly.

What I find amazing is google recovered so quickly. Extended outages are often caused by the horde of systems all attempting to reconnect at once.

This just in! Computers have no sense of humor! ;)

Offit left out information on why he started to advocate vitamins in the first place. He was diagnosed with Bright's Disease. One cause of Bright's disease is a lack of Vitamin D. Taking vitamins was the right course of action in his specific case. He most likely wanted to share his success with others, which is probably why he started advocating vitamins. It's unfortunate that he pushed vitamins as a cure as far as he did. It would be interesting to learn why he took the stance he did from people who knew him personally.

https://en.wikipedia.org/wiki/Bright's_disease

Another good example of misleading information is the last sentence: "In 1994, Linus Pauling died of prostate cancer."

He left out the part where he was 93 at the time of his death (1901-1994). Both the incidence and mortality rate for those over 80 are very high.

http://www.medinfographics.com/cancer-statistics/prostate-ca...

p.s. I do agree with the author in that I do believe taking Vitamins is largely unnecessary if you are eating a healthy diet w/lots of vegetables, legumes and fruit. :)

I believe this was created and presented as simple (contrast to easy) demo to demonstrate BTRFS as a possible backend for images. Docker currently uses AUFS, and was designed to support more fs backends over time. It also demoed a potential path for docker to become more extensible over time.

A github issue was created to incorporate BTRFS: https://github.com/dotcloud/docker/issues/443

Dotcloud blog post on dockerlite: http://blog.docker.io/2013/05/btrfs-support-for-docker/

Source: I saw the author's presentation at the docker meetup held at dotcloud a couple months ago.

This comes from the dotcloud team, who also makes docker. I believe this particular person speaks French as his main language. Cut him some slack :)

According to the TinyMCE, you can use aspell. http://www.tinymce.com/wiki.php/Plugin:spellchecker

You can get a windows build of aspell at http://aspell.net/win32/

Instructions are on the wiki on how to wire it up.