HN user

vasvir

131 karma
Posts2
Comments73
View on HN

This is not my understanding by reading the article. The blade failure will destroy the plane if developed independently of the rest. So modern nacelles will contain the blast as you say but they have decades of integration testing together with the blades in all kind of conditions.

if you develop everything anew there will be mismatches in tolerances and thousands of potential individual failure risks that can be combined in interesting, unexpected and fatal ways.

In the same sense windows are not network transparent when in fact RDP works perfectly, certainly much better that X11 over WAN.

Actually for wayland there is wprs for remote display of apps so here it goes the network transparency argument...

Not only winners but anyone that looks like to know what is doing.

By that I mean that they try to detect and ban any pattern that may be math / ML derived or arbitrage seeking.

I have been banned on an account that was loosing money (around -15eur) and the bet was 2.96eur - yep fractional bets is a big no - no.

So while it is possible to find better odds and win in the long run based on stats and ML with a 3% - 5% profit they will ban you before you do.

Copy pasting images is often hit & miss.

Sometimes I have the image copied but it doesn't paste in the browser. However it can be pasted to GIMP. If I paste it there and copy it from GIMP then I can paste it to the browser.

So who's fault is that? Spectacle's or browser's? Maybe wayland's?

I agree about Kate.

In addition while kate has many plugins, like the one that allows running arbitrary command line utilities with std input the current selection, I would like to point you at something else in case you write / debug SQLs.

Kate has a SQL plugin that allows to send the current selection to the connected SQL server for execution. It displays the output in table form below the editor pane and you can copy paste rows or columns.

That allows to organize your SQLs in markdown files. That was such a productivity booster for me that simply there are no words to describe the difference felt.

Been there done that. At least for life science / health publications. The article is spot on.

Not sure if there is value of that approach in other more rigorous fields but in health for sure it does. The knowledge in health science is generally fragmented and a way to connect islands of knowledge has the potential to unlock a lot of value.

If you would like to see how this article ideas are applied in a playful manner in a web application you can visit: https://www.biovista.com/vizit/

Java uses type erasure which are very cheap in compile time but you cannot do things like

   t = new T(); // T is a template parameter class
C++ uses reified generics which are heavy on compile time but allows the above.

With that level of nit picking everything is off and there is no OS / DE with zero inconsistencies.

KDE is good for me. I admit that I simplify the interface in a new setup turning off some things but the fact that it gives me that capability is a huge plus for me.

KDE Connect rocks by the way...

My bet on this would be to abandon moving to vertices like simplex does and move on facets instead.

However, this requires to solve a quadratic 'best direction' problem each time which if IIRC reduces to 'Linear complementarity problem (LCP)' (https://en.wikipedia.org/wiki/Linear_complementarity_problem). The LCP problem scales with the number of active constraints which is always smaller than the dimensionality (N) of the problem. So if you have number of constraints P >> N you are golden.

Note that Dantzig has also contributed to LCP.

Obviously any breakthrough in these basic methods is directly translatable to more efficient learning algorithms for training single layer neural nets (perceptrons). Extending to multi layer NNs is not far off from there...

Thanks that's an interesting trick.

This is beautified if somebody wants to see how it is done.

  function() {
    var myBody = document.getElementsByTagName('body')[0];
    var myBodyWidth = myBody.style.width;
    if (!myBodyWidth || myBodyWidth === 'auto' || myBodyWidth === 'inherit') {
        myBody.style.width = '1200px';
        myBody.style.marginLeft = 'auto';
        myBody.style.marginRight = 'auto';
        myBody.style.position = 'relative';
        myBody.style.cssFloat = 'none';
    } else {
        myBody.style.width = 'auto';
        myBody.style.position = 'static';
    }
  }

Yes,

Also the other problem of a big monorepo is that nothing ever dies. Let's say you have a library and there are 1000 client programs or other libraries of your API. Some of them are pretty popular and some of them are fringe.

However when you are changing the API they all have the same weight. You have to fix them all. In the non monorepo case the fringe clients will eventually die or their maintainer will invest on them and update them. It's like capitalism vs communism with central planning and all.

That's not my impression. MariaDB looks to me that it has greater development velocity than MySQL.

Do not know about speed difference divergence though. I guess a speed run down would be interesting...

What I found invaluable is the use of Kate (yes the editor) SQL plugin. It can connect to MySQL/MariaDB, Postgres and others.

The main benefit is that you can organize your SQLs in files or even better in markdown files.

God knows how many times I had to retype the same or a very similar SQL in the past.