4 ms·
S-expressions can be mechanically converted to HTML. HTML is more verbose and error prone: </closingtag> vs ) <form><table></form></table> oops. Can't
by erpellan 9y ago
S-expressions can be mechanically converted to HTML. HTML is more verbose and error prone:
</closingtag> vs )
<form><table></form></table> oops. Can't happen with an s-expression
- candiodari 9y agoExactly. The thing that I always remember is that identifiers encoded this way simply can't get out of sync from client to server. Commands, paths, enums, ... Where a form is posted, say, is an easy constant, that defines both the routing AND the string in the form. Where forms always have the fields defined in a structs, never more, or less. And this can result in sites that are very fast to add things to, as opposed to have dozens and dozens of files everywhere. But everyone wants "single page apps". Because client -> server ---[html]--> client --> server --[javascript]--> client --> server --[4*ajax requests necessary to fill in the initial page]--> client --> server --[4*images necessary to fill in said javascript]--> client Is so obviously "much faster" than: client -> server --[html+embedded everything]--> client