# FMS 18.02 WebDirect / CWP

**URL:** <https://the.fmsoup.org/t/fms-18-02-webdirect-cwp/238>\
**Category:** Heads-Up!\
**Created:** [July 23, 2019, 7:44pm UTC](https://the.fmsoup.org/t/fms-18-02-webdirect-cwp/238 "2019-07-23T19:44:07Z")\
**Posts on this page:** 7\
**Page:** 4

<div class="post-metadata">

**Author:** ![DBtailor](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/dbtailor/32/203_2.png) [@DBtailor](https://the.fmsoup.org/u/DBtailor)\
**Post date:** [July 30, 2019, 8:16pm UTC](https://the.fmsoup.org/t/fms-18-02-webdirect-cwp/238/61 "2019-07-30T20:16:43Z")

</div>

Any chance FileMaker moves away from Java altogether in future releases?

---

<div class="post-metadata">

**Author:** ![jormond](https://avatars.discourse-cdn.com/v4/letter/j/35a633/32.png) [@jormond](https://the.fmsoup.org/u/jormond)\
**Post date:** [July 30, 2019, 10:01pm UTC](https://the.fmsoup.org/t/fms-18-02-webdirect-cwp/238/62 "2019-07-30T22:01:17Z")

</div>

They have reduced some dependency on Java, by including Node.js in FileMaker Server. How far they go with that, who knows? I’m sure they have a master plan, but it’s likely part of the 5-year plan they just started.

---

<div class="post-metadata">

**Author:** ![Torsten](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/torsten/32/1574_2.png) [@Torsten](https://the.fmsoup.org/u/Torsten)\
**Post date:** [July 31, 2019, 5:41am UTC](https://the.fmsoup.org/t/fms-18-02-webdirect-cwp/238/63 "2019-07-31T05:41:04Z")

</div>

This may be outlined in the next roadmap.

---

<div class="post-metadata">

**Author:** ![anon45965781](https://avatars.discourse-cdn.com/v4/letter/a/13edae/32.png) [@anon45965781](https://the.fmsoup.org/u/anon45965781)\
**Post date:** [July 31, 2019, 10:06am UTC](https://the.fmsoup.org/t/fms-18-02-webdirect-cwp/238/64 "2019-07-31T10:06:35Z")

</div>

It’s not FMI’s “dependency on Java” that’s the problem… LOL.

---

<div class="post-metadata">

**Author:** ![jormond](https://avatars.discourse-cdn.com/v4/letter/j/35a633/32.png) [@jormond](https://the.fmsoup.org/u/jormond)\
**Post date:** [July 31, 2019, 9:02pm UTC](https://the.fmsoup.org/t/fms-18-02-webdirect-cwp/238/65 "2019-07-31T21:02:43Z")

</div>

I don’t agree, completely. Though partially. I’ll explain.

It may not be Java that is the problem, but if the engineers can’t make it more solid, then it is the wrong tool. This doesn’t even point to a problem with the engineers, per se. It could be the business processes that are the bottleneck. And that may not be the fault of the company. It is mainly about the resources they have to work with. If JavaScript is more in the wheelhouse of the engineers, then moving toward Node.js is a better option, regardless of Java’s capabilities.

Broader scope. The evaluation is beyond whether Java is flawed or the perfect technical choice. It is about what can be done with it, given the resources of the company.

---

<div class="post-metadata">

**Author:** ![AndyHibbs](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/andyhibbs/32/3089_2.png) [@AndyHibbs](https://the.fmsoup.org/u/AndyHibbs)\
**Post date:** [July 31, 2019, 9:43pm UTC](https://the.fmsoup.org/t/fms-18-02-webdirect-cwp/238/66 "2019-07-31T21:43:55Z")

</div>

Maybe a classic tale of a good product spoilt by licensing. But let’s not even go there!

---

<div class="post-metadata">

**Author:** ![anon45965781](https://avatars.discourse-cdn.com/v4/letter/a/13edae/32.png) [@anon45965781](https://the.fmsoup.org/u/anon45965781)\
**Post date:** [August 1, 2019, 9:33am UTC](https://the.fmsoup.org/t/fms-18-02-webdirect-cwp/238/67 "2019-08-01T09:33:04Z")

</div>

Yep, the so-called “elephant in the room”. 🙂

[Previous page](https://the.fmsoup.org/t/fms-18-02-webdirect-cwp/238.md?page=3)