Fork me on GitHub
#off-topic
<
2020-02-24
>
Audrius17:02:34

where you guys keep your blogs?

p-himik17:02:11

In imagination. 😄

😎 12
ben17:02:24

I have a static blog hosted on heroku’s free tier, but I hear netlify is pretty good (also github pages - which I would probably do if starting over)

Kurt Sys23:02:26

or gitlab pages... has more possibilities than github pages, but pretty similar.

👍 8
lilactown18:02:16

What would push one towards using something like a graph lib like ubergraph, vs a datalog lib like datascript?

andy.fingerhut18:02:16

I haven't used datalog lib much to compare them, but have reached for things like Ubergraph in use cases where I wanted to calculate graph-algorithm-like things, such as finding the strongly connected components, shortest paths, maximum flows, reachability among all pairs of nodes, etc.

andy.fingerhut18:02:40

I have no idea whether datalog libs like datascript also typically provide algorithms like those, or whether their data structures are poorly suited to implementing such algorithms on top of the data structures in some way.

lilactown18:02:23

yeah, that makes sense. I’m not completely sure what graph operations I need yet. my general use case is I’d like to have an already-constructed a graph, and then have users score whether they like or dislike certain edges and vertices (in a nominal way). then, show the user their scored graph. I initially started thinking of how I would represent it in datalog / as a “graph of facts” where each edge and vertex was an entity that references each other, but I think that the flexibility of that isn’t something I really need, whereas I’m much more likely to need to leverage similar algorithms to what you listed

lilactown18:02:37

If only ubergraph supported CLJS

Audrius20:02:29

Any plans to port Clojure to COBOL? 🙂

andy.fingerhut20:02:34

It seems likely that the intersection of people interested in Clojure, and interested in COBOL, and like COBOL so much as a hobby programming language that they would be willing to spend the time to do that, is small.

andy.fingerhut20:02:49

Huh, I had never realized that COBOL started in 1959. Pretty close in time of origin to Lisp, Fortran, and Algol.

manutter5120:02:53

We’re waiting for them to finish the object-oriented version, ADD ONE TO COBOL GIVING COBOL.

andy.fingerhut20:02:47

I knew COBOL was used a lot, but had not seen any quantifications for it. Here is an interesting statistic, written about in a 2009 article: "As recently as 1997, the Gartner Group reported, 80 percent of the world's business ran on Cobol with more than 200 billion lines of code in existence and an estimated 5 billion lines of new code annually."

andy.fingerhut20:02:48

I'd bet the rate of growth of many other languages has overtaken COBOL lines of code growth rates since then, but not planning to dig for such statistics any time soon.

seancorfield21:02:19

@manutter51 ANSI Standard COBOL is object-oriented 🙂

manutter5121:02:57

Is it really? How?

seancorfield21:02:01

In fact, COBOL nearly got its ANSI Standard with OO stuff out there before we (J16) got the ANSI C++ Standard out... it was a bit of a sore point for us, at the time.

manutter5121:02:21

That’s pretty wild, I may have to read up on that.

manutter5121:02:00

I debugged one COBOL program in my career--the scan sheet software at a university. 800K of source code, developed over 15 years by I don’t know how many different coders.

manutter5121:02:06

I was pretty impressed with the code, actually. The reported bug was that it wasn’t sorting the list of results correctly, but it turned out to be not a bug. We had bubble sheets that had 3 spaces for an alphabetic department code plus 3 digits for a course number, and a lot of courses had only a 2 letter department code, so some students were filling in _AA and some were filling in AA_ and even some A_A, and the program was (correctly) sorting by dept code, course number, last name, first name.

seancorfield21:02:38

I ported the Microfocus COBOL compiler (which was mostly written in COBOL!) to the Sun 4 (aka SPARC) and Motorola 78000 (aka 88000) in the late 80's -- and I'd also been a COBOL programmer at an insurance company before that.

manutter5121:02:05

That sounds like it has the potential to be awesome and terrifying at the same time.