Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The viability of JavaScript frameworks on mobile

joreteg.com

Post reply on HN
Print view View original

11–20 of 85 posts

Re: The viability of JavaScript frameworks on mobile

#11

Post by aabajian »

I know GWT isn't the most popular framework (it isn't really a framework, is it?), but I've been a fan of it for a while. It solves three critical problems that have plagued web development:

1. Cross-browser compatibility.

2. Code performance.

3. Code organization (there are many JavaScript frameworks whose selling point have been making JavaScript more organized).

But in regards to this article, one often overlooked feature of GWT is that dead-code is automatically removed from the compiled JavaScript:

https://www.quora.com/How-fast-is-GWT-compared-to-JavaScript...

Thus you don't have to include the entire Angular/React/Ember/JQuery whatever library just to get a few features for your site.

Re: The viability of JavaScript frameworks on mobile

#12

Post by Drakim »

aabajian wrote: post #11

I know GWT isn't the most popular framework (it isn't really a framework, is it?), but I've been a fan of it for a while. It solves three critical problems that have plagued web development: 1. Cross-browser compatibility. 2. Code performance. 3. Code organization (there are many JavaScript frameworks whose selling point have been making JavaScript more organized). But in regards to this article, one often overlooked…

I'm not sure I understand, how can a framework "solve" code performance? Do you mean that it's faster than other frameworks?

Re: The viability of JavaScript frameworks on mobile

#13

Post by aabajian »

Drakim wrote: post #12
aabajian wrote: post #11

I know GWT isn't the most popular framework (it isn't really a framework, is it?), but I've been a fan of it for a while. It solves three critical problems that have plagued web development: 1. Cross-browser compatibility. 2. Code performance. 3. Code organization (there are many JavaScript frameworks whose selling point have been making JavaScript more organized). But in regards to this article, one often overlooked…

I'm not sure I understand, how can a framework "solve" code performance? Do you mean that it's faster than other frameworks?

The article mentions load performance. Meaning the time it takes to download and setup the Framework. GWT compiles Java to JavaScript and leaves out code that will never run. JavaScript frameworks load functionality in case that functionality is required, even if you don't use it.

Re: The viability of JavaScript frameworks on mobile

#15

Post by techterrier »

aabajian wrote: post #13
Drakim wrote: post #12

Earlier quoted context omitted.

I'm not sure I understand, how can a framework "solve" code performance? Do you mean that it's faster than other frameworks?

The article mentions load performance. Meaning the time it takes to download and setup the Framework. GWT compiles Java to JavaScript and leaves out code that will never run. JavaScript frameworks load functionality in case that functionality is required, even if you don't use it.

many javascript optimisers / minifiers do this

Re: The viability of JavaScript frameworks on mobile

#17

Post by aikah »

aabajian wrote: post #11

I know GWT isn't the most popular framework (it isn't really a framework, is it?), but I've been a fan of it for a while. It solves three critical problems that have plagued web development: 1. Cross-browser compatibility. 2. Code performance. 3. Code organization (there are many JavaScript frameworks whose selling point have been making JavaScript more organized). But in regards to this article, one often overlooked…

Sure but GWT == writing Java, downloading an heavy an complex SDK , and writing imperative UIs. Sure it comes with widgets but you can find the same widgets in JS.

Compare with React,AngularJS and co : way more popular,declarative UIs , if you need static typing you can use Typescript which needs no heavy runtime.

GWT might make sense for some LOB app for desktop but not for a mobile webpage.

Re: The viability of JavaScript frameworks on mobile

#18

Post by neovive »

vskarine wrote: post #4

Would be interesting to see Meteor stats there too

I've only tested Meteor briefly, but there is a pretty large initial download by default[1]. However, there are solutions using community libraries for pre-rendering and also hosting static assets to a CDN.

[1] https://forums.meteor.com/t/first-visit-loads-are-ridiculous...

Post reply on HN