This is my personal blog and portfolio. Feel free to explore. I tend to write erratically about anything that interests me. As my tagline goes, "Code, photos, books, and anything else". Exactly right! Read more about me...
Also under development: the main element (status) and date-related input types (status).
There are still many steps to be taken, but I see main and srcset as key ones to match the other browsers and to accommodate modern web development. Love it or hate it, Internet Explorer is still a significant browser and these signs of progress are encouraging.
While I’ve always been primarily a Windows user, I have also from time to time used some Linux distro or another. One thing that stand out in sharp contrast is the relative ease of installing software. For example, when using Ubuntu, installing a package is as simple as:
apt-get install [package name]
While on Windows, one must go to the appropriate website, download the package, and run the installer or extract the archive. For one software it may not be an issue, but when, say starting up a new computer or a fresh install, locating and installing all required software becomes tedious quickly.
Chocolatey was devised as a solution to the above described problem. The description of the site’s homepage describes it thusly:
Chocolatey NuGet is a Machine Package Manager, somewhat like apt-get, but built with Windows in mind.
Once installed, Chocolatey can be used similarly to apt-get and other package installers; it can be used to install packages and update those that it was used to install. Chocolatey supports adding package feeds, even private ones. The Chocolatey community contributes and maintains the packages listed on the website (check the listing). The installation for Chocolatey itself is described on the homepage, and can be done with one command in Powershell.
Once Chocolatey is ready, installing, say, LINQPad is as simple as:
choco install linqpad
All of the package entries on the Chocolatey site include the command to run to install the given package. In some cases, there are multiple versions of the package, so a specific command must be used.
Having recently started anew with a fresh Windows install, I decided to use Chocolatey to install some of the software I commonly use. These included, but are not limited to:
I could go on, but it would be a pretty long list. In the above cases, I just had to search the listing, find the package name, and run:
choco install [package name]
And Chocolatey would handle the rest. This saved me having to go to each of the respective websites, download the software, and go through the installer for each. I did have to search for each package on the Chocolatey site and run the appropriate command, but it still saved a fair bit of effort.
Perhaps I haven’t worked out how yet, but it would be useful to be able to install multiple packages at once. Maybe a batch file would be enough.
There has been concern previously about the open nature of the Chocolatey community which might allow miscreants to slip in malicious software as part of a payload. Senior community members have begun reviewing and approving packages, which creates some peace of mind that the community will remain healthy. Further, a recent Kickstarter campaign was successful in raising money to pay for efforts in maturing the ecosystem, adding non-free features, improving the infrastructure, and allowing the core team to put more time into the project.
Further still, it was recently revealed that the upcoming Windows 10 will feature the new OneGet system (1, 2). OneGet is intended to be used for managing package distribution systems, it isn’t itself intended to be a package manger. The current implementation includes support for Chocolatey as a distribution channel. Like Chocolatey, OneGet is open source and a community-driven effort.
It is exciting to see one of the notable remaining differences in Windows versus e.g. Linux being resolved. OneGet looks like it may be one of the upgrade points for Windows 10.
As they say, a project is not any one thing, but made up of many things. So it goes with a degree: many classes, three work terms, long days and late nights (too many to count), caffeine overloads, etc. And the people. Oh yes, I’ve met and worked with many people over the years, such that they became part of the experience.
A degree is not just about the piece of paper waiting at the end. In a big way, it is about the people met and things done along the way.
ASP.NET vNext is looking to be a very interesting release, in part due to the way the team has changed its development process. Various components under the ASP.NET umbrella are being developed separately, and will be distributed in the form of focused libraries through NuGet. The ASP.NET GitHub account shows the way these are progressing individually.
The topic link points to a master list, compiled by Tugberk Ugurlu, which lists literature currently available about the different components in progress. There is much related reading material listed also.
I recently traveled to Seattle. The last time I went, I did not arrange for US-based connectivity for my cell phone, so I was on roaming mode while updating Facebook, taking and uploading photos, and looking up information on the go. I got clobbered on my next phone bill. Well in advance of my more recent trip, I decided to prepare by signing up for a travel-friendly service.
Enter Roam Mobility. This Canada-based company provides mobile connectivity to Canadians traveling to the USA.
To use Roam Mobility, one must have a Roam Mobility SIM card. While this can be ordered from the company website, it is likely also available in local stores. I was able to purchase one in London Drugs for $20. I then had to register the SIM on my Roam Mobility account:
With the SIM attached to my account, I then set up a service plan for the duration of my trip. The offerings are surprisingly inexpensive compared to the prices offered by the Canadian carriers – the comparisons are revealing. There are a number of overall plans available:
While I did not anticipate needing phone calls or text messages, there were no data-only options, so I selected the Talk+Text+Data option. The next view revealed specific options:
Fortunately, I was in Seattle for much of three days (over a weekend), so the 3-day option suited me. Selecting that, I was able to select my already-registered SIM to attach the service:
The option is provided to specify what days/times the service should span. The website notes that multiple plans can be set up consecutively for continuous service over a longer period, if needed.
I then went through the payment process which was straightforward. I purchased the SIM, created an account, and set up the service a few days in advance of the trip.
On arriving in Seattle, I took the cover off my phone, removed my normal SIM, and inserted the Roam Mobility SIM. There is then a little configuration to be done on the mobile device – Roam Mobility provides directions for common smartphone platforms. It’s really just a matter of updating the Access Point Name setting. I made sure to keep my normal SIM in a safe place during the trip; on my return home, I switched the SIMs again to go back to my regular service.
This was overall a straightforward process. The website provided enough information on how to make the network change when appropriate. The network was quick where there was good coverage, which applied to most parts of downtown Seattle that I passed through.
The primary caveat is that the phone must be unlocked so it will work with SIM cards from other carriers. I thought – assumed! – mine was already unlocked, so started my stay in Seattle with a phone that could not use the local network. Oops. Fortunately, my hotel had secure guest Wi-Fi, so I was able to purchase an unlock code and have my phone on the T-Mobile network the next morning. Once I got past that hurdle, all was good.
To sum, I had to purchase a SIM, purchase service for the weekend, and purchase an unlock code. Added up to more than I planned on, but the SIM and the unlock code are one-time purchases. In advance of a future trip, I can just use the same SIM and attach another service plan to it. Lesson learned: make sure the phone is unlocked before traveling!
Catching up on a backlog of news feeds, I happened on the post by Sarah Gooding on WP Tavern regarding the value of blog comments. The post was inspired by CopyBlogger turning comments off earlier this year; ironically, the WP Tavern post has 56 comments as of this writing, in and of itself affirming the value of comments on blog posts, never mind the comments themselves.
Why Comments Matter: My Opinion
My view is that comments are part of what make up the blogging experience, both for the writer and for readers. The following list lays out my reasons for having comments available on my blog, and why I like seeing them on other blogs:
They encourage readers to add supplementary information, link to other resources, or just to thank the writer for the post
This can lead to the comments section adding a wealth of value to the original post, often in the form of additional information or links to elsewhere
Comments provide the writer feedback, acknowledgement for the post, and a sense of satisfaction
I don’t get a lot of comments on this site, but I’m always pleased to receive legitimate (non-spammy) comments
Commenters make themselves known to the blog author, as well as to other readers
Leads to social connections and networking – even if it is over the internet
They encourage conversation on the site, on the same page as the post
Discussion can be done over e.g. Twitter, Facebook, or other means, but having comments as part of the blog keeps the conversation intact and reduces external dependencies
The above list applies to me as both a blog writer and a reader. I get value both ways, and I suspect many others do as well. That is why I keep comments open on this site for some time after posts are published (I do close them eventually to prevent spam trickling in on old posts).
For me, the bottom line is that comments facilitate two-way sharing of information, enable creation of connections, and add a bit of humanity to what would otherwise be monologues.
A very eloquent review of where WordPress stands in today’s web and of what it can be made into. Includes ideas for where WordPress might go in the future, some criticisms, and input from notable community members. Well worth a read for anyone who wants to check the current view of WordPress. Some good discussion in the comments as well – whoever said comments were dead??
TechEd 2014 is on, and I’m envious that I’m not in attendance. However, Telerik, purveyor of controls for application development, are giving away licenses for their Windows 8 and Windows Phone control packs over the duration of TechEd. I’ve gone through the claim process, the licenses are equivalent to the one-year subscription options, and apparently can be renewed or upgraded. Not only that, but Telerik are working on components for the new universal apps, and have stated that these new components will be added free of charge to the accounts of any who get the free tools this week!
This is a fabulous offering for those on the fence over trying the tools, and very timely for me as I was planning to purchase a Windows 8 pack. I save some money now, and just might be renewing later – many thanks to Telerik for the freebie. The generosity is much appreciated so I can get started on Windows 8 application development.