phpdesktop VS website

I am a bit surprised by the critical tone in the comments here. Phpdesktop [1] is, for example, a very nice application, and the ability of php to just make some simple scripts on the go and have something that works, is wonderful (compared to js where you often have to build etc, the threshold of getting started on a new computer is high). I have several times needed to make simple applications with a database, and php is perfect for that usecase. Making it simpler to share these applications to non-technical users for offline use is nice

[1] https://github.com/cztomczak/phpdesktop

I’ve been using PHP Desktop for a while for internal tools. https://github.com/cztomczak/phpdesktop

There's a project to make php apps -- https://github.com/cztomczak/phpdesktop -- but it doesn't have Mac support yet. Alas.

Since we're in the webdev subreddit, I suppose you will use a webstack. Here is what I have been using in an institution with a hellish ton of xp computers: PHPDesktop ChromeV47 . PHP is not mandatory, since it basically searches for and index.* file, which can be a html file with a lot of js. Use jquery with ajax calls to make your life easier for API requests and other stuff of old era JS (I dont remember if it supports fetch api and newish QOL changes). You basically develop a web app in a chrome wrapper. Works just fine on oldies.

re-write it as a desktop app, you could use php desktop to save time.

PHP Desktop seems to use 7.2.12, which reached end of life on late 2020. I wouldn't put my eggs in that basket.

Ever since I found PHP desktop (https://github.com/cztomczak/phpdesktop), I've been having a blast playing around with it. I've created my own "desktop applications" that I use daily. It's quick to build something I need to run locally (on Windows) vs learning/building an actual Windows application. Also I find PHP easier to build MVPs over Javascript (i.e. Electron). I'm curious if anybody else is building anything using PHP desktop? What kind of applications/services did you build or using with it?

Go to this repo https://github.com/cztomczak/phpdesktop by Czarek Tomczak, then search for downloads. As I’m working with Windows, I used PHP Desktop v57.0 for Windows release (https://github.com/cztomczak/phpdesktop/releases/tag/chrome-v57.0-rc). Download the zip file and extract the content wherever you want. Rename the folder as you prefer, you could use the name of your website. Let’s call it Myapp. This is a sort of container with a self-contained web server (Mongoose) and PHP 7.1.3. For example, launching the exe file called phpdesktop-chrome.exe will “read” what’s inside the Myapp/www folder. That’s where you will have to move your entire website to.

There's also phpdesktop which is akin to Electron and other such things.

Also note that that webpage can be somewhat out of date; for instance, see here for some recent edits to it (e.g. features Node had implemented that were marked as unavailable): https://github.com/WebAssembly/website/commits/main/

I would also say that IF blazor worked on a browser plugin like silverlight did, today that's not the case it is built on the webassembly standard which and it is being adopted in the browsers which means once it gets on the web, it is unlikely to ever go out again. Even if Microsoft themselves leave Blazor today, it can still work, the burden of creating a fork and keeping blazor alive will certainly be big but someone will be able to do that, just like the open silver folks revived silverlight via wasm tech without any particular Microsoft involvement.

Moreover, Tsavo and Rutvik also highlighted some ongoing and upcoming improvements in Dart, such as the isomorphic capability, compiling to WebAssembly, and how it has allowed us to communicate with JavaScript code effectively.

WebAssemblyOpen external link (abbreviated as “Wasm”) is a binary format that many languages can be compiled to. This allows you to write Workers using programming language beyond JavaScript, such as Rust, C, C++, Go and more.

In this post, we'll write a server-side Javascript function and then build it into a WebAssembly binary using the open source Spin tool. Our code will be less than a dozen lines long in total, so this is a concise introduction to WebAssembly and serverless functions that won't require you to spend a lot of time figuring out a code sample.

You might've noticed the increasing chatter around WebAssembly (WASM) in the dev community. Its potential is vast, and we've found it invaluable in enhancing our open source project!

WebAssembly.org: nice collection of resouces.

It's a meh deal.

They should've stuck with "this is crossplatform bytecode for the web", and it would've flourished there. Instead, now it's "designed as a portable compilation target for programming languages, enabling deployment on the web for client and server applications." [1]

Servers! Applications! Tigers! Lions! Oh my!

And it's not particularly good, or effective, or performant at any of those.

[1] https://webassembly.org

Today, the idea of optional code-on-demand execution in Web sites, in most cases, is violated. W3C introduced Web Components to extend HTML tags but made it entirely dependable on JavaScript. All modern Client-Side libraries, like React.JS, Angular, Vue.JS, are built with JavaScript. Sun Microsystems introduced Java Applets based on JVM. Adobe presented Macromedia Flash with a browser extension. Microsft made it possible to run reduced .NET applications in a browser with the Silverlight extension and recently introduced Blazor, which compiles C# code to WebAssembly and executes it on the client side.