Hacker Newsnew | comments | show | ask | jobs | submit | abuzzooz's comments login

They said it will happen by the end of 2015.

-----


They said they would make facetime an open standard.

Still waiting.

-----


Here's a story about facetime: http://www.fiercedeveloper.com/story/facetime-open-standard-...

-----


Are you sure this is why Apple went radio silent? Even if Apple was somehow prevented from publishing the standard (I don't see how a patent would prevent them from doing so, but whatever), that doesn't explain why they couldn't just say so.

-----


I am not sure--definitely don't have any real knowledge about this issue. I was just looking for any info about the facetime issue and that came up in the search results.

-----


Apple loses Facetime patent lawsuit.

http://www.bbc.com/news/technology-20236114

-----


Let's hope this waiting has not caused your Facetime to be Faceache!

-----


Which is still not "pulling it off", which is my point.

-----


I think the "pulling it off" here is coercing their megacorp organization into tolerating the idea of open-sourcing something they poured so much time and money into developing. This is also why people have been celebrating Microsoft open sourcing things recently.

-----


"By the end of the year" perhaps suggests that Microsoft got out in front and Apple's hand has been forced into changing their roadmap. I suspect that Apple will struggle with to support cross platform development beyond tossing Swift over the transom. Supporting diverse execution environments is not their core competence historically.

-----


It also suggests that swift version 2.0 isn't out yet and they don't want to deal with open sourcing it until then or have to go through lawyers regardless.

If you followed Chris Lattner on the dev forums he always gave the impression that they wanted it open source from the start but had bigger fish to fry. They reimplemented a ton of the compiler multiple times after finding bugs in the existing language specs. Don't read too far into this that microsoft forced anything. For one, we'll never know and this is at best conjecture.

As for supporting diverse execution environments, I'd argue llvm/clang/webkit proves otherwise. Granted they're not "supporting" it in the sense that they're selling support for it but I'm not sure exactly who would meet your criteria right now.

-----


I think this is where companies like Xamarin and JetBrains can pick up the slack as they have with the Microsoft stack. As long as it's (legitimately) opened-sourced, of course.

-----


Xamarin and Jetbrains live in the enterprise market. It's hard to see Swift quickly gaining traction in that space.

-----


Which is not a very interesting thing to gripe over.. there's nothing wrong with being excited about the announcement, why don't we stop with the pedantry?

-----


There is nothing wrong with being excited about the announcement, but that 1) that isn't what the headline indicated (it's since been changed, but at the time it was something very close to "Apple has open-sourced Swift!"), and 2) the comment I was replying to said Apple had "done it," which seemed to be responding to the inaccurate headline.

I think most people involved in software would realize that the distinction between plan and implementation is extremely important.

-----


Surely any reasonable person would recognize that it looks like swift will be open sourced, barring something unexpected.. You're nitpicking at someones choice of words and not adding anything valuable to the conversation.

-----


I sincerely do not think "They pulled it off" versus "It looks like they will do this sometime in the next six months" is nitpicking somebody's choice of words. The difference between the two is not a minor nuance, it's a large practical difference, and I don't think people would necessarily understand the latter meaning from the former.

When I first saw this thread, I certainly thought Apple had actually open-sourced Swift, as both the headline and the comment I was replying to said so. Then I looked at the linked page and saw it had not happened, so I corrected this materially important piece of information.

-----


The headline and the direct quote from apples website say "Swift will be open source later this year".. I don't think anyone in this thread is trying to say anything to the contrary. Certainly the decision to open source swift has been "pulled off", perhaps that's what LesZedCB was referring to.. who knows? Who bloody cares? It's very much not important.

-----


As I already said, that was not the title when I posted my comment. At the time it was something very much like "Swift is now open-source!" Because of worthless nit-picks like mine, the title was later changed to be accurate.

-----


Yeesh, ok I didn't realize the title was changed

-----


> Which is still not "pulling it off"

Honestly if you're that nervous and scared of what might happen in the future there's probably nothing Apple (and most other companies) can possibly do to comfort you. Probably better for you to avoid the potential pain and skip this one.

-----


Not being a web developer, I don't see any mention of Node, which makes me curious. Is Node not a good option?

-----


Above I mentioned io.js, an up-to-date fork of node. I think either are a great option.

-----


Brings back old memories of Moon Patrol. Thanks!

-----


> It is old Sun technology that Sun abandoned to work only on Java

Not exactly true. Tcl/Tk was not invented at Sun, although Sun did fund its development for a few years by employing its author John Ousterhout.

But, I agree with you that the UI look is outdated, and needs some touching up. Every time this issue is brought up, the Tcl folks point to the "new" theming capabilities that were added in v8.5 (or perhaps v8.4?). I haven't looked at theming in Tcl to make an opinion.

-----


I believe that these days unused CPU cores are physically shut down by turning off the voltage supply that's feeding them, in order to save power. This is a commonly used technique in chip design called "power gating". It is one of the most important techniques for prolonging battery life in mobile devices.

-----


Would be nice to have a demo site set up.

-----


> Would have been nice if you could pay with the Watch instead of pulling out the phone

You can.

-----


probably because the page was cross-linking to images on another host, and the admin of that host switched the images.

edit: this is called "goatse" btw. Don't google it.

-----


I'm not familiar with HackPad, but I don't think that's what's happening, because the `img` tags point directly to goatse.info. I think someone edited the document, removed whatever content was once there, and replaced it with goatse pics. That's a shame, because I was interested in reading the article.

-----


Reverted to the previous version.

-----


Great job. I have my own mongodb of the games/scores that I update manually (not in real time though).

I would love to see something automated like this for the major leagues (La Liga, BPL, Bundesliga, Serie A). I tried my hand at scraping the HTML of different sites, but found out that the main ones guard against that by changing their HTML periodically, so I gave up.

Side question: what does HN think in general about scraping data from HTML? There are websites that charge for live sports data, and scraping them seems borderline unethical.

-----


In the US at least, facts can't be protected with copyright, and sports scores & statistics have been judged facts. So you would be OK, and ethical. But avoid scraping/re-sharing anything of added value, like commentary or analysis.

I suspect rules in other countries vary.

-----


Actually, both will match the '2' in '1 of 2 steps.'

-----

More

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: