This...

"Since Ethereum is running contracts on the blockchain and Lisk is sort of running Dapp on the blockchain (sidechain?), you could see why having a weakly typed language could result in problems, specifically regarding consensus. It is much better to know the problem before it turns into an immutable thing on the chain, rather than discover all funds are trapped, or you fork the blockchain the first time someone tries to interact with it."

...could turn out as a (very) weak point with Ethereum. Because all ETH-contracts are running on the Blockchain while Lisk will use Sidechains. That's the most important point in my opinion and the reason why I don't invest in Ethereum but bought into the Lisk-ICO. It's the complexity of Ethereum that I consider as problematic and it's the base-simplicity of Lisk that could turn out as much more stable and scaleable.

Interesting read about Ethereum and possible coming problems:

https://bitcointalk.org/index.php?topic=1361602.0

ethereum has problems too im not claiming ethereum is the solution to decentralization just stating lisk has even bigger problems

do you not agree with this

"Javascript numbers are....not the greatest or most reliable. Especially when we are dealing with a crypto-currency, you really want your numbers to be on point. Basically JS uses floating point which means some things get approximated and digits get lost in certain cases. Here's some further reading: Be careful with big numbers & Floating point appoximation. So, the fact that everything in Lisk (including Lisk itself) is in Javascript, it means there are potentially big number problems (both in terms of big numbers and big problems)."

I agree it is a downside however I'm not sure it is a real concerns. There are many workarounds to this issue and most javascript developpers that need big numbers know how to deal with it.