šŸ“š Node [[nope changing responsive to reactive doesn t explain why we d specify a server side microsoft]] exact match
Nodes contain individual contributions whose filenames match your search. x

Loading pushes...

šŸ““ Nope--Changing--responsive--to--reactive--doesn-t-explain-why-we-d-specify-a-server-side-Microsoft.md by @enki

Nope! Changing ā€˜responsive’ to ā€˜reactive’ doesn’t explain why we’d specify a

server-side Microsoft…


Nope! Changing ā€˜responsive’ to ā€˜reactive’ doesn’t explain why we’d specify a server-side Microsoft stack in the context of a client-side problem on a blog about CSS, nor does it explain why we would drop words & punctuation in this context. It still seems more likely to me that the author meant ā€œASAPā€ in its conventional sense. Since she appears to be active in this thread, perhaps she can clarify.

By John Ohno on August 30, 2016.

[Canonical link](https://medium.com/@enkiv2/nope-changing-responsive-to- reactive-doesn-t-explain-why-we-d-specify-a-server-side- microsoft-1fcfb64e7be6)

Exported from Medium on September 18, 2020.

Rendering context...