playground VS nvim-gps

Not the parent, but NNs typically work better when you can't linearize your data. For classification, that means a space in which hyperplanes separate classes, and for regression a space in which a linear approximation is good.

For example, take the circle dataset here: https://playground.tensorflow.org

That doesn't look immediately linearly separable, but since it is 2D we have the insight that parameterizing by radius would do the trick. Now try doing that in 1000 dimensions. Sometimes you can, sometimes you can't or do want to bother.

For visualisation and some fun: http://playground.tensorflow.org/

https://seeing-theory.brown.edu/

https://www.3blue1brown.com/

https://playground.tensorflow.org/

There’s an interactive neural network you can train here, which can give some intuition on wider vs larger networks:

https://mlu-explain.github.io/neural-networks/

See also here:

http://playground.tensorflow.org/

This site is worth playing around with to get a feel for neural networks, and somewhat about ML in general. There are lots of strategies for statistical learning, and neural nets are only one of them, but they essentially always boil down into figuring out how to build a “classifier”, to try to classify data points into whatever category they best belong in.

I don’t know much experimenting you’ve done, but many repeated small scale experiments might give you a better intuition at least. I highly recommend this online tool for playing with different environmental variables, even if you’re comfortable coding up your own experiments: http://playground.tensorflow.org

Even if you can’t code, play around with this tool: https://playground.tensorflow.org — you can adjust the shape of the NN and watch how well it classifies the data. Model size obviously matters.

I don't think so. You can easily play around in the browser, using Javascript, or on https://processing.org/, https://playground.tensorflow.org/, https://scratch.mit.edu/, etc.

If anything the problem is that today's kids have too many options. And sure, some are commercial.

Well there is no point of using a multilayer linear neural network, because a cascade of linear transformations can be reduced to a single linear transformation. So you can only approximate linear functions. However if you have prior knowledge about the non linearity of your data lets say you know that it is a linear combination of polynomials up to certain degree, you can expand your input space by explicitly making non linear transformation. For instance a 1D linear regression can be modeled by 2 input neurons and 1 output neuron where the activation of the output is the identity. The input neuron x0 will take a constant input namely 1 and the second input neuron x1 will takes your data x. The output neuron will be y=w_0 * 1+w_1 *x which is equal to y=w_0 +w_1 * x. Let us say that your data follows a polynomial form, the idea is to add input neurons and expand your input to for instance X=[1 x x2] in this case you have 3 input neurons where the third is an explict non linear form of the input so y=w_0 + w_1 x +w_2 x2. The general idea is to find a space where the problem becomes linear. In real life example these spaces are non trivial the power of neural network is that they can find by optimization such space without explicitly encoding these non linearities. Try playing around with https://playground.tensorflow.org/ you can get an intuition about your question.

I've been using winbar.nvim with nvim-gps which depends on treesitter. Unfortunately it's been archived/deprecated but still works fine.

With the deprecation of nvim-gps we are left with LSP's more accurate code context parser nvim-navic or lspsaga. I however only use LSP for like 5 languages as opposed to treesitter since it's just easier to install all language parser

and nvim-navic or in this projects case it is its predecessor - nvim-gps

I currently use feline.nvim as a framework for creating my custom statusline, and before that I was using galaxyline.nvim. A feature that I would really like though is for each section of the statusline to able to dynamically resize based on the window size, and dissappear if the window gets narrow enough, based on some priority that I give them and some truncation rule. By truncation I mean that for instance a file path could get shortened by pathshorten(), the filetype indicator would only display the devicon and not the filetype name, nvim-gps would only use a depth of 1, etc... This behaviour would be defined by the user, but the framework would calculate which components to truncate in order to fit as many as possible in the priority that the user has chosen for each component.

I've added a pull request to support json https://github.com/SmiteshP/nvim-gps/pull/41