2 ms·

Is Texas much different to Rails Turbolinks? Or is it like Turbolinks for Phoenix? PS I'm really happy that you called out "graceful degredation to an applicat

by hnzix 8y ago

Is Texas much different to Rails Turbolinks? Or is it like Turbolinks for Phoenix? PS I'm really happy that you called out "graceful degredation to an application that continues to function in the abscence of any JS.".

toolz 8y ago
very much different - turbolinks just uses AJAX to get a full rendering and replaces the body of the DOM with the response - texas can do realtime updates via pushing only patches (far less data over the wire) over a websocket
- ksec 8y ago
  Given WebSocket is now supported in most browsers, I have been wondering why such technique hasn't been more widely used? I wish HN allows me to search through all the post I have viewed or favourite, I am pretty sure I asked a similar question or saw something similar with Rails. Edit: Found it. ( Not Really similar though) https://fie.eranpeer.co https://fie.eranpeer.co
  - toolz 8y ago
    very cool, yeah I think there are a few novel concepts that texas brings to the table, but I'm super excited to see more projects are trying to leverage persistent connections to make SSR viable again. I believe SSR is not only viable, but optimal given the right techniques. Hopefully texas is pursuing all the most optimal abstractions to make this work, and I think it is, but I'm excited to see more people thinking about this. Time will tell I guess!