71–80 of 146 posts
Earlier quoted context omitted.
chromeos?
Built in Flutter, I believe.
General question: Is there an actual use for this kinds of projects, beyond showing what can be done? I have seen many different "web desktop" projects and while most of them were impressive in their own (technical) ways, I could never see the an actual use case for them.
Personally I can see myself using this to access my homelab from work without having to open extra ports. Since I can't install a personal VPN client on my work machine, a web-based desktop behind a login would give me most of what I want.
I took a peek at the "Explorer" app code base. PHP + JS + jQuery, but surprisingly readable (but a lot of practices in there that are not exactly considered "best" today). Perhaps we have sunk too deep into the SPA/API rabbit hole that we can no longer appreciate simplicity. https://gitlab.com/hsleisink/orb/-/blob/master/public/apps/e... https://gitlab.com/hsleisink/orb/-/blob/master/public/apps/e...
We are, indeed, in a world where Jquery is now the preferable choice. Frontend development is going through what video games went through in the 80s, so much new shovelware every day that people are eventually going to get tired of it.
Earlier quoted context omitted.
Maybe string interpolation is just a bad idea. Let strings be strings, use string formatting functions if you want to shove data in them.
Or maybe they're a very nice convenience, which is why a lot of modern languages are implementing them. String formatting functions use special strings themselves.
Earlier quoted context omitted.
Or maybe they're a very nice convenience, which is why a lot of modern languages are implementing them. String formatting functions use special strings themselves.
They do, but very well-defined ones, little placeholders that just concern themselves with formatting. You include the whole variable name and that makes it brittle, now random bits of string data have to be kept in sync with actual code, and makes it a lot more unwieldy to format in a way that isn't the default representation.
Earlier quoted context omitted.
My Synology NAS uses something like this for its navigation and even if it's initially strange, you instantly miss it when you access it from your phone, when the UI turns into this nested list which is not intuitive at all
I personally hate this from Synology. While their apps are meaningful structured and look good, it is just a natural mismatch to put sub windows into a parent window. Anyone remembering multi sub window apps in the Microsoft office suite in the 90s/00s. Was also horrible without a browser/html involved. This is definitely a taste thing
I took a peek at the "Explorer" app code base. PHP + JS + jQuery, but surprisingly readable (but a lot of practices in there that are not exactly considered "best" today). Perhaps we have sunk too deep into the SPA/API rabbit hole that we can no longer appreciate simplicity. https://gitlab.com/hsleisink/orb/-/blob/master/public/apps/e... https://gitlab.com/hsleisink/orb/-/blob/master/public/apps/e...
For large organisations it's easier to manage a team of workers with narrow specialisations than a single, but almost equally productive developer like here.
It's particularly visible in banking applications, where modules are almost completely independent and built by non-overlapping teams, so they take forever to load due to the limitation on concurrent requests in browsers.
I took a peek at the "Explorer" app code base. PHP + JS + jQuery, but surprisingly readable (but a lot of practices in there that are not exactly considered "best" today). Perhaps we have sunk too deep into the SPA/API rabbit hole that we can no longer appreciate simplicity. https://gitlab.com/hsleisink/orb/-/blob/master/public/apps/e... https://gitlab.com/hsleisink/orb/-/blob/master/public/apps/e...
SPAs are here due to organisational, not technical reasons. For large organisations it's easier to manage a team of workers with narrow specialisations than a single, but almost equally productive developer like here. It's particularly visible in banking applications, where modules are almost completely independent and built by non-overlapping teams, so they take forever to load due to the limitation on concurrent re…
Most of them are classic multi-page PHP apps. It's terrible. I can't stand how it always reloads each time I click on something. I remember it didn't bother me much in the past when everything was like that, but today we have much better options.
I went for a SaaS built as a SPA. When I click on something, for example to create a new entity, I get a modal/side-panel immediately. When I want details, I get them much quicker and can return back to the listing immediately.
> It's particularly visible in banking applications, where modules are almost completely independent and built by non-overlapping teams, so they take forever to load due to the limitation on concurrent requests in browsers.
They just can't code SPAs well. It's perfectly possible to have both quick loading times and very separate modules.
Earlier quoted context omitted.
SPAs are here due to organisational, not technical reasons. For large organisations it's easier to manage a team of workers with narrow specialisations than a single, but almost equally productive developer like here. It's particularly visible in banking applications, where modules are almost completely independent and built by non-overlapping teams, so they take forever to load due to the limitation on concurrent re…
I've been evaluating some self-hosted/open source company management systems this weekend. Most of them are classic multi-page PHP apps. It's terrible. I can't stand how it always reloads each time I click on something. I remember it didn't bother me much in the past when everything was like that, but today we have much better options. I went for a SaaS built as a SPA. When I click on something, for example to create…
They're visibly snappier than server-rendered frontends, or even frontends with JS sprinkled on top when done correctly, but large organisations generally don't do them correctly.