682 karma · joined May 12, 2012
For projects like Blender, where development is a self-reinforcing ecosystem I appreciate what the GPL does, here not so much.
- usdz (standardized zip file of pixar usd and assets) - reality composer (proprietary new format in iOS 13. you can add limited interactivity, but all scripting is in a limited graphical language) - also apps with ARKit + your custom render or SceneKit
Don't bring complexity theory into it.
The "industry standard" platform is only just getting around to switching to Python 3: https://vfxplatform.com
https://www.youtube.com/watch?v=rvkEpstd9os
The engineers doing the work know what it takes to make a good airplane. Let them do their jobs.
Had to make a fake Microsoft account via Sneakemail to even search it, though.
I tried to unlist my number but it said "Deactivation required", ie bait for me to create a real account?
If you only decoded big ones as BigInt, you would have the same problem of updating the code but now you have 2 codepaths at every callsite!
It's perhaps a defect in the JSON spec that it doesn't have a provision to support BigInt, but it's not really clear what should happen!
Why did they pass up the opportunity to make it a more stylish kind of hat?
I really enjoyed this talk from Apple's conference this year—it gives a great overview of the sort of conceptual framework a designer has when making specific choices:
As for android phones, afaik you're pretty boned.
I agree completely: the defaults should be the platform conventions. This wasn't much a part of the original Origami, but we've tried to improve that in the new version by providing some premade iOS and Android components for the most common things.
You can show an iOS styled Action Sheet, Android checkbox, etc., without building it from scratch (look in the layer + menu). While this doesn't include everything you need to know about iOS or Android conventions as a designer, it does encourage people to start with the standard controls and then look to custom solutions only when they don't fit. As much as possible, I tried to make the Ports on the layers match the API that the engineer sees in ObjC or Java so it feels like you're speaking the same language.
You can also break these components open and customize them, somewhat like you would as an engineer by subclassing or composing sub-parts. Internally at FB, we also made some custom layer patches that match the UI conventions for the FB app, Instagram, etc so you can have consistency by default. These bundles of layers & patches are called Systems (still working on docs for this), which you can build and distribute among your team. There is some more about this in our F8 presentation earlier this year.
The idea is that as a designer you can fill in the text for your Alert View or whatever instead of messing around with resizing rounded rectangles & text boxes like in Sketch.
Swift wasn't ready when we started a couple years ago. We actually used some swift for internal things and it has been a bit of a pain, eg with the macOS SDK update for Xcode 8. Combining ObjC and C++ you get a lot of the benefits of swift like functional programming / static type checking etc, paying a similar price in compile time.
It would be hard to achieve the elegance of ComponentKit syntax (https://github.com/facebook/componentkit) in swift though. It lets us express the UI in a functional way :D
Usually you end up making layers of abstraction / cacheing / parallelization atop them that don't have an easy SQL interface for the frontend to query. FQL was heavily sanitized and abstracted anyway, not directly SQL onto the boxes--imagine that security shitshow!
FQL has some holdouts in legacy code, but the vast majority of the iOS app is using GraphQL. There are a bunch of tools built around using it, and it's the "right way" these days. Maybe a year or more ago ago, the notifications tab was using FQL. It makes sense to convert things since the risk in switching is outweighed by a reduction in server CPU, network bytes transferred, and ability of tools to understand the code. When we built Paper, we did notifications on GraphQL because there wasn't the risk of breaking something.
You can almost certainly handle all of your 'data needs' with GraphQL... :D