4 ms·
even if these were the only considerations for moving rendering to the client side (i don't believe this to be true, but it's irrelevant) the vast majority of o
by querulous 7y ago
even if these were the only considerations for moving rendering to the client side (i don't believe this to be true, but it's irrelevant) the vast majority of ongoing http development i see working at both small (< 50 people) and large companies has nothing to do with html
- brightball 7y agoIf it renders in the browser it does. There's nothing stopping you from also building an API. The design of an elixir application pushes you to assume that your code has a job to do and that job may be accessed via multiple different interfaces: - Websocket - API - HTML - Command Line - Another node in the cluster Any of these will be calling the same logic behind the scenes. There's nothing preventing you from breaking it into smaller pieces or still leaning on client side logic if it makes sense. The important thing is that you have the flexibility to attack the problem in an direction that suits it without language limitations dictating the client side approach as your only feasible option.