Earlier quoted context omitted.
Alright, what do you want me to fix then?
It requires a lot of effort to get information. The embedded auto-playing video reminds me of pre-Facebook social networking, requiring further effort turning it off (especially after scrolling down trying to figure out what's what) before a user can then move their cursor around the site to access the content they wants.
Light Table reaches 300k necessary for Python support
21–30 of 37 posts
Re: Light Table reaches 300k necessary for Python support
#22Earlier quoted context omitted.
That website is awful.
Alright, what do you want me to fix then?
The screenshot isn't readable, feels odd tacked on at the bottom, and if you click it, you don't get an enlarged version. This is a language, not an editor, right? That's what the title says. But where is the hello world? Where is the list of snippets to give you a feel for the language?
Re: Light Table reaches 300k necessary for Python support
#23Earlier quoted context omitted.
> As if money would magically make hard things happen :) If those hard things require people working full-time on solving them, then yes, money does magically makes them happen. > Seriously, what if Python is specially hard to support for some reason? This is engineering and computer science, there are no magical reasons, only specifics. What would make Python difficult to support exactly? It has full introspection,…
Well, I imagine one reason is that there are exactly zero static call sites in Python. Everything is called by name, and monkey-patching is, for better or worse, an accepted and widely used tactic. I have seen projects that use Python's source code introspection facility to rewrite code inside decorators. You can even define new keywords in this way. Decorators in general are a widely used tactic to execute arbitrari…
I'd dispute this.
Re: Light Table reaches 300k necessary for Python support
#24Earlier quoted context omitted.
Alright, what do you want me to fix then?
Not the op, but some considerations: The screenshot isn't readable, feels odd tacked on at the bottom, and if you click it, you don't get an enlarged version. This is a language, not an editor, right? That's what the title says. But where is the hello world? Where is the list of snippets to give you a feel for the language?
Re: Light Table reaches 300k necessary for Python support
#25I still can't believe people are paying this much attention to a glorified text editor.
As programmers, we spend most of our working time in glorified text editors (I'm using mostly Emacs at the moment, which that is certainly an apt description of). I guess it's natural to be excited about new alternatives for our primary tool.
Re: Light Table reaches 300k necessary for Python support
#26Earlier quoted context omitted.
> As if money would magically make hard things happen :) If those hard things require people working full-time on solving them, then yes, money does magically makes them happen. > Seriously, what if Python is specially hard to support for some reason? This is engineering and computer science, there are no magical reasons, only specifics. What would make Python difficult to support exactly? It has full introspection,…
Well, I imagine one reason is that there are exactly zero static call sites in Python. Everything is called by name, and monkey-patching is, for better or worse, an accepted and widely used tactic. I have seen projects that use Python's source code introspection facility to rewrite code inside decorators. You can even define new keywords in this way. Decorators in general are a widely used tactic to execute arbitrari…
Where you are certainly right is that monkeypatching may occur in a project and this is only one of many ways that Python's being very dynamic makes it extra hard to write static analysis tools.
The rm -rf problem is not as bad if you are previewing (say) a page view, which hopefully is not being developed on a production server and hopefully doesn't contain an rm -rf. But I agree that solving this in the general case is probably intractable without some kind of container.
Re: Light Table reaches 300k necessary for Python support
#27Re: Light Table reaches 300k necessary for Python support
#28The bp editor has similar features (code bubbles), though dynamic evaluation and code bubble workspaces are still in development. And I'm pretty sure it won't cost me 300k to finish it. http://blitzprog.org/
Editing on an AST is a neat idea. I think it is a neat idea for an editor. Coupling tightly to a particular editor is going to hurt the adoption of your language, just like coupling to a particular language hurts the adoption of your editor.
But it seems like you have some neat ideas and I hope you are not too discouraged by the negative feedback.
Re: Light Table reaches 300k necessary for Python support
#29Earlier quoted context omitted.
What call graphs? Everything in python is call-by-name. `globals()['foo']` isn't exactly a very strong reference, and anyone can change it.
In practice, those things are hardly changed. When they are, users understand that the IDE might not be able to help them,
Re: Light Table reaches 300k necessary for Python support
#30The bp editor has similar features (code bubbles), though dynamic evaluation and code bubble workspaces are still in development. And I'm pretty sure it won't cost me 300k to finish it. http://blitzprog.org/
I would love to see this evolve into something bigger. Keep up the good work!