Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

> Basically, render(a(b)) is not render(ab) where a(b) denotes that the html element a depends on the html element b for its definition.

This is a new example. How does that contradict any of the previous points that I (and the OP) made? I fail to see that, can you explain?



sort by: page size:

> You seem to be stuck on the 3rd definition

Quite possibly. I concede the point.

> It's quite common to refer to things being rendered to another forms

I think it’s my mathematical background. I tend to think of these kinds of processes as ‘transformations’.


> The code is not transformative because the quoted code is not used for some other purpose like as part of an article discussing whatever the code does, it is used to do exactly it's original job.

Hmm..

> The printing press is not transformative because the printed text is not used for some other purpose, it is used to do exactly it's original job.

See the error in your logic? The potentially transformative part is not the code itself. It's the impact to the process of creating the code.


> Most often it is not necessary, and not wanted, to enforce a and b having the same type.

That really depends on what you're trying to do. Presenting these two different declarations as somehow equivalent is very misleading and I'm glad that the author didn't do that.


> Existing code is important, existing implementations are not.

I am having trouble parsing that sentence.... so now there's a distinction between the code and the implementation? wat!?


Ok, sorry. I misunderstood it then. So what does this mean?

"potentially including sub-components but not parent components"


> There's a clear distinction between ...

The distinction is meaningless to the user in the example your parent cites.


>Are completely different things (the latter is actually an error).

Why is the latter an error?


First sentence: “ An iterator is an object that points to an element inside a container”

This is not the primary purpose of an iterator. Does anyone want to hazard a guess as to what an iterator’s primary purpose is? You? You? Bueller?


> * I find it quite unusual in practice for genuinely new symbolic notation to be introduced by an author.

This sentence seems to contradict the rest of your comment; did you mean "I find it quite unusual in practice for genuinely new symbolic notation to NOT be introduced by an author."?


> They are nested in a physical sense, its simply not valid html.

For this to be true, you'd need containment to be a nontransitive relationship. In the sense in which h3 #2 is contained within h3 #1, all of the following hold:

- tr #1 contains h3 #1

- h3 #1 contains h3 #2

- tr #1 does not contain h3 #2


> How is this different

Was it implied that it is different?


> while being less complex

Idk, I found the svelte reactivity model a little confusing.


> TS is just a subset of JS.

Semantic typo: you meant superset of subset of JS.

(pedantically that predicate would apply to all other languages in the universe)


> Data is not code

All code is data, but not all data is code.


> If multiplication can be sometimes commutative and sometimes non-commutative (and it can, and it is) then why cannot addition be sometimes commutative and sometimes non-commutative?

To which I reiterate my response: because addition in plain English is frequently (if not always?) commutative, whereas multiplication in plain English is frequently NOT commutative (even though it sometimes can be).


>is in some sense a single value. In another sense, it is two values.

What I tryed to say is that the sense in which “exactly one element” is used in the definition of function is inclusive of codomain being R^n, so it confused me why you would provide a function that has a codomain of R^2 as something that suggests deviation from the formalism. It just seemed misleading to phrase it that way

I thought consistently would convey the idea I had, nevermind if it doesn’t

My bad about bijectivity, I see it now, you’re right


> if you ask me, differentiable rendering is the next big thing

Do you have a canonical reference for your usage of the adjective "differentiable" ? If people look at the definition they invariably get to this:

https://en.m.wikipedia.org/wiki/Differentiable_function

Which is clearly not what you mean. I'm not asking about what it means, but about a reference. I teach calculus for a living, and I make a big deal about the two meanings of this word, but never found a definitive reference to cite.


> It cannot be both.

I see this mentioned often, as if it's supposed to be obvious, but I don't really get it.

Care to explain?


> can also be viewed

Then I think it's safe to say that that's not the view being used in this discussion.

next

Legal | privacy