Talking about some technology is difficult. You are passioned about some technology, just some technique, some idea how you want to structure your code, a lib or anything that you learned to know and think that could be usefull for your projects. You like that, what ever it is. You think that might be changing your work. Then of course you want tell someone about that. But they don’t get the point.

That might have different reasons.

lack of interest
lack of understanding
is currently passioned about something else

pretending to understand and talk about very general/low level stuff

pretending he had a similar solution by doing somehting different and telling you about his interesting stuff, that you don’t care

pretending to be interested, knowing they can never catch up in a reasonable time to understand

you find someone who understand it, you is giving you further good thoughts, but they are so busy doing other stuff.

find someone else, find someone who got the point and is willing to use that in a project with you

In this article you find a demonstration of the xml parser. type in some xml and see the resulting data as JSON. The xml is parsed on every keystroke and still you will see that the result is generated very fast.

You can also try to break your XML to see the error tollerance of this parser. select the simplefied mode, to see how the result will be affected.(it is the same result as in PHPs SimpleXMLParser). It you like it, install it from npm.


Recently I had a great idea for a node-module to develop. So, first the idea: In tmysqlpromisedao, I have the concept for loading data from related tables by using related DAOs. The new module should generalize that idea and make it awailable for other dao libraries that follow the tDao conventions.I created the github project, pushed an initial, empty project to npm and started to implement the “dao-registry”. In my suprise I was done in 3 lines of code. That was basicly a function returning a new empty object. That was a useless module, so as quick as I can, I deleted the project.

But still, I want to embrase the idea. In the next version of tmysqlpromisedao you will be able to provide a registry object as a parameter. That will allow you to seemlessly mashup datasources.

For example, your application might store users in mysql, but blogposts+comments in couchdb. As a prove of concept, I will soon implement a dao library for lowdb, that will be working together with mysql and the dao2koa API generator.

XML is loosing traction, it seems that every new API uses JSON or alike. But still there are big datasets only available in XML. As I already had a great XML-parser, that is extreamly fast, has a clean API and provides an AST/DOM, I had to fill the last important feature missing for that parser. Until now it was only possible to parse about 10-40 Megabyte strings.

I thought long and I started a few times implementing a parser that is still very fast and has all the features and on top of that is able to parse though large files. Such as a Wikipedia-dump or the openStreetMap-world file. But now about at the fived try, I found a solution to handle streams. I solved it by taking assomptions about the shape of large xml-files. Large XML files usually consist of a root element, containing a long list of items. The new parser is going to provide items one by one. It uses a nodejs-Streams. That makes it possible to use a stream reader for compressed files and use the plane-data stream for the xml-parser.

Each item provided from the xml is an ast on its own and can easily be simplefied by the framework. That makes working with xml-files not just much faster then ever before in JS it is also much more convenient. Developer have an API they are propable already familiar with.

If I would be you and have to work with XML data, I would definetly use tXml!!! If can realy choose, I would use JSON.

Currently I am an intensive user of visual studio code. It is an editor, developed by microsoft, that is extendable with many plugins. My favorit feature is the typescript integreation and its intelisence.

Recently it supports type recognition based on JSdoc comments. reason enough to look deeper into JSdoc. And I found it awefull to defined types. That is so much to type and by that error prone. Below you find a tool, that let you generate some JSdoc comment, from a JSON object. That is usefull for database or API responses.