alexkcd

8 ms·

31.
by alexkcd 10y ago
The solution is actually quite simple. [1] 1. Use TAI-UT1 (International Atomic Time, monotonic, no leap seconds, with zero on 1958 Jan 1) for time keeping 2. Define conversion functions that map TAI-UT1 to/from UTC/UT1/etc U
32.
by alexkcd 10y ago
The graphics stack in Android is badly designed. It is that way for historical reasons. Android used to do CPU-based blitting -- similar to other mobile platforms at the time: Symbian OS and Windows Pocket PC. Then the first iPhone launched
33.
by alexkcd 11y ago
These stations don't get used much because Tesla sells a battery with every car they make. If the cars came without the battery, there would be a lot of demand, but would also require the infrastructure to be in place to support long r
34.
by alexkcd 12y ago
Objective-C is a good example of successfully migrating the language forward. Breaking changes were introduced slowly. Library APIs are marked as deprecated several releases prior to removal. The compiler warns you of their use. Automatic r
35.
by alexkcd 12y ago
Personally, I prefer languages that make small incremental breaking changes, as it prevents cruft from accumulating over time. The important thing is to provide a migration path (e.g., begin by marking something as deprecated). Then provide
36.
by alexkcd 12y ago
Neat! That said, std::sort is a template function, so you can pull the source (e.g., take the one from libc++) and change the comparator to return an int. You will still get all the benefits of inlining and optimizations from lack of type e
37.
by alexkcd 13y ago
You left out the previous paragraph, which explains why Carmack feels the need to partner with a Titan, rather than go at it alone. Not sure that I agree this move was necessary at this point in time, but I definitely see his fear of the po
38.
by alexkcd 13y ago
Poor artists outsource.
39.
by alexkcd 13y ago
I'm not saying you shouldn't use arrays altogether, just that you shouldn't use them when you have uniqueness & no order. For example, consider the posts.comments.users relationship. Here "posts" is the primary document (and let's say a
40.
by alexkcd 13y ago
That's a fair point, but using arrays only where ordering matters adds nice semantics that can be used by a general-purpose client. Using a map for related documents makes it explicit that document entries are unique and unordered (it's imp
41.
by alexkcd 13y ago
I agree with you. "OP" was referring to your suggestion. I edited my pervious comment to clarify.
42.
by alexkcd 13y ago
The related documents are indexed by id from the primary document, so ordering doesn't matter, and it makes sense to use a format suggested by calebio, as it's both more efficient and terse. However, the primary document and other nested en
43.
by alexkcd 13y ago
Work on supporting some provisional C++1y features is already underway: http://clang.llvm.org/cxx_status.html
44.
by alexkcd 14y ago
Well, at least they open sourced the parts of the code they used ;)
45.
by alexkcd 14y ago
I recommend checking out Qt Creator. It's cross platform, has code completion, live syntax checking, supports regular Makefiles, C++11, and much more. Plus, if you're looking to build a cross platform GUI app, Qt is a great toolkit, and Qt
46.
Backend developer? Help Luma (YC W12) scale its HD video sharing service
1 points by alexkcd 14y ago
47.
by alexkcd 14y ago
Luma applies stabilization on playback. We keep all the pixels we get from the camera, even when you upload to our cloud service. As we improve our algorithms your existing videos will continue to improve with time. There's much more that w
48.
by alexkcd 14y ago
Luma's cinematic stabilization performs much better than Nokia's optical stabilizer in daylight. As sensors get better (more light sensitive, higher resolution), the advantages of optical stabilizers will diminish even further and eventuall
49.
by alexkcd 14y ago
(Cofounder here.) Ours is better: http://luma.io/v/CJC You can think of AVFoundation's as dampening handshake. We retarget the motion to be along the smoothest path possible. So we can often completely eliminate handshake. Luma supports b
50.
by alexkcd 14y ago
Here you go: http://luma.io/v/CIt (thanks to cosbynator for letting me make this)
51.
by alexkcd 14y ago
We developed this in-house. We use additional sensor data and fairly advanced optimization algorithms to produce these videos (all done in real-time on your mobile phone!) Due to the lack of sensor data, and subpar camera models, you won't
52.
by alexkcd 14y ago
It's on our todo list :)
53.
by alexkcd 14y ago
(Cofounder here.) That's our motion retargeting algorithm at work. It'll fit the smoothest motion to your recording. In this case a constant panning motion does the trick. You can get perfectly stationary, motorized-tripod-like panning shot
54.
Luma updates its video camera app for iOS, adding cinematic image stabilization(thenextweb.com)
70 points by alexkcd 14y ago|31 comments
55.
by alexkcd 14y ago
I've dropped all iPhones I've ever owned. Never shattered glass yet, but it's only a matter of time.
56.
by alexkcd 14y ago
Doesn't list your email in your profile. Ping me at alex (at) luma.io
57.
by alexkcd 14y ago
Yes, if 1) VP9/Daala are significantly better, and 2) they don't come out much later than h265. VP8 failed on both accounts compared to h264. To see why, read: http://x264dev.multimedia.cx/archives/377 (not an unbiased source admittedly,
58.
by alexkcd 14y ago
Fixed. Thanks!
59.
by alexkcd 14y ago
Sadly, the best compression techniques are fairly obvious and have been patented. The economics of this space have always favored better codecs over licensing concerns. Savings in bandwidth often negate the cost benefits of a free codec. Hi
60.
by alexkcd 14y ago
We remove handshake by computing optimally smooth camera paths. Some example videos shot on a handheld iPhone using our app: http://luma.io/v/Brl http://luma.io/v/BtN http://luma.io/v/Brm More info here: http://luma.io

More ›