roghummal

Hmm.

>Sarcasm can be seen as 'inauthentic' and diminish the immediately perceived value of a piece.

I'd rewrite this as such:

"Sarcasm is seen as 'inauthentic' and diminishes the perceived value of the piece."

>the majority of Gen-Y simply can't process more than 140 characters at a time.

I'd strike 'simply'. It's unnecessarily condescending.

>post-2000

Didn't like it when I wrote^H^H^H^H^Hread it and don't like it now. Clumsy. More forced than I'm comfortable with.

So it was political, like I said.

Not to kick 'em while they're down but it certainly wasn't on technical merit.

And in my opinion it's still very confusing. If there was a more confusing version of this message and it was refined to this then I'm inclined to believe the deception was intentional.

libav is not the successor to ffmpeg. libav is a fork. How'd Debian move so quickly to a(n) (immature) fork?

Politics.

Most of what I do with ffmpeg is change containers.

Example: ffmpeg -i doom4_trailer.mkv -acodec copy -vcodec copy doom4_trailer.mp4

Pretty simple, right?

libav:

>[mp4 @ 0xa33800] Application provided invalid, non monotonically increasing dts to muxer in stream 0: -83 >= -83

>av_interleaved_write_frame(): Invalid argument

(premature exit)

It's something in between.

"The ffmpeg program is only provided for script compatibility and will be removed in a future release. It has been deprecated in the Libav project to allow for incompatible command line syntax improvements in its replacement called avconv (see Changelog for details). Please use avconv instead."

"Gen-Y places a high value on authenticity. Sarcasm can be seen as 'inauthentic' and diminish the immediately perceived value of a piece. Satire, however, is a goodthing. Sarcasm is cheap; Satire is art. ... Sarcasm is more easily absorbed by the digestive tract of Gen-Y due to the short chains it forms. ... Society, long having moved from prechewed, tasteless meat into pre-prechewed, more tasteless meat substitute, the majority of Gen-Y simply can't process more than 140 characters at a time. ... Somewhere in every great satire post-2000 must be sarcasm, how ever much it cheapens the 'experience'."[1]

You'd think I wouldn't be getting killed here. Everything is falling flat. Bah humbug.

1. "The Truth About Satire" -- Faye Weather, 2001, http://thereisnopunchlinehere.com.us/books/weather,faye%20th...

I appreciated your contribution of sarcasm and I'm sorry if my playing off your sarcasm caused you grief. It's stupid that people downvoted (what's the HN euphemism for this?) your comment. It was appropriate.

Keep commenting. Moderate yourself; Fuck karma... just stay positive, I don't know what happens to the people <0. I heard they burn the bodies for fuel to run the server.

In case someone takes his comment seriously, there's mine. In case someone takes my comment seriously they'd agree with the grandparent so no harm done.

There's the chance someone would agree with the grand/parent ('malfunction...', secure, etc.), read my comment, and think... well that's ridiculous.

Case study for "'/s' considered harmful"; Would-be PhDs take note.

Did you read the parent comment? What does tamper-proof mean to you?

It's digitally signed and then the officer's recording system uploads it securely to the police servers when back at the station. This is all to maintain a complete chain-of-custody, so when used as evidence in court it can't be easily dismissed or disregarded by the criminal's attorney.

It can't be edited because there wouldn't be a digital signature!!!?

Cameras will malfunction but not like you're saying they will.

Edits in the middle should've been in NFO. Runtime is short. Good effort w/ the source. For a cam A3/V3.

This article doesn't properly projekt the magik of runes for one or more of the following reasons:

1. Runes are like magik (see my site runesaremagik.tumbler.com)

2. Who cares? Elvish.

3. Who cares? Klingon.

4. Who cares? ... everybodycares.js. It'll make your life as a front-end full-stack developer engineer designer hacker a lot easier by using stuff you already know to make new stuff with runes.

5. Heresy happens when you aren't sufficiently vigilant. Check your corners. They're coming for us.

That's a great way to force you to think about the words you choose to use.

I didn't see it anywhere either. Found it here http://journals.plos.org/plosone/article?id=10.1371/journal....

The article is available here http://journals.plos.org/plosone/article?id=10.1371/journal....

I'm on a roll tonight so I'll ask the dumb, easy question. What cipher/key size are you using?

https://wiki.openssl.org/index.php/FIPS_mode_and_TLS#TLS_1.2 isn't exactly a restrictive sets.

>Maybe(in 10-20 years)

I've seen 20 years of progress. Yeah... not to discourage you; Keep on shooting for the stars.

>We already have software runtimes (various Javascript VMs, .NET, the JVM and its offshoots, etc) that can optimize code at runtime based on the hardware that's present, hotspots in the code, etc.

Are you a hardware guy? :)

