Skip to main content

Browser IDEs for general purpose programming

There are quite a few of them now:

  • cloud9 - sftp did not function properly. That was not a showstopper but it is frustrating. I have a private repo and 'go get' is not pulling from the private repo. This could be a common problem without baking in my ssh creds. (does not support 'go get' since it defaults the workspace to the current folder and does away with the src folder; and the IDE keeps losing my server in it's known_hosts) [latest go on c9: link1, link2; I should note that I was not able to compile go1.4.2]
  • nitrous - this one needs another try, however, it's cost is probably the highest in the group. And then came the truth.  They are charging by the minute.  It's a good thing I discovered this because it's not actually very good. They tried to create a complete container but then I could not clone a private bitbucket repo. My transaction amount is for $0.21 but they will not let me close out my account until they've posted an invoice; and presumably I've paid it.
  • codev - easier to uninstall than login
  • koding - 
  • codebox - 
  • sourcelair - using go version 1.2.1; which happens to be the same version as cloud9. I do not imagine that they are the same vendor or using the same engines underneath but something's wrong.
  • cde - incomplete and does not support bitbucket in git mode as there is a bug at BB and cde refuses to implement a workaround that others have already implemented.
  • caret - no DVCS support and seemed to be limited to the local drive
  • txt - good editor but not much in the way of an IDE and it certainly does not build. It would be nice if there was a terminal session or at least an SFTP option so I could still open an offboard window.
  • zed - just cheap
  • coding the web
  • shift edit
  • codenvy - I was having a good time with this IDE. It lacked any speed as it completely rebuild the target build environment each time making compiled, test a very long operation.
  • codeanywhere - complicated pricing options although they seem cheap. Still seems to be missing something.
  • tailor -  I got stuck in the IDE trying to commit my code.
  • codepress
  • ra - simple and incomplete
  • code your cloud - might be interesting although it's young and seems to be run on my servers. Not a bad thing but I don't trust them yet.
  • tedit - I need to give this one another try. As with cde it does not support bitbucket's version of git and so I would need to move my project.
  • keypress editor - deleted before it could be tested as the help page returned a 404. I hope it has not been hijacked.
There are probably many more but for the moment I'm looking for a few key features: 
  • quality editor with syntax highlighting
  • need to be able to execute goimports against my code
  • github and bitbucket integration
  • compile, test, run my code
  • either checkout my code to my Chromebook or some other similar functionality
And so there are a few things in the works. 
  • I need to get gitlab running on my servers
  • I need to get my turbo editor implemented
  • I need to support git, hg, and fossil
It's my general conclusion that I need a real server to do this work. I can also make a good case for running an IDE like Coda, from Panic.com, and then some docker commands like gnatsd from Apcera. This has been a tremendous waste of time.

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…