HNHacker News
TopNewBestAskShowJobs

darknoon

682 karma · joined May 12, 2012

deep learning, GANs, art, graphics ML for creativity at diagram
submissionscomments
darknoon··on Radeon Open Compute 3.0
No, this is Linux-only.
darknoon··on Show HN: A Simple LocalStorage Hook in React
It is a difficult to recommend a small package that is GPLv3, since your entire app would have to be licensed appropriately (since it runs in the same process).

For projects like Blender, where development is a self-reinforcing ecosystem I appreciate what the GPL does, here not so much.

darknoon··on Canon designed a lens that sucks air to clean sensor
This looks like a great way to ingest air that contains dust and stick it to your sensor. Looks like a useless patent to pad the ol' portfolio.
darknoon··on High-Performance GPU Computing in the Julia Programming Language (2017)
It's because CUDA performs better. It's not nice, but it's the situation we're living in. Particularly AMD support and performance are lot.
darknoon··on Reversing Safeway's private APIs to automate coupon collection
Future of this: computer vision detector on top of frequently-updated satellite data?
darknoon··on Cows painted with zebra-like striping can avoid biting fly attack
The comment above is indicating issues with the pigment, rather than the solvent used to disperse it. You can have very toxic water-based paint, see watercolors with cadmium etc. That being said, it's completely plausible to mix eg chalk with something non-toxic that also doesn't wash off so quickly.
darknoon··on The State of Augmented Reality
WebAR is a term these guys invented. On iOS there are main 2 technologies:

- 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

darknoon··on Silicon Valley is terrified of California’s privacy law
Yes, if you log personal information like IP addresses you need to have a plan to delete it. Maybe storing it long term is a liability not a benefit.

Don't bring complexity theory into it.

darknoon··on Sunsetting Python 2
One of the more annoying aspects of the Python 2 to 3 transition is with large movie / video production houses, eg Pixar. Their USD library only supports Python 2, since they aren't interested in supporting Python 3. I wonder if that will change next year.

The "industry standard" platform is only just getting around to switching to Python 3: https://vfxplatform.com

darknoon··on Sites with dumb password rules
No, because attackers can easily determine the constraints (assuming they are kept "secret") by signing up for an account on their own.
darknoon··on Boeing's Crashes Expose Systemic Failings
I saw this documentary about issues with the 787 back in 2014, and it was clear that something was massively wrong at Boeing:

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.

darknoon··on Betrayed by an app she had never heard of
I found my real name and (former) carrier on Truecaller. Shit.

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?

darknoon··on BigInt Shipping in Firefox
You could decode all of them as BigInt, but then you would be accepting a large overhead for the much greater number of constants like 1 or 42 where it's unnecessary. Everywhere you pass that JSON data would need to be updated to operate in terms of BigInt instead of number.

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!

darknoon··on New brand
The association with fedoras in popular culture is not positive at the moment.

Why did they pass up the opportunity to make it a more stylish kind of hat?

darknoon··on Dataturks – ML data annotations and labeling doesn't need to suck
Does anyone have a good tool for pixel-level annotation? I was thinking an iPad app with pencil support might be nice, but open to whatever is out there.
darknoon··on MNIST training: Showdown between JavaScript and WebAssembly
It would be a more fair comparison to https://deeplearnjs.org/, since CPU training is not standard practice for neural nets these days.
darknoon··on Propel – Machine learning for Javascript
You say this, but coremltools (convert from industry standard to Apple's ML framework) initially only supported python 2, so it was annoying to work with some code in Python 2 and some in 3.5.
darknoon··on New chip reduces neural networks’ power consumption
Uses less power to do less useful work (binary weights)…
darknoon··on React 16
I’ve spent a few months writing code in a moderately large redux app and hadn’t heard of any of these. Maybe more could be done to call them out in redux docs?
darknoon··on Basic Principles of Visual Design
This article touches on _what_ knobs you have to control in a visual design, but a beginning designer often struggles to put these to service in a bigger context.

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:

https://developer.apple.com/videos/play/wwdc2017/802/

darknoon··on New York eyes a 'breathlyzer' for texting while driving
Older iPhones have exploits that allow bypassing some or all of the protections. It's likely exploits will be found or have been found against current (iPhone 7) hardware given the economic incentives. Nonetheless, I am not aware of any out in the wild.

As for android phones, afaik you're pretty boned.

darknoon··on Geological Insights from Malaysia Airlines Flight MH370 Search
Does anyone know if the dataset is available publicly?
darknoon··on Origami Studio – Design Prototyping
Anecdotally, I have a friend who is a designer who did a lot of Quartz Composer prototyping and eventually learned ObjC to implement some of his designs. Seems like once you get the idea of building out gestures and animations it transfers across the specifics of Patches / textual code / etc. Now he writes c++, swift, etc :D
darknoon··on Origami Studio – Design Prototyping
Origami eng here.

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.

darknoon··on Origami Studio – Design Prototyping
Origami eng here:

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

darknoon··on Origami Studio – Design Prototyping
Engineer on Origami here: Yeah, it's rewritten from scratch as a native mac app in ObjC++. Happy to answer any question you have :D
darknoon··on Origami Studio – Design Prototyping
Hey, looking into it. I tried visiting http://origami.design/examples on my phone but it looks fine to me. Try refreshing?
darknoon··on GraphQL Working Draft
Fair enough. In that case, yeah, GraphQL is about the server communication and doesn't specify a particular application architecture. There's usually some data you want saved locally and not persisted to the server, though that's not very common in facebook, since eg preferences are meant to work across devices.
darknoon··on GraphQL Working Draft
Also, keep in mind that most big websites aren't just a single box you can query. A plan for fetching data across >>1000s of boxes works a bit differently than within MySQL or whatever.

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!

darknoon··on GraphQL Working Draft
I think you mean falling back to "FQL," the old SQL-like syntax, since Flux is more of a client architecture thing (paired with GraphQL).

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

← PreviousPage 3 of 4Next →