jamii

33 ms·

301.
by jamii 12y ago
> I think even FRP (as pure data flow as we get) is hierarchical since components (and sub-components) can still encapsulate state. That's an interesting point. We explicitly avoid encapsulating state in that way, preferring views t
302.
by jamii 12y ago
True, I hadn't considered that. The data-flow is not hierarchical, which is what distinguishes it in my mind, although apparently not in my commenting :) Let me back up and state my premises more accurately. Most successful visual lang
303.
by jamii 12y ago
> when you want to configure different executions with different behaviors without invasively passing down contexts That is certainly something we want, but I don't know if scoping is definitely the right way to do it, especially si
304.
by jamii 12y ago
Most of them don't use hierarchical data models, which is what we were discussing (I think?). Excel has one level of nesting (sheet.cell). Labview is a graph where components are grouped for reuse/abstraction. Access is relational
305.
by jamii 12y ago
That distinction is a historical accident. You can page a program heap to disk and you can run a relational database entirely in-memory (this is one of the common use cases for sqlite). True, databases and programming languages are usually
306.
by jamii 12y ago
> if you can manage your namespace separately Subtext style We do > the use cases are still different from dynamic scoping. What are the use cases? We so far haven't felt the need for any kind of scoping (although we admittedly h
307.
by jamii 12y ago
That's basically what we end up doing in the February section. It fixes the information passing problem but then leads to new problems with re-usability. You can't parametrise a function using only global scoping. So then we ended
308.
by jamii 12y ago
> They are going for a visual language 'Visual language' is a very overloaded term and we are in no way set on any particular ideology. Textual languages and visual layout have different strengths and weaknesses and there are l
309.
by jamii 12y ago
You can click though on the images.
310.
by jamii 12y ago
> The bad is not the hierarchical organization of data. That is the correct direction. This is just a repeat of the xml database vs relational database debate. This fight has been fought so many times before - http://citeseerx
311.
by jamii 12y ago
https://groups.google.com/forum/#!topic/light-table-discussi... TLDR: There are three new maintainers ( https://github.com/one-more-minute https://github.com/cldwalker https:&#x2F
312.
by jamii 12y ago
I was thinking of the fact that beautiful software is perceived as more usable, all else being equal ( http://www.ergonomicsclass.com/wp-content/uploads/2011/11/Tr... ). This is irrational but not controll
313.
by jamii 12y ago
Calling people out as #worseisworse is almost certainly going to be ineffective - attacking people just makes them defensive and argumentative. Instead, can we find useful principles to steer us away from the two bogeymen (hack-it-till-it-w
314.
by jamii 12y ago
> ...but rather is a confluence of the state of the market at various points in time... > That is, we do not merely calculate in earnest to what extent tradeoffs are necessary or desirable, keeping in mind our goals and values, there
315.
by jamii 12y ago
I read it more as frustration with the commonly expressed opinion that revolutionary attempts cannot succeed and that only incremental evolution is worth attempting. Not arguing that everything should be revolutionised, just that there is
316.
by jamii 12y ago
Diving in head-first is one of the best ways to get that knowledge. 'One day maybe' is awfully close to 'never'.
317.
The problematic culture of “Worse is Better”(pchiusano.github.io)
126 points by jamii 12y ago|116 comments
318.
by jamii 12y ago
I really enjoy reading the Bitsquid blog (two guys who made a game engine and sold it to autodesk). They have a much more balanced take on the subject (eg http://bitsquid.blogspot.com/2011/12/pragmatic-approach-to-
319.
by jamii 12y ago
There is still plenty of room for improvement. See eg http://arxiv.org/abs/1210.0481
320.
by jamii 12y ago
I'm not sure where you got the idea that we are proposing a language where nothing ever changes :p Both Bloom and Edelweiss are ideas about how to model time/change declaratively ie without having to specify control flow or incide
321.
by jamii 12y ago
Eve will be open source.
322.
by jamii 12y ago
For largely the same reason that relational databases need identity. The classic example is the users table. Everything about the user, from their username to their email address, can be changed. So you need some way to stably reference tha
323.
by jamii 12y ago
Bitsquid recently had an interesting 3-part post on the design of the entity system for their game engine: http://bitsquid.blogspot.com/2014/08/building-data-oriented-... http://bitsquid.blogspot.com&#x
324.
by jamii 12y ago
Have a look at the Edelweiss paper I linked. Stable ids are needed for that model. We would probably be fine with eg random uuids if we stuck with Bloom. EDIT: Thinking about it, the issue is definitely not that it is immutable but that it
325.
by jamii 12y ago
There have been various attempts to build logic languages that deal with uncertain information (eg http://www.is.informatik.uni-duisburg.de/bib/pdf/ir/Fuhr_99a... ).
326.
by jamii 12y ago
From a discussion we had about this paper, in the context of the relational logic language we are working on: Data abstraction is an interesting topic in a language that doesn't really have data structures. ADTs are usually used to des
327.
by jamii 12y ago
> It would be interesting to hear how much of EVE code has it taken to implement compiler or editor. The current iteration of the editor is 350 lines of our text-based Eve dsl plus 450 lines of helper js which will eventually become our
328.
by jamii 12y ago
We also get to have arbitrary names rather than trying to stuff everything into single word. "People who disagree with me on the internet" is a valid name for an Eve table.
329.
by jamii 12y ago
There is also much less stuff to disambiguate. The only names you ever refer to at the moment are tables. Most databases get by just fine with no namespacing at all.
330.
by jamii 12y ago
Programming suffers heavily from path dependencies. There are lots of suboptimal things that we are stuck with because of all the other suboptimal things. We are trying for a clean break.

More ›