Re: [gwt-contrib] Re: Goodbye IE 8–9 

[David Nouls]

We still need IE11 support in the banking sector. We still have a majority of 
customers that use IE11 due to technical reasons (plugins needed for accessing 
secure token don’t install properly in Chrome without internet access amongst 
others).

What do you mean with “next version of GWT” if that is 3.x then I don’t care at 
this point. We have been waiting for that release for a few years now. But 2.x 
releases should not drop IE11 support it is supposed to be a long-term 
supported version.
On 12 Mar 2021, 07:54 +0100, bernhar...@schubec.com 
, wrote:
> Hi all!
>
> I think IE11 support should be dropped soon if it blocks (or makes it 
> difficult) to implement new features in the next version of GWT.
> I understand, that there are enterprises who still use IE11 internally, but 
> developers who service such enterprises should use the current version of 
> GWT, which is not going away. Nobody is forced to upgrade to the next version 
> of GWT.
>
> Thanks,
> Berni
>
> > tony.be...@gmail.com schrieb am Donnerstag, 11. März 2021 um 22:26:21 UTC+1:
> > > IE 11 is still widely used inside corporations, because it is the only 
> > > browser that supports Java applets, and applications such as Oracle 
> > > e-Business Suite still use applets extensively (for Oracle forms). While 
> > > that segment does not move very fast, it does not mean other unrelated 
> > > groups within the same corporation are not updating GWT regularly. It is 
> > > hard to generalize In a multinational company  with tens of thousands of 
> > > employees.
> > >
> > > Regards
> > >
> > > Tony
> > >
> > > > On Thu, Mar 11, 2021 at 9:49 AM Jens  wrote:
> > > > > Dropping IE 8-10 shouldn't really hurt. Companies that require it are 
> > > > > probably not upgrading GWT in a fast pace anyways.
> > > > >
> > > > > However I wouldn't drop IE 11 anytime soon. IE 11 itself is tied to 
> > > > > the lifecycle of Microsoft's operating systems, which means for 
> > > > > Windows 10 it is supported until 2025 (for now). So just because MS 
> > > > > and Google drop support for IE 11 in some/all of their products, the 
> > > > > browser itself is still generally supported by MS. So we should think 
> > > > > twice before removing IE 11 from a library such as GWT, even if it 
> > > > > means to decline/revert certain commits if they break IE 11. From own 
> > > > > experience I have usually seen something around 8% of IE 11 usage in 
> > > > > GWT based apps.
> > > > >
> > > > > However I am pretty sure more and more companies will announce 
> > > > > dropping IE 11 this year or next year. With MS and Google starting, 
> > > > > this could easily have a domino effect. However GWT also also 
> > > > > strongly used internally inside companies so it might not have that 
> > > > > much of an effect in that area.
> > > > >
> > > > > If we ditch IE 8-10 and only leaving gecko1_8 and safari, can't we 
> > > > > kill them both as well and put them together? Are there so many 
> > > > > differences in code between both? From my work migrating GWT code to 
> > > > > elemental2/JsInterop I had the feeling that only some minor stuff is 
> > > > > different between both. So there shouldn't be that much overhead in 
> > > > > code size and performance doing (cached) runtime checks instead.
> > > > >
> > > > > -- J.
> > > > >
> > > > > --
> > > > > You received this message because you are subscribed to the Google 
> > > > > Groups "GWT Contributors" group.
> > > > > To unsubscribe from this group and stop receiving emails from it, 
> > > > > send an email to google-web-toolkit-co...@googlegroups.com.
> > > > > To view this discussion on the web visit 
> > > > > https://groups.google.com/d/msgid/google-web-toolkit-contributors/031f1171-cce9-4c17-b717-80bb5730f7fdn%40googlegroups.com.
> --
> You received this message because you are subscribed to the Google Groups 
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/99f9b82a-a56c-4c3e-b980-e3160581a486n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/5e524a19-81a2-44f6-8246-b25562b40861%40Spark.

Re: [gwt-contrib] Re: Goodbye IE 8–9 

[bernhar...@schubec.com]

Hi all!

I think IE11 support should be dropped soon if it blocks (or makes it 
difficult) to implement new features in the next version of GWT.
I understand, that there are enterprises who still use IE11 internally, but 
developers who service such enterprises should use the current version of 
GWT, which is not going away. Nobody is forced to upgrade to the next 
version of GWT.

Thanks,
Berni 

tony.be...@gmail.com schrieb am Donnerstag, 11. März 2021 um 22:26:21 UTC+1:

