Disney Open Source • Hacker News Board

Re: Disney Open Source

#71

Post by serge2k » Tue, Oct 18, 2016, 2:04 AM UTC

bmuon wrote: post #13

baccredited wrote: post #11

Steps: 1. Fire all the old programmers 2. Make them train their cheap H-1B visa replacements 3. Open source some code 4. Have a magical day! http://www.nytimes.com/2015/06/04/us/last-task-after-layoff-...

Did the NYTimes actually do any research for that piece? H1Bs are required to have a higher salary than average precisely to avoid that from happening

They hired contractors. Tata et al. are experts at this stuff.

Re: Disney Open Source

#72

Post by flukus » Tue, Oct 18, 2016, 2:07 AM UTC

JustSomeNobody wrote: post #33

pzenger wrote: post #16

Earlier quoted context omitted.

I believe it is based on the average for the country, which is much lower than the average in certain areas, like California.... But I may be wrong.

Hope it isn't based on what the government pays developers. I've seen some java devs making upper 30s to low 40s within the past few years. That's just crazy.

Last time I worked with a government department here the entire IT/development team were the local equivalent of H1Bs

Re: Disney Open Source

#73

Post by j0j0r0 » Tue, Oct 18, 2016, 2:08 AM UTC

I work there, and am on the Disney Open Source Committee!

We also just open sourced a hybrid public/private blockchain platform "Dragonchain" with some interesting features.

https://github.com/dragonchain/dragonchain

Architecture document: https://dragonchain.github.io/doc/DragonchainArchitecture.pd...

Code is newly released, and rough around the edges. We're working to get the docs up to par and some Docker containers ready for ease of use. Feedback is welcome.

Re: Disney Open Source

#74

Post by OvidNaso » Tue, Oct 18, 2016, 2:09 AM UTC

gkoberger wrote: post #22

alexkavon wrote: post #5

Can't wait for the Mickey Mouse repo in 2024.

Why? Disney has invested countless dollars into Mickey Mouse over the past 89 years. It's not like the Happy Birthday song, being hoarded without innovation purely for profit; they're actively expanding/investing/improving and making billions of people happy. Why should random companies get to legally print knockoff Mickey t-shirts just because enough time has passed?

Your talking about a company that owns at least 50% of it's success to the i.p. of characters it didn't create. Cinderella, Sleeping Beauty, Pinocchio, Aladdin, Beauty and the Beast...i could go on. I don't think anyone would argue that the films they made, based on the work of others whom they did not pay, contained substantial original creative effort and that they deserve the success they gained from those films due to the significant changes they made. The great hypocrisy though is that Disney would not have nearly the success they have today if Disney had achieved then what they are striving to achieve today.

Re: Disney Open Source

#75

Post by unsignedqword » Tue, Oct 18, 2016, 2:16 AM UTC

JustSomeNobody wrote: post #39

lima wrote: post #8

OpenSubdiv is a game changer in FOSS 3d software. Blender is already using it: https://wiki.blender.org/index.php/Dev:Ref/Release_Notes/2.7... Demo: https://youtu.be/dzIl_S-qHIQ?t=115

Like the entire game has changed, rules, board, pieces and everything? Or like the game has been somewhat improved?

Kind of - it depends on the artist you talk to. OpenSubdiv utilities have been part of the major 3D packages for about a year or two now, and it's true that they can offer some significant speedup, well-needed in both the games and per-rendered CGI industries where high-poly subd models can easily go up to several million triangles.

Besides the speedup, there is a very interesting feature of OpenSubdiv - local edge creasing. To influence the general creasing or smoothing of a subd mesh, an artist usually has to add more or subtract geometry in an area, respectively - whereas OpenSubdiv gives you the alternative option to assign a crease value to an area of the source mesh which influences the apparent creasing of the resultant mesh in that area without the artist having to add more geo. It works some of the time: not every artist likes using local edge creases but for those that do, it can be a very big help, considering the the occasional difficulty in adding new geometry to a mesh that flows correctly and doesn't accidentally ruin the rest of the mesh.

Re: Disney Open Source

#76

Post by chucky_z » Tue, Oct 18, 2016, 2:45 AM UTC

dragonshed wrote: post #12

The DIY style management software for OS X/macOS[1][2] is interesting. I knew commercial packages existed for this sort of thing (and more), but I'm fascinated that Disney admins & engineers chose to implement their own Software Update Servers. [1] https://github.com/munki/munki [2] https://github.com/wdas/reposado

How tied to Disney is munki and reposado? I use the Server app, but the functionality is continually hamstrung and honestly these open-source apps probably have more functionality than was ever in Server.

It's really interesting to hear that they could be tied so closely to Disney though.

Re: Disney Open Source

#77

Post by brazzledazzle » Tue, Oct 18, 2016, 2:47 AM UTC

dragonshed wrote: post #12

The DIY style management software for OS X/macOS[1][2] is interesting. I knew commercial packages existed for this sort of thing (and more), but I'm fascinated that Disney admins & engineers chose to implement their own Software Update Servers. [1] https://github.com/munki/munki [2] https://github.com/wdas/reposado

There's definitely much easier to use tools out there in terms of the UX, learning curve and some features that just aren't in scope for munki/reposado/autopkg but in many respects the commercial competition has been (and still is) playing catch up. Back when it was first introduced the divide was even greater.

Re: Disney Open Source

#78

Post by random567 » Tue, Oct 18, 2016, 3:13 AM UTC

j0j0r0 wrote: post #73

I work there, and am on the Disney Open Source Committee! We also just open sourced a hybrid public/private blockchain platform "Dragonchain" with some interesting features. https://github.com/dragonchain/dragonchain Architecture document: https://dragonchain.github.io/doc/DragonchainArchitecture.pd... Code is newly released, and rough around the edges. We're working to get the docs up to par and some Docker containe…

What do you actually use Dragonchain for within Disney? Why does Disney need a blockchain platform?

Re: Disney Open Source

#79

Post by santaclaus » Tue, Oct 18, 2016, 3:38 AM UTC

j0j0r0 wrote: post #73

I work there, and am on the Disney Open Source Committee! We also just open sourced a hybrid public/private blockchain platform "Dragonchain" with some interesting features. https://github.com/dragonchain/dragonchain Architecture document: https://dragonchain.github.io/doc/DragonchainArchitecture.pd... Code is newly released, and rough around the edges. We're working to get the docs up to par and some Docker containe…

Ya'll should release the source code along with those awesome SIGGRAPH papers every year!

Edit: Hyperion renderer would be the bees knees too.

Re: Disney Open Source

#80

Post by clarkmoody » Tue, Oct 18, 2016, 3:50 AM UTC

random567 wrote: post #78

j0j0r0 wrote: post #73

I work there, and am on the Disney Open Source Committee! We also just open sourced a hybrid public/private blockchain platform "Dragonchain" with some interesting features. https://github.com/dragonchain/dragonchain Architecture document: https://dragonchain.github.io/doc/DragonchainArchitecture.pd... Code is newly released, and rough around the edges. We're working to get the docs up to par and some Docker containe…

What do you actually use Dragonchain for within Disney? Why does Disney need a blockchain platform?

I'm also curious to know the use case and am reminded of the "Do you need a blockchain?" flowcharts [1][2]

[1] https://pbs.twimg.com/media/Cn2zMbTWYAAQA6i.png

[2] https://media.licdn.com/mpr/mpr/shrinknp_400_400/AAEAAQAAAAA...