Skip to main content

Embedding TCL in my Go application

This has interesting potential as I consider the extensibility of both my Macroinator and Flow based programming projects. (flow is not published yet as it is in the middle of a complete refactoring)

The target OS, for this example, is OS X Yosemite. And the first dependency to install is TCL. I'm using homebrew to install tcl (alternatively Jim) instead of the Apple version or the source from the source.

It's important to note that while brew works in userspace and is highly curated this is still an attack vector for the bad guys.

1) install tcl with brew
brew update
brew install homebrew/dupes/tcl-tk
** note that tcl-tk is located in the homebrew/dupes folder. This is to indicate that the project tcl-tk duplicates some of the features in OSX.

** brew installs the proper tcl-tk, not jim, and does not offer Jim as an alternative. The tk portion of the install requires some legacy X11 libraries and that makes me very sad.

For the next step I need to install the tcl/go bindings. Looking at the landing page for gotcl I noticed that there are plenty of missing elements in the project so I'm going to try gothic. (Gothic also supports tcl/tk 8.6 which is what we installed in step 1.

2) install Gothic.go
env GOPATH=/Users/rbucker/gocode go get github.com/nsf/gothic
At this point unless you've previously installed X11 header files and libraries you're going to get a compile error about a missing header file. So at this point I abandoned all hope of the tcl-tk working.

3) uninstall tcl-tk
brew uninstall tcl-tk

4) install cask
brew install caskroom/cask/brew-cask
** cask is a set of edge case brew tools. I'm not sure if there is any additional risk loading from here but I'm trying anyway. My bunny sense is telling me I should have created an OS X VM and practiced there.

5) install tcl
brew cask install tcl
** This is a different version of tcl. This one happens to be from ActiveState. I like those guys. I'm not exactly sure how much is their code but if tcl is going to work these guys are awesome. If you're going to write proper tcl you might want to try their tools. I think they can produce proper cross platform executables but it has been a while since I read anything about them.

** one other note about installing this tcl.  I was prompted for my admin password. So my bunny sense was justified.  Onward we go.

6) install gothic

I tried the same command again.  And got the same response. So now I'm unwinding cask just so I'm not giving up too much space etc.

7) uninstall cask tcl
brew cask uninstall tcl
8) uninstall cask
brew uninstall caskroom/cask/brew-cask
** even though something was installed as an admin user; when I uninstalled I was not prompted for the same admin credentials to remove them. Hmmm...

Now that this was a FAIL... there is one other thing I'm thinking about. The piccolo project shows just how easy it is to implement a variation of the tcl language. In this case batteries are not included but it feels like something I might want to do instead of building my own parser/compiler.... although with my new found experience with generate it might just be an option. But it's a topic for another conversation.

Another link to more tcl info.

UPDATE: This is an interesting implementation from the CoreOS team.  Mayday is a monitoring tool but their task design makes the whole thing interesting and more like I am intending except I still need a hybrid in order to be more general purpose.

Comments

Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: http://www.eeti.com.tw/drivers_Linux.html (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the setup.sh answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…