Light Table 0.6.6(lighttable.com) |
Light Table 0.6.6(lighttable.com) |
I know many of our users/contributors are from here so thanks to all of you for the awesome involvement we've seen. You guys rock :)
Also, I think that the LT team had said that they couldn't achieve as much feedback as they wanted to without developing a new language (that I'm guessing is a bit more progressive than Swift) in order to allow for a more interactive experience.
So, with no insider info, I'm guessing that if they hadn't started developing their own language they may have been leapfrogged, but given that they don't really have to language design constraints around Cocoa/Objective-C semantics maybe they are still pretty far ahead. The harder part is getting enough programmers to care, even if they come out with something really revolutionary.
> The harder part is getting enough programmers to care, even if they come out with something really revolutionary.
That's true, but even programmers will have a hard time ignoring some of the claims we'll be able to make :)
In any case, our work on Light Table is a small step compared to where things are headed and at the very least, I can promise there are interesting times ahead.
I understand lighttable 0.5.9 to be the most recent that works.
I'll get excited when I can CHANGE THE F##KING FONT without editing a F##KING config file (after reading the help and being redirected to watch a #*%!@! video).
Why does Atom send usage data to Google Analytics?
In the same way that aggregate usage information is important when developing a web application, we've found that it's just as important for desktop applications, especially during the beta program. By knowing which Atom features are being used the most, and how the editor is performing, we can focus our development efforts in the right place. For details on what data Atom is sending or to learn how to disable metrics gathering, visit https://github.com/atom/metrics.
Regardless of who will be the users, opt-in is the civilized and respectful way for this sort of thing.
Got me started to think about:
http://mattmaroon.com/2010/11/23/i-quit-hacker-news/
Matt's reasons:
1. Lack of down-vote means vocal minorities are
disproportionately represented.
2. Votes on comments are used to express agreement
or disagreement rather than value, perhaps because
many people simply cannot see the difference
between the two.
3. The community is full of ideologues to the point
where the comments are most often just predictable
talking points being regurgitated ad nauseum.
4. The community is often snobbish and out of touch
with how the other half lives.
5. It's a time suck.
6. It removes comments from where they should be,
on the destination site.
7. It reduces blogging time.
Disclaimer: I'm a devotee of HN; It's home, but also I'm a devotee of critical thinking.
Clearly this is about comparing the editors. Analytics is orthogonal to that. If you want to talk about the costs and benefits of Google Analytics them I'm sure there's another thread where it is more relevant.
Igglyboo's comment is probably downvoted because they don't "seem similar" at all beyond the idea that they both work with code.
Not when it's included in the editor as a default[0]. If we want to strictly compare editors then we should talk about Codemirror instead of LightTable. This point is really moot. I've used both Atom and LightTable and while I'm not going to argue about the pros and cons of either (I ditched Atom for various reasons), even just thinking about putting some Google web tracking device as an opt-out (instead of opt-in) really makes me abhor Atom.
You can disagree with me and you can prefer Atom over LightTable, it's all good, however downvoting because you don't like simple statements that are true won't make them any less true.