YScan8: A YouTube "fervor" calculator.

I deployed a new web application to http://yscan8.herokuapp.com.

It calculates "fervor" for a given YouTube video. You can submit any video link to see its fervor.

The app is built with PHP. I used PHP 7.2.10, and the Laravel app framework.

Current SC2 Strategy Mindsets in All Three Matchups

I am a Diamond 3 Zerg. This is what is on my mind against all three races. I as usual struggle to remember to spread creep, inject my hatcheries, and saturate my expansions (and even main base).

I don't really have detailed builds for any of the three matchups.

ZvZ
I usually have a build like this:
16 hatch
15 Pool and extractor
19 Overlord
First queen, then second queen if the map is small like dreamcatcher, or a third hatch if the map is large like 16-bit.

I expect to make zerglings in the early game to try to have early fights. Then I expect to tech to roaches with speed, followed by 1/1 range/carapace upgrades, followed by hydras and then lurkers. The games usually end here if they have made it this far.

ZvT
17 hatch
16 extractor and pool
19 overlord
Queen and then either another queen or a third hatchery.

I frequently see an early factory and I make 4-5 roaches to counter what I expect will be a 4-hellion runby.

Other things I see are banshees (sometimes pooled), and a marine/tank/medivac push. I try to get a lair so that I can send an overseer into the Terran’s base to see what his plans are. Once the Terran has tanks out (at least one), I find it very hard to attack their base. So I try to max out.

Against marines I make speed banelings. Against mech I make almost pure hydras while trying to reach vipers for blinding cloud.

ZvP
This is a difficult matchup for me.

16-17 hatch, extractor and pool
19 Overlord and queen
Usually a third hatchery if I see that they indeed expanded.

I expect to make hydras against almost anything I see right now. Sometimes I try to use zerglings and speed banelings, too. I don’t really know what tier-3 tech to use. When they make carriers, I try to out maneuver them with nydus canals but this doesn’t work very well. I sometimes also try to make infestors for neural parasite. Actually, I do make lurkers almost every game against P unless they are trying heavy air all game. I find that lurkers and hydras work well, or as well as anyone could ask for at this level.

I will eventually get mutalisks and begin muta attacks on probe lines if the game goes on for that long. I do this against Terran as well.

Rails 5.2 SPA with React.js, Server-side Rendering, and Code Splits

Building on a prior tutorial implementation, I've expanded the functionality of a Rails application so that it is a SPA (Single Page Application). It uses React.js 16, and supports server-side rendering using the react-rails gem.

It also uses React Router to handle navigation between root, or top-level, components.

Server-side rendering makes things pretty difficult in a Rails application. I've had to do some research to get my server-side rendering to work as one would expect.

Dynamic loading of code splits is also something that is difficult to do, but my sample application does support this. The code splits are created using Webpack and the Javascript library react-loadable (not the latest version - I must use an older version of react-loadable to achieve server-side rendering that short-circuits dynamic imports).

The application is a mock Purchase Order tracking application. Items are available to be sold to customers. One can set item prices, and create and edit purchase orders that represent purchases of certain sets of the available Items in the inventory.

Data in the application is predominantly synthetic, and generated using the Faker gem.

This application is deployed to production at reactexperiments.herokuapp.com/. It is indeed hosted on Heroku as a free-tier application.

The Trello page for ToDos on this application is here.

The source code for this application is browsable on Github here.

React.js and Rails 5.1 tutorial implementation

This tutorial is a React.js tutorial from a couple of years ago.

I've completed an implementation of its specification, or goal, here on my Github account.