Why not use the wipeout browser and JAVASCRIPT?
Why not use the wipeout browser and JAVASCRIPT?
it would be simple enough and we wouldnt have to worry about the security as much as we do now. True, javascript cant do everything, but for the httpd and ftpd programs, it could work. and it would bypass the 1.51 and 1.52 lockout.
-
- Posts: 16
- Joined: Wed Apr 06, 2005 8:10 am
If you want to go the java script route, why not wait for 2.0 update on the 27th which includes a built in browser? No need for wipeout.
Javascript is far from the ideal solution for game and homebrew development, especially on a 200-333mhz cpu. Emulators would be a no go, and homebrew games would be very limited.
Javascript is far from the ideal solution for game and homebrew development, especially on a 200-333mhz cpu. Emulators would be a no go, and homebrew games would be very limited.
-
- Posts: 16
- Joined: Wed Apr 06, 2005 8:10 am
Have you ever used Javascript? Really? On a modern PC its slow, imagine running inside of a browser thats running in a 200mhz (or less) system (I doubt the wipeout browser goes over 100mhz, and the new firmware one probably doesnt either)
Emulators would be a no go definitly, and games would be limited.
Assuming you can access local pages (off the mem stick) you can probably call API's and increase the CPU speed, if you cant, then you would need a wifi hotspot to even use the javascript abilities.'
Its not worth it.
Emulators would be a no go definitly, and games would be limited.
Assuming you can access local pages (off the mem stick) you can probably call API's and increase the CPU speed, if you cant, then you would need a wifi hotspot to even use the javascript abilities.'
Its not worth it.
Javascript is in no way designed to make games. It's designed for supposed extra boost when devloping websites. Many developers try to ignore it.
Just give it up. Trust me - most of the stuff you are seeing developed now would be impossible to recreate in javascript....
no one tell him about php connection capabilites either!
Just give it up. Trust me - most of the stuff you are seeing developed now would be impossible to recreate in javascript....
no one tell him about php connection capabilites either!
Why javascript isn't a viable solution:
- no support for filesystem access
no support for api calls
no support for direct memory access
no support for programming the buttons
no support for any kind of hardware access
plain and simple: javascript is a client side single session scripting language - and therefor can only access, manipulate etc data in the single instance that it gets called, and only items in the container and interpreter it is called in. most notably javascript is called via the web and therefor can only access the page (and child pages; or parent pages if it was spawned as a child) where it's code exists. additionally it can only use functionality that exists within it's interpreter - ever notice the differences in javascript implementations from IE, Mozilla, Netscape, Safari, Opera, etc etc...
yes, javascript can be used to make system level calls, if called in a real interpreter that ALLOWS it to do so - this will never be the case for web browsers..
yes, javascript can be used to make system level calls, if called in a real interpreter that ALLOWS it to do so - this will never be the case for web browsers..
...isn't it nice, sugar and spice...
...luring disco dollies to a life of vice...
...luring disco dollies to a life of vice...