It’s very funny to me that the dominant Twentieth Century conception of AI was a slightly awkward nerd with an inhuman mastery of facts and logic, when what we actually got is smooth-talking bullshit artists who can’t do eighth-grade math.

if the C++ people want everyone to stop calling it C/C++ then maybe they should stop letting us compile C as C++

I think it's important to follow a few people where you never have any idea what the fuck they're talking about but it seems interesting

@agdakx Imagine that we needed new set theory axioms to prove the results for each new field (number theory, analysis, group theory, etc.) and that we would regularly discover combinations of those axioms to be contradictory. Why isn't the world like that? We've only had to tweak them a few times, and we only discovered natural independent statements a few times.

Sick of people calling everything in crypto a Ponzi scheme. Some crypto projects are Pump-and-Dump schemes, while others are Pyramid schemes. Others are just middlemen skimming off the top. Others are just standard-issue fraud.

Stop glossing over the diversity in the industry.

"So there is no way, really, to make code go faster, because there is no way to make instructions execute faster. There is only such a thing as making the machine do less."

He paused for emphasis.

"To go fast," he said slowly, "do less."

I don't see how anyone is surprised that the types instance is a little overly restrictive in the rules it enforces to maintain types safety.

Playing around with #OpenAI's #GPT3 text generator led me to perhaps the creepiest behavior yet. As @ct_bergstrom noted, the AI bots are able to cite the sources of their own writing.

I decided to see if it could function as a plagiarism detector. But when I put a few snippets of my own writing in, it found several uncited sources. (Attached.)

Aha! Someone must have plagiarized me! Or so I thought. But the truth was much stranger....

we were so worried about "malware" (software that deliberately spreads and causes harm) that we forgot to protect against "mallware" (software that transforms every single computing experience into a shopping mall) and it took over the world oops

I've just been amusing myself by trying to fix a bug, because apparently that's what passes for fun on a day when I'm on strike.

After several hours I changed an x to a y and everything was fine.

"Hitting the machine with a hammer: £1
Knowing where to hit: £9,999"

When a C++ programmer claims that rusts ownership semantics are vague and confusing I immediately become suspicious of all C++ code they've written

An Incredible Day In Internet History

It started with the Twitter lockout. 10,000 new users per hour. A QUARTER MILLION people migrated to Mastodon in one day. The servers struggled. Remarkably, admins all over the world built up capacity in real time. New users were patient. The system held.

It's running better now. There will be more hard days ahead, but people powered social media has arrived.

#twittermigration #NewUsers #Welcome

Had my compilers class try to break 133 different compilers, which just wrapped up.

types.pl/@dvanhorn/10930589547

OK first, this was fun and I recommend it.

The assignment was to write input programs that would be run on the collection of compilers submitted from the *previous* assignment. If results differed from a reference interpreter, that compiler was considered broken. The goal was to break as many things as possible.

The learning objective here was to learn how to read an informal spec and write test cases that are likely to exercise bugs. I think that worked. For many students it was clear they hadn't done this kind of task before and didn't really know where to start, which was surprising to me.

Students very quickly (like in hours) found overspecifications in the behavior of the interpreter and used it to "win", but I was able to adjust the interpreter and after the first day, that kind of exploit went away.

Many students did what I expected: they wrote small tests based on the assignment spec that broke a good chunk of the compilers. With some effort, they could get ~70-80 of the 133 compilers this way.

A few students wrote tests *not* guided by the assignment spec, but instead just wrote small examples drawn from the whole language. They found bugs in the starter code that was given to students, and thereby knocked out all 133 compilers.

One student found a bug in the parser which in two characters broke all the compilers!

Another student found a bug in the run-time system which read some memory as a uint, when it should've been int.

I look forward to refining and iterating on this in the future.

As more academics reach Fedi, please PLEASE consider not doing research on users here without explicit opt-in consent

This isn't a zoo

It's not just condescending for you to treat us that way, it's also against a lot of instances' terms of use

See "Use of Scholar Social for research" at the following link for an example:

scholar.social/privacy-policy

Niki and Wouter interviewed me on the Haskell Interlude podcast, the episode is out!

haskell.foundation/podcast/18/

Need some numbers that go up and to the right in here.

people look at the fediverse and think "this will never gain mass adoption." they are thinking about it all wrong. fedi isn't about posts going viral or gaining market share. the goal of the fediverse is simple: to find and kill god

Show older
types.pl

A Mastodon instance for programming language theorists and mathematicians. Or just anyone who wants to hang out.