Yahoo’s Mojito is Now Open Source • Hacker News Board

Re: Yahoo’s Mojito is Now Open Source

#21

Post by thezilch » Mon, Apr 02, 2012, 9:12 PM UTC

ary wrote: post #8

debacle wrote: post #3

I was honestly expecting much much more. Yahoo has talent, and YUI was the best library out there when it was new.

YUI was released the same year as jQuery. Care to qualify that a bit? Edit: Had my dates wrong.

At the time and for at least a year following...

  1. Yahoo hosted scripts, including roll-ups
  2. UI components and styles
  3. The best documented library, both outside and inside thde code, hands down
  4. More feature complete (ex. one I can recall off the top of my head, form handling of upload inputs didn't exist in jquery, and extending jquery internals was/is a nightmare in comparison)
  5. The best documentation, hands down
  6. Yahoo hosted scripts, including roll-ups
  7. The best documentation

jquery has come a long way with documentation, but then YUI has evolved even further in becoming a modular library.

Re: Yahoo’s Mojito is Now Open Source

#22

Post by mey » Mon, Apr 02, 2012, 9:39 PM UTC

From a security perspective, this description scares me a little. There is a big difference from code executing in a trusted environment vs code executing in an untrusted environment. Not sure a clear approach on the "correct" way to manage this issue has come out from these cross platform products.

Edit: Note, this is a double edge sword (do I as a user trust the code dynamically loaded at run time?) but I was referring to it from the perspective of the operator (what methods executed must be correct and can't risk being modified in execution).

Re: Yahoo’s Mojito is Now Open Source

#23

Post by mrinterweb » Mon, Apr 02, 2012, 9:42 PM UTC

jzhou wrote: post #18

It's final people, with Mojito, NODE TRULY BECAME THE FUTURE WEB. Thanks, Yahoo!

I'm pretty sure it is safe to say that node will be the only technology the web will ever need from now until the end of time for all web dev tasks. Great job we did it.

Re: Yahoo’s Mojito is Now Open Source

#24

Post by sh1mmer » Mon, Apr 02, 2012, 9:49 PM UTC

blueprint wrote: post #9

sh1mmer wrote: post #6

Earlier quoted context omitted.

I wouldn't call those directly equivalent, although they are in the same space. One of things Mojito is supposed to do is allow progressive enhancement (for performance, etc) by allowing you to define how much rendering takes place on the client and how much on the server.

That's what I gleaned too; maybe "alternative" would have been a better choice than "counterpart". In one of my recent projects I used EJS and DNode to fairly easily implement a system for determining where the rendering takes place. I don't have anything to monitor connection quality & client capabilities though, so Mojito may prove useful when it matures.

DNode is about Node APIs on the client, where as YUI is about x-client code. As such I'm assuming moving YUI based rendering back is a lot more x-client compatible than using DNode to mimic Node's I/O interfaces.

I think my point is that sharing JavaScript isn't the biggest challenge in this space. Having a cross-browser rendering system that also runs effectively in Node is.

While you could use DNode to make that, I'm wondering if it would be nearly as robust as what they are trying to do.

Re: Yahoo’s Mojito is Now Open Source

#25

Post by KaoruAoiShiho » Mon, Apr 02, 2012, 10:54 PM UTC

blueprint wrote: post #4

Here are some of Mojito's existing Node.JS counterparts: * https://github.com/substack/dnode * https://github.com/tblobaum/nodeQuery * https://github.com/socketstream/socketstream

Those aren't really in the same league. It's more like this: https://github.com/codeparty/derby

Re: Yahoo’s Mojito is Now Open Source

#26

Post by underwater » Tue, Apr 03, 2012, 12:38 AM UTC

mey wrote: post #22

From a security perspective, this description scares me a little. There is a big difference from code executing in a trusted environment vs code executing in an untrusted environment. Not sure a clear approach on the "correct" way to manage this issue has come out from these cross platform products. Edit: Note, this is a double edge sword (do I as a user trust the code dynamically loaded at run time?) but I was refer…

I don't think it's so bad if you have a clean server side API that enforces your business rules. The application code can then be run anywhere.

I assume you'd write code for client side execution (i.e. don't fetch unneeded data, reduce round trips) and get the the server side excecution and a battle tested public API for free.

This seems similar to the approach Parse is promoting with their service.

Re: Yahoo’s Mojito is Now Open Source

#27

Post by shirkey » Tue, Apr 03, 2012, 2:21 AM UTC

Using the @ symbol as the hook for a function call would seem to be not only dangerous (corner cases of email or twitter address) but also superfluous -- if Mojito is acting as the web server, shouldn't every request be mapped to some sort of functional request, even in the case of serving static content? If it isn't acting as a web server, would the proxying server in front of it be routing the appropriate functional requests to Mojito?

Re: Yahoo’s Mojito is Now Open Source

#28

Post by wavephorm » Tue, Apr 03, 2012, 3:10 AM UTC

debacle wrote: post #3

I was honestly expecting much much more. Yahoo has talent, and YUI was the best library out there when it was new.

  Yahoo has talent, and YUI was the best library out there

No not really, and not it wasn't. Yahoo's UI library didn't really offer any radically new concepts. It was a recap of other libraries. For example instead of TinyMCE you could use YUI's editor which did almost the same thing, instead of jQuery you could use YUI's dom code, and so on.

I didn't really expect anything amazing from Yahoo. They'd need to come out with something truly extraordinary to make me pay attention. And given their webpage hasn't changed since 1998 I doubt that will ever happen.

Re: Yahoo’s Mojito is Now Open Source

#29

Post by gcb » Tue, Apr 03, 2012, 6:25 AM UTC

wavephorm wrote: post #28

debacle wrote: post #3

I was honestly expecting much much more. Yahoo has talent, and YUI was the best library out there when it was new.

Yahoo has talent, and YUI was the best library out there No not really, and not it wasn't. Yahoo's UI library didn't really offer any radically new concepts. It was a recap of other libraries. For example instead of TinyMCE you could use YUI's editor which did almost the same thing, instead of jQuery you could use YUI's dom code, and so on. I didn't really expect anything amazing from Yahoo. They'd need to come out w…

> For example instead of TinyMCE you could use YUI's editor which did almost the same thing

that's like saying glibc is worthless because you can run your ISO C programs the same. and you are ignoring all the POSIX work done to it.

YUI widgets, i agree, are a little meh.

but YUI did wonders to save us from java and OO programmers that didn't want to "get" javascript but wanted to publish code anyway. it was a library for OO in javascript like no other. now YUI3 is mixing all concepts and going nowhere in particular. sad.

Re: Yahoo’s Mojito is Now Open Source

#30

Post by raphinou » Tue, Apr 03, 2012, 6:36 AM UTC

oblique63 wrote: post #16

raphinou wrote: post #15

http://webtoolkit.eu is for me the future of web development: let the framework handle all the plumbing. Mojito claims to blur the client/server boundary. With Wt, you don't see it anymore. If you're a web developer, really worth a try!

Sounds similar to GWT: https://developers.google.com/web-toolkit/ aside from being in c++, any other differences or reasons why one might choose this over GWT?

It is not similar to GWT: GWT is client side only, with Wt you develop one code-base all in one language (C++ or a JVM language) that handles transparently server side and client side operations, including communication between both sides.