508 karma · joined February 23, 2012
'continuing or enduring without fundamental or marked change'
google gives a similar
'lasting or intended to last or remain unchanged indefinitely.'
Both sites list a bunch of synonyms that are closer to long-lasting and durable, but english is subtle. One can't usually swap in a 'synonym' without changing meaning.
Edit: this is actually to sleep the whole machine I think
I count:
1 Big ass ad 3 "News" items 5 genuine "Search Results" (with no heading or any way to know when the ads and nonsense stops. One of the 5 is a link to the Southwest Airlines Android App 3 "In-Depth Articles" I don't know what this is, i guess long blog posts?
This honestly looks more to me like a domain squatting BS ad page that we hate on ISPs for than a research tool (which is what I used to think of google search as).
I hope they change their name to something that people can take seriously.
The last thing one of these companies would want is a competitor or some kind of unsavory hanger-on diluting their brand with a different message or viagra ads.
I think they could have generated more interest and more money just selling them with more designs and sports team branding (The Surface is already used by the NFL, so some sort of relationship between them and MS already exists).
As for the knobs and sliders, I agree it would look 'cool' to see real LEDs light up for your fader or the active loops on your sequencer or whatever, but the reason actual musicians like physical knobs and sliders is because of the tactile response they provide. Thats why Serato's vynil controllers are still popular with a lot of people (http://serato.com/controlvinyl). With a touch keyboard like the one that the surface has you get the worst of both worlds. The (lack of) flexibilty of a hardware device and the (lack of) tactile response of a touchscreen.
Edit: to clarify, is it safe to say that because cats look mostly alike, they would be easier to recognize consistently? or at least a good place to start?
More about the article:
One of the best parts of touch based interfaces is they can change with context and can be customized/improved/fixed for the cost of changing the software. No need to ship a physical 2.0 for your POS when you want to change the button layout.
Also, with these blades, are you expected to carry around more than one and swap them out based on the activity? Then use the onscreen keyboard when you need to do any text input?
The thing is a computer. It has a USB port. One can attach whatever input devices they want. The only difference about a blade is that this doubles as a screen cover. In the medical and fast food examples he gives, the machines are stationary (and you probably want them to stay that way).
I'm all for dedicated input devices or customized interfaces to make jobs easier, but that's hardly a new idea.
So I clicked through to the MS site for it and found that they won't let me order one. In fact, they're a bit condescending about it:
>Want your own Surface Music Kit? Join the #RemixProject and make a Vine video to show us why you deserve one.
I guess that I am willing to pay is not reason enough to one deserve one.'
Then I got to thinking "what's so innovative about this?"
If anything it's a step backwards, a proprietary connector attaches a keyboard/input device to a single model of (shitty) computer.
What about this is better than an iPad + usb midi controller? More RAM I guess...but then there's the laptop + midi controller option.
----
As for the other uses for this, every other one seems better served by a regular tablet or PC. The Surface is not "no compromises" it's "All compromises".
In my experience, the surface pro sucks as a tablet, it's too heavy and the app selection is terrible, what is there is hacked together and offers few features (see the MLB TV app on win 8 vs iPad for a great example of the quality difference).
It also sucks as a laptop. You can't use it on a couch because they keyboard is not helping to stabilize it, every time you hit a key it wobbles about.
The trackpad is miserable. (Edit: miserable on both the touch and type covers)
Windows does not like high dpi Screens, and does not offer decent scaling ability. In order to have applications look crisp, they need to be tiny, and on an 11" screen with that many pixels tiny is really tiny. There's also no support for multiple scaling settings for screens. Plug in an external monitor and you need to take a trip to the control panel (and log in and out) in order to change the scaling....and it will be applied to BOTH screens.
If you want to use the touchscreen on a table with the kickstand, it tilts and the whole thing moves away from you, again the keyboard does nothing to help stabilize it, and there's no non-slip coating on the kickstand or bottom of the tablet so it just slides away if you push too hard.
RE-EDIT:
removed kvetching
They could have swallowed their pride and used android. I never understood the reasoning behind taking such a huge risk going with MS.
Edit: and of course Samuel L. Jackson.
"reasonable minimum thresholds for acceptability" is a great phrase that I will certainly be stealing.
http://en.wikipedia.org/wiki/Rob_Pike
He has given some really great Go talks which are available on youtube, about an hour each:
Origins of Go Concurrency Style - http://www.youtube.com/watch?v=3DtUzH3zoFo
Lexical Scanning in Go - http://www.youtube.com/watch?v=HxaD_trXwRE
Go Concurrency Patterns (One of my favorites) - http://www.youtube.com/watch?v=f6kdp27TYZs
Absolutely.
I'm not saying throw caution to the wind and poll a remote host constantly and indefinitely, as I said originally, I think it's right to be concerned about resource usage. This is just a baseline for decent software. Be a "good citizen" and all that. (In most cases) If you can make one query for 100 items, rather than 100 queries, or 10 queries, do that. But that's just common sense.
>Excessive power drain is undoubtedly a bug. I absolutely love apps that respect the fact I want to go as long as possible without charging my phone.
Again, I think we are in agreement. Excessive drain is a bug, but my experience is that if you're already following best practices and not doing anything wild, you won't be a battery hog.
The article makes a HUGE list of do's and don'ts
I think it can be a lot shorter:
* just because you can, doesn't mean you should
* learn and follow best practices
* be mindful and conservative in your usage of all resources on the system
> I might often be in a position where I can't charge my phone too. (Carrying a second or third battery is useful, if you've got a phone that has a replaceable battery.)
(gadget aside) Even if your phone doesn't have a replaceable battery, there are a lot of slim, rechargeable battery packs you can buy for around $20, many with short little USB cords that fold up in to them and others where you can use your own cord as well. The nice part is it will still be usable even if you change phones, and can be shared with other devices and people if needed. Some of them will even let you charge them inline with the phone so you're only using one usb port.
What are you doing on your phone/what phone do you have that you need 3 batteries?
And if you're doing something that sucks up battery, you should know about it and act accordingly.
If you're not doing heavy lifting, It's just not something you should have to think about as an app developer, there are so many other areas to focus on to keep users happy.
Apple has a few WWDC sessions that talk about it I think.
Here's what they have to say in their "performance tuning" section:
https://developer.apple.com/library/ios/documentation/iphone...
This is lunacy. Ok, lunacy is a bit strong. But I disagree with this and am throwing a "premature optimization" flag.
Modern phone batteries last plenty long, and the radio being on is nothing compared to the big bright screen.
/edit Given the opportunity to chose, I know I would gladly sacrifice a few minutes per charge battery life for a better user experience, especially since my phone never gets below 20%.
Your users will be better served by you fixing bugs or adding features. Really, unless you're a huge team with a huge budget, there's other stuff to worry about in your app experience before "maximizing battery life" should be a responsibility you want to help the OS/device maker with.(If you're one of the lucky ones who has the time and money to do both, by all means, go nuts.)
Being conservative with resource usage is sound advice. Making battery usage the prime concern for most apps is overkill.
Games and other applications that you know users will have open for extended periods of time, and/or that are already eating up battery should give this issue some thought, everyone else, really, don't worry about it.
I remember seeing this on reddit and thinking that surely it must be staged satire, poking fun at the types (pun intended) of people one sees around Chelsea. Without the context of it being a piece of (really rather compelling) performance art, the photo looks like a person who is trying very hard to be noticed.
Also, Not to be confused with Transporter, which is a hard drive that exposes file access to remote devices, that does a lot of advertising on Apple focused podcasts.
The problem with both technologies is that they're artificially limited and their use is subject to convoluted regulations. In the end, Vettel always wins anyway.
I love F1, but I would love to see a truly forward looking series with active aerodynamics and suspension, and where teams can develop and use their own tires, this kind of "unlimited" racing, on the same amazing circuits and with the same level of drivers would be truly exciting. Driver safety and minimum weight limit regulations, (and of course rules against oil slicks and the like) would be enough to keep the sport sane, but also encourage a more diverse and interesting set of solutions from the teams.
I understand that F1 is not this series, but that doesn't mean I wouldn't love to see the same drivers in some more interesting machines duking it out around Monte Carlo.
I've heard someone suggest that perhaps background sync actually might help battery life in some situations since it is done in batches. this would mean that users are spending less time looking at a power hungry screen that's just showing a loading spinner, assuming that some of this saved time is spent not using the phone at all, there might be a gain.
edit: To expand, although I am unfamiliar with everything that could be/has been done to maximize battery life:
Is it possible that "tweaks" are made in ways that are more relevant to actual usage patterns? (And perhaps ways that sacrifice battery life in the for speed in other areas, in the hopes of maintaining the baseline or improving battery life overall while still improving perceived performance)
What might these kind of changes be?
I'm not trying to be an apologist, genuinely curious about how what sort of optimizations might be made, and trying to make sense of the difference between what Ars is seeing and the anecdotal evidence.
------
(OT) Today I learned that I've been doing this wrong. I always assumed "Tow the line" as in help to keep things moving in the same direction or slavishly and mindlessly do as ordered (or something). I guess I never saw (or noticed) it written down before....thanks!
-----