(This post was going to turn into an incredibly long bitchy rant about crappy directions, bad/lack of signs, and my overall frustration about finding a stop that doesn’t exist; but it’s bedtime and I don’t want to think about this anymore)
Today I needed to make a trip to IKEA and the closest location is in Etobicoke. There is a shuttle bus that goes from Kipling station to IKEA. This is the instructions on their website to get to the shuttle:
“The complimentary IKEA Shuttle leaves the north side of the subway (off of Dundas Street) on Subway crescent/IKEA every 30 minutes”
The location and size of Kipling station makes actually finding the shuttle bus stop very difficult to someone not familiar with the station and the area. Here is the location of the shuttle. It is right in front of a giant transmission line and there is absolutely no fucking sign.
For the last few years I have been poorly maintaining the Safe add-on for Firefox. A quick summary: it’s changes the border of a page and tab colour of secure websites - green for sites with EV certificates, blue for regular SSL, and red for broken SSL. For me, it gave a better visual cue to whether I was on a secure page rather than looking for the lock icon. It’s an addon that you don’t know you have until you feel something’s missing.
With the soon-to-be-released let’s encrypt coming, it gave me pause as to whether pervasive SSL is coming and what that means for the future of the add-on. Some people wish their projects will always stay relevant, but not me - or at least not this. A future where information is private from my machine to a server, whether it be in a trusted place like my home or in a shop’s open wifi, is a future that I would gladly put that add-on to rest.
(OTOH, maybe it would be put to rest without me. Hear about Firefox revamping their add-on ecosystem? :) )
One of the most challenging programming programs I ever attempted was a Pokemon Battle Simulator (PBS from now on).
My first, and most successful, attempt was on the mIRC scripting language. Though it was very buggy and not very easy to debug, it was possible for two people to actually have a battle.
My next few attempts revolved around moving it to C++ and using an OO language, but I was a pretty inexperienced programmer who had little time and those attempts were even less successful. Also C++ was the absolutely wrong choice.
Part of the complexity of creating a PBS are:
- There are straight-foward rules
- There are many exceptions to those straight-forward rules
This caused a lot of if-conditions needing to be sprinkled everywhere.
There were also bugs in the Pokemon game itself that needed to be replicated in the PBS. Things like toxic-leech seed that are likely bugs but it is an actual strategy (and a poor strategy at that).
So nothing ever got complete, and I eventually lost interest in Pokemon.
That was… over a decade ago?
Once in a while I think back and wonder what happened to the community. There were different PBS in existance, even when I left. Today, there seems to be an open source version available called Pokemon Showdown written in Node, though I could swear the last time I checked this out it was written in Java.