Active Topics

 


Reply
Thread Tools
Fargus's Avatar
Posts: 1,217 | Thanked: 446 times | Joined on Oct 2009 @ Bedfordshire, UK
#51
Originally Posted by jwi View Post
It's very hard to understand, why someone would hate the idea getting wrt to maemo. Its cool technology for hacking for example nice looking easy use front ends for web servives etc. Its cool that we have many choices. We all dont want to write assembler to get some simple things done... Its not good for every use, but when its used correctly, its nice technology.
I personally wasn't against the tech being available - what am I against is having this tech forced on me. I have just put the brakes on 4 enterprise application projects we had planned for Maemo ports until this situation is clarified. We work with customers that require byte code to be disabled entirely due to security issues. If the platform can't allow this without being hacked then our business case has just gone up in smoke.
 
Fargus's Avatar
Posts: 1,217 | Thanked: 446 times | Joined on Oct 2009 @ Bedfordshire, UK
#52
Originally Posted by qgil View Post
The main benefit of the Web Runtime is fast development with a programming language widely known. This has the potential of producing plenty more apps with a lower cost.
Funnily enough I thought C and C++ were widely known too. Fast development comes via decent sets of libraries and some wizards in certain IDE's too.
 
Fargus's Avatar
Posts: 1,217 | Thanked: 446 times | Joined on Oct 2009 @ Bedfordshire, UK
#53
Originally Posted by voracity View Post
...
Your Venn diagram also suggests that anything WRT developers can do, native developers can do too, which I doubt very much.
...
Well if the WRT is developed on top of native API then it would be reasonable to assume that it is indeed possible or the WRT developers couldn't have done it in the first place!

Last edited by Fargus; 2009-12-29 at 15:45. Reason: Cut irrelevant part of refernce
 

The Following User Says Thank You to Fargus For This Useful Post:
qgil's Avatar
Posts: 3,105 | Thanked: 11,088 times | Joined on Jul 2007 @ Mountain View (CA, USA)
#54
WRT vs security, what are your concerns?

In Maemo 5 WRT is completely optional.

No matter what is the integration of WRT in Maemo 6, there is going to be a security framework defining policies and what not. http://wiki.maemo.org/Maemo_security

It would be useful to know more about your security concerns to check whether they are being addressed.
 
jcompagner's Avatar
Posts: 290 | Thanked: 165 times | Joined on Sep 2009
#55
Originally Posted by Fargus View Post
I personally wasn't against the tech being available - what am I against is having this tech forced on me. I have just put the brakes on 4 enterprise application projects we had planned for Maemo ports until this situation is clarified. We work with customers that require byte code to be disabled entirely due to security issues. If the platform can't allow this without being hacked then our business case has just gone up in smoke.
byte code disabled due to security issues? what?

If you compare for example byte code language number 1 java against C(++) coded applications. which in all these years had the worst security issues like buffer overflows and son on? It wasnt the sandboxed jvm...
 
Posts: 25 | Thanked: 22 times | Joined on Dec 2009
#56
Originally Posted by Fargus View Post
Well if the WRT is developed on top of native API then it would be reasonable to assume that it is indeed possible or the WRT developers couldn't have done it in the first place!
I should have been more clear. Technically, that is of course true. However, in practice the two groups differ in their skill sets (i.e. in terms of artistic skills, technical skills, experience with developing UIs, abstract problem modelling, user modelling, etc.)

Originally Posted by Fargus
We work with customers that require byte code to be disabled entirely due to security issues.
I am, like others, puzzled by this comment.
 
qgil's Avatar
Posts: 3,105 | Thanked: 11,088 times | Joined on Jul 2007 @ Mountain View (CA, USA)
#57
bump

Originally Posted by qgil View Post
WRT vs security, what are your concerns?

In Maemo 5 WRT is completely optional.

No matter what is the integration of WRT in Maemo 6, there is going to be a security framework defining policies and what not. http://wiki.maemo.org/Maemo_security

It would be useful to know more about your security concerns to check whether they are being addressed.
New year... new reasoning for your security concerns?

More thoughts & questions about the upcoming Web Runtime?
 
Posts: 7 | Thanked: 0 times | Joined on Nov 2009
#58
Originally Posted by qgil View Post
More thoughts & questions about the upcoming Web Runtime?
What about thoughts on the Web Runtime versus Qt's QML? As I said in my previous post, I as under the impression QML would be the "standard" platform for creating Nokia mobile apps but it looks like the Web Runtime is a completely separate and potentially competing technology. Very confusing!

Paul.
 
Fargus's Avatar
Posts: 1,217 | Thanked: 446 times | Joined on Oct 2009 @ Bedfordshire, UK
#59
Originally Posted by qgil View Post
bump



New year... new reasoning for your security concerns?

More thoughts & questions about the upcoming Web Runtime?
Apologies for delay in replying, I wasn't monitoring the thread.

Security concerns arise around the lack of transparency to machine level instructions with Byte code machine, Java being actually completely banned from certain sites. The overhead of having to run through potential security issues with combinations of end code and byte machine would simplify mean nothing would ever be accomplished. I didn't say the situation was useful just how sensitive they are to security issues.
 
Fargus's Avatar
Posts: 1,217 | Thanked: 446 times | Joined on Oct 2009 @ Bedfordshire, UK
#60
Originally Posted by voracity View Post
I should have been more clear. Technically, that is of course true. However, in practice the two groups differ in their skill sets (i.e. in terms of artistic skills, technical skills, experience with developing UIs, abstract problem modelling, user modelling, etc.)
If you were to change that wording to sometimetimes differ I would agree however that is definately not the case with the Software Engineers that I work with.

The arguement above could actually be used to assert that scripting pool ought not to be allowed to develop as they are artistic not technical: sure it's not what you meant but thought worth mentioning before someone with a rant did.
 

The Following User Says Thank You to Fargus For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 14:29.