I haven't used labview, but Knime is both opensource and awesome. I can quickly prototype pretty much any workflow I want and get really good reproducibility. Debugging and unit tests need to be more directly integrated, but it is still a great package for practical science. It has R/Java/python integration as well!
Oh, and please think back to security in the old days of paper checks and manual accounting. It's much hard to forge an SSL cert than it is to fake a doctors prescription.
This sounds like Grace Hoppers rant about hanging 1K feet of optical cable (speed of light @ 1 microsecond) around the necks of programmers that wasted microseconds of compute time.
Computing requires exponential gains so that we can compute additional layers of abstraction. It makes it possible to program what we do. The reason usability has gotten better is because we don't need to write hand-tuned machine code just to get UI widgets working.
And do not tell me that the IT department are that much better than users, usability IS security. Make super secure passwords, users will write them down. Make it hard to install apps, and they will disable security. As Kevin Mitnick has shown time and again, people are the weakest link, not the technology.
Don't worry, we will get encryption and other privacy enhancing products into the hands of end-users soon. Just look at Chromebooks and the iPhone, both have lock-down capabilities that far surpass the average corporate desktop.
Technically, it's a series of pipes.
I know I am not supposed to feed it, but just in case...
Second, When MPEG LA first announced the VP8 pool formation, a rush of companies applied to be in the pool, partly because everyone wanted to see what everyone else had. That gave way to some amount of disappointment. And by 'some amount' I mean 'rather a lot really, more than the MPEG-LA would care to admit.'
Eventually, things whittled down to a few holdouts. Those '11 patent holders' do not assert they have patents that cover the spec. They said '_may_ cover'. The press release itself repeats this. Then these patent holders said 'and we're willing to make that vague threat go away for a little cash'. Google paid the cash. This is what lawyers do.
That's why it's a huge newsworthy deal when companies like NewEgg actually take the more expensive out and litigate a patent. It is always more expensive than settling, even if you'd win the case, and very few companies are willing or able to do it. Google was probably able, but not willing.
As for the quality stuff, WebM is close enough that it doesn't matter. We could argue details of that point, but the real reason Google is doing this is because the use cases for a web-centric codec are VERY different than the use cases for Hollywood and broadcast media. For example, web programmers don't care about encoding speed, we care about battery usage on cell-phones.
Renaming the invisible product doesn't make it any less of a bullshit argument.
There seems to be a lot of confusion about what MPEG LA is and isn't. They're a patent pool. They don't own any patents themselves, they just make it simple to license out a large basket of many (but not all) H.264 patents (one of the conditions is that you also put your own H.264 patents into the pool). You could go out and negotiate patent licenses from the original holders if so inclined.
So they are a convenience method for patent trolls. The older, craggier, the Troll, have enough to sue on their own.
Possessive apostrophe s?
TPB as operating expenses of ~$100,000. If half of that went to a single bandwidth provider, NK would have enough money to cover 1 middle-class contractor at an embassy.
The money coming in from TPB will have exactly zero impact on Kim Jong-un's capacity to violate human rights.
Um, yes it is:
$ traceroute thepiratebay.se
1 192.168.1.1 (192.168.1.1) 2.199 ms 1.119 ms 1.066 ms
21 rvs-rt0003_fe-0-0
22 202.72.96.6 (202.72.96.6) 1024.210 ms 907.023 ms 1024.071 ms
$ whois n 202.72.96.6
% [whois.apnic.net node-2]
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html
inetnum: 202.72.96.0 - 202.72.96.255
netname: INTELSAT-CUS-Camintel2-KH
country: KH
descr: Reassignment to CAMINTEL S. A. customer, KH
status: ASSIGNED NON-PORTABLE
remarks: * For issues of abuse related to this IP address block,
remarks: * including spam, please send email to at:
remarks: * mchsokhom@camintel.com
As a happy middle, we could just change the UI widget to detect when a signal is lying to it and offer up a spinning (or otherwise infinite) processing ball.
I mean, what's worse, being stood up on a date or not knowing for sure if s/he was going to tag-along on a group activity that you invite him/her to?
As an engineer, however, I would argue that we don't have to just give up because the maths proves it to be impossible. Even a reliably incorrect signal would tell us to not trust it and offer up a spinning (or otherwise infinite) processing ball. The reason we have these is to improve perceived performance.
I mean, what's worse, being stood up on a date or not knowing for sure if s/he was going to tag-along on a group activity that you invite him/her to?
Mod parent up: progress bars make for simple bullet point on a requirements spec, but defining one is takes an entire sentence.
"You need tender loving care once a week - so that I can slap you into shape." - Ellyn Mustard
