Blogbejegyzések száma: 4 darab.
|I bought a new 15" a few weeks ago, but I got a deal that was hard to refuse. It cost me exactly the same amount of money that the new entry level Retina MacBook.
As this was a one time opportunity, I took it.
I am well aware of age of this machine and its components, almost obsolete while being brand new, I'm aware that Intel's newer chips should outperform it / be more efficient. Intel's new Iris GPU should be faster. Skylake should bring DDR4, which is essential for the bandwidth-starved integrated graphics chip.
- Intel's late with the quad core Broadwell, as far as I know it's still not - available
- Even if it will be available, it will be a year late anyway
Quad core Skylake CPUs were missing from the latest Intel roadmap
I bet Intel favours the Core Ms when it comes to allocate fab capacity, as they sell at an absurd price, and it's a much smaller silicon. With the new MacBook and its competitors, the demand for those tablet-class chips should be high.
I don't think that Intel will rush to manufacture quad cores with a massive GPU, the successor chips for the 15" line to the 14nm process.
If you get a good refurb deal, take it.
Also note that third party SSD upgrades are still not available to current MacBook Pros, but are promised.
If Apple updates the proprietary SSDs in it's Pro line, or even worse, integrates it to the logic board (as they did with the new MacBook), you will have to pay upfront and/or be stuck with a capacity that was a reasonable compromise in exchange for speed in 2010-2011, but a pain in 2015.
|I stumbled upon the most awesome (third-party) user support I've ever seen:
Q: Is there any way to disable Safari's Show All Tabs feature?
A: Safari definitely does not have a setting for this, as decompiling the binary reveals the following code for the pinch gesture: [code with conditions]
This means that without Apple's involvement, the only way to disable the pinch gesture for the visual tab picker would be to modify the binary in /System/Library/StagedFrameworks/Safari/Safari.framework/Versions/A/Safari.
At byte offset 0x12E024, change 7A to EB.
Open Safari again and confirm that the pinch-to-show-tabs behavior is disabled.
|Using two separate Bitbucket accounts with two different SSH keys is troublesome.
In my example, I have two accounts:
bloghu: company account (blog.hu)
bitbucket: personal account
The name of the two keys are "bloghu" and "bitbucket".
My personal repositories were created after the company account, on my on machine. In order to make Bitbucket work with this new account, I refer to it with an alias in ~/.ssh/config:
Alias: instead of "bitbucket.org", it's referred to as "bitbucket" in SSH connections.
I use git on my machine for both account, but for the repositories that belong to this aliased personal account, I change the name of their repo to the alias:
Note the missing ".org": it's git@bitbucket, not firstname.lastname@example.org
This solved the problem on my machine.
Problem with the company's dev server
When I SSH into my company's dev server, and try to access git remotes, I encounter the following problem: git tries to authenticate me with my personal Bitbucket SSH key, and gets rejected by Bitbucket.
I don't store SSH keys on this server for various reasons (best practice). Instead, AgentForwarding is used by every developer. This of course sends all keys over, and it's the reason why my Bitbucket authorization attempt fails:
If I only had the company key, "bloghu", there wouldn't be a problem.
Unfortunately all the keys are forwarded, and there's no way to exclude "bitbucket", my personal Bitbucket key.
Adding aliases on the dev server for repositories, and then all the dev machines is not an option.
Creating an extra alias on my computer, bitbucket.org->bitbucket.org. While it seems redundant, it allows me to enforce an SSH key to the "bitbucket.org" domain.
Aliases propagate with AgentForwarding, so the dev server now uses the "bloghu" key for all the repositories on it.
|I found a really interesting way to look at the new MacBook, regarding its place and its important shortcomings.
I have an original iPad, the 64GB version with 3G, still used in a speaker dock as a music player. It has the following features:
- Unibody aluminium construction (Apple logo is not backlit)
- Less than 2 lbs (1.6 lbs for the 3G)
- Fanless design (ARM-based SOC, widely speculated as a future choice for light MacBooks)
- Flash based storage
- One port, for charging and data
- One headphone jack
- IPS screen (with touch, a common argument for competing ultrabooks)
- 10 hour battery life
Given that it's a 5 year old design, I will not look at cons when comparing the two. The shortcomings of the original iPad are well known and obvious, and a brand new ultraportable from Apple should best it in every respect.
Looking at the pros is the interesting part:
1. 3G + GPS
The iPad made up for its lack of ports and expandability by allowing premium customers to have internet connection anywhere.
It came at a cost: and extra 0.1 lbs for a larger battery, and a small door on the side for the SIM card tray. It was a premium feature, but a feature that worked as advertised.
The technological problem of integrating cellular connectivity to an ultraportable was solved by Apple 5 years ago.
2. It had an affordable entry version
The 3G + GPS version, with one bump up in storage capacity was $729.
But if you were willing to compromise on both features, you could get one for $499.
The 12" MacBook lacks this, and as much as I despise small SSDs in entry level Macs, they should have made an equivalent.
Just by looking at the original iPad, which was a first generation product, like the 12" MacBook, they should have gone a bit further:
Have a $999 version: 128 GB SSD, no cellular, even cheaper Core M
And keep the same ones, but add cellular.
Apple have made almost this product more than 5 years ago, and in some cases it was even better. The early adoption tax on this is too much, and the reluctance to add cellular to ultraportable Macs cripples this one.