4 ms·

What exactly is "native" about this? I remember there was PHP bindings for GTK [0], which at least looked sort of native on Linux. This could be cool if you c

What exactly is "native" about this? I remember there was PHP bindings for GTK [0], which at least looked sort of native on Linux. This could be cool if you can ship a large PHP backend codebase, allowing a web app to become an offline desktop app. You'd probably have to bundle a MySQL instance many cases though :) 0: https://en.m.wikipedia.org/wiki/PHP-GTK https://en.m.wikipedia.org/wiki/PHP-GTK

Gigachad 3y ago
Is GTK native? Isn't it just another library out of many you can utilize? Is it any more native than QT or wxwidgets?
- simlan 3y ago
  For Windows and Mac OS native is clearly defined by the OS libraries that arenpvoded by the company. For Linux to look very native you need to define the desktop environment. For stock Debian and Gnome desktop GTK bindings will look native. For OpenSuse with KDE QT will look more native.
- smashed 3y ago
  Imho, in the context of a GUI library, native would mean it has the native look and feel of the platform and the performance. This usually means the app is written in exactly the same language/framework/libraries as the built-in, pre-installed core apps. Nowadays, users don't seem to care all that much though, and will tolerate a lot of crap and bloated apps, as long as it gets the job done.
  - anonzzzies 3y ago
    Especially, shiny UI (which I hear many of my colleagues mix with UX) seems more important than anything for many; performance, latency/snappy-ness, memory use, cpu use, battery consumption etc. I can present a high performance, native, tiny binary product with excellent UX but shite UI and a slow, heavy, battery sucking product with horrible UX but great UI and most will pick the latter. Now it's much easier to make that bloated shiny product, as you don't have to think about UX, performance, latency, memory leaks etc; you just stomp something together quickly, wrap Electron and ship. People who carefully weigh all the options and spend time making something great, generally don't get paid for their efforts. So why would they?
TheNewsIsHere 3y ago
Hm. Maybe ODBC or just shopping a PHP client library could do it. It would be a little unusual, but something like PostgreSQL might be particularly well suited.
- oorza 3y ago
  If it's running locally, just use an abstraction around the database and swap in SQLite for local builds.
  - TheNewsIsHere 3y ago
    I was thinking if you were using this as a client for a server-based database. If not, SQLite could certainly be the right choice.
tommica 3y ago
> This could be cool if you can ship a large PHP backend codebase, allowing a web app to become an offline desktop app Isn't this exactly that, just sqlite instead of mysql, html for the frontend

Gigachad 3y ago

Is GTK native? Isn't it just another library out of many you can utilize? Is it any more native than QT or wxwidgets?

simlan 3y ago
For Windows and Mac OS native is clearly defined by the OS libraries that arenpvoded by the company. For Linux to look very native you need to define the desktop environment. For stock Debian and Gnome desktop GTK bindings will look native. For OpenSuse with KDE QT will look more native.
smashed 3y ago
Imho, in the context of a GUI library, native would mean it has the native look and feel of the platform and the performance. This usually means the app is written in exactly the same language/framework/libraries as the built-in, pre-installed core apps. Nowadays, users don't seem to care all that much though, and will tolerate a lot of crap and bloated apps, as long as it gets the job done.
- anonzzzies 3y ago
  Especially, shiny UI (which I hear many of my colleagues mix with UX) seems more important than anything for many; performance, latency/snappy-ness, memory use, cpu use, battery consumption etc. I can present a high performance, native, tiny binary product with excellent UX but shite UI and a slow, heavy, battery sucking product with horrible UX but great UI and most will pick the latter. Now it's much easier to make that bloated shiny product, as you don't have to think about UX, performance, latency, memory leaks etc; you just stomp something together quickly, wrap Electron and ship. People who carefully weigh all the options and spend time making something great, generally don't get paid for their efforts. So why would they?

TheNewsIsHere 3y ago

Hm. Maybe ODBC or just shopping a PHP client library could do it. It would be a little unusual, but something like PostgreSQL might be particularly well suited.

oorza 3y ago
If it's running locally, just use an abstraction around the database and swap in SQLite for local builds.
- TheNewsIsHere 3y ago
  I was thinking if you were using this as a client for a server-based database. If not, SQLite could certainly be the right choice.

tommica 3y ago

> This could be cool if you can ship a large PHP backend codebase, allowing a web app to become an offline desktop app Isn't this exactly that, just sqlite instead of mysql, html for the frontend