Coding your own video editing software

Hello /prog/ I have a question/challenge for you:

If you had to code your own professional video editing software what programming language would you use and why? How would you do it?

Also: Would it be possible to use asm language to make editing software?

C++

Using ASM:
Possible? Yes.
Time span: loooooooooooong
Fucking insane? Yes.

Lisp or some other decent high-level language, although >>2 would be partially right, interoperation with existing codecs would be easier in SEPPLES.

Assembly? Possibly, but it depends what features you want. If it's something like VirtualDub, it might be doable in reasonable amount of time, but if you want to make the next After Effects or some non-linear editor, probably not, unless of course, you don't want a GUI, in which case, there is already AVISynth, which is not very portable because it has huge amounts of itself written in x86 assembly.

>>2
That's pretty much the answer I expected. I ask because asm is the first language I'm professionally going to be learning. But I've had experience with C in the past so I guess I'll start with that. Are there any resources that might be able to help me with this?

>>3
Noted. I've always wanted to learn Lisp. Yeah the program would be more comparable to a combination of Final Cut 7 and After Effects.

Only compiled languages. Don't listen to anyone who mentions Garbage collection/Functional/academic languages they will be very fast to develop but the result code will be shit and unusable for video.

>>6
What would the best compiled language for this project be in your opinion?

Any language which
1.does not have GC pauses, mandatory GC or some OOP layer which hides raw memory.
2.has native hardware types
3.does not impose object/type/function call overhead compared to plain C
4.has inline asm, SSE is a must
5.has easy openGL/OpenCL bindings

>>6
You'd be surprised how fast some of them can be (also most are compiled(such as most Common Lisp implementations), 'interpreted' is rare, although it is the case with some languages like Ruby and Python(only applies for CPython)), but then I should know better than to respond to your posts.

>>8

So pretty much C++

>>8
So pretty much Objective-C

>>8

So pretty much C

>>8'
>GC pauses
This shit really happens? Has no one had the idea I had? Simply track a location, and every pointer pointing to it, and when none are left (Query this on pointer assignment) free said address, and keep all scoped variables in a ``scope'', and clean said scope when a function returns.

Virtual machines ``delay'' for GC? What the fuck is this shit? Is it really that hard?

>>13
http://en.wikipedia.org/wiki/Stop-the-world#Stop-the-world_vs._incremental_vs._concurrent

>>13
Congratulations, you've invented reference counting. Now go read Wikipedia on problems it has.

>>14
God, what an idiot.

Если у тебя есть фонтан, заткни его; дай отдохнуть и фонтану.

Simple stop-the-world garbage collectors completely halt execution of the program to run a collection cycle, thus guaranteeing that new objects are not allocated and objects do not suddenly become unreachable while the collector is running.

This has the obvious disadvantage that the program can perform no useful work while a collection cycle is running (sometimes called the "embarrassing pause"). Stop-the-world garbage collection is therefore mainly suitable for non-interactive programs. Its advantage is that it is both simpler to implement and faster than incremental garbage collection.
GC IS SHIT

Since video editing is not interactive anyway, some pause will not be noticed. Its the video playback that need to be GC-free.