2

Here's how my day's been going:
- decided to learn a quite popular JS framework
- installed with official installer
- used official tool to create an empty project
- ERROR! 20mins of debugging fixed it
- followed the getting started guide
- ANOTHER ERROR!
- "I must be doing something wrong"
- pulled the *official* demo project
- A COMPLETELY DIFFERENT ERROR!

- "Fuck it! I'm making this from scratch"

(the framework is Meteor, btw. fuck Meteor)

Comments
  • 1
    Should have gone with VueJS. Just saying...
  • 0
    @telephantasm the plan was Meteor + Vue. I need real-time sync. But since all the realtime frameworks seem to be utter unsupported garbage, I'll probably just roll my own (trying DerbyJS as a last resort).
  • 2
    @telephantasm meteor and vue are two completely different things....just saying
  • 0
    Any particular issue you were having bud? And for what os? Meteor is great, but fucky on windows
  • 1
    Yep. My fault for speaking without knowing what Meteor is. Sowy.
  • 0
    @AleCx04 Arch Linux (same with AUR package and official installer).

    - The *newest* demo is 10 months old and not compatible with the current version (that apparently contains critical security patches).

    - Following the guide installs some angular-babel package that isn't supported anymore, but is required by the latest angular package (that's AngularJS - the old one).

    - A fresh project spits out some long error about not finding something from Babel. It's a known bug and the workaround is to pin to some random beta version of Babel.

    - After doing that workaround, another error about something else Babel-related gets spit out, at which point I rm -rf the project and start writing the backend in Django

    Also, the whole "meteor-bundled npm and separate node_modules" thing just rubs me the wrong way.
  • 0
    Question : why do you need meteor? I mean isomorphic code is fun in theory and all that but impractical as fuck.

    Also vue should burn, stop advertising it.
  • 1
    @Commodore if nothing else, "isomorphic" code makes prototyping much faster. It's the only reason why I'd ever even think of running JS server-side.
    But the main reason I wanted to use Meteor was for real-time data synchronization and to avoid writing glue code ("full-stack"). But neither of these justify using this ungodly mess of a framework.
  • 0
    @franga2000 well it seems we're on the same page.

    As for quick prototyping, I find that some kind of in memory storage server side goes a long way. You still have to setup the web socket but that's rather fast.
Add Comment