In most other languages this would fail code review as it is overly terse. I can see it does match the mathematical notation but if the language is supposed to provide any layer of abstraction then it doesn't do a very good job IMO. I guess the target market are mathematicians who already understand and write mathematical notation.
Not to be a downer but an academic study found this to have limited effect. I heard about it on freakonomics so can't vouch for how biased it was. Just an interesting point against the economist article. http://freakonomics.com/2013/09/26/would-a-big-bucket-of-cas...
The plugin details seems easiest but they are say "packet" and not http request and not necessarily by a browser. Presuming they have compromised the machine this staining will be affecting the network stack somehow most likely at an IP level.
What's the process for going about decrypting these things? I've seen some that are just base64 and the like - but those have obvious patterns. How are you meant to decrypt something when you don't even know the algorithm? Is it just a series of brute forces against different algos?
To me it sounds like a good thing. We end up with 3 major rendering engines on the desktop; Gecko (Firefox), Trident (IE) and Blink (Opera and Chrome) and 2 major on mobile Blink (Opera and Chrome) and Webkit (Safari). This I think will help shake up some of monoculture.
Chrome definitely doesn't have any level of domination over the enterprise market like IE6 on Windows did. That was the problem with IE6 not the browser per se - it was revolutionary when it was released, MS just killed the team. The chance that enterprises will stick with Chrome is very unlikely.
As it stands at the moment, the only downside is the duplicated development between the Safari and Chrome teams. Webkit will suffer, but the web won't. Apple don't care enough, the web isn't the top of their priority list.
If anything, the iOS monopoly of mobile web traffic (in the first world) is a problem which certainly isn't changed by this fork.
As long as you have the data then you can calculate it. It may be easier with SQL and a normalised form but that forces a lot of other constraints.
With a non-relational DB the idea is to attack it with map reduce and possibly in app calculations. This may not be ideal, but the benefits of easy placement and access of the documents outweigh the aggregation problems on most of the problems I have dealt with.
Neither solution is perfect you just need to make a prediction based on the projects requirements and make a choice.
I appreciate it is written onto a 2d plain. But it does look like 3D. This appearance of looking like 3D when a screen is 2D is complicated and very mathsy (not a word - I know). I've tried reading about it before but it is not straight forward.
Use the cursor keys (right is forward and left is back) to browse through the slides and I had to go into fullscreen mode to see the comments at the bottom of the page.
I use their heroku addon. I had an issue on a Sunday evening and was not expecting it to be fixed until Monday. I went to watch a TV programme and come back 15 minutes later (ad break) to find that they had already fixed it! Congrats guys, you are awesome.