With all the security holes, people actually prefer to use sh1tty libraries like PHP/smarty which absolutely leave your server to be rooted if permissions aren't set up perfectly.
As for Java/Spring/Beans, JSTL is way better because you can define directives and all the default JSTL directives are open.
If somebody is using XSLT, it's because it's a years old application and supporting those types of apps is no fun at all. It's usually sh1tty work a lead developer assigns people who he or she doesn't like from my exp. As a developer you want to do something new and challenging and that will affect a lot of people.
Man. Pretty soon the code to lock threads due to the passage of time can be commented out because they'll all be locked for naughtiness before they take their final breath.
When it gets to personal attacks my patience vanishes. Especially with those who have been banned before for them.
I haven't worked on XSLT for a while. Has anyone developed something like LinqPad for XSLT? Anyways, if it were browser based, which it isn't, I would using the knockout.js templating. It's kind of difficult to figure out the libraries to master, and master them, before something much better appears.
I guess you could host a knockout jobs engine in node.js
To be clear, this is a data transformation/processing job. No web, no JS, nothing of that ilk
To be clear, we don't know what you are doing. We don't know what technology, methodology, or architecture you are using. What we do know is that you are doing it wrong.
Sounds like... if you know XSLT AND you REALLY, REALLY, REALLY need a job, then you should apply
I haven't used XSLT for a while and never did a lot with it, but when I did, I found it kind of useful. What are the apparently better alternatives nowadays then?
Xslt can be handy taking one source and transforming it to another. I myself haven't used it in 7 years or so I think...back when XmlSpy was free.
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.