If you use NodeJS on your Backend, you have probably run into memory problems at one point or another. Compared to other systems where a child process is created and terminated with every request, Node is initiated only once, long-running, and particularly unforgiving in any task that leaves residue behind.
This post is an attempt at explaining how to dive into the seeming mess of memory lane and come up with insights, or better yet, solutions.
Continue readingEither use background image, or the fancy new object-fit on <img> tags, which works almost exactly the same as background image:
Wow… What you can achieve with just JavaScript.
Where to find:
*All the references of the talk are in the Author’s note part under each slide.
Machines need to talk to each other, but they all speak different languages. In order for them to communicate, they need a common ground for talking, a set of rules they could all follow and use to understand each other. XML-RPC is the name of one of the sets of rules people come up with. There are other specification of rules apart from XML-RPC, like JSON-RPC, SOAP, WSDL, CORBA and REST.
Open finder. Press Command + Shift + G. Paste this in:
~/Library/Containers/com.amazon.Kindle/Data/Library/Application Support/Kindle/My Kindle Content
If you see this:
Sometimes the files you’re trying to ignore had already been submitted into version control on previous occasions. To ignore those existing files, you’ll need to re-submit them as deleted files. After which they would be removed from the repository. It looks like .gitignore isn’t working, but it actually is.
How to solve the problem of:
To perform the requested action, WordPress needs to access your web server. Please enter your FTP credentials to proceed.