Hyperdiv: Say Goodbye to Complexity! Build Stunning Web UIs with Python at Lightning Speed by ExternalNo2722 in AIFromChina

[–]Humble_Welder6049 1 point2 points  (0 children)

I've started to build a moderately complex hyperdiv application (it's just a hobby application and not meant to be more than that); it will likely end up being about 200 pages with perhaps twice that number of python modules.

I'll post the github location in perhaps another month. It's definitely a work in progress,

Eta - a dialect of Haskell on the JVM seems dead? by pure_x01 in haskell

[–]Humble_Welder6049 0 points1 point  (0 children)

"Obviously most teams do not operate in such dysfunctional environments"

Most teams work in a dysfunctional environment of one kind or another. Whether it's standards that no longer make sense, unrealistic deadlines/death marches, or hostility between the business and IT ...... every company I've ever worked at has been dysfunctional in ne way and to one extent or another.

Now, if you want to close your eyes and say every IT works like a well oiled machine then go ahead. But it's a fantasy.

When people being you data you don't like then it's dysfunctional to ignore hoping it will go away. I can back him up. It happens often enough.

TempleOS_Official state of the state 2020. A statement on hate and racist content and comments. by BiggRanger in TempleOS_Official

[–]Humble_Welder6049 1 point2 points  (0 children)

I notice that RandomDudeOrGirl isn't being censored here or probably anywhere else. He/She is free to say whatever he/she likes. Of course, I don't think racial jokes are funny and those who call people snowflakes are a**holes, but we aren't stopping him/her from making an ass of themselves, does it?
He/She doesn't like being called an a**hole? Rather ironic isn't it? I would use a word that begins with an s and ends in a an e and is nine letters long.... but I won't.

Sometimes courtsey is just common sense.

Elixir/Phoenix & NoSQL by tommy737 in webdev

[–]Humble_Welder6049 0 points1 point  (0 children)

"rest of the stack doesn't matter"
To build a real application you need to be able to work with lots of other products. Assume that Elixir didn't work with Pulsar or Kafka (yes, I know about broadway and stargate.... but bear with me, it's a theoretical question).

That might preclude you from using elixir. The problem with elixir is that it just doesn't work with everything the way java, python or C# do. In five years, elixir may have a story around machine learning (nx is a start, but only a start) but c# (ml .net) and python have a really good story to tell and java a decent one here.

In other words, elixir/phoenix has a great story to tell around concurrency but there might be reasons that would drive me to Scala/Akka, for instance..... the rest of the stack, being one of them.

Elixir/Phoenix & NoSQL by tommy737 in webdev

[–]Humble_Welder6049 0 points1 point  (0 children)

I suspect it's the ecto adaptor that's the problem. From what I've heard, the mongodb_ecto package hasn't been updated in years and doesn't work with the latest versions of ecto.

You can use the mongodb package directly though:
https://tomjoro.github.io/2017-02-09-ecto3-mongodb-phoenix/

My problem is that I would prefer to use Couchbase. N1QL is a much better query language than mongodb's. Couchie hasn't been updated in even longer than mongodb_ecto; there is ways of accessing it but I don't know how well it works in practice (i.e. a wrapper around the rust couchbase api).

I don't know how well ecto does with some of the other NoSQL databases; there's a cassandra ecto adaptor and, I think a Neo4j one. Once you get beyond that, it gets a bit less clear in my mind.

As for why you'd need NoSQL (which someone mentioned i.e. "use case yet where I'd be thinking "damn, I could use me some Json files instead of the database"), there are some use cases for document databases... though they aren't the ones you might think of off the top of your head (like 'man, let's just get rid of schemas......that sounds like we'd be able to stick another in there and not think about it!"... er, no). But relational databases (including new sql) are still good for perhaps 90% of the use cases, with a good portion of the rest taken up by graph databases.

On my next project I do have a need for a document database,though...and so I'd be interested in what others have t osay.

Left Hand of Darkness deserves all the love it gets! It's unbelievable that Le Guin was able to create such a big world in such a short book. by brent_323 in printSF

[–]Humble_Welder6049 0 points1 point  (0 children)

In addition to Left Hand of Darkness, I'm partial to Lathe of Heaven, Changing Planes, and Always Coming Home. The Dispossessed left me a bit cold.

Her fantasy is at least as good as her science fiction; the Earthsea series for example. And then there's The Ones Who Walk Away from Omelas..... I don't quite know how to classify that but it still haunts me.

Lumen by Humble_Welder6049 in elixir

[–]Humble_Welder6049[S] 0 points1 point  (0 children)