> IE 11 is still widely used inside corporations, because it is the only 
> browser that supports Java applets, and applications such as Oracle 
> e-Business Suite still use applets extensively (for Oracle forms). While 
> that segment does not move very fast, it does not mean other unrelated 
> groups within the same corporation are not updating GWT regularly. It is 
> hard to generalize In a multinational company  with tens of thousands of 
> employees.
>
> Regards
>
> Tony
>
> On Thu, Mar 11, 2021 at 9:49 AM Jens  wrote:
>
>> Dropping IE 8-10 shouldn't really hurt. Companies that require it are 
>> probably not upgrading GWT in a fast pace anyways.
>>
>> However I wouldn't drop IE 11 anytime soon. IE 11 itself is tied to the 
>> lifecycle of Microsoft's operating systems, which means for Windows 10 it 
>> is supported until 2025 (for now). So just because MS and Google drop 
>> support for IE 11 in some/all of their products, the browser itself is 
>> still generally supported by MS. So we should think twice before removing 
>> IE 11 from a library such as GWT, even if it means to decline/revert 
>> certain commits if they break IE 11. From own experience I have usually 
>> seen something around 8% of IE 11 usage in GWT based apps.
>>
>> However I am pretty sure more and more companies will announce dropping 
>> IE 11 this year or next year. With MS and Google starting, this could 
>> easily have a domino effect. However GWT also also strongly used internally 
>> inside companies so it might not have that much of an effect in that area.
>>
>> If we ditch IE 8-10 and only leaving gecko1_8 and safari, can't we kill 
>> them both as well and put them together? Are there so many differences in 
>> code between both? From my work migrating GWT code to elemental2/JsInterop 
>> I had the feeling that only some minor stuff is different between both. So 
>> there shouldn't be that much overhead in code size and performance doing 
>> (cached) runtime checks instead.
>>
>> -- J.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "GWT Contributors" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to google-web-toolkit-co...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/031f1171-cce9-4c17-b717-80bb5730f7fdn%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/99f9b82a-a56c-4c3e-b980-e3160581a486n%40googlegroups.com.

Re: [gwt-contrib] Re: Goodbye IE 8–9 

[Tony BenBrahim]

IE 11 is still widely used inside corporations, because it is the only
browser that supports Java applets, and applications such as Oracle
e-Business Suite still use applets extensively (for Oracle forms). While
that segment does not move very fast, it does not mean other unrelated
groups within the same corporation are not updating GWT regularly. It is
hard to generalize In a multinational company  with tens of thousands of
employees.

Regards

Tony

On Thu, Mar 11, 2021 at 9:49 AM Jens  wrote:

> Dropping IE 8-10 shouldn't really hurt. Companies that require it are
> probably not upgrading GWT in a fast pace anyways.
>
> However I wouldn't drop IE 11 anytime soon. IE 11 itself is tied to the
> lifecycle of Microsoft's operating systems, which means for Windows 10 it
> is supported until 2025 (for now). So just because MS and Google drop
> support for IE 11 in some/all of their products, the browser itself is
> still generally supported by MS. So we should think twice before removing
> IE 11 from a library such as GWT, even if it means to decline/revert
> certain commits if they break IE 11. From own experience I have usually
> seen something around 8% of IE 11 usage in GWT based apps.
>
> However I am pretty sure more and more companies will announce dropping IE
> 11 this year or next year. With MS and Google starting, this could easily
> have a domino effect. However GWT also also strongly used internally inside
> companies so it might not have that much of an effect in that area.
>
> If we ditch IE 8-10 and only leaving gecko1_8 and safari, can't we kill
> them both as well and put them together? Are there so many differences in
> code between both? From my work migrating GWT code to elemental2/JsInterop
> I had the feeling that only some minor stuff is different between both. So
> there shouldn't be that much overhead in code size and performance doing
> (cached) runtime checks instead.
>
> -- J.
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/031f1171-cce9-4c17-b717-80bb5730f7fdn%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CADS2qKu6F10%2B4_8TffndNimEXJV9irhVJP5CtDie1nPMNECgvQ%40mail.gmail.com.

Re: New Article "10 Best Java Frameworks to Use in 2021"

[Thomas Broyer]

On Thursday, March 11, 2021 at 3:39:37 PM UTC+1 Luis Fernando Planella 
Gonzalez wrote:

> We use JPA with EclipseLink. Gave us a lot better performance than 
> Hibernate when we compared both.
> The thing I like more with ORMs is that they are class-first. One creates 
> the entity, annotates it correctly and generate the schema.
>

