We'll pay you $3000/mo to build your startup on Dark

Re:We'll pay you $3000/mo to build your startup on Dark by aylmao on Tuesday April 10, 2018 @02:18PM (#16803696)

Fair comment, thought something similar when I first read this, but ML falls into its own category IMO because it's not part of the "application" most of the time. It's back-end in that it's not front-end, but it's not what you'd normally consider the back-end of an app.

A model is built offline, experimented upon, tested, and then once ready "connected" to the main app. Like, the TensorFlow code you write doesn't "need" to be on the server; it could be running on your laptop for all you care. It's the output model that eventually makes it into the back-end ¯\_(ツ)_/¯.

> Honest question: does "back-end" now mean "the CRUD and API client portions of a web-based CRUD app?"

Back-end has always meant the CRUD/API portions of a CRUD app.

[ Parent | on HN ]

Re:We'll pay you $3000/mo to build your startup on Dark by throwawayjava on Tuesday April 10, 2018 @02:40PM (#16803914)

> It's the output model that eventually makes it into the back-end ¯\_(ツ)_/¯.

Yes, the model itself is part of the backend, not the code used to generate the model. But the website explicitly mentions "machine-learning __models__" as an example of something that's "not backend".

> Back-end has always meant the CRUD/API portions of a CRUD app.

This is not true. Compilers have backends. Speech processing pipelines have backends. The dragon book, which pre-dates the advent of the WWW, distinguished frontend from backend (and in those words).

Web-based CRUD apps inherited the terminology.

[ Parent | on HN ]

Re:We'll pay you $3000/mo to build your startup on Dark by aylmao on Tuesday April 10, 2018 @10:45PM (#16807639)

People have back-ends. Of course I know "back-end" is very broad, I just thought we were in the same page here, talking about a web back-ends, that is all.

Under that broad definition of the term, sure, go ahead and rant.

[ Parent | on HN ]