Conception-go

Thanks. You can see it at https://github.com/shurcooL/Conception-go#screenshot, but it's less than 10% finished at this point. Everything you see is rendered in OpenGL. The text editing component has syntax and diff highlighting support. It's written in Go, but I'm planning to have it running in the browser by compiling Go to JS and using OpenGL bindings with two backends: WebGL and OpenGL. In terms of usability, it's nothing more than a complicated tech demo atm; I need to figure out its future direction.

> Functions should be atomic, re-usable, repeatable, clearly defined, and well encapsulated. And when they're very long, it's a warning flag indicating that they may NOT be atomic, re-usable, repeatable, clearly defined nor well encapsulated. Also bear in mind that code is not carved in stone, but subject to constant change in every project that isn't deprecated, let alone in one under active development. This is why we judge its design not only by what qualities have been achieved up to this point - but also by whether the design serves to prevent them from deteriorating. A long function that's reusable at the moment is at much greater risk of becoming unreusable than a concise one. Readability is of great importance, too, since code is meant to be read by humans. Note that the author himself kindly replied to my comment and admitted tha

"there's nothing inherently wrong with a 500 line method if that's what the problem calls for" Yeah, "if", but that's rarely the case :) Care to show me an open-source example of a function 500 lines long where you don't think one could find proper seams to split the code along? Ideally in https://github.com/shurcooL/Conception-go/blob/master/main.g...

It's an open issue, please see https://github.com/shurcooL/Conception-go/issues/3 for more context. It was helpful to me to keep everything in a huge file during initial development for a few reasons: - I wanted to learn what happens when you break the convention that a project should be split into many files. - I wanted to test the limits of various tools I am using and building. The main.go kinda works as a worst case scenario so I can look at performance of my code and existing tools like sublime text, goimports, gocode, etc. - It allowed me to make faster progress implementing tasks in my limited free time, and I plan to delete/refactor the code to be nicer and more readable over time. It's effectively a compromise/trade off, I did not optimize for having the cleanest code as my top priority.

Sweet lord, https://github.com/shurcooL/Conception-go/blob/master/main.g... is nearly 9k lines long! What a spaghetti. Is that the author or the language?

Author here. I was just about to go sleep when I noticed a retweet and a lot of new stars on Conception; this explains it. The linked C++ project was the result of an initial year of working on it, which culminated in a winning entry to LIVE 2013 contest [1] and me switching to working on a version of it written completely in Go [2]. I no longer work actively on the C++ version, but I do on the Go one [3]. Primarily, it has been an extremely insightful learning experience. I had a lot of ideas and I wanted to try them, and by building Conception I found out the reasons why certain things that are commonly desired do not actually work well in practice, and why our seemingly outdated practices of writing code no different than decades ago are still so predominant and effective. It's really interesting to go back to my old notes and goals an

link to Go repo: https://github.com/shurcooL/Conception-go

Neat and useful. It reminds me of similar work I've done before at https://github.com/shurcooL/Conception-go/commit/02c5b49187d....

These are pretty and simple. Bookmarked for future use. It was only 15 days ago when I changed the background in my app to use a gradient [1], and I still think it makes it look much nicer. [1] https://github.com/shurcooL/Conception-go/commit/92ed6d952f0...

Thanks. :) It's an experimental software development tool, largely inspired by Bret Victor's talks. It's similar to projects like Light Table, Zed editor, but it's nowhere near as complete and focuses on a single programming language (Go). I worked on it full time for a year after finishing my master's degree, culminating in a first place winning demo submission to the LIVE 2013 contest [1]. By then, I ran out of money so I got a full time job and continue to work on Conception in my limited free time. By now, I'm working on a pure Go implementation of Conception [2], which is a lot more advanced in some ways, but is still needs a lot more work before it's actually usable and helpful to other people. Someday, when the time is right, I want to get back into it full time, because it really requires a lot of work. [1] http://liveprogramming.

An awesome idea! http://img691.imageshack.us/img691/1600/hahz.png That's a WIP port of Conception in Go. It's an experimental code editor/live development environment tool. What you see is an experiment at creating a Sublime Text/Atom-like fixed UI, with the list of Go packages in a tree view on the left, code in the middle, and various live widgets on the right. For instance, you can see a live git diff, the type of variable under your cursor, and various other debug things related to the parsed AST. Unfinished Code: https://github.com/shurcooL/Conception-go/commits/master

Compare: https://github.com/shurcooL/Conception-go - Go, 7'500 lines https://github.com/shurcooL/Conception - C++, 15'000 lines Which would you rather work with? You can look at the commit activity to see my preference.

Looks good so far. https://github.com/shurcooL/Conception-go/commit/78c4bad7219...