lost_name

I actually wanted exactly this, because my gigantic smartphone would probably be uncomfortable to run with strapped to my arm.

However, my SO introduced me to the Flipbelt, and that kind of solved all the problems.

I assume if you wait a few weeks, you'll see an announcement for the Steel versions of these.

Lately, it's mostly debugging. I rarely find debugging difficult (tedious at worst), and I like fixing real problems (vs building a new feature or component I don't see the reason behind) so that suits me just fine.

Honestly, I'm probably better at it than building new features anyway.

Re: 2;

Perhaps Apple is thinking that this is the hard part. Nailing down the most difficult areas of self driving cars will both give them the market in China/India or other areas with similar traffic, and also leaving the "easy stuff" for last, which will only need to be supplemental.

Someday I sincerely hope to publish a game. When I read articles like this, though, I begin to realize just how little I understand about working on a project like that. I can't even begin to understand how they make all these systems work together in the same environment.

The Galaxy S4 had something like this, except no one (other than the Samsung apps) implemented the functionality to make use of it.

In the end, all I can remember of it was that you could wave over the top of the screen to change home screens, and see a little light ball would move around on the lock screen when you moved your finger over it.

If you're wondering whether or not to take this with a grain of salt, please note the author has a section of his blog devoted to explaining why javascript is apparently bad.

https://medium.com/javascript-non-grata

I edited it in; my apologies. SECRET was SEKRET, which apparently means "secretion" in German.

Ultimately this doesn't answer the question of why is it named this way.

I had the same question, and without actually cloning the repo I wish I had a better answer.

I found, looking through the tags, that src/React.js was added in 0.14-stable, then I examined the history of React.js to find this commit:

https://github.com/facebook/react/commit/b2ca3349c27b57b1e94...

Additionally, I dug this up:

https://github.com/facebook/react/pull/4814#discussion-diff-...

https://github.com/facebook/react/pull/4814

"I changed it to __SECRET_DOM_DO_NOT_USE_OR_YOU_WILL_BE_FIRED to make our German friends less grossed out. I'm going to do the examples in a separate PR."

I struggle to find the reference, but I'm almost certain that the unveiling of the original iPhone came forward with this intention ("progressively enhanced web sites provide 95% of the functionality we require"), which is why there was no app store or anything until the second release of the iPhone. We were supposed to develop amazing web pages, which could be placed as shortcuts on the home screen and function somewhat like a native app.

Of course, back then, I'm not sure there were any sites that were actually mobile friendly, and developers were more interested in hacking the device to make native apps than using a browser to make crippled apps.

Granted, it's unlikely that they would say anything if they were extorting people as you describe... but from just the other day: https://adblockplus.org/blog/acceptable-ads-explained-moneti...

Discussion (somewhat lacking): https://news.ycombinator.com/item?id=11182174

Is what you're looking to be paranoid about?

https://en.wikipedia.org/wiki/Tempest_(codename)

The first two lines of the article are that you currently don't pay any, and with something that recently passed you'll never have to worry about it.

Well, it might. The FAQ only says this:

https://www.ampproject.org/docs/support/faqs.html#who-will-b...

  By using the AMP format, content producers are making the content in AMP files
  available to be crawled, indexed & displayed (subject to the robots exclusion 
  protocol) and cached by third parties.

https://www.ampproject.org/docs/support/faqs.html#how-do-acc...

  In addition, AMP files can be cached in the cloud in order to reduce the time 
  content takes to get a user’s mobile device. By using the AMP format, content 
  producers are making the content in AMP files available to be cached by third 
  parties. Under this type of framework, publishers continue to control their content, 
  but platforms can easily cache or mirror the content for optimal delivery speed to 
  users. Google has stated that it will provide a cache that can be used by anyone at 
  no cost, and all AMPs will be cached by Google’s cache. Other companies may build 
  their own cache as well.

I imagine that means Google will be caching AMP pages in full, so if your search turns up an AMP page, it will be served from Google's CDN. Presumably, it will be more difficult to determine what is an ad if it's all cached, but maybe ads are an exception to cache -- you can't target a static ad very well.

AMP is just a subset of HTML/JS/CSS, but there is also an AMP CDN and the implication that you agree to allow your content to be cached by third parties.

I think this means that the agreement concerning the AMP CDN says you don't use bad ads, thus discouraging ad blocking.

It really is just another social medium.

We used to have ICQ, AIM, MSN, YIM, and a host of other lesser known methods to chat. This is just one geared toward sending quick pictures. I doubt the privacy part of it is even significant to most users.

NPR did a segment on Instagram that sounds an awful lot like this. See Act One of "Status Update": http://www.thisamericanlife.org/radio-archives/episode/573/s...

From the review:

