I had some time off last week so I built a little tool I've been planning on using for a while now.
Thought I'd just comment on my motivations for building this.
I bought a little chromebook tablet to take on holidays. I've been enjoying the experience of using a remote IDE to code on my personal server.
I thought it would be neat if I could quickly make myself GUIs for other utilities on my remote server that get rendered on my chromebook. Doing this like being able to run bash scripts remotely.
I start utility scripts with this tool and then just use ssh port forwarding to view it locally.
The fun bit is the application itself is then just written in python.
There are some similar alternatives[1] but I wanted to be able to write GUI elements like ImGUI so I decided to build my own tool in the end.
I just wrote it in python because that's what I've been using at work lately.
Seems like you could get away with using an object store and a serverless function for this. Not sure how pricing would compare to a server, but seems doable.
I also (mis)used .gitignore before I realised that there was an easy way to ignore stuff that I have locally without having to commit/ignore a .gitignore file.
> I can hear people asking: “Isn’t it a bit early to predict that, given that we’ve only seen two products?” It’s a very fair question. But it definitely seems like a first step — to me, the Mac Studio line is a clear successor to Apple’s iMac Pro.
I was under the impression that apple is planning on releasing one more M1 device and that could be the iMac Pro [1]. This article feels quite hollow to me.
Interesting! So does safari have different storage rules depending on where the web app is accessed from? Are there docs detailing what else might operate differently? I wonder how many web devs test their apps under the different constraints.
With PWAs the idea is that if the user explicitly "installs" them they get exceptions and better integration, yes. I don't have a reference at hand and don't know the details on iOS, but hopefully "PWA safari support" finds some clearer things.
It keeps running your render method and dynamically updates your client.
The first example documents this a bit better: https://gitlab.com/BenWiser/python-live-gui/-/blob/main/exam...