Skip to main content

Passing on the MacBook Air

Looked into Apple Macintosh Laptop computers, as the new lab is a mac lab and decided to pass on the MacBook Air.

In comparison to the MacBook I found
Pros:
  1. Light - 3 pounds (vs 5 pounds for Macbook and my current HP DV2210us)
  2. Illuminated keyboard
Cons:
  1. Max memory is 2Gb (vs 4Gb)
  2. Max CPU brawn 1.8GHz Core 2 Duo (vs 2.4 GHz Core 2 Duo)
  3. 80GB 4200-rpm 1.8in HDD (vs 250 GB 5400-rpm 2.5in HDD)
  4. No optical drive (vs 8x DVD burner)
  5. 1 USB 2.0 and NO firewire (vs 2 USB 2.0 and 1 firewire)
  6. No ethernet port
  7. The power connector and the USB slots open out awkwardly from the case base [engadget]
Mostly, this machine will be plugged into a keyboard, a large monitor and will sit on a desk doing number crunching and paper writing (Macs do all the work for you, right, not like PCs where you actually have to write the paper yourself). I imagined the awkwardness with which the MacBook Air would sit, with no ethernet cable, always relying on a wireless network, even for DVD burning/loading, with that side slot half propped open because I want to use a flash drive to move a file. So I decided to go with a fully muscled up MacBook that is as small (the tabletop size is just a bit smaller than the Air), slightly heavier, and has double the memory and triple the harddisk, and infinite times more firewire and ethernet.
Labels:

Comments

Post a Comment

Popular posts from this blog

A note on Python's __exit__() and errors

Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or
Post a Comment
Read more

Store numpy arrays in sqlite

Use numpy.getbuffer (or sqlite3.Binary ) in combination with numpy.frombuffer to lug numpy data in and out of the sqlite3 database: import sqlite3, numpy r1d = numpy.random.randn(10) con = sqlite3.connect(':memory:') con.execute("CREATE TABLE eye(id INTEGER PRIMARY KEY, desc TEXT, data BLOB)") con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", sqlite3.Binary(r1d))) con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", numpy.getbuffer(r1d))) res = con.execute("SELECT * FROM eye").fetchall() con.close() #res -> #[(1, u'1d', <read-write buffer ptr 0x10371b220, size 80 at 0x10371b1e0>), # (2, u'1d', <read-write buffer ptr 0x10371b190, size 80 at 0x10371b150>)] print r1d - numpy.frombuffer(res[0][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] print r1d - numpy.frombuffer(res[1][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] Note that for work where data ty
Post a Comment
Read more