> I directly analyzed the Surjtech cable using a Type-C breakout board and a multimeter, and it appears that they completely miswired the cable. The GND pin on the Type-A plug is tied to the Vbus pins on the Type-C plug. The Vbus pin on the Type-A plug is tied to GND on the Type-C plug.

Although I haven't read the spec, following the spec is a key part making use of a standard.

I feel like this is a cool hobby project, but a pretty rough/bold idea for a company to form behind... out of curiosity, which is it?

You're correct, of course, and the Schumpeter curve is not something I'd heard of (I'm not sure that's the textbook name, but I'm sure it's the same concept) and is kind of interesting and frustrating at the same time.

Speaking from a strictly business standpoint I understand the motivation behind these things, but from my day to day programming perspective -- where the revenue doesn't come back to me in any way and building the Next Big Feature is really just looking for a spot for it to fit in among the bramble of previous releases -- all I want is for the software to work better. I tend to think of it as just knowing too much, but maybe it's just time to move on.

I once worked as a consultant to help users implement some software. I moved on to the development of that software, knowing the dozens of areas that could be improved to make life easier for the users, and honestly with little effort (it's a web app, I did that before the consultancy stuff). At that point in time, that was my dream -- I wanted to help make people's lives a little bit easier, and the people I helped would be those who used our software.

After around a year or so of implementing questionable features, I attempted to get approval for updates to old, well used features to improve them (stability and convenience focused, really), but was shot down. This wouldn't sell the software, because it worked well enough, and we needed more revenue more than retaining old customers. At that point I understood that after the software is sold the customer will be too ingrained into the product to leave without financial repercussions.

A while later, we got bought out by Big Company, so that strategy apparently worked. BC doesn't give half a shit about anything we ever did, and we piled on the features release after release with little concern about anything else. I tried a couple times after the buyout to get approved for existing product improvements, but always got shot down.

I continue to find it odd how the company can be so profit oriented, and yet so averse to improvements. I suppose I'm just wrong or don't actually understand. Either way, it makes it very hard to care about my work these days.

Well, coffee is certainly in the future of ordering for delivery, but why wouldn't it be? The article only describes a partnership between Starbucks/Postmates and Dunkin' Donuts/Postmates/DoorDash. Postmates and DoorDash provide delivery for things that traditionally aren't delivered (ie, fast food and coffee).

Frankly it's right up their alley to try this.

The article is about optimizing the delivery of the CSS content, not about making it clear or concise or anything else.

So, the point of the example then is to optimize for the content that is delivered directly on the page. Note that the only style used in the page is '.blue' which is the only style left in the header (they additionally specify that you should do this for content above the fold). The javascript will fetch the rest of the style after the page has finished loading.

By loading only the immediately rendered styles, the entire page content finishes loading then the remaining styles are loaded. This is opposed to loading all of the styles, followed by the page content. Of course, when we're talking about a page that is around 1k in size either way it's not particular important.

> On the other hand, how do you embed a browser component in a forward-compatible way?

Android uses a WebView component. If an app wants to display a webpage, it can make use of this to render HTML. I imagine iOS uses something similar.

I believe this component is compiled separately for different versions of Android, and Android will only update to the newest compatible version.

Docs: https://developer.android.com/reference/android/webkit/WebVi...

Store page: https://play.google.com/store/apps/details?id=com.google.and...

Basically. You need to handle all checked exceptions (Exception class), but not unchecked exceptions (RuntimeException class).

> A new grad at Google/FB/Amazon with a lowball offer will have a total comp (salary + bonus + equity) of $130k/yr.

I think these companies are actually too ideal to draw this conclusion from. For everyone Google/Amazon/FB, you also have a Comcast, an Oracle, an HP or Cisco.

You frequently hear about companies like Apple, Google, Facebook, etc trading employees. You don't hear about the typical big company poaching anyone besides executives.

Edit: The above doesn't seem to represent a clear thought. I'm trying to argue that the average big company doesn't pay as well as those three. Similarly, the average startup isn't going to be able to pay massive dividends in four years.

I feel like this is pretty important since the article is talking about the comparison in the first place.

Here's a couple blog posts on the subject, which I think explain it better.

http://www.dustmop.io/blog/2015/04/28/nes-graphics-part-1/

http://www.dustmop.io/blog/2015/06/08/nes-graphics-part-2/

In all fairness, it has that too, along with Pandora, a Grocery Manager app, and some other things.

http://www.cnet.com/products/samsung-rf4289hars-refrigerator...

It sounds more like they're integrating their stores with their online site. You scan the register you're at when paying for something, and then you can pay with the app -- you probably need your credit card info saved to your Walmart.com profile or something as well.

Static analysis doesn't have to involve typing, but it is only about a program reviewing your code for potential issues. Whether or not it is interpreted isn't important.