Hacker Newsnew | past | comments | ask | show | jobs | submit | lordmatty's commentslogin

I’ve often wished for this!

ICYMI, next best option is plugging your iPhone into MacBook via Lightning cable so the tethering connection doesn't drop and your iPhone stays charged.


Good thought, but Apple is the gatekeeper here - not sure changing your license will help. What if they continue to use the methods without using Mogenerator (they could easily write their own categories to implement the methods for example)?


Idea is that the next version of mogenerator uses new method names, and that version says "Apple can't use this". Apple has no motivation to change the method names they use to match the new mogenerator if they're not using it, so nobody else is affected.


That's not the point - the point is to stop them from updating to a new version and blacklisting the new method names. They already have a license that allows them to use the existing code.


Great resource, but we've always found the issue with these to be the level of polish expected on iOS.

On occasion you spend as much time customizing these controls to fit with your UX/UI as you do building it from scratch.

As an added benefit, building from scratch gives you a clean room implementation.


As I posted on the freshte.ch blog, the commercial drive behind Siri is that you don't use Google when on Apple's platform.

Google coming out with a competitor that stacks up feature-wise doesn't fix that for them because it will only run on Android.

Google's going to miss out on a lot of search/ad revenue due to Siri in the future.


If its better, the question becomes: does Google release it on iOS as well, and will Apple allow them too.

However, i think the US readers are missing the most important aspect: how many people in the world can you serve?

This is a system selling feature during a crucial generation. The speed they can rollout new languages, will determine the world market and the long tail, which will prove crucual.

Currently, Google has the best infrastructure to do that, but Apple seems to care more. I live in Holland, for example. No siri, but at least we can buy content from iTunes. Google isnt selling anything but apps in its playstore.

I think whoever is able to actually give me all these features first, wins Holland. Why would it be any different in any other country?

There are markets up for grabs, and the first one to realize that fully, wins.


>Currently, Google has the best infrastructure to do that, but Apple seems to care more. I live in Holland, for example. No siri, but at least we can buy content from iTunes. Google isnt selling anything but apps in its playstore.

I'm not sure you appreciate the issues at play with licensed content. The iTunes Store opened in 2003 and was restricted to the US for over a year. Apple expanded it into international markets very slowly, over several years time, and didn't even move outside the western world until just last year.

My point is that it takes quite a bit of time and effort to address complex international issues with content licenses and rights holders. Apple has spent almost a decade working on this and they're only recently getting to a level of international ubiquity. Whereas Google has been at it for barely a year, but is moving pretty quickly as far as I can tell.


Apple has one (1) datacenter in the entire world, and it's in the USA. How good do you think the latency from Holland will be? Google has datacenters in Groningen and Eemshaven, and all over Europe.


You are wrong about Apple, they have one huge datacenter in the US where people suspect the Siri backend runs. They also have a smaller data center in California. We don't actually know what runs where, and we don't know what they are running in leased space in 3rd party datacenters. And, they are building other datacenters in the US.

In any case, wherever Siri runs, I don't think that Internet latency comes close to explaining the latency, and, I think, Siri can actually hide a lot of latency.


Yes, so Google has the best infrastructure. But thats not motivating them to very inclusive with dutch consumers. Lets hope that changes.


Any thoughts about putting this on a smartphone?


It compiles with you iOS XCode project (drop the source code in and it will compile).


I can understand the reaction on this community to the news, and I'm sure that there are elements of PR and recruitment strategy here, but I happen to know that the primary driver is pretty sound; job satisfaction for top employees.

Goldmans has its share of top programmers and, like any company, is keen to retain them. One of these people made contributing to Open Source a major goal for last year.

Well done to him, and well done to GS for supporting him. The company (rightly) gets a ton of bad press, but that doesn't mean it can't do good things as well.

Disclaimer: I'm an ex GS employee, but have nothing to gain.


When I interviewed at GS last year, I was explicitly told that I would not be able to go on working on open source (they had checked out both my blog and my Github). This despite none of the technologies in my main project being in use in the group I was interviewing with...


I guess it probably depends on the position/team. I wouldn't expect GS to open source anything they consider a competitive advantage, but then I don't see Google open sourcing their search algos either :-)


There's a difference between "you can't open source some/all of our code" and "you can't work on unrelated open source projects in your free time".


I agree. I can't say I like standard practise of employers owning everything their employees do whether in or out of work, or requiring that you stop anything they don't own.

However, this is hardly something that is limited to Goldmans or financial services. I'm pretty sure that Apple require you not to work on side projects, for example.

We had a discussion regarding this at my company - Future Workshops - last week, and decided that what people work on in their own time is their own business, with the caveats that a) people don't work in conflict with any clients, b) the IP is clearly separate, and c) it doesn't affect their day job in a negative way.


Let's not call this a "standard" practice. In my experience, most companies do no make claims to your off-the-hours projects. And that is how it should be. Unless you're doing some cutting edge AI research or something of that sort, this kind of legal claim is just paranoid stupidity. Even if you do cutting edge AI research, it shouldn't entitle your employer to own a phpBB patch you've done in your free time.


Great example of an acquisition that will work out - two startups motivated by the same type of goals and both, as far as I can work out, optimised for happiness, not optimised for profit.


I got stock options in exchange for sweat as a consultant in what is now a NASDAQ listed company. Great deal, which netted about a 10x profit over the money Id have been paid. Of course, not without it's risks, but as a freelancer I feel my risk was limited.


The guy talks about tired analogies, whilst making one that looks positively sleep deprived in his headline and conclusion!


All of these Apps are small, focused and free...

Loving LiveReload, Mou and Launch Effect.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: