fsmv

Have you not seen vend bench?

I think the difference is in math the problem is fully specified and easily verifiable and in programming it's not. I don't agree that we always know we can solve the problem.

But select statements are the most important part, and second to that is the fact that goroutines are low cost user space threads

But it's not exactly a cosmetic change. x++ is semantically different from x; x++; I wonder if clang would make it branchless if you instead write

  if (BLQS_CMP(x, piv)) { *lwr = x; ++lwr; }
    else { *rwr = x; --rwr; }

Although it's true compilers can be very sensitive to exact phrasing triggering specific optimization passes. So it still might not give the branchless version by changing it to pre increment (which is the same as a normal +=1).

The only way to really know is to dig into what optimization passes clang took in both cases and analyze the difference.

You should just have it OCR a screenshot of the PDF that would probably work better

We don't really know how to program yet, or how to manage our programs. We don't really know what we want to say or how to say it. We don't have good computer languages for expressing what we want to computer to do. We don't know how to think about programming.

I think this is still true today. Software is only just starting and there is a lot of room to find better ways of doing things.

I think the reason writing a compiler is easy today is the theory I learned in compilers class. How to do context free grammars, the concept of abstract syntax trees, the pattern of writing a recursive descent parser and having a lexer that only looks one symbol ahead and has a peek function. On top of that we have experience with lots of languages and type systems to draw from when constructing a new one.

I was just doing some research and apparently all of this stuff was invented around the late 60s and so in the 70s it was still new and by the 90s it was standard practice. The dragon book came out in 1986 and spelled it all out in one place.

Today we have the benefit of knowing the right ideas to use from the start and confidence that if you follow the formula it will all work out.

There's also the major problem of people expecting Google to be right when it tells them something but OpenAI had no starting reputation so it was okay to say "be aware it might be wrong sometimes"

I don't think that's an ongoing debate looks to me that it ended in 2019 https://github.com/golang/go/issues/31440#issuecomment-53724...

Presumably the missile needs GPS to hit the target so if you jam right when the missile is coming in the missile will miss so you can't really jam the warning

Also if you broadcast noise when your missile is about to hit then your own jamming signal acts as an early warning as well, although I guess it wouldn't provide location.

Now the flaps don't melt! The tiles don't fall off!

It's a major overhaul of the design they've been working on for a long time. There was talk of v3 fixing the problems in early v2 test flights. The booster is v3 as well which presumably is why they had some problems. I believe this is also the first time they flew the v3 engines with the plumbing fully integrated in a single piece housing they 3D printed.

I only read the abstract but I got the impression that their solution to this is they have both. They translate all the data as if it was code and if it gets called into they use the translation where if it gets read as memory they use the original.

Edit I found this in the paper

Elevator sidesteps the code-versus-data determination altogether through an application of superset disassembly [6]: we simultaneously interpret every executable byte offset in the original binary as (i) data and (ii) the start of a potential instruction sequence beginning at that offset, and we build the superset control flow graph from every one of the resulting candidate decodes. Every potential target of indirect jumps, callbacks, or other runtime dispatch mechanisms that cannot be statically analyzed therefore has a corresponding landing point in the rewritten binary. These targets are resolved at runtime through a lookup table from original instruction addresses to translated code addresses that we embed in the final binary.

Not true, they were down because they still use bluesky's relay

Trade secrets once made public don't have any legal protection and I haven't signed any contract with anthropic

Implying that programming is not an actual job that takes years of training and experience

To be clear I don't think the AI can do either job

The champion of compatibility lives on

Yes but the lords are not satisfied with this. They demand the 10x productivity they sold to investors. If you do it this way you will not produce 10x the code.

I'm having trouble understanding to what extent the machine learning used for interfacing with the neurons is doing the learning

In reality it's not that hard for them to work around the constitution e.g. by buying data from private companies

Your cookie banner is very inconvenient and made me leave your website and not read the article

It would be nice to give them some kind of attribution in the readme or something since you know which projects you referenced

A good reason to actually test that you reject man in the middle certs if you rely on TLS in your application

I don't understand, yay updates itself. I've never once had this problem.

There was a short thread about this on mastodon involving Rob Pike the other day https://hachyderm.io/@robpike/115896334649905170

The go standard library has an implementation of ed25519 although I did not find ed448 it also has some NIST curves. There are a few libraries that do ed448 like one from cloudflare.

I think what you're doing is really cool.

Your instructions to comment on your blog are incredible, come talk to you face to face. If I didn't live on the other side of the country it would be meaningful to tell you what it meant to me in person.

Skilled humans must understand the problem and write the theorem statement.

I think I was just trying to minimize accidentally matching the wrong thing. Both do work though and it is kinda nice to be more readable.

If I remember right I think ? Is exactly one character only, or maybe it does non greedy .

Best feature of freebsd. I have really messed up the system and successfully restored a boot environment snapshot and everything is fine after.

It happens by default with freebsd-update (I hope the new pkg replacement still does it too)

I made one of these too! I decided not to use // because I use gofmt auto formatting in my editor and it puts a space between the // and the usr. This one isn't changed by gofmt:

    /*?sr/bin/env go run "$0" "$@"; exit $? #*/