No, but it's very nice to be able to share code for things like view rendering or form validation between the server and client without jumping through hoops.
Silly node, emphasizing tech.
I hope it does. If doctors are replaced it's because medical care has improved beyond their capabilities. How could you not want better medical care?
It's not better. I'd say that the Jetbrains integrated debugging is superior.
Seattle has no income tax, and sales tax doesn't apply to most food from the grocery store, so taxes in Seattle really depend on how you choose to spend your money.
Except browser tooling, where they are far ahead of others.
Yes, but even if you follow all of the best practices and deliver a fast page, your site won't show up as "AMPed." In order to be "AMPed" it appears that you need to employ a whole slew of custom elements and syntax.…
This feels very regressive. I thought we got rid of "m." for a reason. Is there anyway to effectively "AMP" a page without maintaining a separate set of HTML/CSS/JS?
You do so in a derogatory manner, but you bring up a decent point. This doesn't really seem to be a JavaScript issue so much as an open source issue.
I don't think it's reasonable that the organizer not be held accountable. From this article: > By the time I’d received notice of the event unfolding on the evening of 2016-09-01, the decision was already made by the…
No, but it's very nice to be able to share code for things like view rendering or form validation between the server and client without jumping through hoops.
Silly node, emphasizing tech.
I hope it does. If doctors are replaced it's because medical care has improved beyond their capabilities. How could you not want better medical care?
It's not better. I'd say that the Jetbrains integrated debugging is superior.
Seattle has no income tax, and sales tax doesn't apply to most food from the grocery store, so taxes in Seattle really depend on how you choose to spend your money.
Except browser tooling, where they are far ahead of others.
Yes, but even if you follow all of the best practices and deliver a fast page, your site won't show up as "AMPed." In order to be "AMPed" it appears that you need to employ a whole slew of custom elements and syntax.…
This feels very regressive. I thought we got rid of "m." for a reason. Is there anyway to effectively "AMP" a page without maintaining a separate set of HTML/CSS/JS?
You do so in a derogatory manner, but you bring up a decent point. This doesn't really seem to be a JavaScript issue so much as an open source issue.
I don't think it's reasonable that the organizer not be held accountable. From this article: > By the time I’d received notice of the event unfolding on the evening of 2016-09-01, the decision was already made by the…