alloy

7 ms·

1.
by alloy 9y ago
At Artsy, my team of long-time native developers, started using React Native on valentine’s day 2016 in our pre-existing iOS app. Overall it has been a net-positive for us. In short, the developer experience and ability to be productive is
2.
by alloy 12y ago
It’s been a great time!
3.
by alloy 12y ago
CocoaPods has been generating aggregated lists of licenses of libraries that you use in your app since a very long time, I don’t know of any other system that people use to pull-in dependencies that does this. We also only accept librarie
4.
by alloy 12y ago
> I don't understand your "build settings" comment. Why would there be any build settings originated from a library? Your project might need to link against frameworks/libraries that the dependency requires. Your proj
5.
by alloy 12y ago
Very fair points. I hope to see the day that they will sanction a small format around clang modules, we can always hope :)
6.
by alloy 12y ago
> It shouldn't be time consuming to manually integrate a dependency either. Add it to your project and go. I’m not going to play the yes-no game with you on this. > I further don't understand how it's a problem if you c
7.
by alloy 12y ago
> editing my Xcode project files underneath me creeps me out You can use the `--no-integrate` flag and it never touches your project, leaving integration of the Pods Xcode project up to you as you see fit.
8.
by alloy 12y ago
Yes, CocoaPods can’t fix API breaking changes, but as we use semantic-versions and encourage authors to follow those, it can at least be mitigated more easily. E.g. A version requirement of: ‘~> 1’ should then install the latest v1.x.x,
9.
by alloy 12y ago
You assume that any code installed through CocoaPods will be created by ‘third-parties’, this is incorrect. Dependencies are simply that. You can use your own, like many companies have been doing successfully internally. E.g. http:/&#
10.
by alloy 12y ago
While on the topiZZzzzZzzzzzzzzz…………
11.
by alloy 13y ago
Alcatraz manages ‘Xcode packages’, e.g. Xcode plugins and color schemes. CocoaPods manages dependencies of your Objective-C project.
12.
CocoaPods: Repairing Our Broken Specs (Git) Repository(blog.cocoapods.org)
18 points by alloy 13y ago|0 comments
13.
CocoaPods 0.27 and improved installation UX(blog.cocoapods.org)
2 points by alloy 13y ago|0 comments
14.
Speed up your Ruby project’s Travis CI test runs with WAD(fngtps.com)
1 points by alloy 13y ago|0 comments
15.
Fast test suite boot times with Ruby on Rails.(fngtps.com)
2 points by alloy 13y ago|0 comments
16.
by alloy 13y ago
Except, he didn’t lie. He spent money to have Watson also do maintenance work on MacRuby.
17.
by alloy 13y ago
[Disclaimer: MacRuby core member here.] I agree, it’s too bad that people can’t just work for free as much as they would like on the stuff they love. Now it is true that Laurent himself has not touched the repo since that email you linked
18.
by alloy 14y ago
> This is kind of the opposite of the standard advice of "don't repeat yourself" and "don't reinvent the wheel". Both those pieces of advice make an awful lot of sense to me. It’s not about re-implementing everything per project, it’s a
19.
by alloy 15y ago
If you mean on the end-user's machine: $ pod repo update
20.
by alloy 15y ago
Is there a specific feature that makes you say that? Or is it the age?
21.
by alloy 15y ago
Also, please please please start contributing specifications: https://github.com/alloy/cocoapods-specs :)
22.
by alloy 15y ago
ZOMG, indeed! You’re welcome! :D On a more serious note, I had been trying not to create this for about a year now. The release of the boilerplate project made me decide it’s time to finally scratch that itch.
23.
by alloy 15y ago
Starts with “J” and ends with “ava” ;)
24.
by alloy 15y ago
* Yes, good documentation is needed. Patches are very welcome :) * The community. The idea is that once you have one patch accepted you get push access. This applies to both https://github.com/alloy/cocoapods and https://github.com/allo
25.
by alloy 15y ago
Good question, it’s because of reading and writing the project.pbxproj file through NSDictionary: https://github.com/alloy/cocoapods/blob/master/lib/cocoapods... .
26.
by alloy 15y ago
Very true. However, judging by the chatter about this article on, for instance, Twitter [1], many don’t really seem to get that the ‘confirmed’ part in the title isn’t true. So I simply wanted to emphasize this point for others, not the au
27.
by alloy 15y ago
I’m talking about “MacRuby on iOS 5 - CONFIRMED!!!”.
28.
by alloy 15y ago
Well, I simply can’t say ‘it will not happen’, because it is open-source software, so for all I know you are currently implementing it. However, I wouldn't hold your breath on someone else stepping up to make this work, because we have been
29.
by alloy 15y ago
Yeah, sorry to rain on your parade, bro. But these kind of ‘confirmed’ articles, in the end, help nobody. Users will be sad when it doesn’t happen, whereas neither Apple nor the MacRuby team have actually confirmed/promised this. Sorrow all
30.
by alloy 15y ago
Although I empathize with your wishes, your article is way too sensationalistic. Let me confirm (I’m not with Apple); MacRuby on iOS has _NOT_ been confirmed.

More ›