bitserf

This is less than I spend on coffee in a month.

When you hear the word "taxpayer" brought up in an argument, it's a good hint that what will follow is a screed against providing anyone any assistance from the public purse whatsoever, despite any such benefits the author may have received and conveniently forgotten in their personal "self made man" narrative.

This will improve in Swift 3.0, via an improved mapping of Cocoa APIs into Swift (naming wise):

https://github.com/apple/swift-evolution/blob/master/proposa...

At some point in the future I imagine we would also see native Swift APIs.

I was working for a startup in 2008, and before everything turned to crap, Sequoia gave us up front warning to start preparing for the coming apocalypse, which probably is the reason we survived and made it to an exit of some sort.

Over-raising seems like more proactive version of that (2008 still being relatively recent in investors' memory), and VCs likely suggested this to portfolio companies.

Apple removing these frameworks is a pretty strong signal that it's going to get harder/impossible to use in a future release.

Probably not a reason to double down on your private API usage.

It's similar in New Zealand...The last time I had cash in my wallet was when I visited Japan a year or so ago.

Basically if you don't have an EFTPOS terminal as a retailer you may as well not exist. Even temporary food stalls at festivals usually have a mobile connected terminal.

Good on you for persisting with it.

I developed a mobile manual entry personal finance tracking application as well, stuck with it for two years, but I'm back to manual entry using Ledger because of the pain in the ass it is to enter data on mobile, whereas I can use automation to import my various bank accounts data (e.g. https://github.com/cantino/reckon) with Ledger.

The reporting on the data is the gold, for me, the mobile app didn't really add that much value, so I just gave up.

No one is suggesting using it as a system package manager, least of all Apple.

It distributes source code and the audience is developers wanting to integrate that into their projects at build time.

Using something like RPM or DEB for that task would be, uh, suboptimal.

Swift does a pretty good job as well for a first attempt.

https://www.mikeash.com/pyblog/friday-qa-2015-11-06-why-is-s...

Overall web browsing is already 60/40 in favour of mobile though, and mobile is high 90% using WebKit or some flavour of it.

Not that this justifies skipping testing on Windows, but it's not impossible to see how it's no longer a top priority, since all of the growth is sitting on the mobile side.

The problem I have with subscription model for my tools is this: It removes the option for me to decide to not upgrade because the improvements are not worth the cost.

Note that I have been upgrading my license most every year, but chances are I'll just make do with what I have next time around.

If the current pricing model isn't viable for them, I'm sorry, but it is not my problem. It's already the most I pay for any tool I use, and I have found it worth it so far, but coercion into a subscription model just doesn't work for me.

Not a great move by JetBrains.

Thank you for this, I really, really like the compactness of it.

Not surprised to see Pragmata as an inspiration, I bought that font a few years ago when it was around US$100, and I still love it today, I probably use it 80% of the time :)

It's highly unlikely that Apple will release any code under an FSF license, ever. The FSF needs to make their peace with that, no shrill screeds are going to change that.

And frankly, if there's going to be a new, modern, high quality language with support for the platforms I care about (Linux, OS X), I'm going to use it.

I wonder if RMS is going to publish a Swift version of "The Java Trap". I don't think it will meet with the same result (relicensing under the GPL).

One potential weakness is that a declarative rule list controlled by the browser (iOS 9) would be slower to adapt to ever changing approaches use to bypass ad blockers.

Whereas the extension model of AdBlock I presume lets it be more clever.

But on the flip side, the Safari approach would be much more performant than having to execute some JS to enforce blocking.

Looks like they're on a CN watchlist, as a result of this reporting.

http://www.charitynavigator.org/index.cfm?bay=search.news&or...

If you went by CharityNavigator data, you'd think the American Red Cross was one of the well run ones.

Cost of living is accordingly lower. I lived quite comfortably on my monthly wage of $400 in South Africa when I was starting out in 1998. When it got to around $1800 a month it was really, really comfortable. Your foreign purchasing power sucks so I never bought Apple, but food, accommodation and anything else in the local economy was affordable as heck.

Did the DNA test through 23andme.com, some interesting East Asian and African skeletons were discovered for a family supposedly of purely European lineage :)

Of the many bugs I reported at 8.0 release, not one has been fixed. Basic intern level stuff to do with messed up orientation bugs, broken locale APIs, text rendering and layout issues.

I honestly can't be fucked any more, they can hire some QA with the billions they're earning. They can build all the fancy APIs they want, I'm not touching it until they haven't decided to discard it after a year and some other poor suckers have suffered through their eternal September of shitty buggy newness while fighting with App Store review team every second version for the privilege to make burger flipping money.

You can get the OpenVPN route quite seamless from a client perspective (server is still a pain in the ass to set up).

You can bundle all the configuration for a particular client into a .ovpn file - this includes the client and CA certificates.

I use this on iPhones and iPads, with the OpenVPN iOS app - works great for a family of iOS devices that need access to some geo-locked services.

What's really great is when you're working on something else, someone sends you an email, and then walks over to discuss the email they just sent, because you didn't reply in 30 seconds.

You can manually retain / release using Unmanaged, but that seems like a lot of work when you can mix C/C++ and Swift in the same target.

What appeal to authority?

The whole point of my comment was that I'm now more unsure of anything than I was when I was younger and more susceptible to appealingly simple solutions.

The world is incredibly grey.

I remember when I was 20, and had just finished reading "Machinery of Freedom", intent on fixing all the glaringly obvious problems in society by applying a medicine of revolutionary libertarianism.

Happily, I have now grown up.

I've been working professionally with Microsoft platforms since the early 2000s.

Not sure why you celebrate that Microsoft is treating everything but the latest as legacy.

His point is that after massive rework for OS X, more than 10 years ago, expertise in Cocoa has been remarkably stable and portable across their ecosystem.

Microsoft in the same time, has been through how many data access layers? How many networking/HTTP APIs? Web frameworks? GUI toolkits? All of it legacy abandonware now.

It's not free to have to continually retool to work with APIs that will still get bugs fixed.

Yes, using the 1998 API will still work. But that API will never be worked on again. Good luck if it has a bug that means something is impossible to do.

Microsoft errs on the side of throwing something out there before it's fully baked, and fixing it by introducing replacement APIs with the learnings from the first couple.

Apple's approach is to keep APIs private up until such time as they're ready to make them public, after which they commit to them and they'll be The Way To Do Things for a much longer time.

Which you prefer I guess depends on the type of developer you are.

The problem is that this doesn't scale. Sure, people are sharing the information now, because it's part of a current story, but 2 years from now? And the party affected isn't an organisation with the reach of the Times?

If everyone wanted more durability and better battery life we'd still be using Nokias that were indestructible and lasted 7 days on a charge.

Fellow NZ citizen. Could not agree more. I hope we will have more engagement of the citizenry this election.

Google's implementation is carrier vetoable, since it's on the SIM.

Additionally, Google's implementation requires the transaction transit their infrastructure, Apple's does not. They don't even know the transaction occurred.

Yes, they're not technically first, but the two systems are not identical.

Personally, the less a large corporation knows about me, the better.