For those who dont know: The iTunes EULA contains this sentence:
You also agree that you will not use these products for any purposes prohibited by United States law, including, without limitation, the development, design, manufacture or production of nuclear, missiles, or chemical or biological weapons.
Apple has a whole gallery promoting the high-end photography and videography shot on iPhones (https://www.apple.com/iphone/world-gallery/). iPhone cameras may not pack the highest number of pixels or the latest gimmicky features, but their optics and image processing are first-rate. See also (http://nofilmschool.com/2014/05/new-ad-for-bentley-shot-on-iphone-5s).
This is a desktop application (Electron framework) that I made, inspired by this post by Seena.
It's open-source and you can get it on GitHub.
So what do you think?
Edit: Holy shit this got more karma than Seena's post in like 4 hours. I know the sub has grown since then but wow... Thanks everyone for the kind words.
u/nnkd hey dude. It seems like you haven't been on reddit lately but if you ever find this, i want you to know that you're awesome, and you're the one that inspired me make this thing. Keep it up!
2nd edit: So i woke up this morning and this got to the top of the Golden Five. I have no words.
3rd edit: OK now its going too far. This thing literally just boosted my career. And i'm still a high school student. I need to take a small break. Enjoy the day one hotfix.
According to Apple's website:
>Working with iPhone, Apple Watch continually checks against the definitive global time standard with the same precision found in GPS satellites.
So it seems the Watch gets its time from the iPhone.
You can just add the <code>--author=&lt;author&gt;</code> flag when committing for anyone curios as to how to do this. There are legitimate uses for that flag, I have used it for committing code my colleague wrote as an example.
No kidding. The number of subdirs isn't the only problem, but it's such an obviously wrong approach that they shouldn't need Github to tell them it's a scalability issue.
Pretty much every filesystem in existence scales poorly as the number of entries in a single directory grows. Some handle it better than others, of course, but it's still a terrible practice to stuff everything into one directory and assume you won't have any problems.
And it's such an easy thing to fix - hash the filename or subdirectory name, take the first 2 hex characters, and use that as an intermediate folder name. Now you have at most 256 top-level subdirectories, and with 16k entries each of those has ~64 children.
If you look at .git/objects/ in any Git repo, you'll see this is exactly what Git does internally.
Seconded. For me the two most useful pieces of literature on the subject of version control via git were:
The online git book, to learn the "language" and how it works
The common git workflows (originally the Git Flow article), to learn how to effectively use it
It's very unlikely for you to learn, for instance, that a branch is nothing but a pointer to a commit, and be able to exploit that aspect of git, if you only follow GUI tutorials.
Haha. Super useful, but easy to get into sticky situations. If you want to be a power user, I highly suggest learning a bit of how git works underneath. Once you know things like branches are just labeled commits, cloning repos literally clones everything over, pulling branches pulls on what's called a remote branch before it's merged with the target branch, etc. you'll be able to use git a lot better and understand what's going on in all those sticky situations.
This book is good: https://git-scm.com/book/en/v2
This is why presubmit scripts are great.
> Error: Messages.strings updated but no corresponding diff found for Plurals.strings
and if Person Who's Not Here Anymore wrote it, just blame the script to find the commit that added the error and read the description to understand why.
As a bonus you can use lolcommits to take a lolcat-style photo from your webcam with every commit.
It's down, but of course the System Status page says everything is a-okay!
They really should take down this page if they're not going to use it when it matters.
EDIT: Yes, hours later they decided to update it... Usually they wait until the downtime is over to put a notice, or never put one at all. This downtime seems to be long enough that they updated it mid-downtime.
The iPhone 6 is 6.9 mm thick. Folding it 42 times gives you a thickness of 3x10^10 m, which is more than 76 times the Earth-moon distance.
Ninja-edit fun fact: This is the first time I have ever used a superscript properly on Reddit. Usually I just make ^dumb ^^jokes ^^^like ^^^^this!
To put it in perspective, the original iPad sold just 300,000 in its first day in the US. (https://www.apple.com/pr/library/2010/04/05Apple-Sells-Over-300-000-iPads-First-Day.html)
The original iPhone sold 270,000 in its first 30 hours in the US(http://www.engadget.com/2007/07/25/apple-sold-270-000-iphones-in-the-first-30-hours/)
If this article is accurate, Apple Watch may be Apple's most successful product category launch.
It's actually both. See page 9 of this white paper: https://www.apple.com/privacy/docs/iOS_Security_Guide_Oct_2014.pdf
Full disk encryption is supported by the dedicated encryption engine in the DMA path. Other cryptographic tasks may be accelerated by the main processor.
I haven't used the GUI recently buy my impression was that it abstracts away some of the steps which makes it more difficult to understand what's happening. Picking up the CLI should be manageable even for junior engineers and it pays off in the long run.
A more balanced discussion about it - https://git-scm.com/book/en/v2/Appendix-A%3A-Git-in-Other-Environments-Graphical-Interfaces
And another, more one-sided, opinion - https://news.ycombinator.com/item?id=25791306
ITT a lot of people who don't understand how security works.
The communication between phones and cell towers is encrypted. The data on the phones themselves is encrypted as well. To get at that data, you have to have a key to the data. Generally the key is device specific and is only unlocked with your passcode. In iOS 7 and earlier, Apple kept a key that could be used to decrypt that data on all iPhones. In iOS 8, Apple simply doesn't have such a key. Snowden's information was always public knowledge and is now outdated.
https://www.apple.com/privacy/docs/iOS_Security_Guide_Oct_2014.pdf
Hah, that is a great story.
For whatever reason it makes me think of:
> g. .. You also agree that you will not use these products for any purposes prohibited by United States law, including, without limitation, the development, design, manufacture or production of nuclear, missiles, or chemical or biological weapons.
It probably isn't Explorer itself consuming the memory. It probably is a misbehaving shell extension that is leaking memory. Unfortunately some applications "helpfully" install shell extensions without informing the user and it is not uncommon for some of those shell extensions are buggy or written improperly causing all kinds of problems.
I suggest running ShellExView or similar utility and taking a look at what shell extensions you have installed, particularly those that are not published by Microsoft.
If enough of us submit complaints, they will fix this.
Let's all submit complaints to:
https://www.apple.com/feedback/macosx.html
I'm putting mine under:
Efficiency/Workflow
Applications/utilities
Feedback: https://www.apple.com/feedback/
Bug reports: https://bugreport.apple.com/
Make sure bugs actually get submitted to the bug reporter. On this sub, I've seen people tell people to submit bugs to the Feedback link. The bug reporter actually gets to Apple's development team, and they can actually respond and follow up about bugs there.
Did they not read the terms and conditions?!?
> You agree not to violate, circumvent, reverse-engineer, decompile, disassemble, or otherwise tamper with any of the security technology related to such Usage Rules for any reason
https://www.apple.com/legal/internet-services/itunes/appstore/jm/terms.html
Apple reserves the right to “use [customer] personal information for internal purposes such as auditing, data analysis, and research to improve Apple’s products, services, and customer communications” across its product line. It permits itself to share this information with “its affiliates” as well (whoever they are).
Source: https://www.apple.com/legal/privacy/en-ww/
EDIT: Things get more complicated further into the terms of use, according to reddittechnica - http://www.reddit.com/r/privacy/comments/2ys6jx/apple_admits_siri_voice_data_is_being_shared_with/cpcwuic
To OP:
Apple made an in-ear headphone with balanced armature drivers. It's not bad. very very balanced. In fact, if you check out the measurements, it's damn accurate.
http://www.innerfidelity.com/images/AppleInEar2013.pdf
The measurements are almost perfect, but there some harmonic distortion in the 2-7Khz range (spike on the 5th graph) that's over 1% which means that these are better for softer listening. If you listen to them too loud, you'll start to hear this distortion. Still... they are VERY good from a technical standpoint.
https://www.apple.com/ipod/in-ear-headphones/ << link of the product, for anyone else curious.
It's also related to how git was developed. First as a collection of command-line tools written in Perl, then slowly one at a time rewritten in a growing C code base. They did a fantastic job of establishing a set of simple primitives, terminology, and file structures early in the project that made this possible. I think this is at least partially attributable to Linus being unusually familiar with the idea of "don't break the user mode API" that he is so serious about when it comes to the kernel.. he applied the same principles to separate git plumbing and porcelain, which allowed vastly different tools to be used during different stages of the development process.
edit: core -> plumbing
I'm currently on an airplane, using mosh to connect to several servers back on the ground.
I originally started the sessions while on my tethered mobile phone connection and as soon as I connected to the in-flight WiFi the sessions reconnected seamlessly. Even though the links have more than 800 ms (!) of latency, the sessions feel responsive due to the local echo. Plus, if I send a ^C
, it actually works :D
I've been using this now for around a year exclusively. It's one of the best pieces of software I've had the pleasure of using.
The research paper and video found here are fascinating!
The only caveat is that there is no scrollback like a typical xterm. You will need to use a tmux session (or similar) on the server to get scrollback. I haven't found this to be too much of a burden.
For $1,299 you can get the 13 inch Macbook Pro instead of the Macbook.
I am literally begging you right now to not be coaxed in by the pretty new "Macbook", and spend your money on the better computer instead.
The terms and conditions for iTunes include this:
> You also agree that you will not use these products for any purposes prohibited by United States law, including, without limitation, the development, design, manufacture or production of nuclear, missiles, or chemical or biological weapons.
I really want to know how iTunes can be used in the production of biological weapons.
I've been using wireless for about 8 years now. My current connection speed on wireless is 0.5-1Mbps slower download than my wired connection. My ping is around 30-40 on games like Path of exile and Diablo 3 and ping is 12 on speedtest.net. I very rarely have any drops in my wireless connection. I live in a house. My access point is a Mac Airport Express dual band N and my wireless adapter is TP Link TL-WDN4800
Yeah... there is a really good breakdown on this page.
https://www.apple.com/environment/reports/docs/AppleTV_Product_Environmental_Report_2012.pdf
Here is a good example... Streaming a movie uses about 2W (Not to include the juice used by your TV, or modem too) That means (@ 14 cents per kW/h) you could have the AppleTV playing a movie 24hrs a day, 7 days a week... at a cost of about $2.50 per year.
Or, lets say your ATV was on for a year, but never used (not a great example, but just for shits and giggles)... it would be sleeping and uses .20 W - So, a full year of the ATV sleeping, would cost about a Quarter... probably just enough to light that pulsing LED.
> then I'm left hanging for weeks or months before a decision is made whether or not to move forward
This is completely broken.
In terms of the git part of it, what you can do is create your feature branch, work on it, and occasionally rebase it on the master to bring it back up to speed with the rest of the codebase.
Author here. Probably the version you'll get on Amazon is a snapshot of the print version, which at this point is 4 years old and has a number of errors. The version you can get at https://git-scm.com/book incorporates innumerable contributions from the community, and so is more up-to-date and correct, so while it won't help my Amazon ranking in tech authors, I'd recommend getting it from the Git website.
For what it's worth.
Early 2011 15" here. 2 GHz i7 with the Radeon 6490M discrete chip.
Was fine for just over 2 years. Then froze one day, required a restart and distorted screen. Wouldn't reach password screen, either on laptop screen or external display.
Went to Apple Store. I was about a week outside of the EU 2 year warranty. Genius mentioned this, but then stated "but we don't care - we will fix this free of charge". New logic board fitted and, touch wood, all OK for now.
My store genius/manager made the call that many think Cupertino should be making. Awful for those who didn't get such good service. I was a lucky one.
They started using BitKeeper instead of patches for scm (source code management). So before 2002 there wasn't any way to really track who was working on what. Since then they have moved over to Git which was developed by Linus Torvalds (original author of Linux).
I think git is what you are looking for and it's never a bad time to learn git. Here is the book about git, how it works and how you use it.
Github is a git host. You can think of Github as the cloud storage of you git repository. Like Dropbox is cloud storage for "regular" files". So Github would (essentially) be to git repositories what Dropbox is to regular files.
Of course Github has some more functionality but it's not really something you "learn" as you would git itself.
The official Apple Widget Browser hasn't been updated in forever. It still uses the pre-Lion scrollbars and kinda fits awkwardly with the newer website layout. So yes, it's safe to say Apple has pretty much forgotten they exist.
Neither.
I use fish.
It has everything a shell should have. Automatically suggests command from history, color syntax, everything you expect from something made later than the 90's.
If you decide to give it a try (Please, do), you're free to use my config.fish file!
Apple has done a lot to improve working conditions for factory workers. They can't easily fix a foreign culture, however. They're also very transparent about their efforts to improve working conditions as well as their efforts to reduce their reliance on conflict minerals. As for paying their taxes, are you suggesting that Apple pay more taxes than they owe by law?
FWIW, I think removing anything containing the confederate flag from the App Store is moronic.
From Wikipedia, iMessage does but others have a mixed history of saying they're encrypted when they're not.
iOS Security p30-32 (PDF Warning)
GitHub hosts software. Specifically the source code. Source code is simply a compilation of instructions. You can download the source code and build it. Assuming the developer hasn't already published a prebuilt release. Collectively, this is called a repository (repo).
To download the source code, you typically use CLI software git
. You clone
the repo to your system and then follow the "build" instructions included in the relevant document file. This may involve setting up what's called "dependencies" that the software relies on to be built. You can also download the source directly from the website in a zip, but this is generally not advisable. Using git
you have file revisions built in. An unzip and overwrite eliminates that. You can always pull
the latest changes without ever having to go to GitHubs site.
It can feel absolutely overwhelming at first. A lot of people are deterred by GitHub and git in general. There's a whole lot more to this than what I've said here. If you interested and do want to learn, check these out:
That is a possible solution and what you're proposing is very similar to Git alternates, which exists today. We didn't use alternates because it doesn't solve the "many files" problem for checkout and status. We needed a complete solution to huge repos.
Having the full repo on my local machine is 90% more content than our average developer in Windows needs. That said, we did prototype an alternates solution where we put the full repo on a local network share, and ran into several performance.
Alternates were designed for a shared local copy. Putting the alternate on a file share behaved poorly as git would often pull the whole packfile across the wire to do simple operations. From what we saw, random access to packfiles pulled the entire packfile off the share and to a temporary location. We tried using all loose objects and ran into different perf issues with share maintenance and millions of loose objects cause other performance issues.
Shared alternate management was also difficult, when do we GC or repack, keeping up with fetching on the alternate is not inherently client driven.
Doesn’t work if the user lacks access to the local network share and many Windows developers work remotely. We would have to make the alternate internet facing and then have to solve the auth management problem. We could have built a Git alternates server into Team Services, but the other issues made GVFS a better choice.
Alternate http is not supported in smart git, so we would have to plumb that if we wanted alternates on the service.
A device 9mm thin like the new surface pro isn't gonna happen because of the keyboard.
Also, the picture of the magsafe connect you linked is incorrect. That's the old connector. New one: pic
You didn't point out that there's a lot of "belly" in the Mac, and the size of the ports isn't the limiting factor in its thinness.
I believe with the current ports, decent keyboard etc the thinnest they could go is around 12-13mm. Instead of having a round belly, it would just be flat, like the rMBP. A thin slab underneath, while still having a wedge shape towards the front.
>You could argue that git should, by default, have some sort of a PR protocol that you could utilize.
It does. It's called "email".
https://git-scm.com/docs/git-request-pull https://git-scm.com/docs/git-send-email
Not the same I guess but it is functional
Apple has already been putting a lot of effort into iOS security, it's just not been widely publicised. Here's their PDF that goes into detail about the hardware and software security features in iOS devices. It's all very impressive considering they don't even advertise security as a selling point. They just really want to make their shit secure.
iMessage for example uses end-to-end encryption. Apple cannot decrypt your iMessages and they are wiped from their servers 10 minutes after they're delivered. This is the way to go, because then if LE comes to them asking for data they simply don't have that data to hand over.
> Are you supposed to just look at bug reports and try to come up with a solution
Yes, that is one approach. I would advise you to debug and fix something you are able to actually reproduce.
Another approach is to reach out to the project's preferred community (irc, mailing lists, whatever) and ask if anyone would be willing to mentor you through a new project. This will probably be something trivial, but it will get you up to speed. This doesn't always work, but can sometimes turn up good stuff to hack on.
> Is there a beginners guide to Git and open source projects out there that could help me get started?
I think the freely available git book is pretty good. The thing with git (and cvs, svn, mercurial, etc...) is that using it to collaborate with other people is much different than learning the basic mechanics of how to create a commit, push/pull, etc... One of the best things you can do to learn git is to simply start using it in a collaborative manner and pick up the parts you don't know as you go. You'll be a git pro in no time.
Guys guys. Let me let you in on a little secret... Git is open source. No hear me out. You can turn any linux computer into a git server. And push your local hithub or gitlab files to your own server. It's not hard.
https://git-scm.com/book/en/v2/Git-on-the-Server-Setting-Up-the-Server
Want to host a readme? Instead of using markdown Install apache and host an html file.
It's old tech but it checks out.
Seriously - look at that board layout. Generally, no one ever looks at these things but they made it work (presumably well) and it looks good.
A macbook pro as another example
I don't even own any apple products - I just appreciate the extra detail work.
Too be fair, you are comparing two year old device / technology to a new device. Also the Iphone 5 has a Battery Replacement Program that she could use/Need to improve the Battery Life. https://www.apple.com/support/iphone5-battery/
Fish is the "Friendliy Interactive SHell. The idea is that it's a shell with good defaults that helps you with a few smart features - autocompletion and suggestion (which also draws from command history), syntax highlighting (especially marking a command if it doesn't exist, but this also ties in to the completion system). It's also not bound to POSIX or other standards so it is free to change the scripting language in a few ways (there's no "$@" or "$*", it's "$argv", word-splitting is much saner than bash)
Basically, bash is the old dinosaur, not actually bad, but lacking in a few features (not as many as people think) and it needs configuration to be usable.
Zsh.... is rather powerful, but bound to POSIX and when I last tried it my zshrc was even larger than my bashrc before I considered it usable (e.g. disabling autocorrection).
The iPod Nano is the only iPod that has ever had a built in FM radio, and they still have this in the current generation Nano with the abilty to pause, play, and rewind up to 15 minutes*
*^must ^listen ^to ^station ^for ^15 ^minutes ^to ^be ^able ^to ^use ^this ^feature.
Holy shit. Does anybody have the numbers for other opening days?
Edit: iPad: 300,000 (first day) iPhone: 700,000 (weekend, 3 days)
https://www.apple.com/pr/library/2010/04/05Apple-Sells-Over-300-000-iPads-First-Day.html
http://techcrunch.com/2007/07/04/iphone-weekend-one-700000-sold-200million-profit-for-apple/
Well it isn't to make it seem like luxury product. It is to protect their trademark; i.e. A bandaid. When you start referring to a brand name as the object, it loses the ability for it to be a specific recognizable name that sets that product apart. Apple doesn't want iPhone to become a generic name for smartphone. If you don't protect your trademark, you lose it. Trademarks are everything.
Edit: https://www.apple.com/legal/intellectual-property/trademark/appletmlist.html
It comes down to security. When you send any iMessage, be it a wink, an LOL, or a top-secret order, it's very securely encrypted. The iMessage servers maintain the public keys for all registered devices, and send these to anybody who starts to send a message. The first time you type in a phone number, you know how it turns from green to blue? That's your phone receiving the public key for that phone number. The private key, used to decrypt the messages, however, is stored only on the receiving device. The only way a web-based session of iMessage would work is if it weren't encrypted at all, or if Apple were storing an additional private key for you, which defeats the entire purpose.
Your messages aren't actually synced between your iPhone and Mac, but are actually separately encrypted by the sending device and sent to each of your receiving devices, to be decrypted by them. If you're on a group chat with three other people and each one has two devices set up with iMessage, your phone will actually send each message six times. (For photos, the photo is encrypted once with a newly-generated key and uploaded to a randomly-generated address in the cloud, and your phone then sends the address and new key for that photo in an encrypted message to each recipient.)
EDIT: If anybody is interested in the really juicy technical details, Apple has an iOS Security white paper. Page 33 explains exactly how iMessage works. The paranoia-level security of iCloud Keychain (page 38) is also fun reading.
Short answer: No.
Long answer: A lot of misinformation in this thread. MacBook batteries are Lithium-ion. One of the key advantages of Lithium-ion has over other other technologies is that the cells require almost no maintenance or special care as long as they have the proper driving circuitry (and if if Apple isn't doing battery-management right, I'll eat my hat). If you have any other battery-related questions for Apple products, you should check out this page.
Lithium-ion cells have no memory effect, meaning that they won't lose any capacity if they are fully recharged after only a little discharge. Also, unlike many other deep-cycle rechargeable batteries, they don't need to be fully discharged and recharged periodically.
In fact, the main factor limiting the lifespan of Lithium-ion batteries is the total number of effective charge/discharge cycles (IIRC, most are rated for 600 full discharges/recharges). So keeping your MacBook plugged in all the time, and discharging the battery less frequently, will make the battery last longer!
Edit: accidentally a clause
<code>git daemon</code> is what you want, though in classic git fashion it's a bit less fire-and-forget than hg
tools. You can setup an alias/defaults to ease usage.
Aliases will do you:
> git config --global alias.yes 'commit -a'
> git config --global alias.no checkout
> git config --global alias.pls 'pull --rebase'
Now you can use git status
per normal, but you can also git yes
to save your changes, git no <file>
to revert changes, and git pls
to get the latest changes from the server.
Some things I think are of note:
I think the worst issue here isn't the idea of microservices (not that it helped matters much), but the horrific misuse of version control. It sounded like a lot of the problems stemmed from
> When pressed for time, engineers would only include the updated versions of these libraries on a single destination’s codebase.
This should not be possible. You should be using a git submodule to include your libraries in each of your repos. It sounded like before they were literally copy and pasting the library across every git repo, which sounds like a recipe for disaster.
And now I know about gitconfig: Conditional includes! That solves quite a few problems for me, wow.
Now if only it also supported remote-url formats of the current git repo, so I could say [includeIf "remote:origin=https://github.com/**"]
or something.
I sent in feed back (https://www.apple.com/feedback/watch.html) about the change in feature. I never had battery life issues with 1.0, and am rather disappointed with the change. Really hard to get a valid record of heart rate if it only records the resting heart rate.
I don't think people are giving enough credit to the display here. A good high-resolution display like the new MacBook has would probably cost hundreds of dollars on its own.
When the iMac with 5K display came out, people shat all over the price then too, but conveniently ignored the fact that if you just wanted to build a PC with the same quality display, the monitor alone would cost as much as the entire iMac.
But Find My iPhone was not compromised on any of the victim's accounts. The passwords were discovered by pure social engineering—there was no breach on Apple's end.
I love this command because it helps people build the correct mental model for what git
is doing:
> git log --oneline --graph --color=auto --decorate --all
Basically, run that, look at your commit tree. Then run whatever command. Then run the log command again and see what it did to your commit tree.
That gives you a good understanding of the commit tree. Then the following article fills the holes with regards to the differences between the head, work tree, and index: https://git-scm.com/blog/2011/07/11/reset.html
Apple not the owners of the content. That would be an even bigger issue. Edit: sorry haven't been on today. Several others fielded but Tl; dr Apple does collect data about user but does not claim any rights to the content saved to the cloud. EULA
They'll regret this when people start using iTunes to make biological weapons.
Last sentence of the 2nd to last paragraph.
https://www.apple.com/legal/internet-services/itunes/appstore/dev/stdeula/
"You also agree that you will not use these products for any purposes prohibited by United States law, including, without limitation, the development, design, manufacture or production of nuclear, missiles, or chemical or biological weapons."
Rebasing is no longer that difficult once you understand the fundamental concepts behind Git. I'd therefore recommend trying to understand that first - afterwards, the official documentation is relatively easy to grok.
As a suggestion, this visual 10m tutorial I made might help with understanding the core concepts.
"If you are blind or have low vision, you can use VoiceOver, an advanced screen reader, to get the most from your iOS device. And Siri and Dictation help you type, launch apps, and read your calendar." https://www.apple.com/accessibility/ios/#vision
To be frank, it's hard to explain. Why is html/css better than a wysiwig? Because I have total control. But I bet wysiwig users would tell me they can do just as much as I can do. They can't, but I don't know how to explain that to them.
Git is the same way. If you actually understand the internals, you can do anything. You're completely free to navigate and manipulate your entire codebase. You can do 50 things, I can do 5,000.
I'd strongly recommend this book, https://git-scm.com/book/en/v2. I'm not sure there's a short explanation that's anywhere near as good as asking you to actually do the work to learn git at a deeper level.
"It’s called the Taptic Engine, a linear actuator inside Apple Watch that produces haptic feedback. In less technical terms, it taps you on the wrist whenever you receive an alert or notification, or press down on the display."
Apple商標および著作権使用に関するガイドライン https://www.apple.com/jp/legal/trademark/guidelinesfor3rdparties.html
>8. スローガンおよびキャッチフレーズ >Appleのスローガンまたはキャッチフレーズを使用または模倣することはできません。 > >使用例)「Think different」
Don't know why they didn't mention this in the keynote, but it has a power reserve function, that limits it to only telling the time when the battery gets too low, which apparently will last for 72 hours.
Batteries are very sensitive to heat.
>Your device is designed to perform well in a wide range of temperatures, with 62° to 72° F (16° to 22° C) as the ideal comfort zone. It’s especially important to avoid exposing your device to temperatures higher than 95° F (35° C), which can permanently damage battery capacity. That is, your battery won’t power your device as long on a given charge. Charging the device in high temperatures can damage it further. Even storing a battery in a hot environment can damage it irreversibly. When using your device in a very cold environment, you may notice a decrease in battery life, but this condition is temporary. Once the battery’s temperature returns to its normal operating range, its performance will return to normal as well.
Source https://www.apple.com/batteries/maximizing-performance/
> commit
Please create quality commit messages. If a developer came back to this shitty message they would have no clue where the ball was.
https://git-scm.com/book/ch5-2.html "Getting in the habit of creating quality commit messages makes using and collaborating with Git a lot easier. As a general rule, your messages should start with a single line that’s no more than about 50 characters and that describes the changeset concisely, followed by a blank line, followed by a more detailed explanation"
Didn't they say launching in 100 countries on June 30th? If assume the UK would be part of that list maybe?
Edit: Got the source. https://www.apple.com/pr/library/2015/06/08Introducing-Apple-Music-All-The-Ways-You-Love-Music-All-in-One-Place-.html "Apple Music will be available starting on June 30 in over 100 countries."
Edit 2: The plot thickens. Read on the same page: "Starting on June 30, music fans around the world are invited to a 3-month free membership..." This makes it sound like /on/ June 30, the option for a free trial starts globally. As in, starting on June 30, users around the world can begin their free trial. The "starting" part clarifies that you're not required to get the free trial on that day.
Or my personal favourite option: Not even Apple know when they're launching. Support don't seem to have a clue, and all the rumours pointed to last minute deals. Could be that they're not sure?
Here is Apple's own status page...
https://www.apple.com/support/systemstatus/
At the bottom of the page currently it says...
iTunes Store - All users are affected Customers may be unable to make purchases from the App Store, iTunes Store, iBooks Store, or Mac App Store.
iCloud Account & Sign In - All users were affected Users may have been unable to sign in.
iCloud Mail - All users were affected Users may have been unable to access iCloud mail.
I have been having trouble signing on to id.apple.com and I wondered what this issue was.
Honestly, for the extra $100 you're getting a better chip, 64 bit, better performance, Touch ID, etc. See the Compare iPhones page it is very helpful in seeing the differences.
If I were you, I'd go for the 5s if you can.
https://www.apple.com/macbook-pro/
The new macbook pro's dont have ethernet ports. We have clients who just purchased them and now they have to buy adapters for it.
Edit: BUT IT HAS RETINA DISPLAY SO OMFG SO COOL
This is from Apple's website directly…
If you want to store your device long term, two key factors will affect the overall health of your battery: the environmental temperature and the percentage of charge on the battery when it’s powered down for storage. Therefore, we recommend the following:
Do not fully charge or fully discharge your device’s battery — charge it to around 50%. If you store a device when its battery is fully discharged, the battery could fall into a deep discharge state, which renders it incapable of holding a charge. Conversely, if you store it fully charged for an extended period of time, the battery may lose some capacity, leading to shorter battery life.
Power down the device to avoid additional battery use.o
Place your device in a cool, moisture-free environment that’s less than 90° F (32° C). If you plan to store your device for longer than six months, charge it to 50% every six months.
Depending on how long you store your device, it may be in a low-battery state when you remove it from long-term storage. After it’s removed from storage, it may require 20 minutes of charging with the original adapter before you can use it.
Source: https://www.apple.com/batteries/maximizing-performance/#general
Another cool feature of bisect is <code>git bisect run</code>. You can use it to automate your tests every step and let git figure out by itself which commit is the culprit.
Start with the pro git book.
Then watch the amazing free Git for beginners by Perrotta. You should have a great understanding after this.
Apple does more than pretty much any other electronics company, by far, to improve the conditions of workers that make the products. You can read details in their annual supplier responsibility reports: https://www.apple.com/supplier-responsibility/
Apple have said that later this year they will release the native SDK for the watch, so probably during WWDC.
Quick Source and Source
You can download Node directly from its website or use NVM for Windows if you want to be able to manage Node versions better.
Microsoft will be launching WSL2 and their new Terminal soon-ish. I haven't used WSL before, but it should allow for more Linux-ish workflow and for Linux programs to run. WSL2 is said to be a much improved version of it.
On some serious shit, though, check out git reflog. If you manage to fuck things up, you can usually find something in your reflog to go back to. Note that running git gc
clears this out, though.
You are expected to know programming. Gone are the days of knowing just CSS and HTML. A competent front-end dev, even a junior, should know basic JavaScript (even if it's through a library like jQuery).
You should know the basics of version control software like git. Not a mastery of it, but the basics (checkout, commit, push, pull).
Resourcefulness and persistence. These are personality qualities that are hard to interview for, but are important to posses. Even if you don't know something, you should be able to figure out how to figure it out, and then figure it out (or figure out that it's likely beyond your experience to do, and thus know when to defer to a more senior developer). It's common for developers of any skill level to tackle problems they've never tackled before, and it's expected that they can do the research necessary to get it done.
Similar to #3, you know how to break down a problem into small, achievable bits so as to arrive at a solution one baby step at a time.
You'll want to be sure that you know how basic CSS works: cascading/inheritance, selector types, box model, positioning (i.e. you know the difference between IDs and classes, borders/padding/margin, relative vs absolute positioning etc)
Obviously HTML, but that's pretty basic stuff.
This post should be upvoted to the top of /r/programming.
By looking at OP's history, it's clear that OP knows how to program. He's been in the industry for some time, he writes Perl, PHP...
But wait. Look at that post about GitHub, the most used code sharing website of all time. The new SourceForge. And in that post, the issues he talks about are not really about GitHub, they're about the tool itself, Git.
Almost all his issues could be fixed by reading the introduction chapters of the Git Book. He could just, you know, RTFM.
There's a very important lesson here: even in your own domain, after decades of gathering experience, there will be times where you think you understood, but you didn't understand anything at all.
out of curiosity, I browsed the related apple page:
MDM can see:
Device name
Phone number
Serial number
Model name and number
Capacity and space available
iOS version number
Installed apps
MDM cannot see:
Personal mail, calendars, contacts
SMS or iMessages
Safari browser history
FaceTime or phone call logs
Personal reminders and notes
Frequency of app use
Device location
I think Microsoft is still at a point where we should be patronizingly congratulating them for even creating this document. It's cute!
Maybe one day they can collectively figure out why this: http://windows.microsoft.com/en-us/windows-10/about
is both objectively and subjective worse than this: https://www.apple.com/osx/
If OP has an iPhone, then by default the device's hard drive is encrypted. If they also have a lock, then that lock is also used to derive additional information to further encrypt files on their device.
Page 9 of iOS security docs
Heyoo.
This project is an interactive console for Ren'py. Way more sophisticated than the original one in DDLC.
This version is far from done yet. So use it if you don't fear uncommented code.
I'll use it for a mod which will teach you Git, the version control system.
There are accessibility options in the phone. It has an option that you tap once for it to read you what app it is or what it says, and tapping twice is "clicking" on it to do its function.
Here's the page for the VoiceOver feature: https://www.apple.com/accessibility/ios/voiceover/
And don't forget about Siri! That definitely helps a lot when you can't see the screen. For example, you can have Siri read you your text messages, and then you can respond with your voice.
The most helpful thing to do regarding fake apps is to make sure the developers of the real packages know about the fakes (by emailing them, etc.), since the real developers can file copyright/trademark complaints with Apple.
Then just ignore the fakes and let the developer and Apple handle it.
Edit: It can be helpful to include that link to Apple's website in your email, since not all developers know they can report things like this. Also, Apple probably doesn't care if the real copyrighted/trademarked work runs on jailbroken devices - their job in this case is to take care of copyright/trademark complaints, unrelated to whatever platform the real thing runs on.
Apple's always been focused on accessibility, so it doesn't surprise me that they've expanded that focus to their retail stores.
As a deaf man, that's one of the reasons why I love Apple so much. FaceTime has been a godsend to the Deaf community.
Thanks for posting this, OP. This thread was good to read.
Here you go, Derek. How to merge two branches of code 101. I do this day in and out, and it's really not a big deal... phew, your 'old school' pre-CVS/SVN never-check-in-your-code-hope-the-power-never-goes-out-mid-save knowledge is showing.
> copy-paste functionality
Apple wants the copy/paste experience to be consistent across apps. I can understand why the developer would be upset, but I can also understand why Apple banned the app.
> the whole maps fiasco.
Huh? I don't think they banned apps as a result of switching off of Google's Map data. In fact the old Maps app wasn't even developed by Google. Apple developed the app themselves, and licensed Google's map data (and since we're talking about anti-competitive behavior, I should mention that Google refused to let Apple use the data for turn-by-turn directions and offline maps – which is part of the reason Apple built their own maps in the first place).
Then Google built and submitted their own Maps app, which was quickly accepted in the App Store. Then Tim Cook issued a public apology for Apple Maps, and even suggested competing map apps.
One thing to consider is that the settings for iTunes Plus (256k AAC -q 127 / constrained) can be a little different from the settings used by some encoders by default on 320k AAC (some of the Quicktime ones in particular produce <em>medium</em> quality encodes and not the max 127 quality setting). This was discussed many moons ago during that whole Tidal kerfuffle. I'd be interested to see if you could repeat the same ABX with the maximum quality iTunes Plus settings. Edit: I've tried a few times and failed pretty miserably each time, but that's just me.
Except this is completely legal within EU Law to put that there.
Section 19.
> For such contracts, the consumer should have a right of withdrawal unless he has consented to the beginning of the performance of the contract during the withdrawal period and has acknowledged that he will consequently lose the right to withdraw from the contract. In addition to the general information requirements, the trader should inform the consumer about the functionality and the relevant interoperability of digital content.
This is part of the the EU Directive on Consumer Rights and was specifically put their for digital retailers and digital content. Apples iTunes ToS also says similar things.
> Exception to the right of cancellation: You cannot cancel your order for the supply of digital content if the delivery has started upon your request and acknowledgement that you thereby lose your cancellation right.
iTunes ToS for EU Customers.
nope, according to the new macbook's area of the apple site you get a USB-C and a headphone port. If you want the other things, you will need adapters. This includes regular f'in USB ports. So basiclly if you want to charge and plug in a USB mouse, your shit out of luck.