Microsoft 3D Movie Maker Source Code

• Microsoft-3D-Movie-Maker

  34 40 2.9 SWIG

  Discontinued This is the source code for the original Microsoft 3D Movie Maker released in 1995. This is not supported software.

  

• Microsoft-3D-Movie-Maker

  2 4 0.0

  This is the source code for the original Microsoft 3D Movie Maker released in 1995. This is not supported software. (by benstone)

Ben Stone is also working on it - maybe join forces :)

https://github.com/benstone/Microsoft-3D-Movie-Maker

there are a few that started to port:

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• BRender-v1.3.2

  13 523 0.0 C

  Argonaut Blazing Render (BRender) 3D engine

• ruby.wasm

  4 619 9.6 Ruby

  ruby.wasm is a collection of WebAssembly ports of the CRuby.

  

• Opal

  36 4,808 9.0 Ruby

  Ruby ♥︎ JavaScript

  

• blog

  3 565 1.0

  Luke Gorrie's blog (by lukego)

It is flawed for (otherwise) veterans too if they are trying to do something that they haven't done before so do not know what they do not know.

This really only works if you have done the same or something very very similar before and so you have practically no unknowns. Notice that the developer who did that commented above that they had already done similar work at the past.

Also related this quote about how Joe Armstrong (of Erlang fame) approached problems (from [0]):

> Joe wrote amazingly simple programs and he did so in a peculiar way. First he wrote down the program any old way just to get it out of his head. Then once it worked he would then immediately create a new directory program2 and write it again. He would repeat this process five or six times (program5, program6, ...) and each time he would understand the problem a little better and sense which parts of the program were essential enough to re-type. He thought this was the most natural thing in the world: of course you throw away the first few implementations, you didn't understand the problem when you wrote those!

[0] https://github.com/lukego/blog/issues/32

Suggest a related project