Thanks for elaborating. I had no idea how you went from "memory latency is a problem, that's why we have L_n caches" to "memory latency is a problem, we'll probably solve it ... (with cache)." This helps.

The biggest problem I see with integrating FPGAs into designs (HW) is educational. An on-die accessory FPGA doesn't amount to much if it doesn't get used. It's coming though. One way or another we're going to see more flexible HW. Taking advantage of it won't be something we're used to.

What good is an FPGA if it isn't 'workload-specific'? That's what they do. That workload might be a processor, it might be an interface, ... you get it.

Workload-specific FPGAs are here, now. They're not 'promising' because they're doing exactly what they were made to do!

>I don't know what the outlook for improving the memory latency situation is. It's probably going to involve gobs of on-chip embedded RAM, which is expensive.

They already have a name for that and you already named it.

It's called cache ;)

HTML5 was an improvement. HTML6?

Intel's 7nm? Anyone?

The golden rule! He who has the something something something something etc. Don't know, don't care.

Only tens of thousands?

Civility works best with mutual respect. That respect might be hollow or fleeting but it's established and traded on. When two people meet for the first time there's a credit exchanged. That's the humanity-freebie.

Don't ask for sympathy ("They don't want civility or truth!!!"), ask yourself why you were treated "uncivilized".

Truth? I suspect that's a glitch in translation.

So I don't confuse you with an edit and for my own gratification, I'd like you to know that I didn't 'trawl' through your posts to find something that supported mine.

Your titles are bait. Their substance is minimal. When you've had something to say it has been said before, better. If you care about the code as much as you claim you should let it go. (I'm questioning this last statement.)

You're a natural born CEO. Find your Woz.

Edit: And then someone to run your company. (I just saw "Judging from this comment and others, you seem uninterested in civility or truth. I doubt anything can change your mind on this issue.")

>Edit: It appears roghummal has significantly revised his comment since I finished my reply.

It doesn't 'appear' that way, that's the way it is. My edit was, just guesstimating here, 25 minutes before your post? Edit was 2-5 minutes after my original post?

You've never said anything you quickly realized was indefensible?

Wrong, even?

If it had we might be running it right now.

If you're ever in the Silicon Valley we should "meet up". I'll be nicer to you but you're buying.

You delved[1] into the vim source and found this. You offered no solution except to use neovim, which happens to be 'supported' by the /amazing/ company you're the CEO of. You're very well practiced in false modesty and apologies but fuck you; I'm not sure you know what sincerity means.

I'm sorry if I don't think you're being sincere. Let's have a drink sometime! Let's network!

1. Anything as old as vim, continuously developed, will have any number of these frankenfunctions. They're not hard to find.

Someday 'vi' might symlink to 'nvim' instead of 'vim'. 'VI Improved Improved'!

Mr. Greer's post was necessarily incendiary; He's building his brand. Wasting space on the front page of HN is a feather in his cap.

If you're going to use 'this is a companion piece to...' as a defense you should link to the original article in the 'companion piece' before you have to use it as a defense.