Not only that, but command line options are generally not secure from other users on the system. Just running `ps -ef` can read command line options from any user. A more secure alternative would be running the program in an interactive mode.
But this is more of a comparison of next-generation fuels. Gasoline is only included in the post to provide a baseline comparison that people can easily understand.
I'm imagining a plane this big and it's awesome. I can already see the Michael Bay film. A little impractical right now though I think we can all agree. I think by the time hydrogen becomes feasible for planes, the landscape will likely be wildly different.
FLIF is not really a format so much as an experiment. There isn't a spec that I can find, nor is there any sort of formal description of the format. Right now, the only available spec is the source code and that leaves a lot of open-ended questions about what to do about inconsistencies in implementations. I hope it develops into something good, but for now it doesn't seem a viable option.
Obviously I have no idea how they've implemented this camera but right off the top I can see several advantages to being able to have multiple sensors firing at one time. The first obvious advantage is HDR photography, where each sensor would use a different setting, then software would combine the images, using different settings for different lighting areas in the picture. Similarly, this same tactic could be used for different focal ranges and depths of field. Personally, I'm just happy to see that someone is trying to rethink what a camera is. Other than being digital, cameras haven't changed much in how they fundamentally work in many years.
At what point does the resolution become good enough for serif fonts I wonder? Unfortunately 1366 x 768 is still quite the norm (118 ppi on a 13.3" screen).
You could try the reverse and float visitors credit. Once they're 5$ in the hole they can't view images anymore until they pay off the balance or something similar. Of course you'd have to find a way to make it so users can't just create a new account after they hit the 5$ limit (possibly by requiring a credit card and deduplicating by that?). Digital Ocean uses a similar model where they automatically bill your credit card once a month for accrued charges.
It is sadly not (my current draw is closer to 300-400 mA at 4.8v). Even if it was though, the current chromecast doesn't have the hardware to support it.
I've had no such issues with speed. My chromecast is generally on by the time I've figured out what I want to watch and buffering is less than 15 seconds to start the video. Seems pretty reasonable to me.
There are plenty of other ways to get that information. Statistics (x number sold * y average casts per user), asking streaming companies (i'm sure netflix and hulu know when you're on a chromecast and could report rough numbers to google), and i'm pretty sure there are other ways that I'm not thinking of.
I doubt it. After seeing how simple the architecture is to run it, I'm sure it's a drop in the proverbial bucket. Pages drives traffic to the site and in order to serve a site from a private repo you have to be a paying customer anyways.
Could be used as an event store. Rather than storing a list of mutable objects as in a normal database, you store the changes themselves as a list of facts. This makes things like replication a lot easier and can be optimized to be much faster than a traditional database.
I would caution that a two-phase commit is not always the best you can do. A two-phase commit is blocking and in event of failure during processing it can cause a deadlock. A three-phase commit offers the same level of guarantee but without blocking.
Linking to an earlier post doesn't really do anything except fragment any conversation across two different posts. I'm sure the original poster won't take it personally that his post didn't make the front page and this one did.
The takeaway is that it is extremely difficult to implement constant time calculations. It might be extended to mean that in order to have constant time crypto, you need to have a set of instructions specifically designed to be constant and predictable time.
Love super simple ideas like this. Is there a way to link directly to a nooot so I don't have to tell my friend to type in a specific phrase? Is there any way to lock a nooot so it can't be edited by other people?