# Julia with respect to reliability, sustainability, critical application, dynamic/static typing, big data, HPC?

**URL:** <https://discourse.julialang.org/t/julia-with-respect-to-reliability-sustainability-critical-application-dynamic-static-typing-big-data-hpc/23135>\
**Category:** Performance\
**Created:** [April 14, 2019, 11:44am UTC](https://discourse.julialang.org/t/julia-with-respect-to-reliability-sustainability-critical-application-dynamic-static-typing-big-data-hpc/23135 "2019-04-14T11:44:03Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![chakravala](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chakravala/32/6832_2.png) [@chakravala](https://discourse.julialang.org/u/chakravala)\
**Post date:** [April 16, 2019, 8:20am UTC](https://discourse.julialang.org/t/julia-with-respect-to-reliability-sustainability-critical-application-dynamic-static-typing-big-data-hpc/23135/17 "2019-04-16T08:20:49Z")

</div>

> [@Tamas\_Papp](#):
>
> Imagine a spectrum where you trade off convenience and flexibility for catching errors at compile time.

Who said anything about making a trade-off? I wasn’t proposing to take anything away.

Also, I was talking about “agda” with an extra `g`, which is not the same as ada. It uses proof by reflection, which Julia might be able to do if it had some extra inductive type features.

The new features don’t have to exactly resemble a previous language, just learn from it.

Are [inductive types](https://en.m.wikipedia.org/wiki/Inductive_type) threatening to other aspects of the Julia language that would cause trade-off?

---

_[View the full topic](https://discourse.julialang.org/t/julia-with-respect-to-reliability-sustainability-critical-application-dynamic-static-typing-big-data-hpc/23135)._