Submissions for mobile apps for iOS are subject to approval by Apple’s App Review team, as outlined in the SDK agreement, for basic reliability testing and other analysis, before being published on the App Store.
Applications may still be distributed ad hoc if they are rejected, by the author manually submitting a request to Apple to license the application to individual iPhones, although Apple may withdraw the ability for authors to do this at a later date.
The terms Stack and Heap get thrown around a lot in the programming world. But what does it means? What is the difference between them and why should we care?
To start, I would like to make a clarification on a possible misconception. Heap is referred here as a memory allocation technique, not as a data structure. Furthermore, when we speak about Heap as opposed to Stack, we do not mean two types of memory, what we mean is two ways of allocating memory.
When your code compiles (or run if interpreted), the compiler needs to consider how to allocate your variable definitions in memory. To understand this process, let’s first examine the pros and cons of each type of allocation.
If you agree that nothing paints a better picture of your software project like a well maintained UML class diagram, then this post is for you.
I have been fascinated with Golang because of the versatility of the language. I wanted to take advantage of the Golang parser and a great software called PlantUML (http://plantuml.com/) to create a program that will translate my Golang code into a neat class diagram.
where Swift is overtaking Objective-C rapidly and the momentum is clear. In the
Android world, presently, the language option is not that clear.
Yes, Kotlin is
there, new, coming forward, garden-fresh, 21-century ready but it isn’t ultimately
taking off, not as expected.
Kotlin was first
introduced by JetBrains in 2011, which is the creator of IntelliJ IDEA,
PyCharm, and many other top IDEs. It got its name from ‘Kotlin Island’ in St.
Petersburg, Russia. Made to strike Java.
That said, the
dominance of Java is still immense, the number of libraries, APIs, code
generally speaking is humongous. Not to mention the readability of it, the many
algorithms and things done or thought already in Java, yeah… Simple as it
sounds, it’s hard to break a solid present for a “uncertain” bright future.
One of the most exciting aspects of the software development process is experiencing the steps leading to a pleasing solution to your problem. That moment when, after some time of thoroughly brainstorming, everything falls into place. I had such a moment today, and I would like to share my story.
This morning I was faced with a simple dilemma. I needed to perform a GET request containing a large payload to the server, but I didn’t want to show it in the URL. The reason for the GET request is that I wanted to give the user the ability to download a file with a click of a button. The purpose of the large payload, the requirements for this file. You see, this file is a zip archive that the service will dynamically construct and deliver to the user. The issue is it can potentially contain thousands of files inside, and I didn’t want to clutter the URL with this payload.
That is when it hit me! I have been using Redis for some time now, and I thought this would be a great use of it. With that in mind, I set up to develop the following idea.