midland_trucker

As someone who has dived into Rust over the past few months, the two main reasons for employing it are: A) Bleeding edge performance (Shares the same problem space as C/C++, zero cost abstractions etc.) B) Memory safety (Giving it a rather unique flavour among systems languages - distinguishing it from the above two)

If you primarily work in C#, the latter won't be a problem you will be looking to solve anyway. I would say if the former intrigues you then Rust would be a great place to start.

Nah, my theory is you're seeing run-of-the-mill brash business dealings with the unusual characteristic of being broadcasted publicly.

You wouldn't accuse the same of CEOs from more 'boring' companies because we only get exposed to the results through sterile PR communication, despite the fact the same candid conversations still happen.

Arianespace of course a huge success for a brief period, until it wasn't.

Liquid-fueled setup is largely unsuitable for ICBMs. Want something that can sit in the silo for years and then be immediately available - so solid rocket motors are the way to go, plenty of other defence companies that are specialists in this.

They only just announced it a few weeks ago, surely not launching it would be the business decision if this was the case.

I'm yet to see a study that convinces me of the potential of this concept. All of them when you get down to the details have at least one of:

  - An unrepresentative test set , i.e. a population with similar blood pressure at recording in which merely predicting a constant 'typical' reading would perform well in terms of accuracy.
  - A major methodology flaw, such as 'demonstrating' an ability to detect fluctuations from a baseline calibration cuff reading in situations where you would expect no significant fluctuations to occur.

I don't have access to this particular paper, but suspect it has the same issue owing to the relatively small sample size.

This is my gut feeling about a lot of activity going on in modern corporations. Private equity firms, for example, have been historically blamed for a lot of once great engineering companies in the UK being combined into a bloated mess of activities - which ends up ultimately sacrificing competitiveness.

However I feel like your average voter shaking my fist angrily a bankers sometimes when trying to put it into words (I don't honestly have a lot of insight on how it all works).

Have you got any good book/essay recommendations on over-financialisation?

I recently needed to render markdown to view some notes. Thought opening chrome w/ a plugin or VSCode felt similarly sluggish options to do such a simple task. Now a few weeks after playing with textualize this pops up! Neat tool.

> In Go, I found that using an interface was not free: it can make the code slower. In C++, if you implement the following type and call count on it, you find that optimizing compilers are able to just figure out that they need to return the size of the inner vector.

I'm surprised at this, do Go interfaces really introduce much overhead? Of course this depends on the level of performance you care about but surely, being a statically typed language, lots of the same optimisations are available.

Exactly, it's just the wrong people at the top and the wrong incentives. Is Arianespace structurally capable of producing economical access to space? Probably not.

Perhaps we're talking past each other, is "loss threshold" a specific term in LLM literature?

Merely pointing out that the debate as to whether we are compute or data limited (OP) has not concluded at all; There are lots of compelling theories on relationship between the two.

That's a fair point. Not at all like training on Wikipedia in which nearly every sentence has novelty to it.

Then again it would give you data on every accent in the country, so the holy grail for modelling human speech.

The WebGL equivalent sites were a delight to go through; So well structured and thoughtfully displayed. It's so great to find a resource you can put some trust in amongst all the outdated and fragmented code out there.

Looking forward to ploughing through this when I have the free time to.