Ah yes, that's also one of those things I dislike about JPA 
And retrofitting JPA on an existing schema is… not easy (or leads to 
non-idiomatic entities). Fortunately I've only had to do that twice I think.
Many performance issues I've seen had to do with databases when doing 
complex queries, so in addition to not fully controlling your SQL queries, 
you also don't fully control the schema; or maybe more accurately you have 
to learn how each JPA mapping strategy translates to SQL.
Unless I'm mistaken, this also leads to putting zero or very few "check 
constraints" in the database (i.e. besides not null, unique constraints and 
referential integrity). Lately I've used exclusion constraints in Postgres 
(https://www.postgresql.org/docs/current/ddl-constraints.html#DDL-CONSTRAINTS-EXCLUSION)
 
to handle complex uniqueness or non-overlapping date ranges, and other 
check constraints for some things others would likely implement as 
"business rules" in the application (things like "if that enum field's 
value is A then this other field must be null, and otherwise then it must 
be non-null and positive", or simpler things like "only one of those 2 
fields can be null at a time", and in some cases they must not both be 
null).
 

> For those liking a schema-first approach, I like a lot the Querydsl 
> project . It is not as active nowadays as it 
> used to be, but is very nice.
> And works both for plain SQL and JPA (I HATE with passion the JPA criteria 
> queries, Querydsl is so much more readable). 
>

Querydsl is quite similar to jOOQ (which can generate code from JPA 
entities 
too: https://www.jooq.org/doc/3.14/manual/code-generation/codegen-jpa/), 
although less "integrated" with 
JPA: 
https://www.jooq.org/doc/3.14/manual/sql-execution/alternative-execution-models/using-jooq-with-jpa/
jOOQ will always do native SQL though, whereas Querydsl will use JPQL (or 
similar).
 

> It gives us typed queries and is very extensible. You can even define your 
> own extensions as annotated static methods and it generates those as 
> methods in the metamodel, so things like these are possible:
>

This is interesting.
I've used extension methods in a Kotlin project, that alleviates the need 
for such a feature; but with Java indeed one would have to write isActive(p) 
without that.
I'm actually not sure what I prefer.

(fwiw, JPA Criteria with JPA Metamodel in JPA 2.0 also gives you typed 
queries; the API still is 濫)
 

>
> // Q* are the generated classes for the Querydsl metamodel
> QPerson p = QPerson.person;
> List admins = query
> .select(p)
> .from(p)
> .where(
> p.role.eq(Role.ADMIN),
> p.isActive()) // This would be a custom method via extension
> .orderBy(p.name.asc())
> .fetch();
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/77504c44-e66e-4df9-a1d7-b31bd1822b76n%40googlegroups.com.

[gwt-contrib] Re: Goodbye IE 8–9 

[Jens]

Dropping IE 8-10 shouldn't really hurt. Companies that require it are 
probably not upgrading GWT in a fast pace anyways.

However I wouldn't drop IE 11 anytime soon. IE 11 itself is tied to the 
lifecycle of Microsoft's operating systems, which means for Windows 10 it 
is supported until 2025 (for now). So just because MS and Google drop 
support for IE 11 in some/all of their products, the browser itself is 
still generally supported by MS. So we should think twice before removing 
IE 11 from a library such as GWT, even if it means to decline/revert 
certain commits if they break IE 11. From own experience I have usually 
seen something around 8% of IE 11 usage in GWT based apps.

However I am pretty sure more and more companies will announce dropping IE 
11 this year or next year. With MS and Google starting, this could easily 
have a domino effect. However GWT also also strongly used internally inside 
companies so it might not have that much of an effect in that area.

If we ditch IE 8-10 and only leaving gecko1_8 and safari, can't we kill 
them both as well and put them together? Are there so many differences in 
code between both? From my work migrating GWT code to elemental2/JsInterop 
I had the feeling that only some minor stuff is different between both. So 
there shouldn't be that much overhead in code size and performance doing 
(cached) runtime checks instead.

-- J.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/031f1171-cce9-4c17-b717-80bb5730f7fdn%40googlegroups.com.

Re: New Article "10 Best Java Frameworks to Use in 2021"

[Luis Fernando Planella Gonzalez]

We ended up using no plugins for GWT with Gradle. Even if there are some, 
none of them fit well.
Luckily, GWT compiler has a nice CLI, so...
Also, we make the gwt a subproject, as we don't use GWT RPC anyway. This 
helps keeping gwt-dev out of any runtime classpath!!!

Below is a trimmed version (not sure it even compiles, and it is the 
build.gradle for a subproject) of the build.gradle file for reference, for 
both compilation (even with a system flag to compile only the dev module) 
and for running the super dev mode:

ext {
buildWebapp = "${project(':web').buildDir}/generated/webapp"
gwtDev = Boolean.getBoolean('gwt.development')
}

configurations {
gwt
}
dependencies {
gwt(project(':api')) { transitive = false }
gwt files(project.sourceSets.main.java.srcDirs)
gwt files(project.sourceSets.main.resources.srcDirs)
gwt files(project(':api').sourceSets.main.java.srcDirs)
gwt "com.google.gwt:gwt-user:$gwtVersion"
gwt "com.google.code.gwtx:gwtx:$gwtxVersion"
gwt "com.github.branflake2267:gwt-maps-api:$googleMapsApiVersion"
gwt "com.google.elemental2:elemental2-webstorage:$elementalVersion"
gwt "com.google.elemental2:elemental2-dom:$elementalVersion"
gwt "com.google.elemental2:elemental2-promise:$elementalVersion"
gwt "com.fasterxml.jackson.core:jackson-annotations:$jacksonVersion"
gwt "com.google.gwt:gwt-dev:$gwtVersion"
}

task compileGwt(type: JavaExec) {
dependsOn compileJava
ext {
outDir = "$buildWebapp/gwt"
}
group = 'Build'
description = 'Compile the GWT source'
inputs.files configurations.gwt
inputs.property 'development', gwtDev
outputs.dir outDir
classpath = configurations.gwt
main = 'com.google.gwt.dev.Compiler'
args = []
args += ['-sourceLevel', "1.$javaVersion"]
args += ['-war', buildWebapp]
args += ['-logLevel', 'INFO']
args += ['-workDir', "$buildDir/tmp/gwt"]
args += ['-XfragmentCount', '6']
args += ['-failOnError']
if (gwtDev) {
args += ['-style', 'PRETTY']
args += ['-draftCompile']
args += ['-optimize', '0']
args += ['-XmethodNameDisplayMode', 'ABBREVIATED']
args += ['org.example.MyModuleDev']
} else {
args += ['-style', 'OBFUSCATED']
args += ['-optimize', '9']
args += ['-XnoclassMetadata']
args += ['org.example.MyModule']
}
}
task cleanGwtTemp {
doLast {
ant.delete(dir: "$buildWebapp/gwt")
ant.delete(dir: "$buildDir/tmp/gwt")
}
}
clean {
dependsOn cleanGwtTemp
}

task gwtSuperDev(type: JavaExec) {
dependsOn compileJava
description = 'Run the GWT code server for Super Dev Mode'
classpath = configurations.gwt
main = 'com.google.gwt.dev.codeserver.CodeServer'
args = []
args += ['-sourceLevel', "1.$javaVersion"]
args += ['-launcherDir', buildWebapp]
args += ['-logLevel', 'INFO']
args += ['-workDir', "$buildDir/tmp/gwt"]
args += ['-precompile']
args += ['-failOnError']
args += ['-bindAddress', '0.0.0.0']
args += ['org.example.MyModuleDev']

doFirst {
file("$buildDir/tmp/gwt").mkdirs()
}
}



Em quarta-feira, 10 de março de 2021 às 12:44:57 UTC-3, aka...@gmail.com 
escreveu:

> Even if it is opinionated, please give us Gradle GWT archetype. :-)
>
> On Wednesday, March 10, 2021 at 5:25:47 PM UTC+2 t.br...@gmail.com wrote:
>
>>
>>
>> On Wednesday, March 10, 2021 at 4:13:03 PM UTC+1 pavel@gmail.com 
>> wrote:
>>
>>> We had the same problem with maven but at the end, maven's multi-module 
>>> project and profiles helped to solve *hack around* it.
>>>
>>
>> There, fixed it for you 
>>
>> Also see https://www.cloudbees.com/blog/maven-profiles-and-maven-way and 
>> https://blog.soebes.de/blog/2013/11/09/why-is-it-bad-to-activate-slash-deactive-modules-by-profiles-in-maven/
>>  
>> among others, by prominent Maven PMC members.
>> (and yet, gwt-maven-archetypes use a "dev" profile 路, but it's know to 
>> be kind of hackish in places due to Maven and jetty-maven-plugin's 
>> limitations)
>>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/b369da9d-78fc-4d5f-9227-68a47b18dd61n%40googlegroups.com.