"If the vision for Qt5 is to create a paradigm shift and move QtQuick to
the core of all future Qt applications, then the only sane option is to
move JS into QtCore."
Non sequitur? I don't see how you or anyone else can create a paradigm shift on
how people write their apps. I DO NOT WANT anyone forcing their paradigm on me.
Just make it available, and let it shift the paradigm on its own. Things
succeed because of adoption not because they were forced on people. And where
the forcing does happen you get people complaining. No one forced people to by
the iPhone but people did because it was way better, never mind that WinCE,
BlackBerry, etc, already existed. The paradigm shift was organic. Why people
adopted the iPhone was because the implementation was superior. And I do think
QML will be a game changer, and its implementation is solid. That's why I'm
sure you'll get your paradigm shift, but I need to be able to leave it out
where not appropriate, because if forced in, that is where it works against
itself.
I am really really excited about the JS/QML additions. I do think it'll be a
paradigm shift in many more ways than are even being thought of (I can think of
a bunch of non-GUI use cases) But I can think of why I don't want it in my
Core. Why does it belong in things that Qt is already great for:
- Command line utilities
- Non DOM oriented network services
- Daemons
- Embedded devices
- iPhones (Can't have a interpreted code on an iPhone)
Thanks for listening.
________________________________
From: Bjørn Erik Nilsen <[email protected]>
To: Jason H <[email protected]>
Cc: "[email protected]" <[email protected]>
Sent: Thursday, September 8, 2011 9:56 AM
Subject: Re: [Qt5-feedback] QML/JS engine in QtCore?
On 9/8/11 3:33 PM, ext Jason H wrote:
> I wholly disagree. It is the core of *your* Qt5 apps, but probably won't
> be mine.
> It is also a poor decision to say "let them eat cake" and by cake I mean
> Qt4.
The root of the problem is that we are not aligned on the vision for Qt5.
If the vision for Qt5 is to create a paradigm shift and move QtQuick to the
core of all future Qt applications, then the only sane option is to move JS
into QtCore.
If we disagree on the vision, we better start figuring out what our vision
should be so that we can all work towards the same goal.
-- Bjørn Erik Nilsen
Software Engineer
Nokia, Qt Development Frameworks
_______________________________________________
Qt5-feedback mailing list
[email protected]
http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
