Light Table 0.8.0-alpha
groups.google.com
groups.google.com
I used LT when learning Clojure but once you graduate to doing major production work, it's not really the best tool, too limiting.
It's also the easiest to extend, modify, and generally make into the perfect(if slow) editor.
Also, it has the prettiest themes. But I'd be fooling myself if I didn't say I'm keeping a serious eye on NeoVIM to possibly alleviate me.
Did I have to adjust my workflow a bit for it? Sure. But honestly, the dividends its paid in terms of making it easy to create snippets, easy to fork and extend addons, and in just making me smile through dumb pretty UI things is totally enough. And the vim folks that use it and keep pushing it further and further are having a good time, 'cause aside from a few buggy commands it's a joy to vi around Atom.
Like I said in my original post- it's slow, but you can make it the perfect(if slow) editor if you want to, and that's pretty well.
I really enjoyed using light table for a few years but not working in clojure, the integrations were never really something i explored to make the weight worth it, and it often had issues with freezing for fairly simple operations.
[1] https://github.com/LightTable/Emacs [2] https://github.com/LightTable/Vim
The first thing I do on a new Windows laptop is swap the left alt and ctrl keys to match the way it was meant to be. From wiki (https://en.wikipedia.org/wiki/Command_key):
> The purpose of the Command key is to allow the user to enter keyboard commands in applications and in the system. The Macintosh Human Interface Guidelines have always recommended that developers use the Command key (and not the Control or Option keys) for this purpose. A small set of keyboard commands (such as cut and paste, open and save) are standard across nearly all applications, and many other commands are standardized (Find, Show Fonts). If an application needs more shortcuts than can be obtained with the twenty-six letters of the Latin alphabet, double modifiers such as Command+Option are used.
> One advantage of this scheme, as contrasted with the Microsoft Windows mixed use of the Control and Alt keys, is that the Control key is available for its original purpose: entering control characters in terminal applications. (Indeed, the very first Macintosh lacked a Control key; it was soon added to allow compatible terminal software.)
This is frustrating. I grew up on Windows machines and remember having frequent discomfort from overstretching my pinky to reach the left control key. When I first began using Macs a few years ago the first thing I remembered was thinking "Wow using the command key is so effortless!". Now I've had years of typing with zero discomfort.
I just bough a Surface Book and was dreading using a Windows keyboard again. So I searched around a bit and most recommended swapping control with alt to match the Mac keyboard like you said.
1. Why do I have to use third party software to swap alt and control in Windows?
2. I know there's some historical reason why control is the primary modifier... but here we have Microsoft developing ergonomic keyboards for 20 years and no one thought, "gee wouldn't it be more ergonomic to put the control key where the alt key is?". If that's too extreme, at least provide a simple software setting to change it!
We have companies spending $500-$1500+ on ergonomic chairs. I wonder what percentage of those using Windows machines have used third party software to swap control with alt (or caps lock). I bet less than 1% - because it's not simple for the average user. I don't know if frequent overextending of fingers leads to any serious problems or simply discomfort like I had, but it seems like such a simple thing to fix. Start releasing keyboards with control and alt swapped and provide a simple checkbox in Windows 10 to revert it for people who want the old behavior. I'm not an Apple fanboy, but hey they were brave enough to reverse the scroll direction on the touchpad and deploy that to every single OS X user AND they provide a simple way to revert the default via settings. /rant
Of course with the right hand on the mouse, the left hand is often used to perform both key presses. If this causes you pain, gaming mice offer programmable buttons which you could configure to give you Cmd/shift/Ctrl or other common modifier keys (or just copy/paste macros). I've seen this done to great effect.
I'll have to disagree with you on using the mouse also. Taking my hand off the keyboard to use the mouse every time I want to Control-C, Control-V or use any other shortcuts is not really an acceptable solution.
Why are we so afraid of simply using the alt key location? :) Are there any Mac users who reassign command key to the "fn" location on their keyboards, caps lock, or their mouse? I think it's unheard of... because the command key location on a mac keyboard is a non-issue. The only time Mac users reassign the command key input is when they are using a Windows keyboard (to make it mimic the mac's keyboard).
If I were them, I'd double down on becoming the de-facto Clojure/Clojurescript IDE. Lots of surprise-and-delight features out of the box.
What I meant was, of all the people I know that have both positive things to say and for that matter anything to say about Light Table, they've been professional Clojure developers. Therefore from my view, if I were guiding Light Table at the moment, since it has been three years, I'd really look into pleasing and making those people a very happy customer base. I would do this at the cost of other support, because in my opinion the other languages aren't being used professionally or personally with Light Table. (Perhaps they have different metrics, but if I were them, I'd double down on making a very happy set of Clojure evangelists and then re-visit support for other languages)
I finally switched to Cursive Clojure, stuff just worked out-of-the-box with no surprises.
Disclaimer: I'm a Light Table maintainer
It is fascinating because both of them are quite similar in nature and picking one instead of the other doesn't mean you're missing out on a major feature.
https://groups.google.com/d/msg/light-table-discussion/fgnl0...