Live data from Hacker News

BeeBase, a programmable relational database with graphical user interface

beebase.sourceforge.io

41–50 of 110 posts

Re: BeeBase, a programmable relational database with graphical user interface

#41
post #35

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…

I haven't seen anything that beats the UI and UX of FileMaker Pro from the 90s.

Re: BeeBase, a programmable relational database with graphical user interface

#42
post #30
post #5

Earlier quoted context omitted.

I don't understand —screenshots and a feature list are among the first few links at the top.

guess I missed it, im used to scrolling and seeing screenshots and features on splash page. I must admit I wasn't very interested in this piece of software to begin with.

> guess I missed it, im used to scrolling and seeing screenshots and features on splash page.

Sigh... A generation conditioned by horrible endless-scroll single-page "applications" (web sites).

Re: BeeBase, a programmable relational database with graphical user interface

#43
post #36
post #29

Earlier quoted context omitted.

not sure if you are trolling or serious here but thats a bad user experience and also very condescending

It's not about a user, it's about someone declining to become a user because the manual is distributed as a separate PDF. I see two solutions for this problem, either use another software or hire someone to adapt this one to you. As a user you know the basic constraints on table names, if you don't you can't use the software.

> As a user you know the basic constraints on table names, if you don't you can't use the software.

1) As a user you shouldn't be required to know weird constraints on table names.

2) As a piece of software objecting to some specific issue with a table name, YTF not mention what that issue is in the error message you throw up?

Re: BeeBase, a programmable relational database with graphical user interface

#44
post #2

Good morning, I wanted to introduce this little, unpretentious piece of software, which is intended as a small programmable database for hobbyists, like a mini Access but with a scripting language for those who like parentheses. Your opinions are welcome. Regards,

Is there any technical docs on internals? How it does I/O, caching, consistency, concurrency etc.?

that's probably not what this is aimed at. especially as most people have SSDs and loads[1] of ram

[1] compared to the days of filemaker

Re: BeeBase, a programmable relational database with graphical user interface

#45
post #35

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…

I haven't seen anything that beats the UI and UX of FileMaker Pro from the 90s.

Truthfully, given the backwards compatibility of Windows and Wine, you could still get away in this day and age with sticking with it as a solution.

Re: BeeBase, a programmable relational database with graphical user interface

#46
Beyond your computer/workstation, I'd love if there was a personal database program that could also access via your phone, so you can use it on the go (even via dynamic DNS if needed) – modern no-code platforms do that, but data sovereignty would be nice.

Re: BeeBase, a programmable relational database with graphical user interface

#47
post #24

Apparently saved project created with BeeBase is basically a sqlite DB, that you can open with any sqlite browser. So i think a lot of value could come from standardised sqlite format, upon which you could build different UI's to manipulate the content of said sqlite DB and then provide a app that would build client UI based on content of same sqlite file.

You can export to SQLite3, but not import it back in again.

No? I haven't tried it yet, but in the docs it says "SQLite3 file format, and import and export facility"

Re: BeeBase, a programmable relational database with graphical user interface

#48
post #30

Earlier quoted context omitted.

guess I missed it, im used to scrolling and seeing screenshots and features on splash page. I must admit I wasn't very interested in this piece of software to begin with.

> guess I missed it, im used to scrolling and seeing screenshots and features on splash page. Sigh... A generation conditioned by horrible endless-scroll single-page "applications" (web sites).

Sure buddy. I began using the web in 1996 and I had the same reaction.

Re: BeeBase, a programmable relational database with graphical user interface

#49
post #27

Earlier quoted context omitted.

[flagged]

No comment would have been better than this comment. Now both the software and its defenders sound really hostile and off-putting.

It's a database for programmers that want to be able to program their database and have a basic GUI on top.

If it's too big a hurdle to read the manual you'll never manage to use it for its purpose. Is this a threat to you somehow? In what way?

Do you have the same opinion about ripgrep?

  $ rg 'function('
  regex parse error:
      function(
            ^
  error: unclosed group

Re: BeeBase, a programmable relational database with graphical user interface

#50
post #36

Earlier quoted context omitted.

It's not about a user, it's about someone declining to become a user because the manual is distributed as a separate PDF. I see two solutions for this problem, either use another software or hire someone to adapt this one to you. As a user you know the basic constraints on table names, if you don't you can't use the software.

> It's not about a user If your users are developers, then this mindset will inevitably lead to poor developer experience (DX). That is a stance that someone could take, but their software would be then only used in spite of the DX, not because of it. In general, this would lead to a more miserable experience. I don't think that's good, even if it's just a lot of small annoyances along the way. Here's a Dylan Beattie…

Yeah, people have been having miserable experiences with this software and its predecessor for decades but still keep at it, they must be a lot less smart than you.
Post reply on HN