Earlier quoted context omitted.
I think you have a good point. The whole reason for standards (like SI units) is so that people don't need to guess or interpret. I don't get why this was downvoted.
You can downvote?
Xcode 8.3 produces binaries 3x larger than Xcode 8.2.1
81–90 of 142 posts
Re: Xcode 8.3 produces binaries 3x larger than Xcode 8.2.1
#82Re: Xcode 8.3 produces binaries 3x larger than Xcode 8.2.1
#83Earlier quoted context omitted.
I think you have a good point. The whole reason for standards (like SI units) is so that people don't need to guess or interpret. I don't get why this was downvoted.
A bit isn't a divisible unit, so nobody is going to be confused as to whether "mb" stands for "millibits". As for the capitalization of "b", if we're going to be pedantic then we should say "Mo" for "megaoctets", since "byte" is, as far as IEEE standards are concerned, of ambiguous length. But I think we can trust people enough to not spend too long puzzling over whether "mb" means megabytes or megabits, just as we c…
Re: Xcode 8.3 produces binaries 3x larger than Xcode 8.2.1
#84Earlier quoted context omitted.
That is expressing a ratio. A more concrete example, .46 a person doesn't exist even if that ratio is useful for expressing statistics.
I think "gaining half a bit of information" about something can correspond to stuff that lets you update your probability distribution about it? I'm not sure.
Re: Xcode 8.3 produces binaries 3x larger than Xcode 8.2.1
#85Earlier quoted context omitted.
I think you have a good point. The whole reason for standards (like SI units) is so that people don't need to guess or interpret. I don't get why this was downvoted.
A bit isn't a divisible unit, so nobody is going to be confused as to whether "mb" stands for "millibits". As for the capitalization of "b", if we're going to be pedantic then we should say "Mo" for "megaoctets", since "byte" is, as far as IEEE standards are concerned, of ambiguous length. But I think we can trust people enough to not spend too long puzzling over whether "mb" means megabytes or megabits, just as we c…
This is putting the burden of collaboration in the wrong place: it shouldn't be a question of, can we expect a reasonable engineer in the industry to understand this unambiguously (with some deductions); but rather, can I hold down the shift key when typing the abbreviation for megabytes.
Obviously this depend on the actual audience, don't bother following this in team chat where speed is more important than clarity.
Re: Xcode 8.3 produces binaries 3x larger than Xcode 8.2.1
#86This appears to be bitcode. It probably means they just starting making use of more metadata or something that is now included in the bitcode. Bitcode also now deliberately trades off size vs speed and includes indexes used for LTO, etc. They could be including those. You should almost always expect bitcode to get beat by "llvm-dis|xz", because the goal of bitcode is not to be the most compact possible format, but in…
Re: Xcode 8.3 produces binaries 3x larger than Xcode 8.2.1
#87Re: Xcode 8.3 produces binaries 3x larger than Xcode 8.2.1
#88Apple charges $1200 to upgrade the latest touch bar rMBP from 512GB to 2TB of flash. Let's not forget that they are a hardware vendor. I don't think it's some grand conspiracy theory, but the interests of the vendor and of the user are not precisely aligned when it comes to efficient usage of storage. (The lack of stripping applications of their alternate language content on install/download also comes to mind.)
No, Apple is not intentionally wasting your storage. That's frankly a very offensive accusation to make. As for alternate language content, honestly that stuff doesn't take up very much space, and stripping it would break the code signature. The only way Apple could strip that is if they perform the equivalent of App Thinning based on a list of languages you specify when downloading the binary from the App Store (and…
Yeah. It's not like Apple had to settle lawsuits about batteries that seemed to be designed to break after a while. Oh, wait...
Re: Xcode 8.3 produces binaries 3x larger than Xcode 8.2.1
#89This appears to be bitcode. It probably means they just starting making use of more metadata or something that is now included in the bitcode. Bitcode also now deliberately trades off size vs speed and includes indexes used for LTO, etc. They could be including those. You should almost always expect bitcode to get beat by "llvm-dis|xz", because the goal of bitcode is not to be the most compact possible format, but in…
So
* the bitcode portion has grown by 4.5x
* the non-bitcode portion of the bundle has grown by 2.2x (40MB to 88MB)