# Make devectorized operation default?

**URL:** <https://discourse.julialang.org/t/make-devectorized-operation-default/99263>\
**Category:** New to Julia\
**Tags:** question, syntax\
**Created:** [May 23, 2023, 6:51am UTC](https://discourse.julialang.org/t/make-devectorized-operation-default/99263 "2023-05-23T06:51:20Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![gustaphe](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gustaphe/32/18174_2.png) [@gustaphe](https://discourse.julialang.org/u/gustaphe)\
**Post date:** [May 23, 2023, 7:15am UTC](https://discourse.julialang.org/t/make-devectorized-operation-default/99263/2 "2023-05-23T07:15:25Z")

</div>

Two things:

1. This change won’t happen, even if it was a good idea, [PSA: Julia is not at that stage of development anymore](https://discourse.julialang.org/t/psa-julia-is-not-at-that-stage-of-development-anymore/44872)
2. Writing unvectorized code is orthogonal to automatic broadcasting. What Julia and the unvectorized paradigm says is “don’t treat vectors special”, which is a much more tenable and extensible way to program. Want to take the length of each vector in a vector of vectors? Just broadcast it. I would recommend trying this out for a while and then trying to go back to matlab, you’ll notice and be annoyed by how arbitrary their broadcasting rules are.

What about `print` and `println` is confusing?

---

_[View the full topic](https://discourse.julialang.org/t/make-devectorized-operation-default/99263)._