Recurring revenue - launch the satellite constellation once and generate monthly subscription revenue potentially running into billions of dollars a month.
Manufacturing limitations & launch pad availability, once they are resolved (along with launcher reuse) will lead to a point where there is not enough demand to fill the launch roster. This internal demand will help them fill it up.
Not sure if your location is covered by Google's Mapmaker.
For my location, I usually provide updates/corrections via Mapmaker; it goes through a community review process and shows up in the main Maps within a couple of months (at most).
Some unintended consequences of playing the video backwards - when I go in reverse from slide 9 (Fan) to slide 8 (Thermal Core), the arrows indicating air flow and thermal flow are animated in reverse :-)
Says Ellsworth: "Gabe was completely behind it... I talked to Gabe, and he talked to the lawyers, and he's like, 'It's theirs, make it happen,' because he could see we were passionate about it."
Not sure what you mean by "rarely beneficial to compress to one single file".
But in multiple situations I have seen significant web load performance improvements when the number of discrete files being loaded is reduced - merge all JS into one file, all CSS into another and sprite images. This is due to HTTP 2-connection rule.
You are the founder of evolup.com. Let us say your product/service becomes a huge success. Seeing your success, existing social games developers want to do the same.
Which action from those existing developers would be best for users?
a) Do not copy your product/service. Continue doing things the old way.
b) Make something different, not because it's better, but only for being different's sake. Forces users to adapt to something new instead of using what they're already used to.
c) Embrace the innovation. Put all that's good about your product/service in their offering. Then iterate through it and improve upon it. Now users have the best of both worlds, they have the brand new innovation, in a format they're used to. And taking benefit from next iterations improved from it.
So where does your preferred option (c) leave you in this scenario? Would you whole-heartedly welcome another player "embracing your innovation"?
If that happens to me, I'll lose all motivation to innovate any further. What is the point after all?
As long as CSS opacity is not explicitly specified for any SVG element, I have found FF is not very slower than Chrome/Safari. But the moment opacity attribute is added even for a single element (even if the value is specified as 1), FF really slows down.
So I tend not to use opacity in my JS rendered SVG especially if there are any animations.
"I actually agree with Google. On that note, I think their search algorithms have become essential for the industry. As much as I've tried switching to Bing or Yahoo, I keep coming back to Google's engine.
Those algorithms should be de facto standards and licensed under FRAND"
"The letter to municipal agencies will cite a 2007 policy that mandates that city funds only be used to purchase EPEAT-certified desktops, laptops and monitors..."
Later on: "...the EPEAT registry does not yet include certifications for smartphones or tablets..."
Finally it also says: "...the city spent $45,579 on Apple desktops, laptops and iPads (the last of which are not certifiable under EPEAT and would not be barred by the city’s policy.)"
Manufacturing limitations & launch pad availability, once they are resolved (along with launcher reuse) will lead to a point where there is not enough demand to fill the launch roster. This internal demand will help them fill it up.