Skip to main content

The fluckiger.org guestbook is back, new and improved!

After a 5 year outage, the fluckiger.org guestbook is back!Please feel free to leave your thoughts, hellos, ideas, comments, poems, rants etc.

Check this out, I just used internet archive to retrieve messages left on the old fluckiger guestbook. The old guestbook was up between 2002 and 2004. It is fun to see the comments, back then having a guestbook was a really cool impressive thing!

I know a guestbook is an old fashioned thing. Old fashioned in Internet years which means anything over 5 years old. In 2002 I built a guestbook using asp.net 1.1 and an Microsoft Access database. My original guestbook at fluckiger.org was pretty popular. This was before facebook and blog comments which make having your own guestbook seem kind of pointless.

But this guestbook gave me a chance to flex my Silverlight muscles and is just the mustard seed. There is a lot of potential in Silverlight to bring back richness to human-computer interaction. We've been suffering through painful primitive UI and slow response times for quite a while now. Silverlight has the potential to bend the computer to the needs of people rather than what we've been doing over the past decade which is bending people to use the HTML in the browser just because that was the easiest and most secure way to deploy applications.

My guestbook is using some pretty cool technology. It is written in Silverlight 2.0 which is delivered from IIS 7 on a virtual Windows Server 2008 instance which is hosted in a 64 bit Windows Server 08 Hypervisor. The physical machine is a box I got off of Craig’s List for only $1500. It has 8 cores, 22 gigs of memory, and a 300 GB Velociraptor hard drive. This gives me plenty of room to run multiple virtuals. I am currently running: a project server farm, an Ubuntu Linux box, a Windows 7 box, and my SUSHI development environment which also hosts this guestbook. Sweet!

Comments

Anonymous said…
This comment has been removed by a blog administrator.
6:26 AM
Financial Services Education & Training said…
This comment has been removed by a blog administrator.
1:17 PM
Post a Comment

Popular posts from this blog

How to Create and Run Tableau Bridge on Linux Containers

Tableau Bridge is now availble on Linux Containers. Yay! Now what does this mean and how do I build and run Linux Containers? We will discuss the advantages of running Bridge on Linux Containers the steps to build them, and finally, we will provide some automation script ideas for monitoring and scaling Linux Bridge agents. Tableau Bridge Today Until recently, Tableau Bridge was only available as a Windows application running on a Windows VM. It supported only one bridge agent per Virtual or Physical Machine. Advantages of Bridge in Containers Better Hardware Utilization: Linux containers are more efficient than Windows VMs, requiring only about 1/50th of the disk space. Ability to Spin Up Multiple Bridge Agents: With Linux Containers, it becomes easier to spin up multiple bridge agents on a single machine, improving scalability and resource utilization. Infrastructure Automation: Linux Containers enable easier automation of provisioning bridge agents and upgrading Tableau Bridge, the...
1 comment
Read more

Unleashing Tableau’s Semantic Layer with AI Agents

⚡ TL;DR I helped built a tool that lets you query Tableau’s semantic layer  using natural language and AI. By integrating a LangChain agent with Tableau’s VizQL Data Service (VDS), we can repurpose Tableau’s trusted data model for conversational analytics . This means you can ask questions in plain English and get answers backed by the same definitions and security that your Tableau dashboards use. In this post, I’ll introduce this open-source agentic tool ( tableau_langchain ), why it’s transformative for analytics, and how it works under the hood. Why Connect LangChain Agents to Tableau? As a user of Tableau, I’ve seen how powerful Tableau’s semantic layer is. It encapsulates our organization’s business logic: things like predefined metrics, calculations, data relationships, and even row-level security rules. Traditionally, that semantic layer is only accessible through Tableau’s interface – you drag and drop fields to build a viz, and Tableau generates the query for you. Rece...
Post a Comment
Read more

RAM Disks do not speed up Visual Studio

  The limiting factor for Visual Studio is disk IO. I got a tip to speed up Visual Studio from Channel 9 by creating a RAM disk which sounded like a great idea. However, when I ran a thorough set of tests, I found that the performance difference between the Ram disk and the hard disk were not appreciably different. This was a big surprise since RAM is 240,000 times faster than disk (see my previous blog post). But the reason is because Visual Studio and Vista do a lot of caching. So compile times for the same project in RAM disk and on hard disk were pretty similar. I also tested the time it took to search the entire solution for a word, and times to open a solution. There was no discernable difference!   If you still want to try it out and create your own RAM disk, you can download a simple RAMDISK.EXE utility to create a RAM disk in just a few minutes. What is a RAM Disk ?   Ramdisk is a virtual drive created in RAM.   Performance Analysis Creating f...
10 comments
Read more