Live data from Hacker News

Meteor and Qt

achipa.blogspot.com

1–10 of 45 posts

Re: Meteor and Qt

#3
Hi, I'm Attila, the developer of Qondrite - the interface between Meteor and Qt in the article. If you have any questions, feel free to ask, I'm always looking for new perspectives, comments and will be happy to answer!

Re: Meteor and Qt

#5
post #2

There is a lot opinions on HNews that Meteor is too monolithic and it's bad: https://news.ycombinator.com/item?id=8772563 However, that kind of projects show the opposite. It is in fact very modular.

The fact that so many dismissed it without giving it a serious look made me interested in seeing what it was really about. Long/short - it's an amazingly focused, fun and easy stack to work with. I think the fact that it's easy, or at least seems easy and probably because it's another javascript framework makes it an easy target to dismiss on HN. If you are coming from a web background like myself (aspx, ruby, etc) then it's quite a revelation how fast, fun and easy it is to work with.

Re: Meteor and Qt

#7
post #2

There is a lot opinions on HNews that Meteor is too monolithic and it's bad: https://news.ycombinator.com/item?id=8772563 However, that kind of projects show the opposite. It is in fact very modular.

Agreed. I think a lot of that is based on Meteor (understandably) pushing their entire stack. I've always been intrigued by their docs which state:

  By default all apps include the meteor-platform 
  package.   This automatically pulls in the packages that 
  make up the core Meteor stack. If you want to build your 
  own custom stack, just remove meteor-platform from your 
  app and add back in whichever of the standard packages you 
  want to keep.[0]
Granted, I've always used the full stack but I'd be interested in seeing some examples of taking a more modular approach at a lower level than adding packages on top of the core stack.

[0] http://docs.meteor.com/#/full/usingpackages

Re: Meteor and Qt

#8

What's the difference between this and Xamarin?

This is a more full-stack approach - Qt and Xamarin are geared more towards creating standalone apps. What you get here is the reactive back-end (plus web-site for free). This setup can be used for both data and UI - you could for example publish a new UI (not just content), and all native apps would automatically be updated on the fly. If you take a look at the video - if you do this with Xamarin (or Qt) you would need to manually connect to a database or poll a RESTful service to see current data.
Post reply on HN