BrowserMetrics

This blog is dead. Long live this blog!

Labels: computing, Nogizaka46

This past Christmas I was fortunate to hold the final number in our annual Kris Kriminal game. Apple AirPods had been revealed already so I stole 'em. Luckily, I ended up the night with them. Most likely the best Kris Kriminal present I had chanced into. So, with that, you know this review will be mostly positive.

Once they were officially mine, I opened the box, pulled them out of the charging case, put them in my ear, and pressed play. Music came through smoothly. I was mostly amazed that the pairing happened almost instantly. It wasn't as quick as my description lets on, but it wasn't a hassle. I didn't even have to open the Blue Tooth settings to start the pairing. It just happened.

I really only tried it that night once and left them in my gift pile for the next few weeks. It wasn't until the new year that I decided to put them to the test. I have kept them in my pocket for the last two weeks. I don't use them every day, but I do pull them out once in a while to listen to Nogizaka jams during work. I am always in amazement that they fit in the ear just right and do fall out. Admittedly, I have not exercised with them in but they feel snug, never loose or ready to fall out. YMMV.

I love the carrying case. It fits in your pocket and also doubles as the charger. You can keep it forever in your pocket, ready to deploy at a moments notice.

My only problem so far is pairing with other devices. I believe you have to erase its knowledge of the previous device in order to add a new one. I think. I didn't read the directions.

Anyhow, it's pretty neat and should make up for the lack of input jack on the newer iPhones.

Labels: computing, review

I gave you Shiraishi Mai yesterday. Her beauty must've blown you away. Today, I'll give you Nishino Nanase. Okay, megane + pony tail. I'll take her back.

Not sure why, but I feel like trading in my Apple stuff...

Labels: computing, NewsRadio quote, Nogizaka46

If I was asked what computer to have for my job, I think I would choose 「マウス」. But only if it comes with Shiraishi-san as tech help.

Labels: computing, NewsRadio quote, Nogizaka46

I should've made 'buying books I don't read' one of my New Year's Resolutions. I stopped into the old B&N and bought a couple of books. I wanted to pass the time and rack up some steps, but I ended up with a couple of books.

The first book is trying to get me to learn Japanese so that I can talk to my idols, Nogizaka46, at one of their handshake events in Japan. I would like to encourage them to do their best: 頑張って！ I've bought several books. And have yet to apply myself to reading and learning. At least I've got a little bit of hiragana and katakana, but without a vocabulary it will be difficult to understanding anything. Hope this book starts me off.

The second is learning about node.js. We're using it at work. And I'm trying to figure out what it is. Will I be able to read it?

Japanese For Beginners by Sachiko Toyozato
Learning Node.js: A Hands-On Guide to Building Web Applications in JavaScript 2nd Edition by Marc Wandschneider

Labels: bookstore haul, computing, learning japanese, software development

Link of the Day [9.24.16]

When you go distributed and base your work in the cloud, always remember, "There are no files on my hard drive." Your local machine does not own the files on the local file system. The cloud does. O, you may think the files are there, but that is just for the moment. The files are in the cloud. Accept that and prepare for it no matter what. Accept that they could disappear at a moment's notice. Prepare for them to disappear at a momennt's notice.

Excuse me while I back up my drive...

http://talkingpointsmemo.com/edblog/maybe-be-careful-with-osx-sierra

Labels: computing, lotd, NewsRadio quote

I prefer Emacs. Vi makes you crazy especially the first time you load it up. You say how the hell do I enter text. Then you want to quit, and you'll say how the heck do I quit this program. Then you force kill the process to exit and never come back.

Plus, there are Emacs key bindings within OS X therefore the muscle memory is there while using my OS of choice.

Vi is the devil.

http://www.slate.com/articles/technology/bitwise/2014/05/
oldest_software_rivalry_emacs_and_vi_two_text_editors_used_by_programmers.html

Labels: computing, lotd

Network storage will become a bigger and important part of the home-consumer market with the adoption of tablet computers. Currently, iPad 2 maxes out its SSD drive with 64 GB worth of disk space. The Kindle and the Nook tablets are on the low end of storage, but Amazon wants you to use their cloud and perhaps Barnes and Noble does, too. Yet, as consumers go digital with their books, magazines, movies, television, and photos, there is going be a need for local storage.

There are Network Attached Storage (NAS) devices already being sold, but it's not a category that the average consumer will know about. This area is ripe for someone with an Apple-like bent to come in and remake the market.

Here's how I would make my own NAS appliance:

First, wireless and wired. Allow it to be connected by a physical connection.

Second, web browser interface. Configuration should be straightforward for the least tech savvy of users, but allow for as much customization under the hood for those techies.

Third, hot swappable. Drop in a drive and it should be ready in a click of the mouse. Plus, the chassis for this thing should contain 1-10 drives slots, but are adapted by price point: cheap is 1 drive, expensive is 10 drives.

