371–380 of 458 posts
Earlier quoted context omitted.
Not to mention, bootstrapping in a language that's not stable yet can be.... quite a pain.
Hahaha, I'm amazed that the Rust developers were able to do that. Saying it was "quite a pain" is the understatement of the year.
Earlier quoted context omitted.
No. This is a childish joke, and inappropriate. As a community of professionals, we should do everything we can to discourage this kind of crap. Joe Cumbo (mooman219), I hope you never apply for a job I'm the hiring manager for, because I would never hire you after seeing this kind of unprofessionalism in your Github profile.
And I would never want to work for you if you've such a dearth of humor :P Exactly how is this inappropriate?
Earlier quoted context omitted.
Can you or someone summarize the salient points, for someone who doesn't have time to watch an hour-long video?
The slides are here: http://www.slideshare.net/bcantrill/fork-yeah-the-rise-and-d... The direct link to the Oracle part: https://www.youtube.com/watch?v=-zRN7XLCRhc&t=2107
Earlier quoted context omitted.
It looks like they used an automated tool to add copyright notices to files in the repository. Probably were required to do that by legal. So it's not 100% faithful history, but close.
This raises some interesting legal questions. If I start a git repo and only add a license in the Nth commit, does that license apply retroactively to a checkout of the first N-1 commits? What if I start out with one license but I change it in the Nth commit? If someone clones the git repo with the Nth commit in it and then checks out an earlier commit, which license applies? (For simplicity, assume I am the only aut…
Earlier quoted context omitted.
OK, that it's the preferred (by Apple) language/platform for iOS development? I'm guessing you knew what I meant.
Except it isn't, the vast majority of Apple's internal iOS stuff is still written in Objective-C.
Earlier quoted context omitted.
This raises some interesting legal questions. If I start a git repo and only add a license in the Nth commit, does that license apply retroactively to a checkout of the first N-1 commits? What if I start out with one license but I change it in the Nth commit? If someone clones the git repo with the Nth commit in it and then checks out an earlier commit, which license applies? (For simplicity, assume I am the only aut…
You can retroactively make a license more open, but you cannot retroactively make it more closed.
However, my original question still stands. If I hack privately on a git repo and never distribute it, and then I only add a license in commit N right before first releasing it publicly, what is the license of commits 1 through N-1, which do not contain a license themselves (or perhaps contain a different license) but were never distributed separately from the license contained in commit N?
A lot of folks to thank at Apple right now, can't wait until all of this propagates so we can take a look at what's new in Swift 3. Two thoughts: - VERY happy to see the open sourcing of much of the Foundation libraries (which includes strings, dates, networking primitives, concurrency/task queues, I/O, etc). It'll provide a very strong start and make working with Swift immediately productive. - Holy crap, there's a…
It doesn't look like they've opened any of the existing Foundation framework we all know and love and that's written in Objective-C. The swift-corelib-foundation repo contains a bunch of .swift files, and those contain lots of calls to NSUnimplemented(). The Core Foundation stuff (included in swift-corelib-foundation) has been open for a while: http://www.opensource.apple.com/source/CF/
"These libraries are part of the work towards the future Swift 3 release. They are not yet ready for production use, and in fact are still in the earliest stages of development"
A lot of folks to thank at Apple right now, can't wait until all of this propagates so we can take a look at what's new in Swift 3. Two thoughts: - VERY happy to see the open sourcing of much of the Foundation libraries (which includes strings, dates, networking primitives, concurrency/task queues, I/O, etc). It'll provide a very strong start and make working with Swift immediately productive. - Holy crap, there's a…
> This has been sorely needed since about day one of Swift development, glad to see that it's been a priority as part of the effort to open source! While not first-party, https://github.com/Carthage/Carthage Swift's appears to possibly be limited to Swift, so Carthage will still be useful to integrate with Objective-C frameworks.
Earlier quoted context omitted.
The same guy who wasn't offered a job at Google because he didn't do well in the interview (or was it code in the interview?)
Google doesn't provide feedback on why they reject you. For example, you could be the world's foremost expert on Erlang. But the department interviewing you needs a C++ programmer. You'd never know that was the reason. You'd just be notified that you weren't called back for another interview and asked to please check back for more positions in a few months.