I was delighted to find that I still remembered the phonetic names after first reading of them back in 2013, though I got the exact result wrong.
801 karma · joined August 11, 2011
I was delighted to find that I still remembered the phonetic names after first reading of them back in 2013, though I got the exact result wrong.
That said, in my experience if Apple has secretly decided they don't like you, they tend to move the goalposts on you in subsequent reviews, so migrating their systems to WebKit may not be time well spent.
If you have sixteen views on a cell and their locations all depend upon each other, it's going to take a long time to solve those constraints. But if you can break up the cell, say into four subviews with four elements inside them, it's likely to be faster (no guarantees, though)
I have looked into this. It is kind of criminal that for most real world languages (Ruby[1], C[2] etc), it's not possible to just define a grammar and throw it at a standard parser generator for them - they generally have one or two quirks which make this infeasible.
In my ideal alternate universe it would be considered unthinkable to publish a language without also publishing a grammar in a standard format for said language, which can then be plugged into your favourite text/semantic/tree editor. Our tools should dictate our languages, not the other way around.
[1] http://programmingisterrible.com/post/42432568185/how-to-par...
I am thankful that these days I get to work with talented designers who know what a UITableView is and understand the limitations of the medium.
I'm not sure if that would be a good thing or a bad thing.
Previous/future states simply appear adjacent to one another so you can scroll through them easily.
I absolutely believe that version control history is something that needs to be treated as a dimension like any other
PS, if you're as enthusiastic about this idea as I am, we should talk, can I email you?
That said, during my research I ran across an ancient Usenet thread from 1989[1]. In it, the OP asks:
> Should the language designers be making work for the language-oriented editor designers or should the language-oriented editor designers be making work for the language designers?
(The thread rapidly devolves into an all out flame war about whether or not C can be considered to be context-free)
Lisp feels like a language designed specifically to make a language-oriented editor designer happy, but most other popular languages fail the context-free test one way or another, thus making them difficult to define good grammars for. The problem seems to be that historically the language designers have far outnumbered the language-oriented editor designers.
[1] https://groups.google.com/d/msg/comp.lang.misc/MCZmQv56--Q/O...
tl;dr: the dream is over
Some links:
* http://everything2.com/title/catting+weird+things+to+%252Fde...
[1] http://www.antipope.org/charlie/blog-static/fiction/toast/to...
[2] http://www.antipope.org/charlie/blog-static/fiction/accelera...