What is the deal with Yaxer?

Question

Remember Aptan Jaxer? It connects to Apache and allows you to use server-side JavaScript as an alternative to languages ​​such as PHP. It comes with a compatible API for accessing the file system, connecting to a database, socket communication, and everything you need.

I wonder why it was not adopted more widely, why more people do not use it? Javascript is a modern and clean programming language, not PHP, and the Jaxer API is much more consistent and neat. Don’t be offended, but the PHP API is just such a big mess with all its inconsistencies and inconsistent function assignment conventions.

Jaxer also makes communication between the client and server really convenient with its runat = "server-proxy", where you can directly refer to the server function on the client side of the script, and Jaxer takes care of all the XML requests for the HTTP request.

So I just really would like here what people think about it or why hardly anyone uses it. Not wanting to start a flamewar there, I'm just wondering.

thanks

Answer 1

Well, firstly, there is Node.JS. Most likely, much more people heard about this. And people really use node, especially when it comes to chats and things like that: Things there are a long survey.

My personal problem with node is that it is so asynchronous. This is a very, very, very big professional, on the one hand, because it allows you to do the most amazing features and makes some things a lot easier, but on the other hand, this is a big minus for those used for synchronous programming languages. I'm just having trouble viewing code that has 15 callbacks nested within each other ...

Answer 2

I remember how I looked at Jister when he went out. At that time I do not remember any sample applications. I wanted to understand what it was good at. Just because the language is “cleaner” may not be enough to get people to switch. What is its "unique benefit"? For example, Node.js is good at real-time applications, and they make it relatively clear in the sample code on their first page.

I think there was also more attention to Javascript since Jaxer was originally released. It seems like more developers who now also know Javascript. I would say that now this is more true than when Jaxer was released. In other words, perhaps it was ahead of its time.

Answer 3

Personally, I liked Jaxer because you could easily use the same code client and server side without duplication (for example, form validation), but I didn’t like that you had practically no control over the generated pages where JavaScript was supported even for the most trivial one pages and made pages heavily dependent on JavaScript, which made unobtrusive JavaScript virtually impossible.

So, I assume that for pure JavaScript-based web applications this is normal, but now there is, for example, the Google Web Toolkit, which is much more efficient, which also allows you to use one language and the server side.