639 karma · joined November 3, 2015
There's not some mystery about who is doing crime. They're arrested all the time and let go! If we simply prosecuted the people who are arrested crime would fall by 90% over night.
There are exceptions of course, But the general trend is worrying.
This kind of law would wreak havoc for certain companies (and content creators). However, just like prediction markets, ads distort and ruin the very thing they are trying to optimize.
What neither I nor the author anticipated was that the easiest way to make the markets "efficient" was to rig them.
In hindsight it's obvious, but optimism is one of the most powerful blinders out there.
Of course, you may not care, and that's fine. It's important that people not be delusional about this though. A person with no medical knowledge and an AI will never be as good as someone with prodigious medical knowledge and an AI. The same is true for any profession, whether programming, music, writing, etc.
The problem is ultimately with how the software is structured from the the start. Pressure to release fast, and the fact that most software engineers are not experts, means that nearly all software systems and libraries have poor design. They will be bloated and buggy, and difficult to work with.
Poor design means that development velocity dramatically slows as a project matures. Frameworks ensure that you start development fast, but eventually it takes a week to add a button.
Is there a safe way to use iouring for a webserver, or is libuv the better way to go, even though it has less performance?
In the book, there is a cargo ship carrying 1/3 of a OTP. Other two other ships from two other companies are carrying the other thirds. This actually is a fairly decent method of transporting a OTP (I'm assuming there's some kind of physical security preventing tampering).
The book even talks later on about how only using the pad isn't enough, since it provides no proof of authorship or tampering. Vinge did a pretty good job w/compsci in the book.
The sad thing is all that silicon will basically be worthless.
The reason we have programming languages is the same reason we have musical notation or math notation. It is a far more concise and precise way of communicating than using natural languages.
We could write music using natural language, but no one does because a single page of music would require dozens of pages of natural language to describe the same thing.
You could imagine creating a modified Go assembler that is more generic and not tied to Go's ABI that could accomplish the same effect as LLVM. However, it'd probably be better to create a project like that from scratch, because most of Go's optimizations happen before reaching the assembler stage.
It would probably be best to have the intermediate language that QBE has and transform that into "intermediate assembly" (IA) very similar to Go's assembly. That way the IL stage could contain nearly all the optimization passes, and the IA stage would focus on code generation that would translate to any OS/arch combo.
LLVM: Pretty much everyone who has created a programming language with it has complained about its design. gingerbill, Jon Blow, and Andrew Kelley have all complained about it. LLVM is a good idea, but it that idea was executed better by Ken Thompson with his C compiler for Plan 9, and then again with his Go compiler design. Ken decided to create his own "architecture agnostic" assembly, which is very similar to the IR idea with LLVM.
Swift: I was very excited with the first release of Swift. But it ultimately did not have a very focused vision outlined for it. Because of this, it has morphed into a mess. It tries to be everything for everyone, like C++, and winds up being mediocre, and slow to compile to top it off.
Mojo isn't doesn't exist for the public yet. I hope it turns out to be awesome, but I'm just not going to get my hopes up this time.
Edit: I explained my position better below.