# A\\b vs LinearSolve.jl at JuliaCon 2022

**URL:** <https://discourse.julialang.org/t/a-b-vs-linearsolve-jl-at-juliacon-2022/85030>\
**Category:** General Usage\
**Created:** [July 30, 2022, 2:37pm UTC](https://discourse.julialang.org/t/a-b-vs-linearsolve-jl-at-juliacon-2022/85030 "2022-07-30T14:37:08Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![fredrikekre](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fredrikekre/32/1688_2.png) [@fredrikekre](https://discourse.julialang.org/u/fredrikekre)\
**Post date:** [July 30, 2022, 2:47pm UTC](https://discourse.julialang.org/t/a-b-vs-linearsolve-jl-at-juliacon-2022/85030/2 "2022-07-30T14:47:53Z")

</div>

`A \ b` has never been optimal. It has always been the case that there are better alternatives. In particular, you can often use knowledge about the specific matrix (structures, size, sparsity, …) to pick a better solver.

However, in some cases `A \ b` is good enough – not all programs spend the majority of time in the linear solver. `A \ b` is not being deprecated, and you can still use it.

---

_[View the full topic](https://discourse.julialang.org/t/a-b-vs-linearsolve-jl-at-juliacon-2022/85030)._