You might remember that `ngIf` can accept some relatively complex syntax as input, like providing an alternative template to render if the condition is false Do you know how this works under the hood? Do you know you can build directives for yourself with such a microsyntax?

Neither of those options is what HTML does natively. A lot of WC discourse has been harmed by the mindset that treats HTML as a shorthand to specify JS stuff declaratively. For relatively shallow data structures, e.g. an array of strings, HTML usually accepts data as a serialized microsyntax that is much simpler than arbitrary JSON. Example: <iframe sandbox>. For more complex data, HTML often accepts them as children, e.g. a <datalist> is essentially an array of objects. The rule of thumb is, a good HTML element should be usable without JS knowledge (at least for common cases).

Thanks for such an incredible talk! I also wanted to share this series I wrote about microsyntax since we talked about it. Maybe it’s of help to some of the people in your workshop: dev.to/this-is-angular/maste… Thanks again and safe travels home!

Likewise. Much prefer JS over microsyntax

#Angular Directive Grammar & Microsyntax: Demystifying the Hidden Parts #javascript #frontend #webdev #dormosheio #learning #programming #frontenddev dormoshe.io/trending-news/an…

CSS와 Web UI의 새로운 기능들: I/O 2023 에디션 news.hada.io/topic?id=9205 - Container queries - Style queries - :has() selector - nth-of microsyntax - text-wrap: balance - initial-letter - Dynamic viewport units - Wide-gamut color spaces - color-mix() ...

This makes a party of 3. I do appreciate Svelte's syntax simplicity for control flow (as compared to microsyntax) and components matching (as compared to selectors).

Issue #71 is out, read about TypeScript 5.0, Angular Testing Tips, Angular Structural Directives and Their Microsyntax and more Authors featured: @DecodedFrontend @bobbyg603 @drosenwasser @Armandotrue @eugeniyoz angularweekly.substack.com/p…

Angular’s microsyntax… 😬 What if you didn’t need it anymore 🤔

Personal notes usually contain enough ad hoc and contextual info (e.g. personal microsyntax and shorthand) that a vanilla LM embedding might not work super well. Semantic search is also neat but not always what you want (e.g. people names, dates)

Conditional rendering is much better with Vue template. It's just intuitive if-else. Every time I need to do if-else in Angular I think about the same thing. In general, IMO, most things involving microsyntax and ng-template makes me think "this could have looked better."

I would suggest to checkout this blogs: timdeschryver.dev/blog/use-a… nartc.me/blog/angular-direct… unicorn-utterances.com/posts… These guys (@tim_deschryver @Nartc1410 @crutchcorn ) has done a wonderful work explaining directives and angular template microsyntax in general.

yes there is apparently an INTERPOLATION MICROSYNTAX for the SUBSTITUTED VALUES SOMETHING HAS GONE VERY WRONG

imagemagick has some microsyntax on top of filenames, like you can prefix a format with a colon, and (based on having tried to work with the /c api/ directly) i don't know if it's even possible to convince it to read from a file named literally 'png:foo.png'

But it’s ✨microsyntax✨ (only documented in some random gist by someone no longer on the Angular team)

I’m finding that the opportunity to “weave an idiosyncratic microsyntax into the fabric of sociality” is among the hardest, but most exciting, challenges facing consumer platform builders.

Dan, you’re always so precise, so concise. You have that rare gift of saying it in such clarity and sobriety within the constraints of today’s microsyntax! You are a true legend.

Not that I'm aware of, but it seems feasible from a microsyntax perspective (IIRC @tabatkins made sure of that). I'm not 100% convinced it'd be more manageable than `<picture>`, but happy to be proven wrong. *Actually* supporting image-set seems higher priority though

Angular Microsyntax - The asterisk (*) prefix #Google #Angular #code #100DaysOfCode #BeyondJS

Since Vue 2, directives (`v-*`) expressions are expected to be parseable as JS¹. If you want arbitrary string, you need to quote it like a JS string. ¹ Except for built-in `v-for`, that uses a JS-like microsyntax.