The future of the web is HTML over the wire
This week we’re joined by long-time web developer Matt Patterson. Earlier this year Matt wrote an evocative article for A List Apart called The Future of Web Software Is HTML-over-WebSockets. In this episode Matt sits down with Jerod to discuss, in-detail, why he believes the future of the web is server-rendered (again) and how Ruby on Rails is well positioned to bring that future to us today.
Discussion
Sign in or Join to comment or subscribe
2021-04-06T05:41:21Z ago
[removed] is the final jingle loud.
it managed to cancel out enjoyment of the entire show within 2 seconds and then some
Jerod Santo
Bennington, Nebraska
Jerod co-hosts The Changelog, crashes JS Party & takes out the trash (his old code) once in awhile.
2021-04-06T20:10:19Z ago
When you say “final jingle” are you referring to the outro music that begins around the 57 minute mark or the very final “CHANGELOG” sound at 58:39?
(I removed part of your comment as it violates our code of conduct)
2021-04-06T20:19:07Z ago
yes, the final 2 seconds with the “ear-reap”, to put it in CoC-friendly terms.
not the first time i heard it, but it was so frustrating this time, that i had to start with a cussing
Jerod Santo
Bennington, Nebraska
Jerod co-hosts The Changelog, crashes JS Party & takes out the trash (his old code) once in awhile.
2021-04-06T20:26:05Z ago
Gotcha, we’ll see about tweaking that decibels on that 👌
2021-04-06T21:53:12Z ago
and it’s not just the volume, also unexpected sudently after the regular closing credits gone quiet. which i assume was inteded to be some kind of easter egg, but it evolved into a tripwire when no one was watching.. why no one complained before? probably b/c pod-apps like overcast have
trim(seconds_start, seconds_end)<sidestep>
but i recently decided to try out “vanila” podcasting experience, just to see all the pain-points one would come across within an “intended” environment.
and, thx to iOS memory management, discovered that not saving the position of podcast on page reload, in a Cookie/localStorage/url.replace() with current timestamp every ~15s – is the biggest pitfall every regular web-player has.
<sidestep/>
Pablo BarrĂa Urenda
2021-04-11T16:25:05Z ago
As opposed to what, exactly? Building two apps inside the same code base, hopelessly coupling UI and business logic making every change have unintended consequences?
I have always failed to understand this argument. It seems to me that no matter how tightly package your application code, you will always be writing two applications, and the extra efforts involved in keeping them in sync are misguided in the first place: they are different tools running on different machines for different purposes.
This to me always sounds like an argument against modularity.