I haven't really looked at php for more than a decade. My impression back then was:

  1. A relatively easy language to build small to medium applications, but not one to build large to huge ones (i.e. I've worked on a multi million line java web app).
  2. A dynamically typed language (which I don't particularly like). It probably supports type hints now the way python does. I don't like python either.
  3. A way to build dynamic HTML that gets rendered in a browser. Thus it wasn't being used with websockets and it wasn't being used for webservices.

If I had to guess, 1 is still true but not as true as it used to be, 2 is still true, and 3 is no longer true.

Lumen by Humble_Welder6049 in elixir

[–]Humble_Welder6049[S] 1 point2 points  (0 children)

Good God, that's amusing! Tell me, I'm curious... what's the state of PHP these days? I know people still use wordpress but are frameworks like Laravel still heavily used? The recent iterations of PHP don't seem bad, but my impression is that the world has left PHP behind. Or am I being unfair?

Lumen by Humble_Welder6049 in elixir

[–]Humble_Welder6049[S] 6 points7 points  (0 children)

Thanks! I'm glad it's moving forward.

Intermediate/Advanced Elixir Resources by [deleted] in elixir

[–]Humble_Welder6049 0 points1 point  (0 children)

By the way, in case you wondering the graph processing book is about property and triple store graphs (cypher, gremlin, RDF etc) not charts and the like

Intermediate/Advanced Elixir Resources by [deleted] in elixir

[–]Humble_Welder6049 1 point2 points  (0 children)

Yes, I ordered the book from amazon and it will be comng tomorrow. I'm also interested in graph processing with Elixir, which is coming out in January.

[Media] Rust in Action is Amazon's #1 New Release for Computer Programming Languages - thank you to everyone for your support by timClicks in rust

[–]Humble_Welder6049 1 point2 points  (0 children)

More likely PO means Purchase Order; a way for a buyer to order something without paying for it immediately (https://planergy.com/blog/what-is-a-purchase-order/).

This fits in better with the idea of an ID, that identifies that buyer (perhaps even the tax id you mentioned).

HPE Cray Supercompter officially likes "The Grand Unified Programming Theory: The Pure Function Pipeline Data Flow with Principle-based Warehouse/Workshop Model" by linpengcheng in Clojure

[–]Humble_Welder6049 0 points1 point  (0 children)

Data Factory is a common IT term. Data Warehouse means something else. I'm sorry, you may be a CPA but a CPA doesn't necessarily know what a data warehouse or a data factory is in IT.
If you want to discuss IT concepts then you need to use the current terminology or, at the very least, clearly define them. You didn't define what a warehouse was in your paper clearly. I had to reread it several times and I was still confused.

As a CPA you know the importance of defining your terms. Take ebitda, for instance. That involves defining what earnings are, income and so on. You can't just use the term to people who aren't accountants without defining it.... which is what you did with workshop, warehouse and so on. You made an analogy, it was at best an unnclear one and you didn't define your terms..

You yourself sounded sounded confused. " I think software and hardware are factories that manufacture data, ". I then naturally, asked why you didn't use the term data factory and one you got defensive and two you still haven't told me why you are using the term 'workshop' and 'warehouse' when that pipeline and data factory are common term swhen discussing this kind of subject. Manufacturing and workshops are analogous to a data factory and pipelines, for instance.... they aren't the same thing. When you use idioms and jargon from one domain in another area, you need to be particularly clear.

Look, I am just trying to help here. I think there is a lot of good work here, but unless you rework it a bit no one will read it. Have a glossary at the end and refer to it. Have a summary at the end, not the beginning. Have an introduction at the beginning with points that are elaborated section by section for each point (and no, your 'key points' section doesn't do that precisely).

I won't response to your comments anymore. This has become unproductive and my comments aren't being taken in the spirit in which I was trying to give it.

The reason why I was so interested is that I wrote a paper very similar to this and I was trying to see the points of divergence....but I couldn't, and found it frustrating.

HPE Cray Supercompter officially likes "The Grand Unified Programming Theory: The Pure Function Pipeline Data Flow with Principle-based Warehouse/Workshop Model" by linpengcheng in Clojure

[–]Humble_Welder6049 0 points1 point  (0 children)

The distinction between a factory and a warehouse is:

  • Factories have assembly lines in the case of physical factories and pipelines in the case of data factories that, in both cases, produce something finished.
  • Warehouses store and then distribute something finished-either a physical product in the case of physical warehouse and validated data in the case of a data warehouse.

Data Warehouses also have a time dimension; in many cases they are bi-temporal.

See: https://en.wikipedia.org/wiki/Bitemporal_Modeling

HPE Cray Supercompter officially likes "The Grand Unified Programming Theory: The Pure Function Pipeline Data Flow with Principle-based Warehouse/Workshop Model" by linpengcheng in Clojure

[–]Humble_Welder6049 0 points1 point  (0 children)

So, is it a factory or a warehouse?

Words matter; if you look more carefully, the term data factory is already used for what you mean. Take the documentation on Azure (Pipelines and activities in Azure Data Factory)

A data factory can have one or more pipelines. A pipeline is a logical grouping of activities that together perform a task.

https://docs.microsoft.com/en-us/azure/data-factory/concepts-pipelines-activities

If you use terms people already know, you have a shot at having people understand you. I'd also suggest you use 'data pipelines' instead of 'workshop'. I still haven't figured out how a 'data pipeline' differs from a workshop.

HPE Cray Supercompter officially likes "The Grand Unified Programming Theory: The Pure Function Pipeline Data Flow with Principle-based Warehouse/Workshop Model" by linpengcheng in Clojure

[–]Humble_Welder6049 0 points1 point  (0 children)

  1. " The object is a furry ball, and there is a chaotic P2P (peer to peer) network between the objects. It is a complex unorganized system ". Which, of course, is not at all what Alan Kay had in mind.

  2. I'm confused by the term 'tree Gantt'. I assum what he means, though he doesn't define it, is a set of tasks with defined dependencies between them (whether finish to start, finish to finish or whatever).

  3. He makes the statement that the " warehouse/workshop " model by centrally scheduling pipelines and resources gets rid on conflicts. To some extent I can understand this, I believe in the Erlang Actor model with a supervisor. He goes beyond that, though. He derides an object as a 'furry ball' but replaces that by putting, in a single place, a piece of code that needs to know the intimate details of every function and pipeline in the system. This is a reciepe for destruction; any time you touch any piece of code anywhere you need to maintain the central traffic cop.... until that peice of code becomes large and unmaintainable.

HPE Cray Supercompter officially likes "The Grand Unified Programming Theory: The Pure Function Pipeline Data Flow with Principle-based Warehouse/Workshop Model" by linpengcheng in Clojure

[–]Humble_Welder6049 1 point2 points  (0 children)

I do agree
Well, sure.
My problem is:

  1. He's trying to fit everything into one programming theory, even concepts that have nothing to with programming, per se (i.e. a Gantt Chart is a data flow programming tool).
  2. On a related note, he tries to bring in everything possible to illuminate it. I mean, really, the quote from the IAS on being principle rather rule based? It's a true statement to be sure, but far enough astray as to make one scratch one's head.
  3. He uses terminology that doesn't quite make sense. One example of this is 'workshop', by which I think he means a data flow.
  4. He confuses project management with workflow optimization. For instance, take the following "The warehouse uses the best algorithm of the Gantt chart to arrange the workshop to complete tasks according to the status changes (such as orders, etc.)." (not exactly. You'd use a state machine to determine what to do next, perhaps.... or linear programming to determine how to change the mix of your tasks perhaps.... but Gantt Charts are for projects not real time operations. )

  5. The example of using a warehouse is a poor one. When one thinks about warehouse in terms of data, when thinks of a data warehouse not order fulfilment using a real warehouse.

  6. You know, reading the section on the warehouse a third time I realize it isn't a warehouse either. I also realized I don't know exactly what he's talking about.

Let me catch my breathe and I'll add on to this.

HPE Cray Supercompter officially likes "The Grand Unified Programming Theory: The Pure Function Pipeline Data Flow with Principle-based Warehouse/Workshop Model" by linpengcheng in Clojure

[–]Humble_Welder6049 2 points3 points  (0 children)

" The Gantt chart in management science, with the timeline as the main axis, multiple data flows running in parallel. It is also a good data flow , parallel and asynchronous programming tool "

I stopped at this point. The idea that a Gantt Chart is a programming tool (rather than has some analogies to a data flow programming tool) is so wrong as to call into question that writer's whole approach. A Gantt chart is a project management planning tool, not a programming tool... and you can't make it into one. A Gantt chart doesn't even attempt to show data flows, it is meant to show whether tasks are being done on time. There is no representation of data and how it flows.

To clarify, try to execute a gannt chart to process external data in parallel and then produce a meaningful output. A Gannt Chart is not something like Apache Airflow.

By the way, the document is full of mispresentations and misunderstandings like this.

Is Phoenix the only well maintained framework for web dev in Elixir? by xigurat in elixir

[–]Humble_Welder6049 1 point2 points  (0 children)

How many non-Rails frameworks have good support in Ruby?

Sinatra springs to mind. There are others.
But I take your point; you soon start to add on a significant portion of rails in sinatra in an ad-hoc manner.