Exactly, it's a bad error message if you need to read 8 pages of tutorial to get that basic feedback.
Let's take a look at how the big boys handle something similar... SELECT * FROM logs WHERE KEY = 'blah' LIMIT 10; /* SQL Error (1064): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'KEY = 'blah' LIMIT 10' at line 1 */ I think there is some expectation of technical literacy for the use of a database. This would include being able…
I have to use Access at work. Im wondering if this could be a replacement. Certainly LO Base is not, much as I'd want it to be. I suppose it depends on whether the scripting language can do what vba can, especially with regards to xslx files.
Javascript and python supposedly are coming to excel.
I've been asked to develop python scripts for libreoffice and it was not fun.
Honestly I think LibreOffice Base (and its brethren) are underappreciated and underdeveloped pieces of software these days. In 80s/90s stuff like dBase and Access seemingly were relatively popular, but that whole category of software seems to have mostly died out which is imho a shame. I suppose Access being somewhat notoriously horrible has something to do with that, suffocating the whole field. Considering how much…
to give some perspective, there is an app i've written as a complicated google sheets script, which would have been way simpler to maintain as a desktop app, but what the end-users want is the ability to have multiple people use it from multiple devices at once. that's become table stakes for a lot of software now, and it's really what has killed desktop apps for stuff like this.
Very interesting point that multiuser killed desktop apps. Couldn’t desktop apps implement multiuser?
Who are you referring to? Is it even someone in this thread?
I was quoting you, using the > sign to refer to what you said directly. I thought the quote was useful to highlight that it can be easy to have a mental disconnect, or even an antagonism, between developers and their stakeholders.
Who exactly are the "customers" and "stakeholders" here?
That says more about you then it does about the site. :)
Yes, I believe it is intended to say that he is definitively not part of “ A generation conditioned by horrible endless-scroll single-page "applications" ”
Well, seems at least part of older generations are conditioned too. I never specified any hard age limits, did I?
I was quoting you, using the > sign to refer to what you said directly. I thought the quote was useful to highlight that it can be easy to have a mental disconnect, or even an antagonism, between developers and their stakeholders.
Who exactly are the "customers" and "stakeholders" here?
The people who use the software of the people who write the software. If the word "customers" is triggering, the argument holds just as well as for "users".
to give some perspective, there is an app i've written as a complicated google sheets script, which would have been way simpler to maintain as a desktop app, but what the end-users want is the ability to have multiple people use it from multiple devices at once. that's become table stakes for a lot of software now, and it's really what has killed desktop apps for stuff like this.
Very interesting point that multiuser killed desktop apps. Couldn’t desktop apps implement multiuser?
they could, but you would have to do pretty much everything from scratch - set up a server, figure out client-server communication, handle state changes, flaky networks, etc. with a webapp you get a lot of that infrastructure "for free" insofar as the entire stack is designed around the multiuser experience, and you are going with the grain of the platform. not to mention all the frameworks and libraries that help you with most of the common tasks you will face. you can follow a rails tutorial and get a small database with a multi-user read/write user interface working within a day or two.
Very interesting point that multiuser killed desktop apps. Couldn’t desktop apps implement multiuser?
they could, but you would have to do pretty much everything from scratch - set up a server, figure out client-server communication, handle state changes, flaky networks, etc. with a webapp you get a lot of that infrastructure "for free" insofar as the entire stack is designed around the multiuser experience, and you are going with the grain of the platform. not to mention all the frameworks and libraries that help yo…
Desktop apps can use HTTP(/grpc/rest/graphql) for communication just fine, that's not really problem.
Who exactly are the "customers" and "stakeholders" here?
The people who use the software of the people who write the software. If the word "customers" is triggering, the argument holds just as well as for "users".
Why are you dodging the question? Who are you talking about, and why?
It's not the commenters above that complained about the error message, they aren't users and highly unlikely to ever become users. Instead you've brought in some unspecified other for unspecified reasons.