I know that LINQ is an alternative to XSLT for queries Umbraco data, but LINQ can be more simple to write and debug, but uncomfortable to deploy than XSLT because you are able to write it into Umbraco Admin. So, I made this question, not for opening a XSLT/LINQ war.
Linq Vs Xslt
Hi,
Have you any speed test LINQ4Umbraco vs XSLT?
I'd like to see some stats too. Although from what I'm told, XSLT is faster. Albeit, slower to debug O_o
doesn't that depend on who is debugging it ? :p
*ehem* stacktrace *ehem* ;)
Can people please stop trying to compare LINQ and XSLT, they aren't comparitable!
One is a compiled, statically typed language, the other is a dynamic scripting language.
One is designed for finding data based off strongly typed queries, the other is designed for finding data off dynamic queries.
If you have to do comparisons compare LINQ to NodeFactory or compare XSLT to the DLR.
Apples != fish
I'm new at Umbraco, but don't people compare them because you can often use both methods to achieve the same goal?
I was told in the Level 2 Certification course that linq2umbraco is an alternative for xslt.
So is the DLR, so is NodeFactory.
Don't get hung up on any one particular technology, when the only tool in your toolbox is a hammer everything looks like a screw.
I know that LINQ is an alternative to XSLT for queries Umbraco data, but LINQ can be more simple to write and debug, but uncomfortable to deploy than XSLT because you are able to write it into Umbraco Admin. So, I made this question, not for opening a XSLT/LINQ war.
is working on a reply...