El Tue Nov 25 2014 at 2:06:36 PM, kilon alios <[email protected]> escribió:
> > >> The comparison you're doing is wrong, you're comparing apples to > oranges. > > If humans had not the capacity to compare apple and oranges and find the > differences we would never have came down the trees. > It wasn't humans what came down the trees. But I got it ;-) > I don't mind being wrong, thats life. > > its huge for you, I have no problem with that , I wish you success to your > ever going saga of reducing size. I have no clue how tiny sizes will > benefit you as developer and your users. I would love to read your > reasoning. > > I am talking about the user experience , I am an adroind user I am not an > android developer nor do I care to enter the suffering zone of android and > web development , I had enough nightmares with C++. Out of curiosity I > check app reviews because I like to know that the app I am about to install > is not crap . I never , ever, ever , recall anyone complain about an app > being 60Mbs and saying "fuck this bloated shit I am unistalling it right > now" . 99.9% the complains are that the app was not even able to run and > usually is because of the know android incompatibilities , or the phone / > tablet is crap , or just the occasional bug. > I also speak about user experience. Updating a large app takes more time than updating a small one. A shorter period of installation means more conversions. > For me I would define as huge an app that takes around 80% of disk space > thats around 6GB since my nexus is 8GB in size. I am sorry bur I cant > justify calling something huge based on my simple skill on reasoning > something that takes 0.25 % of my storage . Its not even a 1%. > > As a developer if Pharo was 1GB large but could make android development a > piece of cake I would not hesitate to install it, assuming my phone would > be able to run it smoothly . I am serious. > The last assumption you make is the key here. Not all phones are Galaxy S5 or iPhone 5, and it will get worse as the upcoming wave of "Internet of things" devices will require software to run of it. But with a similar reasoning one could argue that it doesn't make sense to optimize communication protocols because links are getting faster everyday. Somehow it holds true, but if you start big, it's really hard to trim it down. I also dont care how one counts the size of an app, for me anything that is > associated with the app is part of the app, that includes all the data. > So deploying an app to manage 1000 pictures is the same as deploying THE SAME APP to manage Instagram? Sorry, but I don't get this. Usually your app server and your app data don't even share the same host computer, considering it is only one and it is not sharded/clustered. I ran Smalltalk applications with <20 MB of executable file / assets, and databases going from 10MB to lots of GB. And it was the same application. When I updated it I just had to update the exec files (the image mostly), the database was unchanged. So it was a 10MB update as much. > > Ironically we sit here and talk about the size of pharo would take on > android but Pharo cannot even run on android. I dont know I just feel Pharo > has much bigger things to worry about out than 30+ MBs. > It runs on Android. Even though it doesn't have a native Android look, nor it complies to most of the Android Development Guidelines. But I agree that 30 MBs is not something to worry about. I simply raised my longwinded opinion that I don't consider 30MB to be small on a mobile device.
