Posts: 105
Threads: 30
Joined: Apr 2022
Reputation:
6
If only because I have a habit of checking for a newer version I came across 3.0, which became 3.1 I was on 0.8.2 Only today I got 3.1 almost a week after first release.
A nice feature/option to check once a week or month for a newer version and inform the user on startup. There isn't even a check for update in the IDE.
Posts: 1,581
Threads: 59
Joined: Jul 2022
Reputation:
52
Nope. I'm glad Galleon gave up quickly on the "update" feature before QB64 hit version 1. It could become a complicated mess that nobody would want to maintain. Who's going to maintain it?
Imagine while someone is using QB64 editor and his/her Internet is enabled, suddenly a pop-up cries there is an update. Who wants to deal with that, even if he/she expected to be informed of updates? An entire operating system is being dumped on because of it...
Also a "new" release doesn't necessarily mean it's better according to the user's program written. If the program for QB64 to compile was created during v0.98 then v3.1 or any other later release isn't going to make it better. Maybe except how compilation proceeds, how fast it goes down and the size of the EXE or Linux/MacOS executable. Trust me that I have done that last night.
Posts: 105
Threads: 30
Joined: Apr 2022
Reputation:
6
My point was to inform. There was a couple of interested new things. I don't care what people thought of shift left and shift right. I know I have used that function inside of processors from way back. Important for fast search of sorted arrays. And quick math shift left (once doubles), right (once halves it).
Now that it's there. I can rethink some search routines.
Posts: 730
Threads: 30
Joined: Apr 2022
Reputation:
43
I don't think there needs to be any sort of message for a new update. You can star the GitHub repo and know when stuff happens. That should be enough.
Tread on those who tread on you
