21–27 of 27 posts
Earlier quoted context omitted.
Lets just hope there aren't any binary trees in need of inverting at Apple ;) Seriously though, seems like a perfect fit, much better than him working on something unrelated at Google etc
As an Android hobby developer, given the amount of issues that have been lagging all these years and the quality of each "stable" release, I really don't get where do all those genius that Google does eventually hire work.
It's seriously so cool that the Homebrew guy (Max Howell) is behind this. Great fit for him at Apple. =P
Lets just hope there aren't any binary trees in need of inverting at Apple ;) Seriously though, seems like a perfect fit, much better than him working on something unrelated at Google etc
Okay, I'm gonna have to enter rant mode here, because this is aggravating me. Why in the bloody fuck do we need another package format? Okay, cool, you have a project, it has needs, you wanna track it. How hard is it to use one of the pre-existing formats? We have rpm, deb, pkg, pkgng, etc as system packaging formats. Is your language such a precious and delicate flower that it needs its own packaging format? You can…
So you want every developer to produce rpm, deb, msi, depot, bff, pkg, dmg, taking into consideration OS specific paths and configuration settings for every single library, specially for packages common across OSes?!!
Okay, I'm gonna have to enter rant mode here, because this is aggravating me. Why in the bloody fuck do we need another package format? Okay, cool, you have a project, it has needs, you wanna track it. How hard is it to use one of the pre-existing formats? We have rpm, deb, pkg, pkgng, etc as system packaging formats. Is your language such a precious and delicate flower that it needs its own packaging format? You can…
So, do you manage cocoapods or carthage for your iOS/OS X developers right now? Go away and rant how all languages except one your favourite should be banned, because that would make ops job so much easier. Though I am still not sure what ops are doing on developers' machines.
The current state of the world means that it is currently entirely feasible that some components will be managed by cocoapods, and some by this new format. What world-shattering difference between the two exists such that they can't share a metadata format to describe a development package? How does the new format make life easier?
Earlier quoted context omitted.
So you want every developer to produce rpm, deb, msi, depot, bff, pkg, dmg, taking into consideration OS specific paths and configuration settings for every single library, specially for packages common across OSes?!!
No. I want people to stop reinventing the metadata wheel. I used system packages as an example. We now have Package.swift for swift and package.json for node, cargo.toml for rust, etc. What problem does Package.swift solve that package.json doesn't?
Earlier quoted context omitted.
No. I want people to stop reinventing the metadata wheel. I used system packages as an example. We now have Package.swift for swift and package.json for node, cargo.toml for rust, etc. What problem does Package.swift solve that package.json doesn't?
How does package.json handle compiler semantics, linker, library, modules, architectures, incremental compilation, cross-compilation, dependencies to Objective-C and C libraries, ... ?
Earlier quoted context omitted.
As an Android hobby developer, given the amount of issues that have been lagging all these years and the quality of each "stable" release, I really don't get where do all those genius that Google does eventually hire work.
Optimizing ad revenue.