Fourth, BYOD. The user can use any drive they want. Old 5200 RPM spinning platters? Go for it. SSD? Go for it. Mix and match. Do it.

I know about Apple's own NAS, Time Capsule, but that is for Apple's backup use case. I'm talking about something for everyone. I'm sure that you'll be buying something of this type in the next year or so.

Labels: computing, genius

We are all going to IPv6 sooner or later. Today, they are starting to roll out the changes. If you didn't notice anything wrong with the internet, then all is well.

You should test out if you're ISP is ready. Or is this only for ISPs?

http://test-ipv6.com/

Labels: computing, doom, lotd

So with iOS5 Twitter integration, will my number of followers increase? And what's it mean for ping?

Labels: computing, iPhone, just asking, tweet

When Artificial Intelligence goes dumb.

It's an interesting item, because it is an example dumb computing. Dumb computing is dangerous. If they don't learn, how do we? WOPR should show us the way.

http://www.michaeleisen.org/blog/?p=358

Labels: computing, lotd, oops

"I think they started out with the goal of being open, but they are learning that this approach doesn’t work in the world of phones where tight tolerances on user experience require much more coordination between hardware and software."

iOS versus Android: OS Footprint is not a Proxy for Application Footprint

Labels: computing, qotd, software development

Last weekend I replaced the venerable LinkSys WRT54g router with the completely awesome AirPort Extreme.

The week prior I had noticed a whine coming from the LinkSys. That was strange as routers don't have a spinning hard drive. What could be making that noise? So to shut it up, I unplugged it to reboot. That did the job no more whine.

I went about doing house chores for an hour before I had the chance to use a computer. When I did use my computers, I found that I couldn't access the internet. I quickly glanced at the lights on the LinkSys. It looked okay.

I tried to access LinkSys's browser-based configuration screen. "No route to host." I tried pinging its IP address. "100% packet loss." I looked closer at the router's lights and noticed that the LAN LED wasn't on. Since it was next to another LED that was on, it looked alright but, sadly, wasn't.

The LinkSys router was kaput.

Luckily, I have had an AirportExtreme in my possession for a year now. I was going to replace the LinkSys a year ago, but was too lazy to shut down all computing devices, change out the router, then reboot all computing devices and configure them. Out of necessity, I now had to do it.

I shut down all laptops, except my main MBP. I took the Mac Mini down, too. IPhone can stay on but I switched to just the cellular network. The 0G iPhone I didn't bother. Using the MBP, I began configuring the replacement network.

Apple's Airport utilities make this easy. You could just follow the wizard to set it up, but I liked to have control of my configuration. Manually, I went about configuring the AirportExtreme router. Lots of same settings, I ported from the defunct LinkSys -- network IP addressing, MAC address filtering. Others I changed -- new wireless ID.

I brought online all computing devices and reconfigured them for the new wireless network. The TiBook gave me trouble because, I think OSX Tiger, didn't like to remember the new wireless network name until I created a new Location for it.

Overall, it went smoothly. At work, I have to deal with networked software nodes, and it is a pain in the ass to debug network trouble. Who's causing what to whom all happens in the invisible ethernet and it takes some understanding of how networks work to find and fix the trouble. My new house wireless network was stood up without too much hassles.

The sole issue I have with my new wireless network is what to do about the AirportExpress. I had originally used this to extend the LinkSys network via bridging, because I couldn't get wireless coverage throughout the house with just the LinkSys router. With the new AirportExtreme, I don't need it, but I didn't know when I started reconfiguring the network. I tried configuring the Express for bridging, but it cause conflicts on the Extreme. Only when I abandoned the Express did I realize that the Extreme is powerful enough to provide coverage throughout my house (and my neighbors, too). Therefore, the Express sits silent on the floor waiting for a use. I'll probably try to configure it with my stereo system so I can stream music through it.

The new network is up. I'm planning to put a network drive off of it, perhaps SSD. I want to try that back to my Mac feature. It's also faster since there is only one wireless station.

I'm back online thanks to the Apple's AirportExtreme router; it's cold white face and unblinking, green LED comforts me.

Labels: computing, Saturday Evening Post

Looking for storage solutions for my computers at home, I settled on this external hard drive. 500 GB of space! Like the title suggests, this drive is more space than all the computers sitting in my house currently have combined!

What to do?

Partition it? Should I break it down into smaller logical spaces? Most of my computers are already partitioned. I'm afraid that I may need to save a 300 GB file.

Start back ups? Eh. I'm not too worried about losing data. Yet.

Re-install Tiger, 10.4? Booting off the fire wire would be cool. But why?

It's a lot, but I really would've liked to put this on the network as a network drive. The solution to that would be this, but that's another expense. I tried looking at this, but it would've forced me to use a weird PC file system. Complicated.

