nathana
That said, given the dearth of good options out there right now, I just replaced an old MacBook Air with a Surface Book 2, and with a few exceptions, I couldn't be happier right now:
1. This touchpad is just as good as pre-Force Touch ones from Apple. No joke. (If you must have the super-size ones with the Force Touch feedback instead of the "spring-board" style real button click, sorry...nobody else has that. But the non-Force Touch ones were "best in class" before, and that wasn't very long ago...)
2. The keyboard is easily the best laptop keyboard I have ever used. And that's coming from someone who used ThinkPads (I had the 770, the T42p, and the T60p) before switching to MacBooks, and who uses a Model M daily while at my desk. :-P
3. I have the base-model Surface Book. It's only a dual-core i5. But, again, I'm fine with that. The CPU is also housed in the screen, since the screen is made to be detachable from the keyboard. And since I have the base-model, I don't have the dGPU in my keyboard base either. So the base of the laptop stays cool while I use it on my lap. Oh...did I mention that the entire device (both keyboard base and screen) on the non-dGPU model is fanless? So no moving parts in the entire thing, noise-free, and isn't constantly sucking dust from the surrounding environment into itself.
4. There is a battery in both the screen and the keyboard base. Combined, I get amazing battery life, easily 8 hours or more depending. (I use it in laptop-mode 90% of the time.)
5. Screen on this is fantastic. Higher DPI than my 15" Retina MacBook Pro from 2012, way brighter, and the backlighting is more even. (I have the Samsung LCD on my 2012 rMBP...the model that never developed "image retention". I think the SB2 panel is made by Panasonic.)
6. It's got 2 USB-A, 1 USB-C (sadly no Thunderbolt, but it can handle DisplayPort), and a full-size SD.
7. Repairability is one area where it really falls flat, and in even bigger ways than the past MacBooks I own. :-( This thing I think got a repairability index of 1 (out of 10) from iFixIt. It's a sealed box for all intents and purposes. What really pisses me off, though, is that the SSD is not soldered onto the mainboard (it's a standard M.2 module), but there is absolutely no way of accessing it without basically destroying the computer in the process. If there was ONE area where I wish Microsoft had NOT taken any cues from Apple...gah, don't get me started. (And even then, at least with pre-2016 MacBook Pros, you could take the bottom cover off and get at the storage module in an emergency.)
8. The particular model I purchased ranges from $1,100 - 1,500 USD depending (list price is 1,500 but it's usually on sale). Don't know how that translates to your specific market.
9. I have not tried to use "desktop" Linux on it. I have booted SystemRescueCD off of a USB flash drive, though, in order to make a bit-for-bit image of my current Windows installation, and that worked fine (though to be fair I never bothered to start up X11). My understanding is that a lot of the hardware is supported even on current models; you can check out https://www.reddit.com/r/SurfaceLinux/comments/7kazwp/curren... for more details.
Anyway, just FYI.
But I have slowly found myself leaving the Apple ranks over the years, and the 2012 Retina was the last Mac I spent money on. I also ditched iOS (and iPhone along with it) for Android (long story) well before macOS began to take a back seat for me.
In January, I requisitioned a Surface Book 2 from my employer, and it has been fantastic so far. Easily the best laptop keyboard I have ever* used.
If you told 20-years-ago me that I would be buying PCs manufactured by Microsoft and praising them, I would have had you committed. But it has been fascinating watching a hungry Microsoft compete in this space...
For the record, I have the same rMBP 2012 model that the person you're replying to talked about, and it still runs great. But I'm typing this reply to you on a MacBook Air from 2010, running macOS 10.12 Sierra, in Chrome. Still works surprisingly well...
Decentralizing the Web (2008)
I miss USENET. Nowadays, my digital identity has been spread to the four corners, across Facebook, Twitter, various unrelated phpBB-based sites, and places such as /. and HN. Even if I wanted to, there is no possible way that I could re-locate every digital utterance I have ever made publicly. Not only that, but I don't truly "own" anything I write anymore. It's stored in some unmarked server somewhere, stuffed into a schema that has no published documentation. I still have e-mail archives going back 10+ years, but if Facebook ceases to exist 10 years into the future, it will be like the (admittedly few) worthwhile written conversations and interactions I had with people on there never happened. There will be no record of it.
There's got to be a better way.
That awkward moment when Gmail thought I was spamming myself
If more websites would verify, then this wouldn't be a problem.
I may be in the minority, but let me give you some perspective as a potential customer who has experienced this kind of hands-on "service" from other SaaS-y outfits: I WANT automation from your service. I have worked with 2 companies that made me jump through all kinds of hoops to get an account set up with them when I could have had a usable account provisioned and active in 5 minutes had they automated their processes. As a result, it took days, because (surprise) their employees have their hands full, and I also have better things to do (you know, actual work responsibilities and customers of my own to respond to) than to have my hands held jumping through all of your contrived and artificial hoops just to use your service. That's just a waste of my time and yours and something that only ends up causing unnecessary delays to service turn-up, and in both cases, it seriously soured my taste for the service and almost made me contemplate throwing in the towel and going with a different solution.
This isn't the feeling that you want to leave your new customers with who are trying very hard to give you their money. You mean every time we need to make a change to service parameters, I need to submit a spreadsheet with my change request to somebody that's going to plug it in on your side by hand? MAYBE 24 hours later, if I'm lucky? Forget that: I'll go with somebody that gives me an API or a web portal that I can use to make the changes myself in a matter of minutes.
A helicopter carrying a dinosaur: the case against VC
In my case (and in the case of some other customers of other MVNOs), my carrier, Straight Talk, is really just a company that buys wholesale access to AT&T's network and then resells it as a prepaid service to customers. Thus a Straight Talk SIM card looks identical to an AT&T SIM card to the iPhone. And AT&T's iOS carrier profile blocks access to the APN editing submenu. So my situation is different from yours because in your case, your Brazilian service provider and your European service providers had no corporate connections with each other, nor did they share a singular common network, as is the case with AT&T and Straight Talk.
There is next-to-nothing Straight Talk can do about this, at least without both AT&T's and Apple's co-operation.
It seems to me that given this fact, there really is no reason why Apple has to continue to kowtow to the carriers. Apple should stop sucking up to them and push direct sales of unlocked phones harder than ever. People will still buy them. They should then show a complete and fearless disregard for carriers by discarding the concessions they have made to them in the hardware and software design. Just throw stuff like carrier profile restriction features completely out. Sell iPhones to and for your end-users again.
If Apple decided to actually do this, what could any of the carriers really do about it? Nothing, that's what. Ban the iPhone from their networks? They wouldn't dare. (Or at least the GSM ones wouldn't...IS-95/CDMA2K is a slightly stickier subject, I'll admit.) There always seems to be a lot of talk (especially State-side) about carriers being open-access and what that means (remember the rider on the 700MHz auctions that Google convinced the FCC to sneak in which Verizon is now bound to as the winner of that spectrum block?), but GSM carriers have always mostly been "open" with respect to devices. Part of the promise of the SIM "personality module" is that it brings to the wireless industry what modular plugs in the home brought to the wireline industry following events such as the FCC's Carterphone ruling: a decoupling of the carrier and the end-user's device. I want to see the wireless industry move in that exact same direction. Sure, AT&T could decide to block iPhones from their network, but then they'd be turning down revenue from potential customers solely out of spite, and they aren't going to do that.
So far, the only company to have the balls to pursue a strategy like this, surprisingly, is Google. For some time now, you've been able to buy an unlocked Galaxy Nexus phone from them at a very reasonable price, and the Nexus 4 continues that tradition and even goes a step further: the ONLY sales channel (at least at this time) for the Nexus 4 is direct from Google. There are no subsidized or carrier-locked versions of this phone sold through carriers. There's a single SKU (well two, really, if you count the two fixed storage capacity options) for an unlocked GSM/UMTS phone. Google may have consulted with AT&T and T-Mobile here in the States out of courtesy before releasing the phone; I don't know. But I don't think that there's anything that says they had to get their approval to make and sell the phone, and there's nothing that says a user can't buy one without consulting their carrier first and put their own SIM card in it once it arrives.
Some may point out that Google isn't moving very many phones by themselves at the moment with this sales system, so doesn't that prove that this is not a viable business plan? I would counter that Google doesn't have quite the cachet that Apple does in this market at this time for reasons completely unrelated to how phones are sold, and that Apple, unlike Google, is in a position right now where it hold all of the cards. And for the sake of the consumer, Apple should take advantage of that position. That they don't appear to be ready and willing to do this (and in fact seem to be trending in the opposite direction) worries me.
I definitely salute Google for their move, and wish other phone manufacturers would follow in their footsteps. C'mon guys: take your destiny into your own hands rather than leave it in the trust of the carriers. Seriously.
I think that Apple has worked very hard to cast this image of themselves as the champion of the end-user. If that's the case, then they need to start proving it with mobile devices like the iPhone, which occupies a market segment where users have traditionally not been regarded as much more than pawns. I feel as though Apple here is treating this situation like their ongoing business relationship with AT&T and other carriers is more important than satisfying the needs of their customers whenever the two are in conflict. I suspect that Apple wouldn't want that kind of press.
...I still think APN blocking is entirely irrational on the part of the carrier. There's no way a user can subject their carrier's network to fraud or abuse by having access to the APNs (http://forums.macrumors.com/showthread.php?p=16266682#post16...)
Both of these options (backup or clean start) are burdens I am more than willing to accept and bear in exchange for having the freedom to backlevel my software as I see fit. Apple doesn't need to support people's downgrading efforts (as in, hold their hand, explain how to do it, etc.), but they've gone way beyond "not supporting" it. Going out of your way to develop a system that prevents downgrading? WTF?
I've said this on other forums, so I apologize if it sounds like I'm repeating myself, but the way I look at it is that if Apple is going to insist that I can never, ever reinstall an older version of the OS, then they are absolutely on the hook to deliver 100% bug-free software every single release. That's impossible, even for Apple (:-P). People aren't perfect, and they make mistakes. So it is absolutely imperative that they give their customers an "out" that they can elect to take if a bug or shortcoming of a software update introduces an undue burden for the user, and they need that functionality to work the way it did before while a new version (hopefully with a fix to your problem) is developed, tested/QA'd, and finally shipped. That kind of thing doesn't happen overnight, and it is not reasonable for software companies to expect people to live with certain classes of bugs or other problems while the fix takes 2-3 months to ship.
Enterprise system operators wouldn't stand for that kind of behavior from a vendor; if Cisco has a showstopper regression in their latest code that ends up biting people in the butt, there is NO way an admin worth his salt is going to keep running that version until the fix is in.
Heck, PC users wouldn't stand for that kind of behavior, either: can you imagine the outcry that would have resulted if Microsoft had told everybody who upgraded their PCs that were previously running XP to Vista that they're not allowed to undo the upgrade, even via a format and reinstall? Or what would have happened if, once Vista had been released, Microsoft told people that if anyone still running XP ever needs or wants to perform a clean-install of Windows, they would be forced to install the latest available version of Windows (Vista)? (Technically they could kind of do this if they elected to shut down the product activation servers for XP, but to Microsoft's credit, they have not done so and have shown no indications that they are even thinking about doing this.)
Apple does both of these things with iOS: technical enforcement of downgrade prevention, and also technical enforcement (through the same mechanism) of forced upgrade to the latest version during OS reinstall, regardless of what you're currently running. I find it crazy that people put up with it.
1) iOS does ship with a collection of the latest versions of partner carrier profiles as of the ship-date of that iOS version, as you point out. So you can't try to do an end-run around the AT&T profile restrictions by, say, doing a complete restore of iOS on your phone, followed by activation of the phone using a SIM that isn't from a carrier partner in order to cause it to use the generic carrier profile (for example, T-Mobile U.S.), followed by SIM-swapping back to your AT&T SIM. The AT&T profile is lurking in there, ready to be consulted when you switch SIMs, on every iPhone.
2) This is still a proprietary Apple scheme for pushing APNs for carriers (carrier profiles are plists), and not some universal standard for doing carrier programming updates "over the air." Carriers can build and submit their carrier profiles to Apple, but Apple then centrally distributes the profile updates from their own servers. And AFAIK, if you're a carrier, Apple is not going to host a carrier profile for you unless you have some formal relationship with Apple (become a "supported" carrier).
Apple provides an automatic APN configuration subsystem that the carriers control, but it is completely proprietary to iPhone, and it is in fact this exact subsystem that is causing me grief.
Some final notes of clarification:
1) Straight Talk isn't a "small carrier" (read: regional carrier with "rural" possibly implied) in the U.S., at least in terms of the size of the network itself. In fact, Straight Talk doesn't actually own any of their own infrastructure: they ride the nationwide AT&T network.
2) This proprietary iPhone automatic APN configuration system is used on ALL iPhones worldwide, regardless of carrier. So this has nothing to do with how carriers in the U.S. do or do not accomplish this vs. how you think other carriers outside the U.S. accomplish this. If you own an iPhone and have a SIM card in it that was issued by a carrier anywhere in the world that Apple has a contractual relationship with, your phone was configured this way, and you could run into the same problem I documented here depending on the situation.
This is iOS 6, remember. I think the instructions you linked to on the HF wiki were written for iOS 5, since they talk about General -> Network -> Cellular Data, instead of General -> Cellular -> Cellular Data...that menu got renamed in iOS 6. They no workie, at least without a T-Mobile SIM.
If you put in a SIM card that the iPhone has no clue about (such as T-Mobile U.S.)., then iOS will fall back to a generic carrier profile, which does allow access to the APN editing submenu.
The problem is that Straight Talk is an AT&T MVNO, and so Straight Talk SIMs are indistinguishable from AT&T SIM cards from the iPhone's perspective. The iPhone engineers made a bad assumption, which is that all cards issued by carrier X should be treated exactly the same.