He SED, She SED: Toshiba’s new SED TV

Another tv technology is on the horizon. Should be interesting to see how it really stacks up.


Toshiba SED TV

We hate to drop yet another acronym on you, but we really have no choice now that Toshiba has just unveiled their first flat-panel TV that kicks LCD, DLP, LCoS, and plasma to the curb and instead uses a new technology called surface-conduction electron-emitter display, or SED, which is supposed to have the brightness and contrast of CRT displays, but use one-third less power than of plasma TVs. First ones could go on sale as early as next year.

…excerpt from: http://www.engadget.com/entry/5732841184005838/

More on Subversion

Been using it a bit more, so have some further comments. It’s definitely setup to allow for offline work. Basically having a local copy of the repository attached to your working directory means all diffs and reverts could be done without having server access. In my case, this doesn’t matter as I’m running locally, but could be very useful if you wanted to do some work away from server access.

One shortcoming I’ve come across is removing a group of files. Quite often you will delete a file outside Subversion, and then want to remove all the deleted files from version control. With CVS, all you did was do a cvs remove in the directory, and it would schedule all the missing files for removal. Subversion lists the missing files, but I haven’t found a way to tell it with one command to remove all the missing files from version control. I have to do a svn delete on each file. Hopefully I’ll find a way to do this.

Version Control – Subversion

Just recently started using a CVS replacement called Subversion. Thus far, seems very good.

It’s big advantage is it recognizes directories as well as files. Uses binary differences for binary files, rather than storing a completely new copy of the file. Allows for renaming/copying of files and directories. Understands what deletion of a directory means.

The other big thing is it understands a big change. i.e. it treats a commit of multiple files as a unit of work. The revision numbers are updated for an entire directory when a commit is done, and are global across a repository. This means can see all the files changed for a given commit, rather than CVSs approach of merely incrementing the revision of each file individually.

The claim is that Subversion is more network friendly. It does this by basically keeping a local copy of the files in your working directory. The feeling is that hard drive space is really inexpensive, and network traffic is best minimized.

Supports branching more elegantly than CVS ever did. A branch is created by making a copy of a repository directory. Has commands for retrieving some changes and merging, but I haven’t used this portion yet, so don’t know how useful it is.

There is a tool for converting a CVS repository to an SVN one. I tried running it, but I must have mixed up my tags when I originally created my repository as it complained. Since I don’t really care that much about my change history, I didn’t bother trying to track it down to get my repository imported to SVN. I just started fresh.

Well worth a look.