Monday, July 27, 2015
Artyom.js – Voice Recognition with Javascript
Artyom.js is a voice recognition javascript library. You can make awesome stuff with Google Chrome speech synthesis and speech recognition. You can build your own Siri, Google Now or Cortana within your web application.
by via jQuery-Plugins.net RSS Feed
Speeding up Existing Apps with a Redis Cache
We’ve gone through the basics of Redis in PHP before, but it’s time to cover a real life use case. In this tutorial, we’ll add it to an already deployed application to give the app the appearance of speed.
You can easily follow along by cloning the 0.6 release of the app.
The Problem
Before applying a solution, we need to have a clear definition of the problem.
The application in question, when executing a query, runs off to Diffbot’s API and makes it query the dataset. The subset is then returned and displayed. This can take up to 5 or so seconds, depending on the busyness of Diffbot’s servers. While the situation will undoubtedly improve as they expand their computational capacity, it would be nice if a query executed once were remembered and reused for 24 hours, seeing as the collection is only refreshed that often anyway.
“But what good is caching a single query?” you might wonder. It’s not like most people will search for one and the same thing often.
Well… as a matter of fact, not only has research shown that they will often search for one and the same thing (React is trending? Sudden influx of “react” queries), they will also very reliably search for prolific authors (or themselves). Considering the fact that implementing this cache costs us literally nothing (and actually reduces costs by reducing strain on the servers), adding it in is an easy win, even if it weren’t used as often as one would hope. There is no reason not to add it - it can only benefit us.
With the problem clearly defined, let’s handle the prerequisites.
Continue reading %Speeding up Existing Apps with a Redis Cache%
by Bruno Skvorc via SitePoint
Counting Real Words with Ruby
Wait a minute, do you mean this blog post is just about counting words in a document? First, it is easy enough, and second, this can be done by any word processor on the fly.
You are right in that it is about counting words. However, the aim of this blog post is to show how flexible Ruby can be in meeting our desires on counting what we determine are considered words. This is in opposition to the word processors we use, which likely will not be able to determine such criteria.
Let me clarify this point a bit further. When a word processor is counting words, it takes the white space as a delimiter. As a result, what comes after that will be considered a new word and included in the word count.
What if you have a number, a standalone letter, email address, etc.? Do you consider those words? I don't. Word processors will not give you the option to filter the counted words.
Continue reading %Counting Real Words with Ruby%
by A. Hasan via SitePoint