Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×

Comment Runtime (Score 1) 201

The runtime is the most interesting part to me. They are effectively replacing the LSB with a "binary LSB" that you can distribute with your game.

By ensuring any application compiled against the Steam Runtime will work on SteamOS, they are providing a solid baseline for developers. From now on, developers will know they can relay on Steam Runtime.

Next thing may be we start to see other applications (not games) to use the Steam Runtime and provide it on non-SteamOS distributions.

Comment News at 11 (Score 1) 130

How is this news? In Europe obstetricians advise women to start taking folic acid (AKA vitamin B9) at least two months before trying to get pregnant. Isn't the same advice given in America?

Comment Re:Local webapp (Score 1) 209

Local webapps are easy to port only because they are simple apps. Start adding the kind of complexity and features you have in native app developed in C++, C# or Delphi and we'll talk about porting complexity.

Also, C++, C#, Delphi apps are expected to integrate PERFECTLY in the platform: colors, behavior, etc. Local webapps do nothing of that. No wonder there are no "porting complexities". Ugh.

Comment Local webapp (Score 5, Interesting) 209

First we tried to replace desktop apps with webapps and that's why we stood the awkwardness and immaturity of JavaScript, CSS and HTML. At least, we could justify it by saying "you'll be able to access the application from everywhere" (not true: new versions of browsers broke apps everytime)

Now, we are using those same immature and awkward technologies (JS, CSS, HTML) to develop local apps, which could be developed in C#, C++ or even Delphi in a fraction of time, integrate better with the platform and have more direct access to local APIs. I'm sorry but I don't understand this.

And yes, JavaScript, CSS, etc are way immature if you compare with what you can do in C# (WinForms, WPF), C++ (Qt, Boost) or even Delphi. The debugging process in itself is a nightmare.

Comment Ministro (Score 1) 86

Na, you are wrong. You can of course package a private copy of Qt for Android/iOS/etc with your application but you can also use the shared copy provided by Ministro:

https://play.google.com/store/apps/details?id=org.kde.necessitas.ministro&hl=es

Digia is already working on a "Ministro for iOS" to provide a shared Qt copy for all the apps.

Comment Re:QT makes for big apps (Score 1) 86

Fortunately, Hello World apps are rarely distributed. Adding Qt to your application, any real world application, is usually perfectly acceptable. You can even statically-compile the appliation to get a single executable.

I really wonder why people complain about 10 MB when we are using operating systems that take gigabytes of hard disk space and RAM.

Comment Re:One Framework to rule them all... (Score 2) 86

In 2013, cross-platform does not mean Win32 and Linux. And the developers of QT broadcast this archaic viewpoint with an exclamation point.

Qt supports these platforms: Linux, Windows, Mac, BSD, OS/2, BeOS/Haiku, Amiga, Android, iOS, Blackberry 10, Symbian, MeeGo/Mer, Tizen, Windows CE/Mobile/Embedded, Embedded Linux, VxWorks, QNX, bare metal (Boot to Qt). In the past, it also supported Solaris, AIX, HP-UX, webOS and there was an experimental port to Amazon Kindle.

The only way to write a more portable application than with Qt is to use HTML, which is unfit for many applications.

Slashdot Top Deals

He has not acquired a fortune; the fortune has acquired him. -- Bion

Working...