Slashdot Mirror


Are App Sizes Out of Control?

In a blog post, Trevor Elkins points out the large sizes of common apps like LinkedIn and Facebook. "I went to update all my apps the other day when something caught my eye... since when does LinkedIn take up 275MB of space?!" Elkins wrote. "In fact, the six apps in this picture average roughly 230MB in size, 1387MB in total. That would take an 8Mbit internet connection 24 minutes to download, and I'd still be left with 27 additional apps to update! More and more companies are adopting shorter release cycles (two weeks or so) and it's becoming unsustainable as a consumer to update frequently."

Should Apple do something to solve this "systematic" problem? Elkins writes, "how does an app that occasionally sends me a connection request and recruiter spam take up 275MB?"

Further discussion via Hacker News.

386 comments

  1. lol know nothings by Anonymous Coward · · Score: 2, Funny

    I know you old perl grognards don't know anything about the size that graphical assets take up, but when you need a 2086x1080 image for every screen because iphone resolution is fuckhueg you get ballooning app sizes.

    1. Re:lol know nothings by Anonymous Coward · · Score: 5, Informative

      Image compression exists for a reason. If you neglect to optimize your images, the best compression in the world won't help. Check out PNGQuant; it can often achieve perceptually lossless compression through careful palette selection and dithering. Vector graphics are also a thing; you can create your bitmaps at runtime.

    2. Re:lol know nothings by Anonymous Coward · · Score: 4, Insightful

      Bullshit. Image sizes for simplistic apps like that would never consume that much space. The actual reason these apps are ballooning is size is because developers nowadays are complete shit and don't understand code reuse, optimisation or assembly language.

    3. Re:lol know nothings by Anonymous Coward · · Score: 5, Funny

      simplistic apps like that

      how is facebook simplistic? it needs to:

      track your location at all times
      record everything via the mic even when backgrounded
      send you push notifications when your gradeschool girlfriend makes a post about how men suck
      deliver you the quality ad content you deserve
      let your HR department creep on your comings and goings because they have nothing else to do
      support hashtaggings

    4. Re:lol know nothings by jellomizer · · Score: 2

      How many of these images are really needed? And how many of the remaining images could be done with some simple vector graphics calculations?
      Back in the old days, the customer wanted a shadow effect on a table border to make it stick out. At the time CSS didn't have shadow ability. So I had 5 small png
      TopRight 5x5, Right 5x1, BottomRight 5x5, Bottom 1x5, BottomLeft 5x5. Then I just stretched the images in the right spot to create the effect. during this time people were still using dial-up modems, so we needed to keep download size small while trying to keep the product visually appealing.
      A lot of places that I see now, if they didn't choose to use the CSS or didn't know how, I just see huge pictures to do the place of a small picture used smartly.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    5. Re:lol know nothings by Daemonik · · Score: 4, Insightful

      Okay, no app developer is going to use assembly, because their app will be on a range of hardware from different manufacturers. Portability is mandatory in the app world.

    6. Re:lol know nothings by tbuddy · · Score: 5, Informative

      Total bullshit. LinkedIn, for example, is 247 mb uncompressed of frameworks and 1.6 mb of images, 14.9 mb of language localizations for the 25 languages it supports.

    7. Re:lol know nothings by Applehu+Akbar · · Score: 2

      Even within Apple's walled garden, app developers must write for an increasing array of different screen sizes, and to take advantage of optional hardware like Touch ID when available.

    8. Re:lol know nothings by Anonymous Coward · · Score: 5, Interesting

      Actually, they ARE re-using code. These days every schmoe has a library that is "built on" some other schmoe's library. You can't even flush the urinal without going through 99 million layers of schmoe software. It's schmoes all the way down.

      These clowns are worried about size -- frankly, it's a damn miracle that any of it even functions at all.

    9. Re:lol know nothings by Anonymous Coward · · Score: 0

      how is facebook simplistic? it needs to:

      track your location at all times - it can get GPS coordinates from the phone, it doesn't have to run it's own processes
      record everything via the mic even when backgrounded - again, use the phone
      send you push notifications when your gradeschool girlfriend makes a post about how men suck - this actually has nothing to do with the app
      deliver you the quality ad content you deserve - ad content is hosted online, else it would be immediately stale
      let your HR department creep on your comings and goings because they have nothing else to do - also has nothing to do with the app
      support hashtaggings - # - so much code used there!

      Even an app as craptacular as Facebook doesn't need to be that large.

    10. Re:lol know nothings by maestroX · · Score: 1

      Don't forget it requires HHVM because that's so much faster than PHP ;-P

    11. Re:lol know nothings by Anonymous Coward · · Score: 0

      I gather that developers nowadays don't understand basic TI things like "bytes" or "computational resource optimization". We are living the age of absolute TI resources waste just because we can afford it and current development people hardly have any incentive to care.

    12. Re:lol know nothings by Anonymous Coward · · Score: 0

      It's the same as websites these days. They pull in a hundred different libraries to use a function or two out of each. Because they think writing a few of your own functions has a cost but somehow learning a hundred frameworks and transferring them on every connection don't.

    13. Re:lol know nothings by Anonymous Coward · · Score: 0

      VECTOR graphics you koon.

    14. Re: lol know nothings by tigersha · · Score: 2

      This. And in order to render HTML one library happens to be an entire browser. This is the case for Electron apps

      --
      The dangers of excessive individualism are nothing compared to the oppressiveness of excessive collectivism
    15. Re:lol know nothings by Anonymous Coward · · Score: 0

      I remember a nice trick I found on the web that I used for Windows XP (back when Ubuntu and Vista were around barely). Create a two pixel or four pixel, six pixel bmp image, set it as a stretched wallpaper. You get a nice gradient background for free!

      I think .bmp is supported in all browsers (not sure about historical or mobile ones), should have a smaller file size than .png for such contrived use.

    16. Re:lol know nothings by tatman · · Score: 1

      this is it! no one can just write their own code any more. they gotta download a library. and as you stated, that has to download another library and cycle repeats.

      --
      I've always said English was my second language. Had Romeo and Juliet been written in C, I might have understood it.
    17. Re:lol know nothings by Zocalo · · Score: 1

      Those proportions seem sane enough, at least from looking at the contents of packages on Android, but unless iOS does things very differently I doubt that the frameworks are going to be entirely code either. The next step would be work out how much that 247MB is actual code, how much is images or other media resources, localizations, and even other frameworks (which may contain their own non-code resources and other frameworks...)?

      More importantly, and I suspect the main reason for the bloat, even when you get down to the actual code how much of the code provided by the frameworks is actually used by the app? The answer is probably not a great deal, and if you're linking in several humongous frameworks just for a handful of the routines they provide then unless your optimization and linking can strip that redundant code out then you're going to end up with exactly the kind of bloat described.

      --
      UNIX? They're not even circumcised! Savages!
    18. Re:lol know nothings by skids · · Score: 5, Insightful

      How code re-use works on a real linux distro:

      1) application A wants to perform operation B
      2) application A depends on libB
      3) A bug in libB is discovered that prevents Application C from using it
      4) Application C embeds a fixed version of libB
      5) libB eventually gets upgraded while maintaining ABI compatibility
      6) Application C drops its embedded version of libB and resumes sharing the system libB by depending on it with a version restriction in their next version

      How code re-use works on andriod:

      1) application A wants to perform operation B
      2) Luckily android happens to have libB preinstalled (for argument's sake) so application A just uses it
      3) A bug is discovered in the preinstalled libB that prevents Application C from using it
      4) Application C embeds a fixed version of libB
      5) nothing happens for a year or so until all major carriers upgrade the whole OS
      6) The whole OS gets upgraded and other things in the upgrade break both application A and C even while libB gets fixed
      7) The authors of application A and B say "screw this, that sucked" and embed their own copies of everything
              so they never have to deal with that kind of mess again.

    19. Re:lol know nothings by Anonymous Coward · · Score: 0

      Never underestimate the power or stupidity of frameworks.

      A good framework can cut out years of labor by providing canned versions of every bit of code that wasn't your application's business logic or content.

      But that means these frameworks may need to include support for liking hotpockets and displaying pictures Guy Fiere at a moments notice.

    20. Re:lol know nothings by Gr8Apes · · Score: 1

      how is facebook simplistic? it needs to:

      • track your location at all times Phone supplied
      • record everything via the mic even when backgrounded Phone supplied - data isn't part of app
      • send you push notifications when your gradeschool girlfriend makes a post about how men suck Phone/System supplied
      • deliver you the quality ad content you deserve Phone/System supplied, data not part of app
      • let your HR department creep on your comings and goings because they have nothing else to do System supplied
      • support hashtaggings

      So, we have hashtagging sucking up most of 275MB of space. Excellent programmers there!

      --
      The cesspool just got a check and balance.
    21. Re:lol know nothings by dilvish_the_damned · · Score: 1

      Okay, no app developer is going to use assembly, because their app will be on a range of hardware from different manufacturers. Portability is mandatory in the app world.

      And because apps need features to sell, assembly isn't one. At least not here.

      --
      I think you underestimate just how much I just dont care.
    22. Re:lol know nothings by TheCastro1689 · · Score: 1

      Why is this downvoted?

    23. Re:lol know nothings by DontBeAMoran · · Score: 2

      There's the basic problem of all Adobe software making bloated PNGs in the first place. Easily solved if you use a PNG optimization program as you say. Myself, I use ImageOptim when working on websites.

      The problem, however, is probably moron programmers who save everything in JPEG at 100% quality instead of using PNG.

      --
      #DeleteFacebook
    24. Re:lol know nothings by Anonymous Coward · · Score: 0

      Neither particularly insightful nor really relevant.

      Just knowing assembly makes you a better developer with a deeper understanding for your platform and have some healthy respect for it's limitations.

      Nobody said you should write your apps in it.

    25. Re:lol know nothings by Immerman · · Score: 1

      As I recall that's basically how iOS (used to?) handle custom button styles - you just provide it with a small image that was almost all border, and it would gracefully stretch the middle portions horizontally and vertically as required for whatever size you needed while preserving the corners and border gradients. One of the more elegantly handled methods I've encountered.

      It does seem like a lot of modern app programmers completely ignore even such reasonably simple optimizations though, which is a real shame, especially for those of us who prefer to stick to fairly low-end phones.

      --
      --- Most topics have many sides worth arguing, allow me to take one opposite you.
    26. Re:lol know nothings by DontBeAMoran · · Score: 1

      Ladies and gentlemen, we have a new meme: It's librairies all the way down.

      --
      #DeleteFacebook
    27. Re:lol know nothings by Anonymous Coward · · Score: 0

      and HOW is this mobile related?

    28. Re: lol know nothings by Anonymous Coward · · Score: 0

      Why is this just being asked now? This has been a problem for a while. Using angular the functionality is down to about 100k but with all the assets it's about 12mb. This is a s a bad design on Apple's part.

    29. Re:lol know nothings by Creepy · · Score: 1

      Good luck with the assembly language part. Have you tried optimizing in assembly language in a modern processor? Out of order execution and compiler optimizations for it make compilers often more efficient than good assembly coders.

        The real reason apps are bloating is that apps are never finished and the creators keep adding on features. Look at the traditional game market (pre-DLC) - in the game world, the game was written, sent out the door, and was finished. If the developer wanted to add more features to the game, they'd write a sequel. In the app market, that was never the case. Facebook wants to be the be-all, end-all application people use, so they added bloated features like Messenger. On mobile that was forked out into a separate app, but the web version has it built in.

    30. Re:lol know nothings by hord · · Score: 1

      From what I have seen via Docker and other container technologies, what you have with mobile apps is basically a small O/S image that can be easily tested and pushed to many devices. The 247MB probably contains entire libraries that are never even touched since they are just wholesale pulled in from a dependency list that "works". The core install of Perl, for example, is 77MB before you start messing with CPAN. If you have even one part of your app that uses Perl, you just installed 77MB worth of data and code to your machine image.

    31. Re:lol know nothings by Creepy · · Score: 1

      Yeah, not to mention that if the application is running in html5 javascript (i.e. web), it is entirely text probably including programmer comments. Often applications are written in this for the web and the functional parts repackaged as apps. My former job did exactly that - had a React UI (for stuff in the canvas) and AngularJS WebGL application that wrote to a web page canvas with hooks to real application functionality around it. The app I worked on was all native for the device except for the parts in the canvas. React and AngularJS alone can kill older phones (they are decent sized libraries). I'm actually ditching Angular on the app I'm personally working on to reduce overhead (the parts I needed it for can be rewritten fairly easily, I don't really need MVC, and the sorting I need is easy to do in javascript - quicksort will do it). Next up may be Howler.js - it is overkill for the html5 sound I need.

    32. Re:lol know nothings by 93+Escort+Wagon · · Score: 1

      Don't forget it requires HHVM because that's so much faster than PHP ;-P

      I think you're confusing the server side of things with the client side.

      --
      #DeleteChrome
    33. Re:lol know nothings by MachineShedFred · · Score: 5, Insightful

      It's a good comparison, except that step 6 on the Android list very rarely happens at all.

      --
      Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
    34. Re:lol know nothings by 93+Escort+Wagon · · Score: 5, Insightful

      Here's something I really don't get.

      The blogger - and many of the responders here - are debating the size of LinkedIn's app. But, given the bad things we know that LinkedIn has tried to do with that app on more than one occasion... why does anyone even consider having that piece of malware on their phone at all?

      --
      #DeleteChrome
    35. Re:lol know nothings by Khyber · · Score: 1

      "because their app will be on a range of hardware from different manufacturers"

      Uhh, in case you don't know, they all use the same underlying hardware architecture. It's called ARM. And ARM ASM ten years ago is the exact same as it is now, with extra features added.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    36. Re: lol know nothings by Anonymous Coward · · Score: 0

      I aagree. The problem is when apple decides you do t need an expansion slot so you're stuck with the 8gb they give you. The OS eats half of it. So you get 4gb to install apps, hold some music, photos, and {dirty} help you is you want to take a video.

    37. Re:lol know nothings by Pahroza · · Score: 1

      If I had to guess, because it missed the obvious sarcastic joke.

    38. Re:lol know nothings by SirSlud · · Score: 1

      The actual reason these apps are ballooning is size is because developers nowadays are complete shit and don't understand code reuse, optimisation or assembly language.

      Funny you'd have that sentiment while simultaneously outing yourself as clearly not a programmer.

      --
      "Old man yells at systemd"
    39. Re:lol know nothings by Tool+Man · · Score: 1

      Good point. I got bitten, and uninstalled LInkedIn's iOS app after my contacts got uploaded without asking. As in, getting notifications later like "Invite [nickname] to LinkedIn", where [nickname] exists only in my contacts.I can still pull up the site in the phone browser if I'm so inclined, but there is zero value in having its spammy, creepy, intrusive self pestering me.
      Ditto with Facebook's app. Again, it's useful TO ME to control what info it has and what it does, so I use it from the browser and not their app. It didn't hurt to notice that the space taken up was over 400MB. The app was nicer to use than the browser on the phone, but the bloat and lack of control convinced me otherwise.

    40. Re:lol know nothings by painandgreed · · Score: 1

      Even an app as craptacular as Facebook doesn't need to be that large.

      App? Why are people even bothering to complain about apps taking too much space? have you checked the RAM requirements of things like the webpages of Facebook or Office 365? I've caught both taking up to 3GB of RAM, just for a web page!

    41. Re:lol know nothings by unrtst · · Score: 1

      if you're linking in several humongous frameworks just for a handful of the routines they provide then unless your optimization and linking can strip that redundant code out then you're going to end up with exactly the kind of bloat described.

      I think that's exactly the point. This is just one of the areas where there is little focus on optimization, and it's ridiculous. The problems exist across the board...
      * assets may not be optimized
      * assets may be redundant (including assets for many platforms in one package, rather than packing for specific targets)
      * frameworks may be redundant (multiple apps using same libraries, but packaging within the app due to poor/inconvenient library handling in the OS)
      * frameworks are bloated (if they were broken into smaller function groups, then they wouldn't have to include all of it to get the handful of functions they use)
      * apps aren't stripped (there is some of this happening, but obviously not as much as could be done, especially WRT libraries/frameworks)
      * they just don't care... when an app grows 10-20x's in size, but doesn't gain any significant features, they should be asking themselves WTF

      I'm slightly curious if a deduping filesystem could help. I suspect most things get compressed and stay somewhat packaged up, so this may not be feasible today, but, if all apps were fully extracted onto a deduping filesystem, how much of the bloat would vanish due to duplicate frameworks (or pieces of frameworks)? Maybe that'll have almost no effect though, due to how these frameworks slap everything in one blob and version bits... still seems like that'd have some potential though.

    42. Re:lol know nothings by bytestorm · · Score: 1

      Pretty sure this is the old meme. See reference npm left-pad fiasco.

    43. Re:lol know nothings by Anonymous Coward · · Score: 0

      Because smartphones typically have 16GB of storage total, with the OS taking a chunk of that, and because most people have limited monthly data available, which huge, frequent updates eat into quicker.

      (And in before "modern iPhones start at 32GB"; typical storage over smartphones. Older iPhones exist, as do Android devices, and app bloat isn't limited to the latest Apples.)

    44. Re:lol know nothings by Zumbs · · Score: 1

      The next step would be work out how much that 247MB is actual code, how much is images or other media resources, localizations, and even other frameworks (which may contain their own non-code resources and other frameworks...)?

      If I recall correctly, one feature of Android since 4.x is that if you want to use a new feature not available on earlier Android versions and still want to target earlier Android versions with the same app, the updated parts can be included in your app. Could be that was what happened here?

      --
      The truth may be out there, but lies are inside your head
    45. Re:lol know nothings by AAWood · · Score: 1

      What, your smartphone isn't running Windows XP?!?

    46. Re: lol know nothings by minstrelmike · · Score: 1

      Same old same old. I remember folks wanting to make DOS prompts prettier and error messages brighter. They quickly ran into the 640K barrier. Bling sells (and costs).

    47. Re:lol know nothings by Dog-Cow · · Score: 1

      If you regularly come across moron programmers like that, you need to find a new place to live, or at least work. No iOS programmer does that.

    48. Re:lol know nothings by Anonymous Coward · · Score: 0

      Apps on a mobile platform, and Docker, should be vastly different things.

      If they aren't, then there is something very wrong with the mobile app platform.

    49. Re:lol know nothings by Anonymous Coward · · Score: 0

      Mod parent up!

      The number of Android phones financed for two years that get a year or less of OS updates, while the apps sojourn on, is ridiculous.

    50. Re:lol know nothings by mikael · · Score: 1

      Workstations had this problem in the past. Every application, command line utility, shell utility was statically linked to whatever libraries they used. Every command line utility ended up using 10 megabytes of storage or more just for the standard IO libraries. So they invented dynamic linking and that saved a large amount of space by having a single copy of every library in use in memory. But then applications end up using hundreds of different libraries on both Windows and Linux. Then leading to DLL Hell when they don't match (32 bit vs. 64-bit, 4K vs 8K kernel space, instruction set extensions).

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
    51. Re:lol know nothings by TheRaven64 · · Score: 1

      True. Your app is going to run on ARM devices, other ARM devices, and possibly even a third kind of ARM device.

      --
      I am TheRaven on Soylent News
    52. Re:lol know nothings by flargleblarg · · Score: 1

      And ARM ASM ten years ago is the exact same as it is now, with extra features added.

      There are some pretty serious differences between 32-bit and 64-bit ARM.

    53. Re:lol know nothings by flargleblarg · · Score: 1

      Yeah, not to mention that if the application is running in html5 javascript (i.e. web), it is entirely text probably including programmer comments. ...

      What are these “programmer comments” of which you speak?

    54. Re:lol know nothings by DontBeAMoran · · Score: 2

      I work as a front-end and back-end Web developer. You have no idea how many times users, clients and even developers do this mistake. Somewhere, there's a tutorial about file formats, teachers, FAQs or something that teaches things the wrong way.

      I call it the "JPEG for everything" syndrome. I once taught a lesson to a friend who kept doing this. One day he asked for an Excel file and I sent it a screen capture of the data, saved in JPEG at 1% quality.

      --
      #DeleteFacebook
    55. Re:lol know nothings by tepples · · Score: 1

      And ARM ASM ten years ago is the exact same as it is now, with extra features added.

      AArch64 assembly language isn't the same as 32-bit ARM assembly language, and even within 32-bit, ARMv7 adds several instructions not in ARMv6.

    56. Re:lol know nothings by Anonymous Coward · · Score: 0

      The applicationg authors should be horse-whipped for wanting their applications to work well Shame on them

    57. Re:lol know nothings by Megol · · Score: 1

      That means that ARMv6 code is forwards compatible with ARMv7 but ARMv7 code isn't backwards compatible with ARMv6. In other words the old assembly code written to the ARMv6 target will still run on later processors.

      Aarch64 is a completely different ISA from the same company.

    58. Re:lol know nothings by Megol · · Score: 1

      IMO that's the real problem with todays software - not too little reuse but too much reuse in the form of bloated incestuous libraries.

    59. Re:lol know nothings by OrangeTide · · Score: 1

      This old grognard knows about the differences between JPEG, PNG and BMP. Let's stop using PNG in our applications for the rectangular images that don't need an alpha channel. (JPEG style algorithms are not great for alpha layer compression)
      Also you can do a fair bit with SVG and bitmap textures (PNG or JPG). But the tools kind of suck for creating them.
      And in terms of UX, sometimes a simple color scheme or gradient looks nicer than complex 8K scenery/photographs that you want to use. Plus if it's simple enough you can specify it as vector graphics and scale it to any size you want.

      --
      “Common sense is not so common.” — Voltaire
    60. Re:lol know nothings by Megol · · Score: 1

      Good luck with the assembly language part. Have you tried optimizing in assembly language in a modern processor? Out of order execution and compiler optimizations for it make compilers often more efficient than good assembly coders.

      That meme is old (at least since the 80's) and still not correct. A skilled assembly programmer can do better than a compiler due to the lower level of abstraction, that will be the case until the processors actually run high-level programs in hardware. That compilers have improved and processors are optimizing execution towards compiler generated code just decreases how large the assembly advantage will be and how often the increased effort of using asm will pay off.

      The meme will never be true. Assembly language provides a skilled programmer with a more direct interface to the execution hardware that the higher level language just can't give.

    61. Re: lol know nothings by KGIII · · Score: 1

      In my head, PNG stands for Pretty Neat Graphics. I've never bothered to find out what it really stands for.

      No, I don't actually have a point. I just wanted share.

      --
      "So long and thanks for all the fish."
    62. Re:lol know nothings by Desler · · Score: 1

      Good luck with the assembly language part. Have you tried optimizing in assembly language in a modern processor? Out of order execution and compiler optimizations for it make compilers often more efficient than good assembly coders.

      This is bullshit. It's easy to beat a compiler at SIMD optimization as auto-vectorization is still mostly universally crappy. If you don't want to write straight up assembly you need at minimum compiler intrinsics because without them the compiler will almost always just generate shitty, slow scalar code.

    63. Re: lol know nothings by KGIII · · Score: 1

      Slashdot has never stayed on topic. Hell, we don't even read the summary, never mind the article.

      If you're expecting on topic replies, not even filtering by moderation will help. Good luck with your quest.

      --
      "So long and thanks for all the fish."
    64. Re: lol know nothings by Anonymous Coward · · Score: 0

      Judging by the primary use case, it's "Pictures of Naked Genitals". Compare with the previous standard, "Just Pictures of Exposed Genitals" and the classic "Genitals In Files".

    65. Re:lol know nothings by Pseudonym · · Score: 1

      In case you didn't know, a lot of Android tablets are x86.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    66. Re:lol know nothings by ichimunki · · Score: 1

      Thank you. Thank Medium link made my day.

      --
      I do not have a signature
    67. Re:lol know nothings by Carewolf · · Score: 2

      It is much, much, much worse than that.

      Chrome for instance, has four separate copies of zlib. The copy used by most Chrome code, the copy in Skia, the copy in Pdfium, the copy used by libpng, and I might be forgetting some... They solve link time problem by prepending every copy with a separate prefix.. You know, you discover you are doing something retarded, and solves it by double down and making it more retarded.

      This is the future: Utter crap!!

    68. Re:lol know nothings by Daemonik · · Score: 1

      In case *you* didn't know, most of those ARM CPU's are part of a SOC with a mix of graphics/audio/video/networking tied into the same chip, all of which can be manufactured and cross licensed from other people. Not to mention that ARM licenses out their basic core, chip developers are able to add their own functionality as they choose. So assembly code that works on a Samsung SOC isn't necessarily going to work on an Atmel chip.

      iPhones use an ARM chip, but try getting iOS to work on a Google Pixel :P

    69. Re: lol know nothings by Anonymous Coward · · Score: 0

      Things change. Always aim for a standard higher than it is, and let the next generation benefit.

    70. Re: lol know nothings by Brockmire · · Score: 1

      That taught him you're an asshole. Seriously, you think you taught him a lesson? Fuck, you are full of yourself.

    71. Re: lol know nothings by Brockmire · · Score: 1

      App developers are not embedded developers. Not all embedded developers should call themselves that. Also, modern C compilers often get optimized to the same assembly as you'd hand code. At least from reading a thread where a guy went through 4 compiler optimizations and compared the output to see how optimized the options were. Conclusion: I don't really need to code in assembly anymore.

    72. Re: lol know nothings by KGIII · · Score: 1

      Black Man's Penis

      --
      "So long and thanks for all the fish."
    73. Re: lol know nothings by reboot246 · · Score: 1

      So that's why all those .bmp files are so damned big!

    74. Re:lol know nothings by Atryn · · Score: 1

      True. Your app is going to run on ARM devices, other ARM devices, and possibly even a third kind of ARM device.

      Now now, third arms just make you look weird.

      --
      Come play Moral Decay!
    75. Re:lol know nothings by Anonymous Coward · · Score: 0

      What about the kernel? and then the drivers? cpu microcode?

    76. Re: lol know nothings by DontBeAMoran · · Score: 1

      That's after trying to teach him to use the proper format for given images.

      If you saw workers on a construction site using hammers to punch screws into 2x4's, you'd think they were idiots.

      --
      #DeleteFacebook
    77. Re: lol know nothings by Anonymous Coward · · Score: 0

      Image compression exists for a reason.

      True.

      If you neglect to optimize your images, the best compression in the world won't help.

      False. PNG, gif, and even fucking RLE can shrink an image size, especially if it's not photographic.

    78. Re:lol know nothings by ayesnymous · · Score: 1
      > code reuse, optimisation or assembly language.

      The compiler's supposed to do that.

    79. Re:lol know nothings by Khyber · · Score: 1

      No they're not, they're RISC cores implementing part of the x86 architecture and additional featuresets.

      x86 !=RISC

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    80. Re:lol know nothings by Khyber · · Score: 1

      You must be a really cruddy coder to not be able to take advantage of what's called 'base instruction set.'

      It's like you've never really made embedded hardware before.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    81. Re:lol know nothings by Anonymous Coward · · Score: 0

      even if you never write assembly lang directly, it still is useful to know when you're debugging

    82. Re:lol know nothings by Anonymous Coward · · Score: 0

      A skilled assembly programmer can do better than a compiler due to the lower level of abstraction

      A task is to be done. 2 scenarios.

      First: A programmer creates a program to perform that task in a high-level language; we can, essentially, think of that as a description of the task in a language the compiler can understand. A compiler take that high-level description of that task, figures out how to do it, and pumps out a set of instructions for the processor.

      Second: A programmer creates a program to perform that task in assembly. This is already (more or less) the set of instructions for the processors: not quite 1-to-1, but that's a functionally irrelevant tangent for our purposes.

      Here's the thing. If that assembly programmer finds a clever trick that lets them perform a certain action efficiently, they can implement that, sure, great. They can do that thing better than a given compiler at a given point in time. But a compiler isn't doing any magic. It's examining the high-level description of the task and making choices about efficient ways to perform them too, based on how it was programmed. It is the sum of all the clever tricks of everyone who has ever worked on it. Whatever method that assembly programmer is using to make that task go faster, all it takes is for someone working on that compiler to figure out how to identify the same circumstances in the higher-level language, and how to implement that trick, once, and that advantage is gone. Forever.

      Even if they can't do that, even if there's some translation issue at play where the high-level language simply can't describe that task in a sufficient way that a compiler could ever really know that, yes, this is when that clever trick should be employed... it's still just one trick. It has others. To consistently beat that compiler, you need to consistently know ways to implement your tasks that are either none-obvious when that task is described in a higher-level language, or obvious but none-describable within that language, such that the task-specific methods you're using always wind up more efficient than all the description-led, none-specific methods the compiler is built to consider. And you're right, we're not there yet, right now a decent assembly programmer can consistently beat the compiler, but the idea that threshold will never be crossed is ludicrous. The compilers will keep improving, and there are only so many tricks.

      I actually suspect the real limit lies not with the compiler, but the none-assembly programmers (like myself): if the program they write is providing a "description" to the compiler that is inherently inefficient, having apparent needs that in reality serve no purpose to the overall task, the compiler is going to dutifully provide a program that fills all those needs anyway. At that point, we're not talking "assembly programmers vs compilers", but "assembly programmers vs [some language] programmers"... and I'm willing to bet that, if you're making money from programming in assembly, you're probably good enough to win that competition no matter how good the compiler is.

    83. Re:lol know nothings by Anonymous Coward · · Score: 0

      It was a useless comment, but I did use a file less than 10 bytes instead of generating some large uncompressed or png 1024x768 or 1280x1024 picture.
      Used to be Windows didn't support png on the desktop when you disabled Active Desktop, too. So would you use a 1280x1024 24bit bmp, that is 3.75 MB of wasted hard disk space.

    84. Re:lol know nothings by Cinnamon+Beige · · Score: 1

      I'd think you could also have it be so the localizations are compartmentalized enough that you could have it only install the ones relevant--otherwise, at least stick something in the settings so I can switch languages the program's in for my own personal amusement...wait, no, that should have been 'in order to justify having them all installed anyway.' (Yes, I will do that. Being multilingual means it's fun, and the one app I've met that lets me do it has it set up so well that you don't even need to actually know a word of the language the app is in to successfully switch languages.)

    85. Re:lol know nothings by Ann+O'Nymous-Coward · · Score: 1

      But third legs make you really popular! ;}

    86. Re: lol know nothings by TemporalBeing · · Score: 1

      In my head, PNG stands for Pretty Neat Graphics. I've never bothered to find out what it really stands for.

      No, I don't actually have a point. I just wanted share.

      Portable Network Graphic, along with its cousin MNG - Multiple-Network Graphic.

      --
      Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
  2. Natural consequence by gillbates · · Score: 4, Insightful

    This is the natural consequence of choosing languages based on their library support. These languages were chosen for their ease of creating deployable solutions, not for the size of their executables.

    Storage utilization is the user's problem, not the software engineer's.

    --
    The society for a thought-free internet welcomes you.
    1. Re:Natural consequence by Anonymous Coward · · Score: 4, Insightful

      This is the natural consequence of choosing languages based on their library support. These languages were chosen for their ease of creating deployable solutions, not for the size of their executables.

      Storage utilization is the user's problem, not the software engineer's.

      Incorrect. Resource management is the software engineer's problem, not the user's. Using inappropriate amounts of resources is a sign of a poor software engineer who has no idea how to design, code and use resources properly, not a user with an old small phone.

    2. Re:Natural consequence by BasilBrush · · Score: 4, Interesting

      Large size app packages are invariably caused by sizes of assets, not code. In the case of games that's usually inevitable. But for most other apps, it usually means that no engineer has bothered to look at what assets are shipping, and get rid of the ones that aren't used, and think of ways to save space on those that are.

    3. Re:Natural consequence by oh_my_080980980 · · Score: 1

      Except:

      "As app developers, we should be more conscious of the space we use. Take some time to remove the cruft that builds up and push back against needless waste." https://trevore.com/blog/posts...

      So no it's not natural consequences.

    4. Re:Natural consequence by Anonymous Coward · · Score: 0

      Not only the size of the executable, but the processing power that's needed to run them. What should be simple chat programs on my (work)phone keep slowing down the phone to halt ( i admit, it's a very low processing power device, but should be able to use for chatting). And why the hell do they need so many updates anyway. Isn't chat a god damn solved problem already?

    5. Re: Natural consequence by Anonymous Coward · · Score: 0

      and when the user deletes the app, it's not the user's problem..it's the software engineer's problem.

    6. Re:Natural consequence by LordWabbit2 · · Score: 5, Informative

      Wrong, it's the software engineers problem. Most of these apps are huge because the decision was made to go with a framework which would make it easier to build for all relevant platforms without specifically catering for that platform (except maybe UI). Just before my last phone upgrade I was seriously hunting for space, and guess what apps got nuked first?
      The largest that I don't use often or can live without. {{{ That makes it a software engineers problem, not the users.

      If no one is using your application because they consider your flash light app that clocks in at 70mb too big to bother with, then you may as well not have written the software at all.
      Xamarin is a prime example of this, a hello world app is over 16mb (the last time I looked) the same app in native Java is a couple kb.

      --
      There are three kinds of falsehood: the first is a 'fib,' the second is a downright lie, and the third is statistics.
    7. Re:Natural consequence by gillbates · · Score: 1

      There are other reasons. In many large companies, bugs are assigned a priority, and something like "app size too large" would fall well below segfaults and operational bugs. While management and programmer alike may agree that resource utilization is a problem, it is often a difficult issue to resolve because it's an open-ended task, and it can be difficult to tell what "done" means - does it mean reduction of 50%? 90%?

      poor software engineer who has no idea how to design, code and use resources properly

      Yes, but try telling management that they should fire a guy who makes his deadlines more often than not, and who works for a song...

      Some issues are organizational. The guy who ships on time will always be more favored than the one who makes no mistakes.

      --
      The society for a thought-free internet welcomes you.
    8. Re:Natural consequence by LordWabbit2 · · Score: 3, Insightful

      It would be if messaging apps only do messaging, but they keep shoving more and more functionality (not related to messaging) into every app.
      Maybe their logic is that if you are going to uninstall some apps for space you pick the one that is less useful, I don't know. It annoys the crap out of me though because if the only reason you have the app is for messaging, being able to order a pizza through one is fucking useless to me.

      And while I'm on a rant, I hate the fact that more and more websites keep popping up with "It's better in the app!" and nagging you to install their retarded, badly designed, cookie cutter application when all you are trying to do is follow a link on your phone that someone sent to you from their PC.

      Also, why does a torchlight application require access to my contacts? Camera sure, but contacts WTF? It's getting almost as bad as blackberry was before it died.

      --
      There are three kinds of falsehood: the first is a 'fib,' the second is a downright lie, and the third is statistics.
    9. Re:Natural consequence by geekmux · · Score: 2

      Storage utilization is the user's problem, not the software engineer's.

      The CEO from Bloatware, Inc. just called.

      He wants you to stop infringing on his legally protected slogan.

    10. Re:Natural consequence by jellomizer · · Score: 3, Interesting

      Most Apps are not really made by professional software developers. It reminds me back in the early desktop era, where most applications were made by people who had their own problem to solve. Without actual practice in coding, they wrote a program to do what was needed, but without much planning or for-site. Being these computers did one thing at a time, if it took 0.5 second vs 0.01 second wasn't a big deal, because it didn't affect other systems. So if you wanted a pause you can figure out the speed of your cpu and just loop x thousand of times. Moved to a multi-tasking system, that is great way to kill your jobs.

      Now companies are trying to race to Device Apps. But except for bringing in the old developers and get them to learn the new software, they hire flashy new App developers, who have Objective C and Swift and all the buzzword systems on their resumes, but not people with experience with coding, and for these new devices, which are relativity low powered, the talent to think about system resources.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    11. Re:Natural consequence by Anonymous Coward · · Score: 0

      Isn't chat a god damn solved problem already?

      Considering that every other month there's a new $50 billion startup with nothing to offer the world except a minor variation on text messaging, apparently not.

    12. Re:Natural consequence by Anonymous Coward · · Score: 0

      That's a bit difficult to do when it's Google's apps that are hogging up all the memory with updates. I used to be able to run Skype off my old LG smartphone, but by the time all those apps have updated, I then need to uninstall them in order to allow Skype to update.

    13. Re: Natural consequence by Anonymous Coward · · Score: 0

      There's nothing native about java.

    14. Re:Natural consequence by Anonymous Coward · · Score: 0

      And why the hell do they need so many updates anyway.

      Telemetry, keyloggers, ads, spyware....

    15. Re:Natural consequence by Anonymous Coward · · Score: 0

      And while I'm on a rant, I hate the fact that more and more websites keep popping up with "It's better in the app!" and nagging you to install their retarded, badly designed, cookie cutter application

      That's why its generally better that the site don't even know you are on a phone/tablet. Just change the browser agent and be happy. Apps are just a doorway for further private info access abuse.

    16. Re:Natural consequence by beelsebob · · Score: 2

      From what I understand of the chaos at some of these companies (particularly FaceBook and Twitter), it's got more to do with the lack of engineering discipline, and a lack of good quality engineers.

      Facebook at one stage had 17,000 classes in their app. Most of them duplicated each other, but because the whole app is just a wild west of development, no one knows, or cares what their code duplicates.

      It's more important to throw in the new feature than to make sure the code is structured in a sensible way.

    17. Re:Natural consequence by beelsebob · · Score: 1

      The prioritisation of these bugs is indeed a problem, but I would argue that the problem is not with prioritising bugs, it's directly with how people think that these particular bugs should be prioritised.

      Significant size, performance, and power regressions should be considered right up their with the operational bugs, and severe ones should be considered more important. The only bugs that should beat them out should be security bugs (which I guess means most crashes too).

    18. Re:Natural consequence by beelsebob · · Score: 5, Interesting

      Actually, that's not true. Facebook for example is huge because of code size, not because of asset size.

      They have literally thousands of classes for a super simple application. In fact, their code is so large, unwieldy and complex that they wrote an entire IDE, because the traditional IDEs couldn't deal with the sheer amount of code they have.

      I don't know why it didn't occur to them to just write better code, but apparently it didn't.

    19. Re:Natural consequence by Shotgun · · Score: 4, Insightful

      In this world, the software engineer's problem is getting paid.

      The software companies problem is adding candy to the app to get you to choose it over the other app, and installation size doesn't get considered. The Google PlayStore doesn't even tell you how large an app is until you decide to install it.

      So the situation is that the company gets judged on how fast "features" get added...engineer gets judged on what and how quickly she adds features. The fastest way to add a feature is to add a library that supplies it. Eliminating cruft earns no points, so no one works for it, but learning a new library will make the engineer's resume look better, so he might choose to add one even if the library used in a different part of the code would do the job.

      The result is that what is rewarded get optimized.

      --
      Aah, change is good. -- Rafiki
      Yeah, but it ain't easy. -- Simba
    20. Re:Natural consequence by ceoyoyo · · Score: 1

      Precisely. Only when users solve their storage utilization problem by deleting the bloated software will it become a problem for the engineers.

    21. Re: Natural consequence by Anonymous Coward · · Score: 0

      As users are more likely to buy new phone with more storage than delete an app they use this is not generally a problem for apps that deliver desired functionality.

    22. Re:Natural consequence by Anonymous Coward · · Score: 0

      This is not correct. Storage utilization is indeed a concern of the developer. If you're making an application, choosing what frameworks to include, if any, is important. So is the file size of any graphics. Beyond the size of the application itself, what if it creates data on the user's device? Are you able to do so with a good compression algorithm, if it makes sense? If you need to push out updates to the app, do you understand the effect the transfer of that file will have on both the networks used to transmit it and, in the case of mobile users, the effect it will have on their data plan?

      These are all things that relate to file size that should indeed be considered when building an app.

    23. Re:Natural consequence by Anonymous Coward · · Score: 0

      Yup, just write it in the new "safe": languages, like Rust... on Linux "Hello World" creates a 2.2 megabyte executable!!!! What The?

      Way back when, WordStar - came on ONE 360k floppy disk. The mailmerge and spellchecker were another WHOLE floppy. OMG, TWO diskettes!!!!

      Firefox - one megabyte per version number. Firefox 3 was 3MB, Firefox 56 is 56MB. PS - (hint) I do NOT need notetaking etc IN my browser.

    24. Re:Natural consequence by Kjella · · Score: 1

      The largest that I don't use often or can live without. {{{ That makes it a software engineers problem, not the users.

      Well if I put on my manager hat I'd say "So our application was not important enough for him to keep?", "You mean he cleaned out the back closet of apps he barely or never used anyway?" and "If it was nice-to-have, he'll probably install it again once he gets more space." Even Apple who is the most overcharged of overchargers only took $100 to upgrade my iPhone SE from 16GB to 64GB, which makes app space a total non-issue. Freeing up 100MB of space should be worth about 100/(48*1024)*$100 = $0.20. If you got SD slots, I imagine much less. So really.... is this the problem you would focus on? If so you're the kind of engineer that needs to be managed.

      --
      Live today, because you never know what tomorrow brings
    25. Re:Natural consequence by Dusty · · Score: 4, Interesting

      The writers of the Halide app also went into this:-
      One Weird Trick to Lose Size.

    26. Re:Natural consequence by crafoo · · Score: 1

      I hope everyone is enjoying 40GB PC game downloads that contain audio files for voice acting in all 8 languages.

    27. Re:Natural consequence by Anonymous Coward · · Score: 1

      Well, there's a difference in app sizes between Android and Apple as well.

      For whatever reason, packaged Android apps are usually in the tens of megabyte sizes. Apple apps are typically 80 - 160MB in size.

      I suspect the difference is caused by the linking stage. The only reason I can think of for Apple apps being that large is that all of the required libraries are statically linked into every single application and that there is no common runtime like the different versions of Android, but that is pure speculation on my part.

    28. Re:Natural consequence by Anonymous Coward · · Score: 1

      Wrong attitude. I didn't install Facebook messenger because I was sick of the size and battery drain of their original app. When they made it hard for me to send messages via my mobile browser, I just stopped messaging from my phone. They lost a user permanently, and others in my circle too. I've learnt I don't need their app(s) - is that what you want from your user base?

    29. Re:Natural consequence by Malc · · Score: 1

      I can't really tell what their app does now that it didn't do before when it was much smaller. I think they removed messaging and added lots of annoying advertising. They constantly want to send me updates, but I don't see why I should bother because I'm just seeing decreasing value.

    30. Re:Natural consequence by Anonymous Coward · · Score: 2, Insightful

      wrong. it's a sign that the app wasn't created by a 'software engineer' at all... but rather, by a poorly trained, poorly educated, inexperienced h1-b visa holder or online freelancer, whose poorly paid job it is is to crank out apps fast.. and the bigger apps and more frequent updates means the visa holder is just trying to justify their petty existence, or some other freelancer is trying (and failing) to clean up a mess of bugs some other one left behind.

      the real 'software engineers' were the guys that crammed defender or space invaders into a 4k rom cartridge. app makers are NOT 'engineers'.

    31. Re:Natural consequence by Anonymous Coward · · Score: 0


      This is the natural consequence of choosing languages based on their library support.

      You're putting the cart before the horse. This isn't a technical problem, it's a human problem. Humans have decided to privilege ease of development over executable size. That lead to just throwing more libs in the app willy-nilly. It's not the languages fault that the developer decided to throw in a 10 MB library for one function that does one simple thing because he/she didn't have time to do it more efficiently.

      This is a solvable problem, but it involves software producers deciding to actually care about these executable sizes, and putting limits on them. That's the only way it'll happen. Individual software developers aren't going to change this because they're generally at the mercy of management who wants features-features-features fast-fast-fast.

    32. Re:Natural consequence by Anonymous Coward · · Score: 0

      Android supports many display densities and different assets may need to be embedded into the apk to support all of them. Unfortunately, for a given device, only one display density set of assets will actually be used. Publishing multiple apks for different devices or dynamically downloading the graphics on the fly may be required to reduce the storage requirements.

      https://developer.android.com/guide/practices/screens_support.html#range

    33. Re:Natural consequence by Anonymous Coward · · Score: 0

      There was an interview/documentary about FB in which they revealed that the first 5+ years or so of Facebook, the website was a 900mb executable file that just got copied between servers. I don't think writing better code has ever been their concern.

    34. Re:Natural consequence by Anonymous Coward · · Score: 0

      I think it's outrageous too but I believe Facebook has done a ton with PHP and other server-side codes that execute in-browser. The problem is that the mobile browsers don't run all that and their app has to mimic all that server stuff, so the app is bloated.

      But Messenger...I don't know how it takes almost 200MB to have an instant messaging program.

    35. Re:Natural consequence by Anonymous Coward · · Score: 0

      Even Apple who is the most overcharged of overchargers only took $100 to upgrade my iPhone SE from 16GB to 64GB, which makes app space a total non-issue.

      So the onus is on the end-user to spend more money to accommodate useless bloat? You are the type of engineer who graduated in the bottom of his/her class.

    36. Re:Natural consequence by 93+Escort+Wagon · · Score: 1

      I don't know why it didn't occur to them to just write better code, but apparently it didn't.

      When you're trying to conquer the world, you can't be bothered with trifles.

      --
      #DeleteChrome
    37. Re:Natural consequence by Anonymous Coward · · Score: 0

      If Apple didn't have such low storage sizing on their phones, it wouldn't be an issue. Just a few years ago 8GB was the base model storage. Just recently they did bump it to 32GB but even that is not enough. The minimum should be 64GB now.

    38. Re:Natural consequence by Anonymous Coward · · Score: 0

      }}}

      You forgot those.

    39. Re: Natural consequence by tepples · · Score: 1

      LordWabbit2 may have used a misnomer, but the intended meaning is as follows:

      Unlike the system libraries for Xamarin, the system libraries for a Java dialect are included with the Android operating system.

    40. Re:Natural consequence by Anonymous Coward · · Score: 1

      Cost and time of "rewriting the whole thing." I deal with the consequences of letting bad code foster all fucking day.

      "So how long would it take to rewrite the whole front end?"
      "12 months"
      "I see, can't you just rewrite this page to use this new... what did you call it.. framework?"
      "Yes"
      "How long would that take?"
      "3 Months"
      "OK DO IT"

      Some time later
      "Can you add this button that does that to the menu? How long would that take?"
      "2 weeks"
      "But it's just a button!"
      "Well if I rewrote the whole app last year, it would take me 5 minutes to add this button, but now it will take me 2 weeks"

    41. Re:Natural consequence by Anonymous Coward · · Score: 0

      I worked for a company where the marketing team would gin up management on the great things A, B, and/or C would bring.

      Then management would tell IT and the developers to make A, B, and/or C happen.

      By the time we were invited into the discussion it was too late to tell the Mahogany Row folks that what they were asking us to do was going to double the size of the datacenters, triple support cosets, and trash the users device.

      The problem is developers, C level executives, shareholders, marketing departments, and IT management. It's not end users, it's us.

    42. Re:Natural consequence by Anonymous Coward · · Score: 0

      Curious , how did you come across this information? (any links to articles or more information? I'm curious why they needed so many classes...) Also, how on earth did they write an IDE (which are typically very complex!) if they had so many problems with their simple application? You mean they customized something open source like Eclipse to meet their needs better, or did they really write one from the ground up?

    43. Re:Natural consequence by Anonymous Coward · · Score: 0

      I agree that resource management is the software engineer's problem. However, I feel that the wrong question is being asked. The question should be "Are Apps and their developers out of control?" I think that they are, considering that every single app seems to want permission to access all information on a phone or tablet, and send information back to what I consider to questionable entities. Why do the simplest of apps need access to every bit of data on the phone or tablet, and internet access to to send that (stolen) data to who knows where? The answer is that they don't!

      Collection and sale of people's personal data has become a huge business...one that in my not at all humble opinion needs to be stopped. Outlawed totally, killed dead. NOW!

      What is really needed are Operating Systems for people's personal devices (phones, tablets etc...) that give people total control of their devices. By total control I mean that any default app that came pre-installed can be removed, and that the user can control exactly what permissions to grant each app on an individual app and individual permission basis. That also means that our personal devices need unbreakable encryption. As in its not possible to get any info whatsoever from a device without the owner's pass-code. Period!

      In other words, our personal devices need to be truly ours to control completely instead of being the devices that are used to spy on us on a daily basis!!

    44. Re:Natural consequence by Anonymous Coward · · Score: 0

      YGBSM.

      It could be written in PERL, with an entire runtime shell, and that would barely be a drop in the bucket.

      The problem is, quite simply, that every image you see on the screen is a "layer cake" of 24-bit PNG files; with different versions optimized for different screen resolutions.

      As Apple has come out with new devices with different densities, they've added layers.

      Here's the app that I use to generate my assets. Check out how many it makes.

      You don't HAVE to add every image layer, but your app can look like crap if you don't. You can also do the same kind of optimizations that you do for Web pages (like reduced-palette indexed PNGs and whatnot), but that's a lot of work, and adds a lot of overhead to release engineering and CM.

      Apple is working on the problem, in that the newer OSes are using some kind of JIT installation that's supposed to do stuff like strip out assets that don't fit the profile of your device. We'll see how effective that is.

      I write these apps. I should know; but that probably means my comment will be down voted into the dust in favor of all the AppleHater posts.

    45. Re:Natural consequence by Rockoon · · Score: 1, Interesting

      psst:

      The base size of a class is 0 bytes.

      The number of classes is irrelevant. Even if each line of code produced 100 bytes of binary which is a very generous to your position value, and the software is 200 MB binary, that still means 2 million lines of code, right?

      Why does facebooks app have 2 million lines of code?

      The answer is: IT CERTAINLY DOESNT
      The answer is also: YOU DONT KNOW WHAT YOU ARE TALKING ABOUT
      The answer finally is: STOP MAKING THINGS UP

      My guess is crap like a language support pack is done poorly using grossly inefficient data hierarchy format(s) and that these language support packs just keep growing in size and number and that the whole language support monstrosity is shipped to everybody.regardless of what language they speak.

      --
      "His name was James Damore."
    46. Re:Natural consequence by Anonymous Coward · · Score: 0

      I'd say MVP focused development strategies factor in quite a bit.

    47. Re:Natural consequence by Anonymous Coward · · Score: 0

      Don't forget that for the Apple world, they have been making a few architecture transitions, and in doing so have been distributing so-called "Fat" binaries that contain the binaries for both architectures. For example, 32- and 64-bit both. They're dropping the hammer on 32-bit fairly soon here, so we'll probably start to see app sizes reducing as new versions come out that no longer contain the legacy binaries.

    48. Re:Natural consequence by Glarimore · · Score: 1

      Storage utilization is the user's problem, not the software engineer's.

      Uh, no. It may not be "the software engineer's problem", since they are often just coding to spec, but it is certainly not the user's problem. The user may have to deal with the annoyance of storage limitations presented by the app, but it's the responsibility of the app manufacturer to avoid the limitation in the first place or to mitigate it once identified.

      Dismissing the problem and putting it on the stakeholder is a sure-fire way to lose customers.

    49. Re:Natural consequence by MachineShedFred · · Score: 1

      this actually explains quite nicely what the fuck happened to my 512GB SSD...

      --
      Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
    50. Re:Natural consequence by Anonymous Coward · · Score: 0

      This reminds me of when a developer on my team at work was working on a report, and added a python library that made his development faster in order to get it done, and that library download and compiled FORTRAN on installation. It added 20 minutes to the deployment time for the application to the servers, and I had to pitch a major fit to get them to refactor it for the one or two functions they were using from that library, because rolling hotfixes were no longer an option due to laziness.

    51. Re:Natural consequence by parkinglot777 · · Score: 1

      There are other reasons. In many large companies, bugs are assigned a priority, and something like "app size too large" would fall well below segfaults and operational bugs. While management and programmer alike may agree that resource utilization is a problem, it is often a difficult issue to resolve because it's an open-ended task, and it can be difficult to tell what "done" means - does it mean reduction of 50%? 90%?

      poor software engineer who has no idea how to design, code and use resources properly

      Yes, but try telling management that they should fire a guy who makes his deadlines more often than not, and who works for a song...

      Some issues are organizational. The guy who ships on time will always be more favored than the one who makes no mistakes.

      Storage utilization is the user's problem, not the software engineer's.

      So the storage utilization should NOT be pushed to users as their problem then.

    52. Re:Natural consequence by Anonymous Coward · · Score: 0

      Joke's on you, the user's problems are the software engineer's problems.

    53. Re:Natural consequence by Anonymous Coward · · Score: 0

      Simple solution, do use Facebook and remove the app.

    54. Re:Natural consequence by Anonymous Coward · · Score: 0

      Actually the base size of a class is at least 1 byte.

    55. Re: Natural consequence by KGIII · · Score: 1

      I am too lazy to google and not the OP. I also don't use Facebook. But, it might be Jarvis? I see people mention that, fairly often.

      --
      "So long and thanks for all the fish."
    56. Re:Natural consequence by Anonymous Coward · · Score: 0

      Get your facts straight, PlayStore DOES specify app size in the same way AppStore does. Neither of them has any mechanism to catch apps that have small binaries and download tons of data on first start (mostly games).

      If you are on a desktop, your comment makes not sense at all. If you are on a small screen, you should check for something like "more details" or so.

    57. Re:Natural consequence by Anonymous Coward · · Score: 0

      PHP doesn't execute in-browser so it doesn't matter what the client is, but the rest of your comment is right. One of the most annoying things about Facebook as a website is its overuse of bloated AJAX-y Web 2.0 garbage, and inefficient use at that. I can scroll down a Twitter page through hundreds of tweets and whatever they're using seems to be garbage-collected well. On Facebook I get 3 or 4 pages down and the browser instance is up to 2GB of RAM and I hit a point where it won't even scroll anymore. What the hell.

    58. Re:Natural consequence by Atryn · · Score: 1

      My guess is crap like a language support pack is done poorly using grossly inefficient data hierarchy format(s) and that these language support packs just keep growing in size and number and that the whole language support monstrosity is shipped to everybody.regardless of what language they speak.

      That's getting closer to the issue. It isn't what the app needs, it is what *I* need from the app. If I don't need 30 languages, don't ship em to me. Further, when I'm downloading an application update, don't ship the whole app again, only ship whatever changed. It isn't just storage space that needs to be optimized, but bandwidth utilization too. Frequency and size of updates is out of control.

      --
      Come play Moral Decay!
    59. Re:Natural consequence by ElizabethGreene · · Score: 1

      I respectfully submit that by shining a light on this developers will fix it. It's like how old apps used to ask for every permission under the sun. When users started complaining about it they trimmed it down. Same deal here.

    60. Re:Natural consequence by Rockoon · · Score: 1

      No, thats not a class, thats a class instance.

      Class instances consume memory at runtime. They do not consume memory in the applications binary.

      --
      "His name was James Damore."
    61. Re:Natural consequence by Anonymous Coward · · Score: 0

      SOLUTION:

      Don't use apps. I never install apps on my phone, preferring to go direct to the website (just as I would on my laptop or desktop computer). It leaves all the room I want on my phone, and also reduces the amount of data use for updates to zero.

    62. Re:Natural consequence by Anonymous Coward · · Score: 0

      Making their code base as big as possible would be logical if they have something to hide in it.

    63. Re:Natural consequence by Anonymous Coward · · Score: 0

      Not sure what you're referring to exactly, but I had occasion to use Xamarin for a mobile app project recently and was surprised at how small it's deployable package ended up being. Less than 17 MB when compiled in Release mode. Even in Debug mode it was only 39 MB. And that was with a fair number of Nuget packages used.

      If anything, the only way I could see a Xamarin app getting particularly large would be if you used a lot of graphical assets.

    64. Re:Natural consequence by Anonymous Coward · · Score: 0

      Even more concerning: I read about a game from the last five years (I can't seem to find it with a quick web search) that clocked in at a 50GB install footprint, and one of the reasons was that all of the in-game audio was in PCM format. When queried on this the developers claimed that they had been unable to get compressed (assume MP3) audio to work in their game without playback problems. I was shocked that this was regarded as acceptable by anyone working on that project. Even if the game pre-decompressed the MP3 files into PCM format in memory (sure, a huge RAM hog) it would be better than what they did. Fuck, even if they pre-decompressed the required MP3 files into a temporary folder prior to starting the game for each level/region, it would have been better than what they did.

      Anyone remember the game title?

    65. Re:Natural consequence by Anonymous Coward · · Score: 0

      PS: Also, I'm making excuses for them anyway - there's no reason why the MP3 files shouldn't playback as smoothly as PCM on modern hardware. Their game framework was probably fucked.

    66. Re:Natural consequence by Cinnamon+Beige · · Score: 1

      It's not just that, the messaging app I'm most likely to keep is one that does...messaging, really really well. The one that's got lots of features? Especially if it's dropping the few features I want and making it worse overall at messaging? That one goes.

    67. Re:Natural consequence by Cinnamon+Beige · · Score: 1

      I hope everyone is enjoying 40GB PC game downloads that contain audio files for voice acting in all 8 languages.

      How much of a problem I find this depends on various factors like if I'm able to cull the languages I don't want during install--though I'd admittedly prefer it if you get one language automatically...and, given that they usually charge me for all eight anyway, I'd want the others as free DLC. Doesn't really hurt that I know I'm fluent enough in enough of them that if I get annoyed by the voice acting in one, I can switch and not find the game unplayable.

    68. Re:Natural consequence by suutar · · Score: 1

      According to this info on the dex format, the base size of a class in the binary (the size of a class_def_item) is 32 bytes - 8 fields at 4 bytes each; more if it's not just a marker interface (and I think even for that there's type name data elsewhere).

  3. Source code. by themusicgod1 · · Score: 0, Troll

    Presumably since we have the source code to every app that runs on our devices, we can see what the problem on a case by case basis, is n'est pas?

    What's this, LinkedIn doesn't offer this? Then no one should be using it, period.

    --
    GENERATION 26: The first time you see this, copy it into your sig on any forum and add 1 to the generation.
    1. Re:Source code. by BasilBrush · · Score: 1

      Why would we need the source? The app is a folder of files. app code separate from libraries and assets. We can see from that what's taking up space. We can't see if from looking at the source.

    2. Re:Source code. by jellomizer · · Score: 1

      Yep, I will dedicate years of my life analysis the source code before I use the app. I might as well write it myself.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    3. Re:Source code. by ledow · · Score: 2

      I'll give you the source code to systemd. You tell me what it's doing.

      The "open" system is an absolute myth anyway. You have no idea what your computer is actually doing, no matter what it is or where it was bought from. Even the "open" / "coreboot" laptops do things like apply closed-source Intel microcode updates to the processors on boot or they wouldn't work properly at all,

  4. The laws of nature are confounded by El+Cubano · · Score: 2

    Good job, guys.

    On the one hand we have Bettridges law of headlines telling us that the answer is "no", and on the other the fact that it is rather obvious to pretty much anybody who owns a smart device that the answer is "yes".

    Since you're on a roll, why don't you just spread butter on the back of a cat and drop it from the ceiling to watch it float?

    1. Re:The laws of nature are confounded by Videospike · · Score: 2

      That doesn't work unless you cool your cat to a few tenths of a degree above absolute zero, the point at which house cats become superconducting, and drop the cat in a near-perfect vacuum. On the bright side, the cat becomes much more cooperative.

    2. Re:The laws of nature are confounded by Anonymous Coward · · Score: 0

      If you just butter the cat's back, it'll simply land on it's legs.

      You need to strap a buttered toast on the cat's back. And then watch fall on its head.

  5. Are App Sizes Out of Control? by thegreatbob · · Score: 1

    Yes. Probably. Maybe not, once your start ruling out the apps that you probably shouldn't be using in the first place.

    --
    There is no XUL, only WebExtensions...
    1. Re:Are App Sizes Out of Control? by MightyYar · · Score: 2

      Yeah, about a year ago I got fed up with the Facebook app using up hundreds of megabytes of space without really adding anything above and beyond the mobile web version. Still use Facebook, though - just through the web browser.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    2. Re:Are App Sizes Out of Control? by Anonymous Coward · · Score: 0

      The same reason i don't use hang over, i mean hang up, i mean hang out app is because it's basically just the whole damn chrome with a plugin or special website or something, just for chatting. Yes, unfortunately i need to use it, but i use the browser for that. I have a separate low resource browser for running chat programs.

    3. Re:Are App Sizes Out of Control? by i.r.id10t · · Score: 2

      This is my big complaint with "apps". Why the hell do I need to sacrifice ANY space on my device (aside from maybe a few kb for cookies etc) to do something on my phone/tablet that I do from a browser on my desktop/laptop? Why can't I do it in the browser on the phjone?

      My storage is for my mp3s, pics of my kids, my ebooks, MY stuff.

      --
      Don't blame me, I voted for Kodos
    4. Re:Are App Sizes Out of Control? by ichimunki · · Score: 1

      Because when they aren't on a wifi connection, phones tend to be slow in the data transfer department. Because your phone isn't a desktop browser, it's a device with its own constraints and capabilities. Because marketing marketing marketing.

      --
      I do not have a signature
    5. Re:Are App Sizes Out of Control? by MightyYar · · Score: 1

      Yeah, but Facebook is useless without an internet connection anyway, so I really don't see the need for hundreds of megabytes of persistent and cache storage. I'm mostly only interested in the newest content, so why so much cache?

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    6. Re:Are App Sizes Out of Control? by Anonymous Coward · · Score: 0

      You CAN use your browser.

    7. Re:Are App Sizes Out of Control? by Anonymous Coward · · Score: 0

      Because some apps provide long runner background services and notifications. Because there are some apps you want to be able to access device hardware features and data. Apps provide a permissions system that you can't easily implement in a browser.

  6. Yes by Anonymous Coward · · Score: 0

    Nothing to see here...

    1. Re:Yes by Anonymous Coward · · Score: 0

      It takes a lot of code to spy on your every action on the device.

      Apps are just limited programs that spy on you. (linkedin wants to know your gps location?)

  7. Because node.js? by mfearby · · Score: 4, Insightful

    Node.js apps are a dime a dozen these days, and they're all fat slugs of things. Sad.

    1. Re:Because node.js? by SomeoneFromBelgium · · Score: 2

      Yep. Make the app great again!

    2. Re:Because node.js? by TFlan91 · · Score: 1

      As are packages and code snippets for other languages?

      The only "problem" with Nodejs is that it's very easy to use these packages. And then for the incompetent, it's very easy to forget them, not read and understand what those packages do and how they do it. But that can also be said for other languages.

      So I guess the true problem is that the entry-level expertise required to write JavaScript is too low for your high horse. You can't bitch about shitty developers then turn around and shun any aspiring ones.

    3. Re:Because node.js? by zifn4b · · Score: 1

      Node.js apps are a dime a dozen these days, and they're all fat slugs of things. Sad.

      No way it's all those Python apps. They're all the fat slugs of things. Dime a dozen

      --
      We'll make great pets
    4. Re:Because node.js? by Anonymous Coward · · Score: 0

      Donald?

    5. Re:Because node.js? by chispito · · Score: 2

      Node.js apps are a dime a dozen these days, and they're all fat slugs of things. Sad.

      I'm genuinely confused. How does server side software cause mobile apps to become bloated? What difference does it make if the app is pulling from Node or Ruby or Python or anything else?

      --
      The Daddy casts sleep on the Baby. The Baby resists!
    6. Re:Because node.js? by Anonymous Coward · · Score: 0

      node.js apps bloated?

      During a node conference, I saw the source tree Target wrote when they switched their entire consumer front-end to node, it was 200kbytes.

      So, um, maybe learn some shit before talking?

      Fucking poser.

    7. Re:Because node.js? by doom · · Score: 1

      Node.js apps are a dime a dozen these days, and they're all fat slugs of things. Sad.

      No, no, you are not allowed to use a Trumpism except when engaging in heavy-handed irony.

    8. Re:Because node.js? by Anonymous Coward · · Score: 0

      As someone that loves him some Python, this is a fair complaint.

      I made a wxPython tool, and compiled it into an exe with py2exe. The tool itself was about 30 lines of Python code, the executable was 16Mb. I assume that py2exe just took all of Python and all of wxPython and packaged it with my 30 lines of code.

      For comparison, I later wrote a similar program in C#. It required many more lines of code, but took 10s of kbs instead of 10s of Mb.

    9. Re:Because node.js? by Anonymous Coward · · Score: 0

      Found the java developer.

      Making a python app, a language designed to force simplicity, be bloated would be an impressive feat. Perhaps you don't know. With python, you are not competent. In python, it's easier and faster to just write decent code.

    10. Re:Because node.js? by Anonymous Coward · · Score: 0

      wrong OS

    11. Re:Because node.js? by Anonymous Coward · · Score: 0

      So I guess the true problem is that the entry-level expertise required to write JavaScript is too low for your high horse.

      Javascript? Who in their right mind uses Javascript with Node and/or Angular? It's Typescript all the way down, man!

    12. Re:Because node.js? by mfearby · · Score: 1

      That 200 KB wouldn't have included the node_modules directory, I suspect.

  8. App Update Size is not the same as App Size by Snowhare · · Score: 4, Informative

    https://developer.apple.com/li...

    Technical Q&A QA1779
    Reducing Download Size for iOS App Updates

    Q: How can I reduce the downloaded size of my app update for users that already have the previous version installed?

    A: This document is specific to app updates. See Technical Q&A QA1795: Reducing the size of my App for a collection of techniques to reduce the size of an app when it is downloaded and installed for the first time.

    Starting with iOS 6, the app store will automatically produce an update package for all new versions of apps submitted to the store. When generating the update package, the app store compares one or more prior versions of your app to the new version and creates an optimized package for each that contains only the content that has changed between versions of your app, excluding any content that did not change. This comparison looks at everything in the application bundle, including the application executable, nibs, localizations, image files, video files, audio files, text files, and files containing data in a custom format.

    Note: The ability to create update packages is not currently available to developers who do not distribute their apps through the app store, such as those distributing enterprise apps.
    When used optimally, an update package is significantly smaller to download than the full package of the app and the update will install more quickly. Also, in many cases, this mechanism allows updates to large apps to be downloadable over cellular networks where app downloads are subject to a size limit.

    In addition to new content, the update package contains instructions on how to transform the prior version of the app into the new version of the app. New files will be added, modified files will be replaced with their updated counterpart, and deleted files will be removed as part of this transformation. As far as the developer and user are concerned, this process is entirely transparent and the resulting updated app will be indistinguishable from a full download of the corresponding updated version of their app.

    To optimize the size of your app updates, you should consider two tips:

    Do not make unnecessary modifications to files. Compare the contents of the prior and new versions of your app with diff or another directory comparison tool and verify that you've only changed what you expect within your app bundle.
    Content that you expect to change in an update should be stored in separate files from content that you don't expect to change. This reduces the size of the update package and increases its install speed.
    For devices running iOS 6.x and iOS 7.0, the update package will include any file, in its entirety, that has changed in the new version of the app. For example, if you have a 10 MB file in your app and only change 1 KB of content within that file in the new version of the app, the update package for that new version will contain the full 10 MB file.

    For devices running iOS 7.1 and later, the update package may include only the differences between the old and new versions of a changed file instead of the full file. This may significantly reduce the size of the update package in the case where only a small part of a large file changes, but will increase the update's installation time on the device. For this reason, the two tips above are still important even for updates on iOS 7.1 and later. Minimizing changed content and localizing it to many smaller files instead of one larger monolithic file will reduce the download size in all cases and will speed up installation on devices running iOS 7.1 and later.

    1. Re:App Update Size is not the same as App Size by LordWabbit2 · · Score: 1

      Damnit I would mod you up, but I have already left several comments. Thank you for this information, it's nice to know that at least some attempt is being made to reduce upgrade sizes. Does this also hold true for Android?

      --
      There are three kinds of falsehood: the first is a 'fib,' the second is a downright lie, and the third is statistics.
    2. Re:App Update Size is not the same as App Size by geekmux · · Score: 1

      "App Update Size is not the same as App Size"

      Tends to get reduced to bullshit semantics outside of bandwidth concerns. At the end of the day, even "optimized" updates are feeding bloated appware that's consuming precious device storage.

      And I find Apples give-a-shit level quite low when they are in the highly profitable business of selling soldered-memory upgrades for app-enabled hardware. Hell, their default bloatware says volumes about that. Garageband and iMovie apps consume over 2GB? Fucking seriously...

    3. Re:App Update Size is not the same as App Size by Anonymous Coward · · Score: 0

      Yeah. Update size is more of a "bloat maintenance" thing than anything else.

      From the App size optimization QA (https://developer.apple.com/library/content/qa/qa1795/_index.html):

      "Use 8-bit Images Where Possible"
      Pfff... fuck it if current app developers even know what a bit is.

    4. Re:App Update Size is not the same as App Size by Tool+Man · · Score: 1

      The updates may be much smaller, but the end result is still massively bloated. I killed off my Facebook app when I needed space and iOS was telling me that FB was taking up around 400MB. Sure, the innumerable updates are relatively small, but that's of less consequence anyway if not doing updates over a mobile data plan.

    5. Re:App Update Size is not the same as App Size by MachineShedFred · · Score: 1

      They're also paying for the untold amount of terabytes of bloated app updates passing through their CDN. They have a pretty good per-month incentive to slim it down.

      --
      Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
    6. Re:App Update Size is not the same as App Size by jittles · · Score: 1

      The updates may be much smaller, but the end result is still massively bloated. I killed off my Facebook app when I needed space and iOS was telling me that FB was taking up around 400MB. Sure, the innumerable updates are relatively small, but that's of less consequence anyway if not doing updates over a mobile data plan.

      Relatively small? Facebook pushes an update to the store every week that is on the order of 250MB per week! Are they really changing that much? Is the update slimming process not working for Facebook? Why does Facebook's app even need that much space? It's a glorified Safari web app, lets be honest. Except that the site is actually easier to use in Safari than their app, or at least used to be until they started looking at the user agent and stripping out functionality to try and get you to install Facebook Messenger.

    7. Re:App Update Size is not the same as App Size by geekmux · · Score: 1

      They're also paying for the untold amount of terabytes of bloated app updates passing through their CDN. They have a pretty good per-month incentive to slim it down.

      Chumps pay by the drink. Kings pay fixed cost.

      In the grand scheme of things, Apple is no chump.

  9. UI Overkill by randomErr · · Score: 4, Insightful

    This is just plain overkill on UI components. ost companies are more worried about bells and whistles then functionality right now. That's why tablets and phone apps became so popular. Everything was light, small, simple which desktops and laptops really aren't. That's also my Facebook offers a slim version of their application in countries that has slow network connections.

    My guess is that the pendulum will switch away from native apps to something like Progressive Web Apps (God I hate that marketing term.) Light static websites that pull from RESTful service will become popular again. The base site will be 1 meg at most in size. Until thos ebecome as bloated as native apps. Then a new disruptive technology will come along and start the process all over again.

    --
    You say things that offend me and I can deal with it. Can you?
    1. Re:UI Overkill by nine-times · · Score: 3, Insightful

      Then a new disruptive technology will come along and start the process all over again.

      Not likely. If the past few decades have been any indication, storage capacities will grow and available bandwidth will increase, and people's idea of "small" will grow. Mobile apps will be 2 GB, and people will be saying, "Man, these app sizes are growing out of control. Remember the good old days when an app like this would only be 1 GB?"

    2. Re:UI Overkill by Anonymous Coward · · Score: 0

      For what it's worth, I uninstalled the FB app to replace it with the light version. After a few months of excruciating slowness I went on to using the mobile webpage and haven't looked back since. No app updates, as fast as the regular app (and much faster than the "light" for some reason), can benefit from browser plugins like adblock, etc.

    3. Re:UI Overkill by Shotgun · · Score: 1

      I remember when the good old days was a large app on a 1.4Mb floppy disk.

      --
      Aah, change is good. -- Rafiki
      Yeah, but it ain't easy. -- Simba
    4. Re:UI Overkill by clodney · · Score: 1

      Then a new disruptive technology will come along and start the process all over again.

      Not likely. If the past few decades have been any indication, storage capacities will grow and available bandwidth will increase, and people's idea of "small" will grow. Mobile apps will be 2 GB, and people will be saying, "Man, these app sizes are growing out of control. Remember the good old days when an app like this would only be 1 GB?"

      And people still won't care. I am at the age where I have to stop myself from telling stories of the "why when I was your age I thought 64KB was a lot of memory" kind, and as long as I have enough storage and bandwidth that that app sizes don't fill up my phone or take forever to download I don't pay any attention at all to the app sizes. And as someone who has done project management over the years, I know I am not going to put effort into shrinking down package size until my customers start telling me I have to.

      So long as bandwidth and storage grow faster than app sizes, solve more interesting problems.

    5. Re:UI Overkill by Anonymous Coward · · Score: 0

      QNX had an operating system, gui, web browser, text editor and more on a 1.4Mb floppy.

    6. Re: UI Overkill by Anonymous Coward · · Score: 0

      POSIX certified OS

    7. Re:UI Overkill by Anonymous Coward · · Score: 0

      Or a whole OS

      https://www.youtube.com/watch?v=K_VlI6IBEJ0

  10. Re:Microsoft updates / apple updates - No proxy ca by jerquiaga · · Score: 5, Informative

    There is a solution for Microsoft, and it's built in to Windows server. It's called Windows Server Update Services, and it does exactly what you're talking about for Windows.

    Mac OS also has exactly the same thing, called Software Update services and it's included with Mac OS Server.

    Neither of these are Unix based, but if you've already invested in 1000 clients, it's pretty likely you have at least one Windows/Mac OS server for all the other ancillary things they provide.

  11. The obvious solution is... by Nutria · · Score: 0

    don't have LinkedIn and track running apps on your cell phone. Twitter and Uber are pretty damned useless, too, and FB is for parents with children.

    --
    "I don't know, therefore Aliens" Wafflebox1
    1. Re:The obvious solution is... by Anonymous Coward · · Score: 0

      As apposed to parents without children? I'm curious as to how one achieves being a parent without a child?

    2. Re:The obvious solution is... by Nutria · · Score: 2

      how one achieves being a parent without a child?

      People can die before their parents.

      --
      "I don't know, therefore Aliens" Wafflebox1
    3. Re: The obvious solution is... by Anonymous Coward · · Score: 0

      But in that case you have a child, a dead child but a child nonetheless

  12. Same thing just happened... by ckatko · · Score: 4, Interesting

    ...on my Android phone. Except my phone is full, so every update... I have to delete another app, or clear the cache for it to download.

    It's !#@$!ing pathetic.

    I've got maybe 4 apps that aren't stock on my phone. It runs slow as piss compared to the two years ago when I bought it used. A freakin Samsung S5. You know... an "enterprise model / top-of-the-line" phone when it came out. No Facebook. Nothing. Just Google's, T-Mobile and Samsung's defaults.

    "Maybe you just need to upgrade."

    Bull. Shit. It's got a quad-core CPU and a GPU that would make my netbook cry, and yet... somehow... my Linux laptop sits there, every day, just as fast. And my phone keeps getting slower. Same websites. Same hardware (from purchase date). And yet... mysteriously... it keeps getting slower.

    I would not be surprised at all if there's some planned obsolescence at play. I've seen countless stories of people "reseting to factory default" their phone or tablet, and then once it installed all the normal updates... it's slow as mud again. It shouldn't take me 7+ seconds to load my bloody GMAIL app on a quadcore ghz CPU. It's _e-mail_. It's practically a word processor without the word processing.

    Then again, it's probably just a conspiracy theory. It's not like large corporations have ever colluded to bypass things like environmental regulations to increase profit.

    1. Re:Same thing just happened... by Anonymous Coward · · Score: 0

      I applaude your comment. Well put, very well put.

    2. Re:Same thing just happened... by DNS-and-BIND · · Score: 5, Insightful

      Developers develop their apps on emulators, not on the phones themselves. When they do use phones, they are the latest high-performance ones. They never see the slowness, or if they ever do, it is handwaved away with "upgrade your damn phone, Luddite."

      --
      Shutting down free speech with violence isn't fighting fascism. It IS fascism!
    3. Re:Same thing just happened... by enjar · · Score: 1

      Nothing. Just Google's, T-Mobile and Samsung's defaults.

      This is why when my Samsung Galaxy S4 needed replacement, I went with a (used, unlocked, GSM) Nexus 6P with 128 GB of storage. No crap Samsung apps, no carrier apps. There were the Google apps (which can be removed) but otherwise it was clean. Plus if my provider decides to be a jerk, I can take my business elsewhere.

    4. Re:Same thing just happened... by Anonymous Coward · · Score: 0

      I hear ya. I have the exact same problem. I have a Samsung S5 on AT&T and I've been having to juggle apps by moving them to my SD card whenever I can to make enough room to allow the phone to run and for it to update. HATE IT!

    5. Re:Same thing just happened... by Wycliffe · · Score: 3, Interesting

      Developers develop their apps on emulators, not on the phones themselves. When they do use phones, they are the latest high-performance ones. They never see the slowness, or if they ever do, it is handwaved away with "upgrade your damn phone, Luddite."

      Why is this modded down? This is absolutely the truth. Most apps are developed for the newest version of the phone and most developers tend to have the latest phones anyways. My company's solution to this was to send our developers to the store and have them each buy several $20 prepaid devices. Even this though isn't a perfect solution because developers still tend to do most of their testing and development on the higher end devices first and only switch to the crap phones during final testing or when there is a problem.

    6. Re:Same thing just happened... by s_p_oneil · · Score: 2

      I had similar things happen with other Android phones (I've also seen it happen with older iPhones/iPods each time you apply a new iOS version), which is why I decided to go with an unlocked Nexus 5. So far everything is still working great except for certain sites on Chrome, and those sites seem to be the ones that try to cram too much crap (that no one wants) into their mobile pages.

      Take weather.com as an example. Don't give me an app with alerts that drains battery life and CPU performance 24/7. Just let me bookmark two pages for hourly and 10-day (maybe a third page for the current weather radar), show me the freaking temperature, tell me when it might rain, and include some static ads if you have to. Get rid of the fancy JavaScript, options to add/save 10 locations, high-res videos and animated ads, and the rest of the crap that makes it so painful that I gave up on visiting that web site on my cell phone.

      P.S. - I just pulled up weather.com on my cell for the first time in a while, and it's actually a lot better than it was 6-12 months ago. It's still got a bunch of extra crap in the web page I don't want, but it's loading a LOT faster than it used to.

    7. Re:Same thing just happened... by enjar · · Score: 1

      Take weather.com as an example. Don't give me an app with alerts that drains battery life and CPU performance 24/7. Just let me bookmark two pages for hourly and 10-day (maybe a third page for the current weather radar), show me the freaking temperature, tell me when it might rain, and include some static ads if you have to. Get rid of the fancy JavaScript, options to add/save 10 locations, high-res videos and animated ads, and the rest of the crap that makes it so painful that I gave up on visiting that web site on my cell phone.

      I just say "ok google, what's the weather" and it does exactly what you want. After you ask it enough times it notes the habit and then starts displaying it as a notification. Kind of equal parts creepy and awesome.

    8. Re:Same thing just happened... by Anonymous Coward · · Score: 0

      They ought to be forced to run on the really emulating emulators (i.e. run ARM binary of application on x86), then they might change their view....

    9. Re:Same thing just happened... by s_p_oneil · · Score: 1

      As cool as it is, I quickly get tired of speaking to my devices. My main way to use it is "Ok Google, call John Smith on speakerphone" (which is an awesome hands-free way to call someone when driving an older car).

    10. Re:Same thing just happened... by tepples · · Score: 2

      Don't give me an app with alerts that drains battery life and CPU performance 24/7. Just let me bookmark two pages for hourly and 10-day (maybe a third page for the current weather radar)

      When Weather.com got all bloated, I switched to Weather.gov.

    11. Re:Same thing just happened... by Anonymous Coward · · Score: 0

      I just say "ok google, what's the weather" and it does exactly what you want. After you ask it enough times it notes the habit and then starts displaying it as a notification. Kind of equal parts creepy and awesome.

      Saying "Ok google, what's the weather." opens up an app with three different sections, one for current weather, one for ten-day, and one for radar all in less time it takes to load an app that was already downloaded all with no ads, bloat, or spyware?

      Amazing! /s

    12. Re:Same thing just happened... by MobyDisk · · Score: 1

      I've got maybe 4 apps that aren't stock on my phone. It runs slow as piss compared to the two years ago when I bought it used. A freakin Samsung S5.

      I have an S5 with the same issue. I haven't installed OS updates in over a year because even if I move every app to my SD card, I still don't have enough space to install the upgrade. I think I need to root it to uninstall all the built-in crud, so I can install the OS upgrade.

  13. Re:Microsoft updates / apple updates - No proxy ca by david.emery · · Score: 1

    And Mac OS X Server costs only $20. It's worth it for the update server and the ability to host remote Time Machine backups, even if you use nothing else.

  14. Having not read the article.. by fishscene · · Score: 1

    ... doesn't Apple use delta updates? Or is my phone somehow magically updating faster than my brand-new $1800 PC can download through a wired ethernet connection? Also: https://developer.apple.com/li... So yea, the initial download is huge, but the updates, specifically for Apple, are much, much smaller - depending on how much was changed in the update.

  15. Absolutely by Dan+East · · Score: 5, Insightful

    Yes, absolutely. I was just complaining to a fellow developer about this recently. As an "old school" software developer, who compiled code on an Amiga with two floppy disk drives (one for the compiler and libraries, and the other for my workspace), I am greatly annoyed by the bloat I see in apps. In my opinion, for an app to be 300 MB, it either is comprised of at least 1 trillion lines of source code, or contain a 298 MB video showing how to use the app. The latter of course being totally unnecessary. The FB app is over 300 MB. The images and icons it contains are most certainly not taking up the bulk of that space. Does it contain its own build of Linux or something? Does it contain translations for every known human language? Really, there is no reason for applications of that kind to be nearly that large.

    Two things I know for sure are that iOS apps do not need to be that large - there are some really good games that are only around 5 MB. Second, and I haven't used Android in years so maybe it has changed, but a given Android app always seemed to be smaller than the iOS version.

    --
    Better known as 318230.
    1. Re:Absolutely by Anonymous Coward · · Score: 0

      300 MB is around 200 floppy disks. Windows 95 came on 21 1.44 MB floppy disks.

    2. Re:Absolutely by Anonymous Coward · · Score: 0

      It's called the Inner Platform Effect.

      https://en.wikipedia.org/wiki/Inner-platform_effect

      The app contains an OS, which contains another app, which contains another OS. Inside that inner OS is yet another app...

      It's just OSes and Apps, all the way down!

    3. Re:Absolutely by Anonymous Coward · · Score: 0

      Stop whining, if you really believe there is a market for small apps by all means write a business plan and knock on some doors. I personally think functionality, reliability and speed are far more important the a few hundred megabytes of storage. (A 32GB memory card is less than $15 or about 5 cents for 100 MB)

    4. Re:Absolutely by Jason1729 · · Score: 1

      Look past the first link on google. It's wrong.

      Win 95 came on 13 1.68 MB DMF floppies. DMF was a special format giving you 21 sectors per track (maybe that's where the 21 came from). It would have been 15 1.44 MB floppies, and DMF was much harder to copy, at least at first.

      Also, you think the simplistic little facebook App is worth 20 times the space of all of windows 95?

    5. Re:Absolutely by Jason1729 · · Score: 1

      Except the bloat kills reliability and speed. And that kills functionality

      All software so so buggy these days it's amazing anything works at all. But it's so easy to push parches, who cares about getting it right the first (or twenty-first) time?

  16. Keep him away from printer drivers.. by Anonymous Coward · · Score: 0

    Don't let this guy see how big his HP printer driver, or Adobe reader, has become...

  17. BACK IN MY DAY WE FIT THINGS ON FLOPPIES by enjar · · Score: 2

    AND WE LIKED IT THAT WAY. Sometimes you had to swap a floppy, then people got 10 MB hard drives and everybody started throwing around memory like it was free.

    1. Re:BACK IN MY DAY WE FIT THINGS ON FLOPPIES by SomeoneFromBelgium · · Score: 1

      Sorry to break it to you.
      Yes we did our best to fit as much data as possible on one floppy disk (664 blocks in use anyone?).
      But no we did not like it (boot - switch floppy - wp51/wp51 - switch floppy - load document - switch floppy again ...)
      And don't get me started on disk dupe and stacker from the times you could easily fill a hard drive a few times over with software alone..

      So, yes it's agreeable to go down the memory lane but longing back to floppies? Really?

    2. Re:BACK IN MY DAY WE FIT THINGS ON FLOPPIES by Anonymous Coward · · Score: 0

      Floppies? Fuck you, punk and your rotating media.

      In my day we moved from punched paper tape to cassette decks/tapes and thought we were in heaven.

    3. Re:BACK IN MY DAY WE FIT THINGS ON FLOPPIES by Anonymous Coward · · Score: 0

      True dat.
      On the original Macintosh, with 128KB RAM (not MB), you could fit a stripped down version of the operating system (all but a couple fonts, and maybe just the scrapbook desk accessory), MacWrite and MacPaint on a single 400K floppy. "But wait!" you say, "What about all that ROM?" -- the ROM is only 64KB including the boot routine.

      The MacWrite that shipped with the original Mac was only 57KB for the executable, plus a spelling dictionary.

    4. Re:BACK IN MY DAY WE FIT THINGS ON FLOPPIES by swb · · Score: 5, Interesting

      I don't miss the size constraint nature of floppies, but I do miss the portable environment nature of floppies.

      It was awesome to have my own little box of 5.25 floppies that I could bring from home and then in computer class, boot the Apple ][ with my own disks and utilities.

      I kind of wish it was more practical to do this with Windows. Of course there are close workalikes, (RDP, web based environments, Windows to go, etc) but nothing with the elegant simplicity of just booting the dumb thing from a 128 GB USB stick and using it as normal, and then carting it off.

    5. Re:BACK IN MY DAY WE FIT THINGS ON FLOPPIES by enjar · · Score: 1

      I don't miss floppies wearing out, usually at the most critical point, like when a big deadline came up. I do not recall the long grinding sound and the inevitable "Abort, Retry, Ignore" that followed. Dropbox has replaced a lot of the reasons I used a thumb drive or a floppy nowadays.

      Didn't the Apple ][ boot from a ROM? I could be remembering wrong on that, I had a PC clone which I booted from floppy at home, and we used Commodore PETs at school, which might have booted from ROM but I can't remember. I do remember loading BASIC programs from cassette tape on the PET, though

    6. Re:BACK IN MY DAY WE FIT THINGS ON FLOPPIES by Anonymous Coward · · Score: 0

      Sorry to break it to you.
      Yes we did our best to fit as much data as possible on one floppy disk (664 blocks in use anyone?).
      But no we did not like it (boot - switch floppy - wp51/wp51 - switch floppy - load document - switch floppy again ...)
      And don't get me started on disk dupe and stacker from the times you could easily fill a hard drive a few times over with software alone..

      So, yes it's agreeable to go down the memory lane but longing back to floppies? Really?

      Wrong, we liked it.

    7. Re:BACK IN MY DAY WE FIT THINGS ON FLOPPIES by Anonymous Coward · · Score: 0

      Isn't this exactly what Windows to go is supposed to do?

    8. Re:BACK IN MY DAY WE FIT THINGS ON FLOPPIES by Anonymous Coward · · Score: 0

      You are r a modernist in my day we used paper tape and punched cards.

    9. Re:BACK IN MY DAY WE FIT THINGS ON FLOPPIES by Anonymous Coward · · Score: 0

      Man you are out of date.Today just being their own laptops to class.

    10. Re:BACK IN MY DAY WE FIT THINGS ON FLOPPIES by Anonymous Coward · · Score: 0

      my c64 came with a cassette player. But let's be honest the head was a bitch to calibrate. When floppy drives arrived, I loaded up a calibrator software and with that cassettes were easy to use.
      Then XTs became affordable and C64s died lol...

    11. Re:BACK IN MY DAY WE FIT THINGS ON FLOPPIES by Anonymous Coward · · Score: 0

      What's wrong with the box of USB disks?

    12. Re:BACK IN MY DAY WE FIT THINGS ON FLOPPIES by Megol · · Score: 1

      Another example: the (old) QNX demonstration floppy. Unix type OS + GUI + networking drivers + browser on one 1.44MB floppy.

  18. Printer Driver Included by Anonymous Coward · · Score: 0

    They just forgot to remove the printer driver that came bundled with the framework...

  19. Why an app ? by Pascal+Sartoretti · · Score: 1

    For LinkedIn, I don't even see the point in having a dedicated app, it provides no added value compared to the web site as seen in a browser.

    1. Re:Why an app ? by Anonymous Coward · · Score: 0

      Because the Linkedin app give them access to your entire addressbook which is great for their data mining.

    2. Re:Why an app ? by green1 · · Score: 1

      Except that Linkedin does their absolute best to prohibit use of the browser version on mobile devices, going to their site just re-directs you to download their app. To even get their website working on my phone I had to change my browser user agent string, something your average user doesn't exactly play with.

      And that really is the thing that bugs me most about these apps, it's not their size, it's the fact that we need to use them at all. If I access your product from my computer 100% in a browser, that same functionality should be available from my phone without downloading an app at all, after all, my phone has a browser on it already. If you're going to cram an app down my throat, it had better provide me some additional functionality that I can't get at all from your website on my computer.

      Somewhat related note, if I access your webpage, any webpage, from the browser on my phone, I should see exactly the same thing I see when I access it from my computer. There is ZERO excuse to serve me something different, save yourself a bunch of money, and stop developing separate, crippled, versions of your sites for mobile. My phone has a big screen, and the ability to zoom and scroll. I don't want a different page when I go to the same site on a different device.

    3. Re:Why an app ? by unixisc · · Score: 1

      Yeah, I absolutely hate this! I have an email account dedicated to LinkedIn, and other email accounts for other things, including one for friends & family. I sometimes get on the latter invitations to connect on LinkedIn. Obviously, they used the LinkedIn feature to look in one's address book and send invitations to either connect if they're already there, or join if they're not!

      Search for me separately on LinkedIn, and then invite me to connect. I won't get spam that way from people I know.

    4. Re:Why an app ? by Anonymous Coward · · Score: 0

      Yeah, why even bother looking at Linked In on your phone? If you can't wait until you're at a computer, you're just sucked into Microsoft's "give me your data NOW" bull.

    5. Re:Why an app ? by tepples · · Score: 1

      Some of my co-workers don't have a computer at home. To use a non-company computer, they'd have to go to a public library during regular library hours, which often means not at all on weekends.

    6. Re:Why an app ? by Anonymous Coward · · Score: 0

      For you, the end user, that is true. I've long suspected the reason for native apps like this is not about you. It is about what the company can get from you and your device by having a native app. They get your contacts and your mobile info and can use that to target ads and build more of a social map.

    7. Re:Why an app ? by doom · · Score: 1

      Yes, I was going to propose a solution to this terrible problem, though this may seem strangely radical: if you think an App is bloated, don't use it. In fact, you could just dump your "smart" phone, and life would go on.

      You know, I've heard about these strange advanced devices with big displays and really fast input devices known as "keyboards"...

  20. Re:Microsoft updates / apple updates - No proxy ca by Bert64 · · Score: 1

    Except that Apple don't provide any server hardware to run it on, so you'd end up having to buy a mac mini and some kind of stand so you could mount it in the rack, and it still has no lights out remote management capability.
    For time machine all kinds of remote shares will work for hosting backups, most NAS devices include support.

    It's also annoying having to buy a windows server license just to cache updates, but at least you can run that in any hypervisor.

    If the updates were downloaded in a standard way, eg over http, then they would be much easier to cache. There's no reason not to download the large binary files in a standard way, and then verify the checksums/signatures afterwards to ensure the files haven't been tampered with.

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  21. But why? by zmooc · · Score: 1

    Why would you install a LinkedIn App? Is your browser retarded?

    --
    0x or or snor perron?!
    1. Re:But why? by apoc.famine · · Score: 1

      Because you're the sort of coked-up monkey that's addicted to push notifications interrupting every waking moment and keeping you up at night. It blows my mind how pavlovian some people are.

      --
      Velociraptor = Distiraptor / Timeraptor
    2. Re:But why? by zmooc · · Score: 1

      My browser already supports push notifications if I'm not mistaken.

      --
      0x or or snor perron?!
    3. Re:But why? by supremebob · · Score: 1

      The OP kinda covered this in his original post when they mentioned "recruiter spam". Microsoft needs the app to collect as much personal information that it can to provide to job placement sites and job recruiters. That's how the app pays for itself, and it another good reason why you should just use the web site instead.

    4. Re:But why? by whoever57 · · Score: 1

      Why would you install a LinkedIn App?

      Because you want to send the details of all your contacts to LinkedIn (Microsoft), so that, at some time in the future, LinkedIn can send them all some SPAM that appears to come from you.

      --
      The real "Libtards" are the Libertarians!
    5. Re:But why? by apoc.famine · · Score: 1

      Push to lock screen? If so, god that's awful, and no wonder browsers are so bloated.

      --
      Velociraptor = Distiraptor / Timeraptor
    6. Re:But why? by unixisc · · Score: 1

      Funny, b'cos Microsoft recently discontinued the LinkedIn app for Windows Phone, and recommended that people use the browser instead. In which case, why don't they do it for iOS and Android as well?

  22. Re:Microsoft updates / apple updates - No proxy ca by enjar · · Score: 1

    Microsoft's answer is to use SMS/MOM/SCCM/WSUS/whatever they call it nowadays, and run in a domain, and push the updates when you want. If you have 1000 users on your network, you likely have the domain infrastructure.

  23. I dont run Microsoft I run a network by johnjones · · Score: 1

    I run a network I dont run any Mac or windows machines they are clients of that network...

    there are plenty of education facilities in the same boat, we pay for bandwidth and frankly the amount that updates take downloading the same thing is incredible
    I cant run a WSUS server as the clients are not owned by us

    doesnt anyone measure this ?

    1. Re:I dont run Microsoft I run a network by jerquiaga · · Score: 1

      If you run a network then it shouldn't matter to you what runs over the network. Presumably you're charging the end user appropriately for their usage. If not, then start. When they ask why their bill is so high, tell them it's because of updates (probably not true in an era of streaming everything) and that they could lower their bill by running a local update server. Ultimately it isn't your problem to deal with. Make sure the network is up and stable, and that's it.

    2. Re:I dont run Microsoft I run a network by ledow · · Score: 1

      You have a choice:

      - Block Windows Update
      - Provide a WSUS server and insist they use it (e.g. by blocking Windows Update), or even insist they use a proxy server of your choice (Windows Update will respect the one specified in Internet Settings, for instance).
      - Don't block Windows Update, and charge for your services appropriately.

      To be honest, things like Apple Caching would be much more of a concern on my networks as I have no idea how they operate, how much they are transmitting, or what they are doing, without actually monitoring everything they do. At least with Windows Updates, you can just block a handful of URL's.

      Newer Windows has the same kind of local sharing mechanisms in the pipeline, but that's not really going to help you either. You'd still need to set up controls for them, such as having a domain and an instruction of what to cache/update.

      Personally, I'd just block Windows update and provide a WSUS server they could use.

    3. Re:I dont run Microsoft I run a network by Anonymous Coward · · Score: 0

      So what you're saying is "I'm making conscious choices about what hardware and software we use to run the network with that have negative impacts on the user"

      I mean - the software and hardware that does this for you has been pointed out. It doesn't cost much. Go buy it, install it, and be done. "I currently only have Linux boxes" doesn't change the fact that the software exists, and works.

  24. Re:Microsoft updates / apple updates - No proxy ca by guruevi · · Score: 1

    There are and you can (at least for Apple). I once wrote my own Apple update server since we moved away from Apple hardware for servers. All you do is download an XML, parse it and download the URL's that it's telling you to download. Then make them available with Apache or nginx.

    Not sure about Windows, from what I understand you need Windows Server ($500-6000) and then set up WSUS and then have an Active Directory. Ever seen the WSUS interface? It's absolutely horrid and the organization of updates makes no sense.

    --
    Custom electronics and digital signage for your business: www.evcircuits.com
  25. Use the mobile web site instead. (Closed - Solved) by xxxJonBoyxxx · · Score: 1

    >> I went to update all my apps the other day when something caught my eye... since when does LinkedIn take up 275MB of space?!

    Use the mobile web site instead. (Closed - Solved)

  26. Bloat by DarthVain · · Score: 1

    I've noticed this recently as well. Usually I have a 64GB sdcard in my phone, and it has 32GB internally so I normally don't notice/care. However recently the sdcard failed, and I had to make some room on my phone for music and things. So I actually spent the time to go through my apps, I was a bit appalled. I mean I got rid of a bunch that I never use, but there were a lot of apps that are very bloated for what they are. Many of which were a couple hundred MB, some of which are glorified mobile webpages.

    However I guess one of the good things that might come about is that phone makers will actually start putting in reasonable amounts of internal storage as a result. I mean internal storage has been super cheap for many years, and restricting most users to 16GB (!!!) and 32GB seems a bit silly. I know many use that as a way to sell higher end versions of the exact same phone for pure profit, but perhaps this will signal the end of that due to demand. Or at least it will bump them all a step up to the next higher storage size...

    1. Re:Bloat by Anonymous Coward · · Score: 0

      Perhaps you overlook the other storage/RAM... the system area. As apps grow in size, so will their footprint. I think this is what the thread is more about too/more. At some point, even if you can install the app, you can't run it because you lack the system ram requirements.

  27. Re:Microsoft updates / apple updates - No proxy ca by johnjones · · Score: 0

    $20 + $$$$ for mac... I dont have a mac to run it on that fits in a rack and apple stopped making those...

    its closed source magic that I cant debug or change

    all I want to do is cache the updates... admittedly Apple do a reasonable job and I can cache most of the HTTP objects its the microsoft updates that are crazy...

  28. Farmer's Market by zifn4b · · Score: 1

    Should the Farmer's Market do something to solve the inadequate quantity or quality of the produce of its vendors?

    --
    We'll make great pets
  29. Re:Microsoft updates / apple updates - No proxy ca by fredan · · Score: 1

    > why are their no unix/proxy/gateway solutions ?

    The Open Edge Content Distribution Network, TOECDN, has been developed for exactly this.

    The whole purpose of TOECDN is that you, as a end user, can setup a cache server at your home, to be able to cache software updates like this. And its not just for software updates. Its for all static content.

    The thing is, nobody care about this solution.

  30. That's why I'm not using Facebook App anymore by Anonymous Coward · · Score: 0

    When the app surpassed 200MB i removed it, left a negative feedback and started using the browser. It does 99% of the job, it's faster and doesn't bother me with huge updated every two week. I also removed LinkedIN because it's just a spam deliverer, doesn't work and it's complete garbage.

  31. App Store should rate apps on footprint and update by Anonymous Coward · · Score: 0

    Developers should have a push back on size. Applications in the store should have a visible end user rating based on the application size and the size of updates in the last 6 months. Rate it in elephants and Rhinos.
    The bigger the memory foot print the more elephants. More elephants are not good.
    The larger the 6month update foot print the more rhinos. More rhinos are not good.

  32. How much of the bloat is spyware? by Anonymous Coward · · Score: 0

    Is it the app designers, or the spyware, adware, and tracking they are including to be able to monetize their applications?

  33. Re:Microsoft updates / apple updates - No proxy ca by david.emery · · Score: 1

    The presumption would be that you have an existing Mac to run it on. For a large operation, the cost of buying hardware for this function is 'in the noise.' For a smaller operation that already has an investment in Macs, taking an older Mac, adding an external hard drive (if necessary) and running OS X Server on it for Software Updates is a wise use of existing resources.

    As far as lights-out, Server comes with a remote manager that you can run on other machines (although you might have to pay $20 to get it on the machine you want to use to manage the otherwise headless server installations.) So that's not an issue. That being said, Minis do have some annoying issues rebooting when they're "headless". My Mini systems running Server get rebooted only when there's a Mac OS X update, that happens maybe 4 times/year. So screwing with the monitor and keyboard when rebooting the Mini is an acceptable cost for me.

    I've been running OS X Server on low-end Minis since "Tiger", for at least 10 years, for file server, web server, internal DNS, LDAP, VPN for my small/home office. Earlier versions of Server were -expensive- (retail $1k!) and hard to configure. Over the years it's become a lot easier to configure (once you get DNS set up exactly right) and of course you can't complain about 2 orders of magnitude price decrease, particularly for what you get.

    Now if you have the skill and the patience and the significant user base to justify a pure web-cache solution, go for it! But it's not quite clear to me that solution will understand some nuances on whether the currently cached software update (Mac OS or iOS) will work for all devices on your network.

  34. Same song, different verse by p51d007 · · Score: 1

    It's the same thing that people said years ago about programs installed on your computer. Reason why? Why should a software company, worry about the size of the code for their program, when storage space is not at a premium? People routinely have 64gb or more space on their phones, so why spend the time to tighten the code, when the space is there? Lazy coders, and or bottom line pencil pushers don't care about the size of the program.

    1. Re:Same song, different verse by freeze128 · · Score: 1

      Devs of desktop apps didn't care because you could always just install a larger Hard Drive. It's not always so easy with a phone.

  35. Size limitations by Bender+Unit+22 · · Score: 0

    Didn't they have size limitations on apps a long time ago? Of course it makes sense(for them) not to have it.
    Why would you buy a 256GB iPhone 7 if you store everything in their cloud?
    To make room for apps of course!

    1. Re:Size limitations by unixisc · · Score: 1

      Speaking of clouds, Apple & Microsoft both have just 5GB, which fills up quickly after enough pictures & videos over iMessage or WhatsApp. On OneDrive, I happen to have 1TB due to my having Office 365. But all the apps that I have on my iPhone right now uses 12GB, and on my iPad, 14GB. Which would be a lot on a 16 or even 32GB device, but perfectly okay on a 64GB or 128GB device.

  36. Can't even tell before installing by Stonent1 · · Score: 1

    The play store used to show you the app size before you installed it, now it doesn't. I would frequently look at an app and find the smallest one. Especially if it was something like a basic utility like a compass, specialized calculator. No need for an app like that to be more than 1 or 2 MB unless they've packed it full of junk.

  37. Low-capacity phones get hammered out of the box by nctritech · · Score: 1

    I have a phone that's a year or two old which I don't really need more than 1-2 apps on because it's not my main personal phone. This phone has 4GB of total flash storage, of which 2.25GB is the Android system. What's very interesting is that when I set up this phone and my Google account, the built-in apps auto-updated and they have to use the remaining free space to do so.

    It ran out of space halfway through.

    What I had to do is turn off auto-updating, remove all the app updates for apps I didn't use, and now I have to constantly hand-pick updates. Just updating the Google Play {Newsstand,Music,Movies,Books,Games,KitchenSink} crap that almost no one actually uses is enough to kill off most of the phone's remaining storage. App bloat today is obscene. There is no valid excuse for triple-digit megabyte app sizes in all but a very small set of cases, especially for Web-centric stuff like LinkedIn.

    All of this app bloat would easily explain why expensive 8-core Android devices today are far slower than the HTC Dream with Android 1.5 that I originally started with.

    1. Re:Low-capacity phones get hammered out of the box by unixisc · · Score: 1

      The worst part of this is that in a lot of devices, one cannot remove apps that one has no use for. Like on my Moto X, there was no way I could remove Gallery, Verizon's NFL mobile, Verizon Navigate, Google+ and so on. And unfortunately, Android 5 is not yet upgradable to 6 or 7, where I could have re-defined the 128GB SD card as main memory and let the internal memory of that device be the secondary memory

  38. Re:Use the mobile web site instead. (Closed - Solv by acroyear · · Score: 1

    oh, but then you're asking Apple users to run Javascript.

    As we saw from the post on PWAs last week, that's like asking Disney to give up its Copyrights.

    --
    "But remember, most lynch mobs aren't this nice." (H.Simpson)
    -- Joe
  39. Take Control by Anonymous Coward · · Score: 0

    Delete all apps that don't actually make your life easier.
    Most of them are crap, malware or spyware anyway.
    "Social Media" is our version of Huxley's "SOMA".

  40. Re:Microsoft updates / apple updates - No proxy ca by LordWabbit2 · · Score: 1

    The only reason I can think of is they don't want to lose control of distributing the application, which can be a big deal if you get a bad actor between you and the proxy or god forbid he takes over the proxy. So added security, other than that???

    --
    There are three kinds of falsehood: the first is a 'fib,' the second is a downright lie, and the third is statistics.
  41. Solution by Anonymous Coward · · Score: 0

    Don't download all those apps.
    Seriously, do you REALLY need the LinkedIn app? Can't you just use their website to update your profile once in a while? Do you REALLY need a GPS tracker for when you're running? All those apps are essentially glorified web portals that you could do the same thing if you just went directly to their website instead, for less data usage.

    You're the one downloading those bulky apps, don't question why they are so big in size, but why do you even need them in the first place.

  42. 24 minutes to download by scourfish · · Score: 0

    Oh my god that's way too long! Whatever will someone do for a whole 24 minutes?
    Maybe they could microwave something while they wait...
    Oh no the burrito will take 6 minutes!
    Why is life so cruel?

    1. Re:24 minutes to download by Anonymous Coward · · Score: 0

      This self-entitled drivel brought to you by someone who has a 1TB internet connection.

  43. Re:Use the mobile web site instead. (Closed - Solv by xxxJonBoyxxx · · Score: 1

    >> (REOPENED) then you're asking Apple users to run Javascript.

    Toss Apple-branded Chinese cell phone, replace with Google-branded Chinese cell phone. (Re-Closed, Solved)

  44. Must be an iOS problem by Topwiz · · Score: 1

    On my Android phone LinkedIn is only 108MB. Twitter - 81MB., Chrome - 131MB, Facebook - 397MB.

    1. Re:Must be an iOS problem by Anonymous Coward · · Score: 0

      "only"

    2. Re:Must be an iOS problem by Shotgun · · Score: 0

      Considering that none of them are doing anything that should require more than 1MB......

      --
      Aah, change is good. -- Rafiki
      Yeah, but it ain't easy. -- Simba
    3. Re:Must be an iOS problem by Anonymous Coward · · Score: 0

      Not sure if missing the ...
      Chrome is fine for 130MB, it is basically an OS to itself.

      the others ones.... Seriously?
      They shouldn't be more than a few MB's.

      I program embedded systems, 64KB of code is a LOT. Think on a 8bits cpu that can be 32000 instructions, lots of them easily re-used with function
      Complete system can be built from less than 2KB.

      And for "normal" computer usage there is a linux distro, slitaz with a 52MB iso. with a web browser and desktop environnement.
      But facebook, a scrolling webpage with picture & vid embedded in is nearly 400MB riiiiiiiight...

  45. Size fits their purpose by Anonymous Coward · · Score: 0

    Yes, a "social" messaging app wouldn't need to be that complex. But these apps were made for surveillance, not for messaging.

  46. Super-Highway Effect by s_p_oneil · · Score: 1

    It's like the super-highway effect. The larger you make the highways, the more drivers it attracts, causing drivers to change their driving patterns until it gets over-congested. Expand it again? It attracts even more. If you build it, they will come.

    In this case, the more storage space the average phone has, the less app developers will care about size. When it comes to games, the artists will go nuts adding more and higher-res images/video/music/sound effects. I worked with a company on a few iPhone/Android games 5-7 years ago, and roughly 80% of the app sizes was for music and sound effects. Devs like me had to argue with the artists to keep the app from being 4 times the size.

  47. Re:Microsoft updates / apple updates - No proxy ca by Anonymous Coward · · Score: 0

    You are the only person I have ever seen post about TOECDN on /.

    Are you the dev? Also what happened to the toecdn.org site?

  48. Re:Microsoft updates / apple updates - No proxy ca by Anonymous Coward · · Score: 0

    >TOECDN has been developed for exactly this

    Your pet project homepage has no documentation, its archive.org version says it's a "concept", which sounds like "not runnable software".

  49. Apps by ledow · · Score: 1

    There is zero need for that size.

    There's no way that a Facebook app contains 200+Mbytes of code that are required to render a Facebook interface. It makes me wonder what ELSE it's doing.

    Also, Facebook doesn't even contain messenger functionality, that's a separate app. A copy of Chromium, branded with the Facebook logo, with the titlebar removed, and locked to only accessing Facebook URL's, would be smaller and more featureful.

    Facebook is the one app that I have had to advice my girlfriend to remove. Before we got new smartphones, the Facebook app filled her old one up with app and cached posts in a matter of days. Rather than transport that junk over to a newer phone when we got one, I told her to just use Chrome. At least then she can do all the same things, and do messenger too (alright, you have to click a bit, but it's there).

    And what does the app add? Nothing. It's basically a copy of the website. Same for LinkedIn, etc.

    Apps are the VRML fly-through, the MARQUEE tags, the pointless animated GIF, and the Flash-based swishy intro, of the modern age. "We have a website, we should have an app!"

    But 200Mb just reeks of someone saying "Who cares?" and just lobbing everything into it rather than trying to actually make an app people want to use. My app for Google Drive is smaller than that and I yet it does a thousand times more.

  50. Yep by Lumpy · · Score: 1

    Linked in and Facebook apps are complete crap written by no talent hacks. When the Mobile version of the site is significantly faster and has a better UI than your app? you fire your entire app developer team and hire some that understand efficient and fast.

    --
    Do not look at laser with remaining good eye.
  51. Runtime Libraries by Ronin+Developer · · Score: 1

    Many apps are built with tools like Xamarin or Appcelerator which require a large run-time library. This is downloaded for each app and not shared.

    I would be concerned if native apps were of this size.

    1. Re:Runtime Libraries by Anonymous Coward · · Score: 0

      Many apps are built with tools like Xamarin or Appcelerator which require a large run-time library. This is downloaded for each app and not shared.

      I would be concerned if native apps were of this size.

      Nailed it.

      Shared objects. You won't find this feature in any app store, probably because the app store's developers (or managers or whatever) just didn't want to deal with the "dependencies" problem.

      But desktop package managers have dependencies and desktop operating systems have shared objects for a reason, and this is it.

  52. Bullshit. by Anonymous Coward · · Score: 2, Informative

    Reaper, a highly sophisticated digital audio workstation for PC that is decades more advanced than any phone equivalent, weighs in at 10MB installed.

    1. Re:Bullshit. by OrangeTide · · Score: 1

      That's because Justin is an excellent programmer, unlike the majority of knuckdraggers who write mobile apps as marketing for big companies. Not everyone can be him, and not everyone can afford to hire a team like his.

      --
      “Common sense is not so common.” — Voltaire
  53. A lot of these apps shouldn't even exist by Solandri · · Score: 1

    A lot of apps don't even need to be apps. They worked fine as a website, but the company wants you to use their app instead so they can better track you. Now multiply that by the 20-50 sites you frequently visit. One web browser with 20-50 bookmarks, vs. 20-50 apps at 5-300 MB each.

    LinkedIn is a great example. Push content (notification of contact request) worked fine over email, and could even be sent as a SMS. Pull content works fine via their web portal. Web forums which try to get you to install their app with an annoying popup whenever you visit the site on a mobile device are another example. Sites like forums, where all the heavy lifting is done server-side, belong in a web browser. Unless there's something that needs to run locally on the phone/tablet, there is no reason for the app to exist.

    Fix your website so it'll scale properly to the smaller screen space (but higher resolution) of a phone or tablet. Yes your web designer will probably cry, but it's their own damn fault. The whole purpose of the web was to transmit content but leave rendering up to the browser so it could display the content in a manner most suitable for the display device. It wasn't supposed to be a mechanism for designers to force their idea of a perfect graphic design (which doesn't even render properly in certain cases) onto everyone.

    1. Re:A lot of these apps shouldn't even exist by unixisc · · Score: 1

      There is no need for the 'responsive' or one-size-fits-all website. Have something like foobar.com for your main website that one views from a PC or tablet, where space is not at a premium. If the site detects that a phone, or a small form factor device is requesting it, send m.foobar.com to that, which will have a totally different appearance based on that needs.

      The 'responsive' page is the same sort of thinking that gave us Windows 8 'Metro' - trying to redefine the desktop according to the needs of a phone. No need for it. Have the web team develop 2 websites, and have them fed from the same data sources, so that there will be no inconsistency b/w the 2

    2. Re:A lot of these apps shouldn't even exist by tepples · · Score: 1

      If the site detects that a phone, or a small form factor device is requesting it, send m.foobar.com to that, which will have a totally different appearance based on that needs.

      "m." sites have two practical problems. One is that they often lag behind in functionality and updates. The other is that public forums often look down on sharing links to "m." sites.

  54. why not just use resoective websites? by Anonymous Coward · · Score: 0

    hmm... Facebook, LinkedIn, etc. still work fine through web browser on my phone. But I guess I still manage to live without checking either frequently.

    I found the Facebook app annoying to use compared to website anyways.

    Obviously your mileage varies...

  55. Most apps unnecessary... by bradley13 · · Score: 1

    For most sites, an app is unnecessary. The ordinary, mobile web page works just as well, takes up a fraction of the space, and is likely to have fewer security risks (since it is sandboxed within a browser).

    More: if you install an app, as often as not you have just given them permission to lots of personal data. For example, it's pretty normal for every app out there to request access to your contact list. Usually this doesn't even make sense, but it helps them identify you, and gives them data to sell. And the number of people who actually check their apps security settings, and restrict them to the minimum? Near zero...

    --
    Enjoy life! This is not a dress rehearsal.
  56. Link to web site instead by wirelessjb · · Score: 1

    I have a shortcut to the facebook mobile site on my android home screen instead of the app. Much more space efficient. I just have to ignore all the requests to download the app instead. It works fine.

  57. Android "Lite" Apps by smileham · · Score: 1

    With the mobile push to India/Africa a couple of vendors have started to push "Lite" versions of their Android apps. Although not available via the Google Play store in the US/UK they still work fine and dandy if side-loaded. Highly recommended... Facebook Lite: 1.5mb - https://www.apkmirror.com/apk/... Linked In Lite: 0.64mb - https://www.apkmirror.com/apk/...

  58. WTF? by Cajun+Hell · · Score: 1

    Facebook and LinkedIn are websites. Why are you installing their ads? Oops, I mean, why are you installing their apps?

    The only storage those companies should be using on your computers are cookies, at the most.

    --
    "Believe me!" -- Donald Trump
    1. Re:WTF? by hackel · · Score: 1

      Cookies... and localStorage, and indexedDB / web SQL, and web workers, and application cache...
      Otherwise, yes, I completely agree. It's just not quite that simple.

  59. Re:Microsoft updates / apple updates - No proxy ca by Anonymous Coward · · Score: 0

    WSUS is an update management system, it is not (primarily) a cache/proxy, and it certainly isn't a transparent one (i.e. every computer connected to your network can and will use it).

  60. Re:Microsoft updates / apple updates - No proxy ca by fredan · · Score: 1

    > Are you the dev? Also what happened to the toecdn.org site?

    Yes I am. The site hasn't been updated since I've got no feedback for TOECDN. You can access the site at https://www.toecdn.org/

    There is no site at http://www.toecdn.org/ if that was you were trying to use.

    Right now I'm currently rewriting my authority dns server from scratch, which has the required functionality for TOECDN as Lua scripts.

    These script can be found at https://github.com/fredan/fDns under lua/toecdn directory. However, I have not been updated that for almost a year now.

  61. You misunderstand by Anonymous Coward · · Score: 0

    No, very few "apps" have any business with assembly, for starters because they'll be in java or somethin similar. Even so, understanding that you don't need several gigabytes of "framework" for what can be done in but a few machine instructions helps enormously with increasing code quality and decreasing code size. In other words, as a developer you need to understand the nature of low-level details to fuel your intuition about what is a reasonable "app" and what isn't. So yes, having some experience with assembly is still pretty important for any "app developer", programmer, and so on.

  62. fat apps by l3v1 · · Score: 2

    This is not a new phenomenon, it's been going on in the desktop PC world since the beginnings, and it's been going on in the mobile world since day one. I absolutely hate the trend but there's not much one person can do about it. As I see it, especially in the mobile world, there are lots of coders who use and link large libraries even for small tasks, usually don't even try to implement it themselves, and usually don't even search for other solutions or smaller libs providing the same functionality, they just stick with the first they find, and never care for the size of the apps. This applies for average junk apps as well as for large company apps like linkedin or spotify or here maps, and I could just go on. Gone are the days when efficient and small coding was the norm. And most of young coders don't even, or can't even think about writing small and efficient code. Just a couple of months ago I was given a code to use for some task, handling images, at a speed of ~14s/image, which was unacceptable for the specific task. After a complete rewrite in about two weeks I got it to run at ~1s/image, which was still slow, but at least was good enough for a proof-of-concept. And everyone was looking at me like I was some alien.

    Lots of coders prefer fast prototyping and quickly throwing together some app and spending very little time on making it small or as efficient as possible - upgrade your device/hw/PC is their mantra. Well, f*k that.

    --
    I am putting myself to the fullest possible use, which is all I can think that any conscious entity can ever hope to do.
  63. Use the website? by evilRhino · · Score: 1

    Phones are pretty intimate devices, so I understand why the owners of these apps would want to use them as hooks to extract as much out of their users as possible because there is money in information. I think I'm pretty fair when it comes to granting permissions, but Facebook and LinkedIn are examples of apps that go way too far. I get that a social network would want to access my address book and calendar, but I can't think of a good reason to give them that privilege. I use the mobile website for Facebook and Twitter, and generally only use LinkedIn on my desktop browser.

  64. Those numbers aren't real (but not a lie either) by omibus · · Score: 4, Interesting

    OK, the numbers are "real" in that "that is how much space the app is taking on Apple's server". It is not real in that "this is not the size of the files being moved to your device."

    What those numbers include: Multiple assemblies for different architecture platforms. The whole 32/64 bit thing is rearing its ugly head. There are also shared assemblies, not all of which get sent to your device (because they might already be there).

    Source: I'm an app developer who has had to explain this a few times as well.

    --
    Bad User. No biscuit!
  65. Re:Microsoft updates / apple updates - No proxy ca by Anonymous Coward · · Score: 0

    Windows 10's "evil" P2P update mechanism might be an actual solution or perhaps even honest attempt to that problem?

    Like everything good about Windows 10 the problem is you have to install and run Windows 10, and we don't want to because it's ugly crap.

    Maybe they do have a domain infrastructure, but that's useless if you expect hundreds of laptops/desktops that belong to their users. (and even tablets with consumer Windows, and things must function whether on site or not)
    If you control everything why not go thin client : a pile of 1U
    machines that run Windows Server, with like 50 desktop users per machine.

    For added fun, your entire user facing network is locked down in a fascistic way that only allows to run an RDP client (web or desktop based)
    That way you only have to update 20 Windows PCs not 1000 :). I wonder though how do you reboot that for updates. Kick the users 50 at a time losing all their work and sessions while the PC reboots? (wasting most of the time at BIOS and RAID initialization. Or use a VM host with a single VM)

  66. Printer Drivers! by Zorro · · Score: 2

    This all started with HP Printer Drivers.

    I just want to print a list on a Laser Jet should be 1-2 MB MAX.

    But NO! I have to download a 100 MB+ PRINTING PHILOSOPHY!

  67. Re:Microsoft updates / apple updates - No proxy ca by fredan · · Score: 1

    > it's a "concept", which sounds like "not runnable software".

    It is a concept! The required software to be able to run TOECDN is a authority dns server and a http cache server. My examples are with apache traffic server, which require no modification to their source code to be able to cache content with TOECDN.

    For the authority dns server, my own fDns (https://github.com/fredan/fDns) has been developed with TOECDN in mind. Having sad that, other authority dns server(s) could be modified to be able to provide the required TOECDN functionality at dns level.

  68. Re:Microsoft updates / apple updates - No proxy ca by fredan · · Score: 1

    > The only reason I can think of is they don't want to lose control of distributing the application, which can be a big deal if you get a bad actor between you and the proxy or god forbid he takes over the proxy.

    You can use this argument for Unix distribution which are using voluntary mirrors around the world. I do believe they work around this with the help of checksums, which they sign with a signature know to them within their software for updating the operating system.

  69. Re:Use the mobile web site instead. (Closed - Solv by green1 · · Score: 1

    Except that LinkedIn's website refuses to let mobile browsers connect to it and instead re-directs you to download their app. I had to change my browser's user agent string before it would even let me use it on my Android phone. Not exactly something that the average user knows how to do.

  70. App ecosystem by argStyopa · · Score: 1

    I don't really "get" apps in the FIRST place.

    I mean sure, I get that you have an app for scanning barcodes or other phone/tablet functions. I'm talking about apps for Pandora, or Delta airlines, IMDB, Amazon, etc.

    We have the internet.
    We have the web atop the internet, to provide a flexible and consistent UI for access of internet content.
    Why do I need to have separate apps for every bloody thing in 2017? It's like going back to the days of DOS where I had to have a separate program for anything I want to accomplish.

    --
    -Styopa
  71. It was only a matter of time... by Anonymous Coward · · Score: 0

    It's the natural progression of things. Personal computers started off with 38K or less, and now you can buy terabytes of hard drive storage for far less than a Commodore 64 and 1541 cost back in the day. As long as phone manufacturers keep adding CPU/RAM/Storage, developers will keep using it. IMHO It isn't necessarily a bad thing, as long as hardware innovation keeps up.

    (takes off Captain Obvious hat; hangs it up on a hook)

  72. Machine Lang People!! by Anonymous Coward · · Score: 0

    Write that shit in ML or GTFO!

  73. facebook ceo are pedophiles by Anonymous Coward · · Score: 0

    zuckershit know artificial intelligence as I know how to make heart sugery. that ai shit they created is a bot that messes up with google translator

  74. welcome to web 2.0 by Anonymous Coward · · Score: 0

    I don't see the problem. You all WANTED this. Its web 2.0. Some k0d3rz created appz. YOU wanted appz. Why the complaining? APPZ!

  75. When updates eat up your data cap by tepples · · Score: 1

    Even Apple who is the most overcharged of overchargers only took $100 to upgrade my iPhone SE from 16GB to 64GB, which makes app space a total non-issue

    Except Apple isn't "the most overcharged of overchargers" next to U.S. ISPs. If you have to cut home Internet from your budget in order to afford your cell phone bill, you have to make the best use of a connection that may cost 5 to 10 per GB, and it's impractical for app updates to consume the majority of your monthly data transfer quota.

    1. Re:When updates eat up your data cap by Anonymous Coward · · Score: 0

      U.S. ISP and cell carriers have nothing on Canadian carriers. I would give a kidney to get the service and price the majority of the U.S. has.

  76. In the old days... by Anonymous Coward · · Score: 0

    Developers weren't lazy and always looking for shortcuts. There are a lot of people who want to be developers for the cash-out but if skill = paycheck most would do better financially flipping hamburgers. Unfortunately, this is not the case.

  77. Features that WebKit leaves out by tepples · · Score: 1

    Why the hell do I need to sacrifice ANY space on my device (aside from maybe a few kb for cookies etc) to do something on my phone/tablet that I do from a browser on my desktop/laptop?

    This may happen when a web application uses HTML5 features that Apple has deliberately left out of Apple WebKit, which is the only web browser engine allowed to run on iOS. On an iMac or MacBook, an affected user can switch to a browser that runs Gecko (such as Pale Moon, IceDragon, or Firefox) or Blink (such as Vivaldi, Dragon, or Google Chrome). On iOS, on the other hand, Firefox and Chrome are wrappers around Apple WebKit.

  78. It Starts in Freshmen College Classes by Anonymous Coward · · Score: 0

    The first thing you are told in your first college programming class is that "resources are unlimited."

    Problem is, this mantra continues all the way through graduation, and on through careers. Nobody gives a shit about resources because they have always been told to assume resources are unlimited.

  79. Spam, SMS costs, and NNTP by tepples · · Score: 1

    Push content (notification of contact request) worked fine over email

    Until major email services' spam blockers started treating them as unwanted by default.

    and could even be sent as a SMS.

    Which costs a lot more to send (as in cents per) than a push over the platform's notification server.

    Sites like forums, where all the heavy lifting is done server-side, belong in a web browser.

    Long-time users of Usenet would disagree with you. They want forums to be available through NNTP, a protocol specifically designed for threaded discussions that has been around since 1986.

  80. Offline reading by tepples · · Score: 1

    Facebook is useless without an internet connection anyway

    Whatever happened to the use case of downloading updates while connected to the Internet, reading and composing replies while offline, and submitting the replies the next time you connect? That's how AOL used to work in the dial-up era.

    1. Re:Offline reading by MightyYar · · Score: 1

      I'd say what happened to that is reduced demand as internet has become more ubiquitous.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    2. Re:Offline reading by flargleblarg · · Score: 1

      I'd say what happened to that is reduced demand as internet has become more ubiquitous.

      And more mendacious. And more polyglottal.

    3. Re:Offline reading by MightyYar · · Score: 1

      Yeah I used to get teased for my vocabulary. When I was 10.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    4. Re:Offline reading by ShaunC · · Score: 1

      FlashSessions, now there's something I hadn't thought about in 20 years.

      --
      Thanks to the War on Drugs, it's easier to buy meth than it is to buy cold medicine!
    5. Re:Offline reading by flargleblarg · · Score: 1

      'Twas a reference to an episode of The Expanse. :-)

    6. Re:Offline reading by MightyYar · · Score: 1

      My apologies. :)

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
  81. Libraries and Frameworks by Tomahawk · · Score: 1

    Sorry from images, libraries and Frameworks bloat app size. You want to use this one feature from my libraries, but you need to include the full several-MB jar file with all the stuff you don't use. Multiply by many.

  82. Re:Use the mobile web site instead. (Closed - Solv by tepples · · Score: 1

    How many people actually carry both an iPhone to run apps exclusive to iOS and an Android phone to run apps exclusive to Android?

  83. From the silent minority... by Anonymous Coward · · Score: 0

    what apps? I can't trust my phone to be secure even if I take extraordinary steps to secure it, and I can't trust the app makers to respect my privacy. So I don't download or install nearly anything on my phone, and I sure as hell don't use social media, access anything important, or by anything using my phone.

  84. Suck it up by ilsaloving · · Score: 2

    What exactly would you have Apple or Google or any other app distributor do?

    The fact of the matter is modern day applications are *shit*. Todays average "developer" is a glorified script kiddy that slaps a bunch of components together, adds some glue, and calls it done. And the bits that developers write themselves are so shockingly bad, that bloat is inevitable.

    I mean, seriously..... Look at Facebook for example. The Facebook App + the Messenger app takes a whopping 3/4 GIGABYTE on iOS. The Slack desktop application, as good as it is, takes up a stupid amount of resources.

    This is what happens when you lower the bar to programming to the point where any John Doe can slap some crap together and think that they are now a professional developer. This is what happens, when you push a culture of "You don't need a degree to write code!", of "young and new is always better than old and previous".

    The focus is now on slapping some crap together and shoving it out the door, than doing things properly. As long as it runs, everyone is happy. The end result is low quality, ridiculously bloated apps that are replete with security issues. This has been a steady hole that everyone has been reveling in digging deeper and deeper, and that's exacerbated by the attitude that people who have learned from their previous mistakes should be fired to make room for young people who are still deep in dunning-kruger territory.

    App sizes are just a symptom of a much larger issue: Computing in general have gone to shit, and the tech industry is happily dancing a jig in their own filth because they've so completely drank the koolaid of their own marketing that they think that filth is full of rainbow sparkles, and they ostracize anyone willing to lift their head up and go, "Wait a sec here...."

  85. Of course not, totally fine by WillAffleckUW · · Score: 1

    I don't know what your problem is, using Internet 3 with a 100 Gbps port, that kind of file is easy to download.

    I mean, don't you all have 128 core blade servers with 512 TB storage?

    --
    -- Tigger warning: This post may contain tiggers! --
    1. Re:Of course not, totally fine by Anonymous Coward · · Score: 0

      I don't know what your problem is, using Internet 3 with a 100 Gbps port, that kind of file is easy to download.

      I mean, don't you all have 128 core blade servers with 512 TB storage?

      You must have a huge back pocket on your pants to walk around with hardware like that sticking out of it. Does it come with a it's own "Lumee" case?

      Tell me something. How big are your hands to pick up something like that to hold it to your ear to talk? Or do you use Bluetooth?

  86. We need the C64 back by MoarSauce123 · · Score: 1

    Back in the day where we had the C64 we would tweak and twist things so that space is saved. RAM was a premium, storage was in short supply, and load times were high. These days there are fat apps that include fat libraries of which only a fraction is used, and it all only works on really fat frameworks that run on fat operating systems. The exception here is Linux where a full OS with GUI and enterprise apps can fit on a dinky SD card that runs on an equally dinky 35$ Pi. The biggest kicker was the Windows app for WhatsApp which does not even allow to communicate with other WhatsApp users, but seemingly produces only a QR code that needs to get scanned with the phone...and that I could not get to work at all. The download package is about 80MB in size!! What the frack??

    1. Re:We need the C64 back by hackel · · Score: 1

      Unfortunately the trend is going in the opposite direction, even on Linux, with Snaps and Flatpack apps being distributed with their own complete runtime, unique versions of all required libraries, etc. ;It's disturbing.

  87. bloated app size means by Anonymous Coward · · Score: 0

    apps are approaching the realm of...

    programs? who would have thought that?

    apps were supposed to be small little programs that didn't do everything. or try to.

  88. Isn't Node.js server side? by rsilvergun · · Score: 2

    It's a JavaScript runtime. Is anyone using a JavaScript runtime for native client side apps that aren't just running in a browser? I'm not sure I see the point of complaining about server side apps. You trade performance and size for programmer hours.

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
    1. Re:Isn't Node.js server side? by mfearby · · Score: 1

      You can write client apps using node.js these days. Check out Electron, for example.

  89. This is the problem with the smartphone industry.. by hackel · · Score: 1

    When the vast majority of your users are non-technical people, you don't have to worry about things like file sizes. You just tell people to get a newer/bigger/faster phone, and they do it, because, you know...keeping up with the Joneses or something. Pretty pathetic.;

    This is why we need to get away from native apps as much as possible. They do have their place, but that place is a very narrow niche and getting smaller every day. Regular apps like Facebook and LinkedIn are literally just interfaces to these websites. Mobile web APIs are sufficient for pretty much everything these apps do. There is just no excuse for these massive mobile apps.

    I highly encourage the use of mobile websites (or wrappers for them to bridge the gap), and "light" versions of apps like Facebook and Messenger Lite. (Download size: 1.53M) Apps like these just prove that it *can* be done right. We just need to get the plebs to demand it.

  90. "how does an app that occasionally sends me a conn by Anonymous Coward · · Score: 0

    BECAUSE YOU WERE DUMB ENOUGH TO INSTALL IT!

    Filter error: Don't use so many caps. It's like YELLING.
    Filter error: Don't use so many caps. It's like YELLING.
    Filter error: Don't use so many caps. It's like YELLING.

  91. Here's what really happened by Anonymous Coward · · Score: 0

    Step 1: Developers write app for iOS because that's cool. It's 2010 and smartphones are new and hot.
    Step 2: Developers rewrite app from the ground-up for Android.
    Step 3: Developers rewrite app from the ground-up a third time for Windows Phone.
    Step 4: Developers rewrite app from the ground-up for iOS because Apple required it.
    Step 5: Developers rewrite app from the ground-up for Android to mirror newer best-practices.
    Step 6: Developers rewrite app from the ground-up for iOS because Apple required it again.
    Step 7: Developers rewrite app from the ground-up for iOS because Apple required it another time.
    Step 8: Developers rewrite app from the ground-up for Android in Android Studio because no one uses Eclipse any more.

    Step 9: Developers (finally) get tired of rewriting the same application over and over again from the ground-up every single damn year and start using frameworks that cross-compile for all platforms and libraries like the Android support library so that they can stay semi-current without too much effort. They also stop caring how big the final executable is. "Screw you Apple and Google and Microsoft. Get your act together already" is the common thought.

    Step 10: Blogger writes an article about app size bloat and Slashdot picks it up. "Screw you blogger. You try writing software for these mobile devices and see how far you get" is the common thought. It's also 2017 and smartphones and app development are mostly normalized.

  92. Framework fundamentals by jma05 · · Score: 1

    I was looking at app development frameworks a couple of years ago. What struck me was the sad logic of framework choice. If you wanted a cross platform app, the choice was a HTML based framework. HTML apps can be as tiny as web pages. Except the problem was, not all system browsers (across OS versions, across platforms) behaved the same way. So the devs are encouraged to bundle an entire browser runtime with even the simplest app. Modern browsers are very large applications.

    Another problem here is that mobile operating systems do not have really have package management. So every app keeps repeating some very large runtimes.

    It used to be that in 2003, when I wrote mobile apps, one considered desktop apps as resource free-for-alls and mobile apps as something where you carefully optimized for size, memory, performance etc. Mobile devices are much more powerful now, but they are still meant for efficient programming since the battery life is not a solved problem. Other resources are not that cheap either. I am always strapped for space on devices where a microsd expansion slot is not available. Yet, we are now behaving as if these problems have disappeared.

  93. It's simpler than that by cwsumner · · Score: 1

    This is an example of: "Code will expand to fill all available RAM space."

    If users don't complain then coders won't care.

    There are very few "software Engineers", but those that exist should care because the largest app gets deleted first. And word spreads fast, particularly these days.

    Fight back, check out apps before installing them. Particularly size and speed! ;-)

  94. When it's either home or cellular by tepples · · Score: 1

    internet has become more ubiquitous.

    Closer to ubiquitous, yes, but not quite. Wi-Fi isn't available on city buses in my home town, for instance, and I imagine that many aren't willing to pay for subscriptions to a both high-volume wired broadband ISP for use at home and a cellular ISP for use on the bus. Some choose to give up cellular Internet and are offline while riding the bus; others choose to give up home Internet and constantly worry about hitting their cap.

    1. Re:When it's either home or cellular by Cinnamon+Beige · · Score: 1

      internet has become more ubiquitous.

      Closer to ubiquitous, yes, but not quite. Wi-Fi isn't available on city buses in my home town, for instance, and I imagine that many aren't willing to pay for subscriptions to a both high-volume wired broadband ISP for use at home and a cellular ISP for use on the bus. Some choose to give up cellular Internet and are offline while riding the bus; others choose to give up home Internet and constantly worry about hitting their cap.

      And even people who do have both may well want offline capabilities, because we still go places where there is no WiFi and you're lucky if you can get a reliable enough signal to make a cell phone call.

      Which doesn't require that much: I live in one of the major metropolitian areas of the US, and there are parts of the cities within it that are locally infamous as being an excellent place to go if you don't want people to be able to reach you via cell phone. (Some of it gets kinda hilarious, because one of these dead spots is the main set of dorms for a major university...)

  95. Re:Microsoft updates / apple updates - No proxy ca by MachineShedFred · · Score: 1

    Under previous versions of Windows they had the "branch cache" service in the Enterprise edition. This would locally cache WSUS content if configured properly. Note that "configured properly" means having accurate records in Active Directory Sites and Services.

    --
    Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
  96. Re:Microsoft updates / apple updates - No proxy ca by tepples · · Score: 1

    The required software to be able to run TOECDN is a authority dns server and a http cache server.

    With web browsers deprecating cleartext HTTP in favor of HTTPS, how long will this remain relevant?

  97. Storage is cheap by Anonymous Coward · · Score: 0

    Storage is cheap so stop crying about it.

    I will make my apps as large as I need to, and you have no say in the issue. It's not subject to your "control".

    1. Re:Storage is cheap by Travelsonic · · Score: 1

      Disliking a trend =/= crying. Besides, storage may be cheap, but resource use should still be reasonable, and controlled when able - whether it be disk space, RAM, etc.

      --
      If you believe in privacy, and believe you have "nothing to hide" at the same time, you're a goddammed idiot
  98. Some games are smaller than these apps. by cgiannelli · · Score: 1

    My full IOS game Rocket Shark came in at 32 megs. It's absolutely insane how big these "mega corp" apps are. Is it all just packed with spyware or something?

    1. Re:Some games are smaller than these apps. by Anonymous Coward · · Score: 0

      itunes says it's 56 Mb ... like wtf?!...

  99. MS Outlook by Hamsterdan · · Score: 1

    Last time I downloaded that monstrosity on my iPhone 4S, it was a 113MB download. Seriously? 113MB for something that checks email? Last time I fired up my C64, I was running Skyfox in under 64K RAM (probably less, unless you bank-switched that 6510 you had 38K free RAM)...

    --
    I've got better things to do tonight than die.
  100. Re:Those numbers aren't real (but not a lie either by jittles · · Score: 1

    OK, the numbers are "real" in that "that is how much space the app is taking on Apple's server". It is not real in that "this is not the size of the files being moved to your device."

    What those numbers include: Multiple assemblies for different architecture platforms. The whole 32/64 bit thing is rearing its ugly head. There are also shared assemblies, not all of which get sent to your device (because they might already be there).

    Source: I'm an app developer who has had to explain this a few times as well.

    Sure that increases the size some but how exactly do you explain a 478.8MB Facebook install? 2 years of health-kit data doesn't even take up half that much space, including the health-kit app itself. And if you add in the cached data that my Facebook app has saved right now? It's almost a gig. Ridiculous.

  101. Whoa, a headline that violates Betteridge's Law!!! by Anonymous Coward · · Score: 0

    https://en.wikipedia.org/wiki/Betteridge%27s_law_of_headlines

  102. Easy to fix by Anonymous Coward · · Score: 0

    delete linked in from your phone. thats what I did.

  103. Interesting to compare to Android by ElizabethGreene · · Score: 1

    It would be interesting to compare this to android. The Uber app's apk is 30mb courtesy of https://apps.evozi.com/apk-dow... . Unzipping that dumps 97 megs of stuff.

    60 MB of java class dex files,
    18.2 MB of pseudo XML binary files in \res
    11 MB in \lib
    5 MB in \assets, half of which is a timezone database
    and the rest in yada yada.

    Can someone reply or PM a download link for the iUber package so I can compare it?

  104. Enough with it already by geekymachoman · · Score: 1

    So scrolling down I noticed most of the messages are about how bad programmers are nowdays (while discussing facebook, linkedin, etc. apps).
    That's just silly. These apps are not huge because nobody at facebook knows how to develop an application... such an assertion is stupid, and it's not true.

    Reality is often a lot different than what we (geeks) want it to be. It is not 1998 anymore, and modern requirements are forcing developers to make compromises that usually affect size and resource usage, and most geeks don't care about those compromises, but most users do.

    So you might be fine with a webpage that uses no JS, no CSS, just a couple of sprites and text and looks like it's been made in 1997, but common people (that companies generate money from) do care about site being sleek, modern and functional; something that just cannot be accomplished without using some kind of libraries that make life easier under pressure.

    Now carry on thinking how everybody else is stupid because they don't develop web sites in ASM.

    1. Re:Enough with it already by Anonymous Coward · · Score: 0

      Slow, bloated crap is not functional you dumb fuck.

  105. Re:Microsoft updates / apple updates - No proxy ca by fredan · · Score: 1

    > With web browsers deprecating cleartext HTTP in favor of HTTPS, how long will this remain relevant?

    Web browsers should and shall prefer HTTPS over HTTP. Have in mind that you don't know if the content served via HTTPS is secure or not. The protection that we get from HTTPS is that (hopefully) no one is listening to our communication between ourself and the server.

    If you would like to have HTTPS for TOECDN you will be required to distribute our private key to every single person on this planet! And that is just for one web site. And if you are re-newing your certificate, distribute that once more to everybody. The reason for this is that every house hold around the world is allowed to run their own http cache server. That's why you can't use HTTPS with TOECDN.

    If the web browsers had the capability to load for example a image file from a external host with the known checksum of that file, you
    can load that file from a HTTP host (read; over TOECDN) and you will know if the content match or not. If it does, well, treat it like you would if the content was served via HTTPS.

  106. Solution is just use the website by Anonymous Coward · · Score: 0

    Apps could be a lot lighter if they depended on standard web browsers to accomplish the view and then used web services to provide the browser with data.

  107. A rather insightful video about app bloat by Anonymous Coward · · Score: 0

    Watch Jonathan Blow's presentation about application bloat on youtube. Well worth the time and quite funny. The guy makes some valid points.

  108. Sandboxing = file duplication by Anonymous Coward · · Score: 0

    Unless the executable files are provided by the OS, they are going to be completely duplicated per install to the point where instead of installing an app you really are installing an OS update and an app. Code is very well factored and elaborate today, so these libraries aren't going to be tiny. It's just that a long time ago everyone would copy their libraries to System32 or w/e instead of the app folder so they only existed in one place per system.

  109. Re:Those numbers aren't real (but not a lie either by Anonymous Coward · · Score: 0

    That's right. That's why I can do a 150Mb app update in a few seconds - do people not look at this part?

  110. Re:Microsoft updates / apple updates - No proxy ca by Bert64 · · Score: 1

    Our old macs are all laptops, which are awkward and messy to put in the racks. Sure they work, and even have a built in UPS (which doesnt last very long anymore as the batteries are old), but they attract complaints from the datacenter staff as they look out of place.

    And i'm not talking about remote management once the OS is running, that's simple enough. I mean remote lights out management for when the OS isn't booted for whatever reason. Most server grade hardware has this facility, and its extremely useful especially when you have servers colocated in remote locations. Apple don't offer any hardware with this capability anymore.

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  111. I spy... by sad_ · · Score: 1

    it's because those apps are full of spyware and other bs. there was research done which found a popular weather app to contain more then 300 spyware links, no wonder it was big. Just write an app yourself, or check out those app sizes on f-droid, they are not that big, because they don't cary all that extra weight that you don't need (but the companies that make those apps sure do).

    --
    On a long enough timeline, the survival rate for everyone drops to zero.
  112. So what is the argument? by YoungManKlaus · · Score: 1

    That Android phones are "years behind" because you have to use the Vendor's app to get all camera features? Srsly?

  113. Apps AND Programs in general are FAT. by Anonymous Coward · · Score: 0

    Not only are Apps getting pretty thick around the waist, program sizes are out of control these days.
    If you've ever looked at the size of a lot of popular games these days, they are also stupidly big.

    Most devs simply don't care for optimization because they assume everyone has a decent device to run it because they have a decent device to run it.
    That's the problem right there, they don't care to test their stuff on anything but their own hardware, and maybe a couple friends at best. Once that bit is done, they NEVER test it again because they automatically assume that everything else they will do to it will still run fine on the same specs.

    Great example of this is Minecraft, a fairly simplistic voxel blockworld.
    It used to run on netbooks very quickly. Fast-forward a few years, lucky if you got 5FPS. Now? Literally can't run.
    Relatively speaking, the most demanding things updated were pathfinding, amount of resources actively loaded and a new (still pretty basic) lighting system, and the back-end chunk-loading system. That last one is what killed it.
    The new chunk-loading system is atrocious. Better than the McRegion chunk loading system, but still pretty damn awful.
    A technically more advanced game engine than Minecraft DOES run on them, however. (Minetest)