On 11-Oct-2014 12:38:50:
Yii; .; .;;`.
YY;ii._ .;`.;;;; :
_.;YYYYYYiiiiiiYYYii .;;. ;;;
`. :MM$$b.,dYY$$Yii" :' :YYYYllYiiYYYiYY
.,._ $b`P` "4$$$$$iiiiiiii$$$$YY$$$$$$YiY;
$Fi$$ .. ``:iii.`-":YYYYY$$YY$$$$$YYYiiYiYYY
:Y$$rb ```` `_..;;i;YYY$YY$$$$$$$YYYYYYYiYY:
On 31-May-2014 02:02:52:
As my twitter followers are already aware, I recently realized just how stupid Subversion's "tagging" behavior actually is. As someone who had never been forced to use CVS, I wasn't aware of what I was missing by not having real repository tagging. While goofing around with the various git web frontends, it finally dawned on me just how broken Subversion was. Let's take a little journey through some web frontends as a demonstration.
First off, this is a page most Subversion users will be familiar with. This is the commit log for a file as display by the popular frontend ViewVC. There isn't much more to say other than the top revision shown has a few tags made from it. (it is really hard to find a public repo with just the right amount of activity to make these screenshots)
Here is the git repository for git itself as displayed in the popular web frontend GitList. If you view a project on GitHub you would see a very similar interface. Coming from Subversion you wouldn't see anything wrong with this, GitList is a perfectly cromulent feature match for ViewVC's Subversion viewer. Of course, the reason you don't see anything wrong with this is because you've suffered brain damage from using Subversion too long.
This is a screenshot of CVSweb showing part of OpenBSD's repository. Notice how just by looking at the commit log, we can see where along the line each one of the tags was made? Because CVS has real repository tagging, it can easily connect each revision with the relevant tags. The CVS command line tools are more than happy to display this information as well, its not just a trick in the web frontend. The lack of this information in ViewVC isn't an oversight because ViewVC actually supports both Subversion and CVS and when it is used with CVS it display this information.
GitList on the other hand did simply leave it out, this is the exact same set of commits shown in the GitList image above but in the cgit repository viewer. Like CVS, git has real repository tags and the information is readily available at the command line by passing --decorate. Comparing cgit and GitList is what drew my attention to this. Of course, there is nothing wrong with GitList omitting this information, the git command line tools don't share it by default either. What drew my attention was that as an Subversion user I was completely unaware that this information was so easily available!
Subversion is effectively incapable of sharing information like this because Subversion does not have tags. Instead it simply has copies of directories that a team has agreed have special meanings based upon location. Doing some very basic operations on tags (like say show the commit log between two tags on the same branch) require you to jump through ridiculous hoops. People who have only experienced Subversion probably don't even realize how crippled they are by these "tags".
Subversion's atomic commit operations are definitely an improvement over CVS, but the fake tags are not as harmless as the Subversion manual leads you to believe. If you have only ever used Subversion, be warned that this unique "tag" behavior has likely warped your sense of what a VCS is capable of.
PS: Since inevitably someone will ask about Mercurial, as far as I am aware based on the hg documentation, it (like git and CVS) displays any tags associated with revision when viewing history. Finding a good public repo to use for a Subversion screenshot was hard enough, I didn't want to go try to find one for hg.
PPS: I made it my whole rant without bringing up the fact that Subversion "tags" are not read-only! (shit, nevermind)
On 18-May-2014 22:12:51:
Dell, we've got to have a little talk...
This rant has been 3 months in the making because I was hoping the situation would improve, but its not. You see, I have this little problem where I need a new laptop at work. Which means I need to nagivate the abomination that is your website...
Broken Search Functionality
A search of Lattitude laptops with the following options checked:
- Screen Size: 11" - 14"
- Hard Drive: Solid State Drive
- Graphics Card: Integrated Graphics Only
Returns exactly 3 unique models (9 total configurations. They are
- Lattitue 12 7000
- Lattitue 14 7000
- Lattitue 6430 ATG
Why have you omitted the following models:
There used to be more models omitted from the results, it appears to have been cleaned up a bit. The system also used to return results for laptops that were not actually available with an SSD. I'll give you some credit here, its better than it was 3 months ago, but its still pretty broken. I'm sure if I actually played around with it more I could find plenty more examples, this didn't exactly take long to notice.
Tech Specs do not match what you can buy
You can pretty much throw a dartboard at the website and find tech specs that are not actually available for purchase. Likewise, finding things available for purchase which aren't listed at all. Take the Lattitude 14 7000's processor options
- Specs list: Intel Core i3 (4010U)
- Actually available: Intel Core i3 (4010U), Intel Core i5 (4300U), Intel Core i5 (4310U)
It doesn't take much browsing to find tech specs unavailable for purchase, but I am not Dell's unpaid QA department.
So Dell, please fix your website.
Seriously, how hard should it be to find a laptop? I don't exactly have complicated criteria:
- 14" screen
- Have an actual gigabit ethernet jack
- Solid State Drive
- Intel Wireless (not gonna try to deal with your rebranded
broadcomatheros chips under Linux)
- Integrated Graphics
- Nipple Mouse (they are superior to touch pads)
Is that really that hard? Even six months ago you had machines that fit this, mostly because you actually allowed customization of machines. These days if the 4 pre-configured machines for each model don't fit the bill you are screwed. If you simply brought back the ability to truely customize machines these criteria would easily be matched by any number of models on your website.
On 17-May-2014 17:57:26:
On 17-May-2014 17:53:27:
Got sick of my overly complicated blog, still working out how the old simpler SQL-free stuff worked...
Looks like I have some mediocre category support, will probably remove that... seems to be working otherwise
Needs support for post titles too