Hacker News Reader

Comment by invalidname | Hacker News Reader

Site is down but it seems like server side rendering which is pretty terrible. There are better solutions for Java developers such as teavm one which Codename One built the web UI support. It supports both web assembly and plain JS. The latter has the advantage of smaller size.

Transpiles Java threads into async/await calls. Pretty cool stuff.

View on HN

What's so bad about server rendering

Well.. I come from the age of dumb terminals so trauma. We have powerful machines today. Using them like a dumb terminal rubs me the wrong way.

I've recently come to appreciate server rendering for its simplicity, at least for the tasks it is suited for. But I know what you mean. As a user, it's better to have local apps doing the real work.

Welcome to cloud computing.

Serverless is the new timeshare.

The new CGI actually.

Your code is running on their hardware. But I get your point...

So it isn't terrible?

  - higher latency
  - uses more server resources per-client,
    therefore it's more expensive
  - harder to do SPA-like apps

- waiting for javascript to load is not considered latency but kills user experience

- depends how you do it

- not all apps need to be SPA but also you can render fragments if you really want

> - higher latency

Which is a tradeoff, and it's okay as long as the client doesn't notice it.

> - uses more server resources per-client, therefore it's more expensive

Which is okay as long as the added expense is inconsequential (which it is).

> - harder to do SPA-like apps

Why?

JPro can also target WebAssembly.

Reply on news.ycombinator.com