Labels: computing, Macs

The new MacIntel hardware was shown off yesterday and surprises of surprises, a new laptop that is not a updated iBook was revealed. Sadly, it was saddled with the lamest of lame names: MacBook Pro. That makes such a sexy piece of equipment sound like a dorky financial application.

I cried when I saw it though. It makes it all the more harder to get the dual PPC G5 desktop I so crave. Hmm. Can I have more Macs in my house than need?

Labels: Apple, computing, Macross

Okay it's been almost a week since I have set up my Mac Mini. Really only 5 days. I want to make note of some things that I have experienced while using it.

1. I need an Apple specific keyboard. I am using a split keyboard that I have had since my old Dell PC Win95. It works for typing, but there are things missing. The Windows key is the Apple/Command Key. I don't know what the Alt key is for. Honestly, I had a hard time telling what the option key was for on a Mac keyboard. The arrow keys don't work correctly. The home, end and page down/up keys don't work either. I know that I can always get a key mapping software and correctly map these things, but I would really like to have a Apple specific keyboard. Split keyboard. For Christmas. See my Amazon Wish List.


2. At first, I thought that the fan was as loud as my laptop, but I am wrong. It's quiet. The CD/DVD drive though is loud.


3. I partitioned the drive into three partitions. 25 Gb for the system. 12 Gb for Users. 35 Gb for Data. Is that enough or should I get an external drive?


4. I want to turn it into a file serving machine. Can anyone help me find out how to do that?


5. Installed the dev tools on the machine after a 900 Mb download. Apple does not include the dev disk with this machine. That's a mistake as having free dev tools is a plus in my book. How can you convince people to develop software for the OS if you don't give them some help?


6. Trying to figure out a synchronization issue for my machines. How do I go about maintaining two different computers with similar data? Like if I want to access files off my laptop how should I do it? This will begin to be a complicated issue once I have the third of my PPC Macs.


7. Should I install all applications that I have on my laptop here? Or should I wait for the third machine?


8. Tiger is pretty cool. I use the widgets a lot. I have a sudoku widget and also the Rejks widget for the Rejks museum. There pretty neat.

Overall, I am happy with my purchase. This is what I bought with my promotion.

Labels: computing, Macs, mini

I now know why they have established a net meeting protocol. I have to coordinate putting together a slied presentation for class on monday. And I only have my part done. What happened to the other stuff? We need some collaboration tools online. Tout de suite!

Labels: computing, school

Low End Mac does a run down on how Apple created notebook fever. People wanted one of these from the get go. In fact, my first Apple was a PowerBook 140. I currently own a TiBook and have been trying to resurrect my PowerBook 190. For as much as I have loved Apple, I have only owned their laptops. No desktops. Yet.

Labels: computing, Macs

On monday, Steve Jobs turned my world upside down. He announced that Apple is intending to switch to using intel processors. So long PowerPC. Hello x86.

It has been rumored for a long time now that Apple always had a build of OS X which compiled on x86 chips. Monday saw confirmation of that rumor and a bold new direction for Apple.

It has taken me days to figure out how I want to blog about this. I am an Apple loyalist. My family has owned an Apple since the early 80s. I know where my Apple ][e is. I had an original Powerbook 140. It became the ultimate Civ machine for my brother. I bought the last of the Powerbook 190s. Imagine a world of 8 bit graphics. Nothing but shades of grey when the world was going color. I write this on my 1GHz TiBook, the one before the Aluminum ones. I love Apple. Always rooted for them.

It was more than Apple being not Microsoft. It was also about not being Intel. Remember Wintel is an insult in Mac circles. Now Apple has embraced the dark side. As if the megahertz war would not been won "not by a PPC chip."

As software engineer and comp sci student, I have been exposed to x86 instruction set. It sucks compared to PPC. It is halfass backwards and inelegant. It also has to support a lot of older instructions from the 80s. The PPC chip was RISC. Gorgeous and nice instruction set.

I am mourning the loss of the chip more than I can imagine. Strange. Being an Apple loyalist means that you understand that Apple is more than just the computer, the OS, the box, the chip, but is a lifestyle brand. But to me the PPC chip is also part of the brand. Can I support Apple? Is Apple still Apple with Intel Inside?

Ars Technica sums up my feelings of the loss of the PowerPC chip. John Gruber is a good read to understand what needs to happen for Apple.

Labels: Apple, computing, it's over

Forgive me for the crappy shot that this picture is, but I had to show some of the fun stuff I recently purchased or was sent to me. I took this shot with an iSight that my cousin sent to me as part of a payment he owes me. It is of my new 20" cinema display. I have it hooked up to my TiBook and using it as a second monitor. Having dual displays rocks.

Labels: computing, home, Macs, picture