Technology

59472 readers

5003 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

164

"waves of technological innovation" have gotten faster over time, "students might now find themselves learning skills in college that are obsolete by the time they graduate" (www.businessinsider.com)

submitted 1 year ago by cyu@sh.itjust.works to c/technology@lemmy.world

56 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] glad_cat@lemmy.sdf.org 17 points 1 year ago* (last edited 1 year ago) (2 children)

I learned how "object-oriented databases" worked in college. After 20 years of work, I still don’t know if such a thing exists at all. I read books regularly instead.

[–] tony@lemmy.hoyle.me.uk 6 points 1 year ago (1 children)

Wiki says they existed, and may still do.. never come across one. I thought mongodb might be one but apparently not.

[–] DrDeadCrash@programming.dev 5 points 1 year ago

Eplan, electrical controls layout tool, used an object oriented database as its file format, It still may. I saw recently that they entered a partnership of some sort with SolidWorks, so they're still kicking.

[–] Paradox@lemdro.id 3 points 1 year ago

I've used one before. Maglev is a ruby runtime built atop GemStone/S, which is an object db. Gives Ruby some distributed powers, like BEAM languages (Elixir and Erlang) have.

Practically all it meant was you didn't have to worry about serializing ruby objects to store them in your datastore, and they could be distributed across many systems. You didn't have to use message buses and the like. It worked, but not as well as you'd hope.

Amusingly, BEAM languages, have access to tools a lot like oodbmses right out of the box. ets, dets, and mnesia loosely fit the definition of an oodb. BEAM is functional and doesn't have objects at all, so the comparisons can be a tad strained.

Postgres also loosely satisfies the definition, with jsonb columns having first class query support.