I'm reading... but it is like reading a patch file for a language I don't understand, when I don't have the file that is being patched.
     

That might as well be:
     

It looks like they are trying to say that, in order to bulk collect data, they must have a specific search they are running that involves a specific telephone line. See SEC 201.

Can someone define "tangible things" as in "SEC. 103. Prohibition on bulk collection of tangible things" or "“(i) Emergency authority for production of tangible things."

Out of four garden lamps I put in about five years ago, only one functions and that very poorly.

The LED lights themselves may still work, but the solar collectors on top get clouded or dirty (or both) and stop providing power.

I would come here more often if orasio wrote the summaries.

The problem with the summary is that it assumes the reader is already familiar with the device. Your summary does not suffer from that problem. For instance "prototype eight-terminal device consisting of a magnetic matrix with micro-antennas to excite and detect the spin waves." WHAT spin waves? What is a terminal in this context and why is the a key thing in the summary? The summary already presupposes too much, even for a technical news site.

On the flip side, it would be nice if you didn't also insult the person who asked for clarification. The summary is indeed confusing.

+1 for insightful explanation.
-1 for being an asshat about it.

The recommended break point is as it is with any language - whatever is most readable.

Sometimes that might be the return value being on the next line.

Sometimes it might be each parameter on it's own line.

I myself prefer to either have the whole thing on one line, or everything broken out per line if that will not fit. But I'll admit I let some longer methods sometimes wrap to two lines on the display (even though it's really one long line).

The second is for the return value, yes.

Although you can absolutely name the return values something different, I just had in mind some optional transformative thing where you could use it or not and treat the data tuple the same way.

Before this new version of Firefox, the DRM was delivered via Silverlight. Either way, you are running a closed-source binary blob that handles DRM.

DRM = encryption + key obfuscation.

If DRM was merely encryption that would be great. Then we could save the encrypted streams to our hard disk, then play them while on vacation. Or we could copy those encrypted streams for time shifting. We could decrypt them, then re-encode them into another format for playing on another device. Or take fair-use protected clips from them.

The goal of DRM is to prevent the the end-user from doing the things listed above. But encryption alone isn't enough to do that. You need a way to give the key to the user, but obfuscate the key so that they can only use it limited circumstances. It's infuriating to the user.

I've done Objective-C since before the release of the iOS App Store, and Swift almost full time since Apple released it last year...

Some of the things you mention beginners do not have to use (generics, and struts for example). To keep things simple to start with, they could just use classes instead.

I will agree that optionals might be a bit rough on the beginner - but perhaps not as starting from nothing, the concept of a bucket that holds a value instead of just using the value directly, would not be so foreign...

You also mention different ways to specify params, and shortcuts - but I see those as a major plus. You can just pick a level of detail that makes sense to you and work with that, until you feel comfortable with reducing further the syntax you use.

I think the function syntax is one of the cleanest and easiest styles to understand... I believe a few other languages have this form also, but in swift you just say something like "a function named takes in these params, and outputs those params" So it looks like:

func myFunc (a:String, b:Int) -> (a:String, b:Int)

it's just so balanced that you can have any number of things in or out.

There are a few things I think make Objective-C less approachable.

The separate header files, and the heavy modern use of private categories to define most internal properties confuse people as to where they need to define things.

Simply more verbose syntax all over. I like verbosity myself, I love named parameters... you get that with Swift though with a lot fewer characters typing.

Part of that extra syntax in ObjC is the shorthand to make arrays like @[] and @(value) to make NSNumbers... but in Swift Integer is treated the same as String, both are first class objects that you can do things with so it's more consistent. That in particular is I think a large benefit for newcomers.

Wrapping it in foil means it won't function as anything.

But it also means the work application will not record any downtime for the app running.

If you are "on call" then you are technically working, so that phone needs to be 100% functional and they have the right to track it.

True enough (I totally agree the company as the right to track their own equipment) but if a boss said something creepy like "I can see how fast you are driving" in the bag it would go when I was driving anywhere and I'd just blame bad cell reception on the dropoff... I could pull it out every 15 min or so to see if there were any messages. But it would technically be dereliction of being on-duty...

It is important to note, however, that putting the phone in the Faraday bag emulated loss of signal, instead of loss of power,

I was mulling that over after I posted, but after some thought I think that ends up being OK also as it's easy enough to claim your car blocks cellular signals really well or just were in a bad area... at any rate the app wouldn't show it had been shut down which I think would be the main trigger they would get onto you about.

That's a great point but it does seem like a company should have the right to enable GPS tracking for company assets. Perhaps a good compromise would be that you could indicate when you were off-work to avoid tracking, but if required the device could be signaled to turn back on tracking.

I personally would probably get one of those signal shielding bags and drop it in there when I wasn't to be on-call. Then you could carry it with you even. Then it also appears just as if it lost power for a while, so it would be hard to get in trouble over it...

Reading is one thing, browsing quite another...

Also worth considering - the Pebble display is 30x50mm on the old Pebble, just 20.1x23.44mm on the Time.

The Apple Watch 38mm has a 21.2x26.5mm display, the 42mm version has 2.3x30.8mm...

So the old Pebble is substantially larger than any of the new models, and somewhat easier to read as a result.

I have a Pebble Time on order, it will be interesting to compare... but I just can't see browsing on any of them at all useful beyond something like an RSS feed worth of info.

and frankly you can always bring the watch closer to your face.

You have an unpleasant surprise in store for you as you age. Minimum close focus gets further back, to where you really cannot just bring the tiny screen closer...

Go into an Apple Store, reading the web on that display is just not practical.

Before getting alarmed about numbers with no context, take a look at Charity Navigator. Compare The Wikimedia foundation with your favorite charity and see how they look.

Charity navigator rates the Wikimedia foundation as 4/4 stars. The system they use is quite fascinating: the site is generates the numbers mathematically from non-profit tax filings. What the site doesn't tell you is if the charity is actually doing good work. If a charity's goal is to feed babies to demons, and they do it efficiently, they will get good marks.

I used to browse the web on a Palm Treo with almost the same number of pixels as the Apple Watch has.

  I didn't have the Treo but I seem to remember the screen being a lot larger, and it also had a keyboard too...