cellularmitosis

I first learned of the concept of “buffer bloat” from him, and how artificially limiting your upload bandwidth a bit can avoid huge lag spikes https://www.cringely.com/2011/01/04/2011-predictions-one-wor...

A YouTuber by the name of Codacus has been pushing the envelope in this area.

I found figma’s remote MCP to be a poor fit for iOS development (it sets tokens on fire and gives Claude the details as React+Tailwind) and got much better results by having Claude build a set of “lens” tools around their REST API (“give me all of the fonts”, “give me the layout dimensions”, “give me the colors”, etc).

The key to making it token efficient was allowing Claude to invent its own plaintext markup format for the lens output.

We don’t know what quantization level was used for the weights or the kv cache for you or for parent poster, so this is probably an apples to oranges comparison.

Maybe switching effort routes you to a different rack of gpu’s which don’t have the cache

The simplest version of this is to just tell two sessions to coordinate by taking turns appending to a markdown file.

related: https://powerfox.jazzzny.me/

Any chance you can throw lzop into that table just as a reference point?

Klipsch was famous for making speakers using acoustic horns, which was somewhat esoteric. When they finally made a speaker which used a conventional woofer, they named it “the heresy”.

A 3dfx card running in an O2 surely deserves a similar moniker :)

Any fans of retrocomputing will certainly agree. Much of the plain-HTTP internet that's left is there by them and for them.

Can you elaborate on “no way back”?

I would guess that most folks would consider a bunch of problem prompts with no reference solutions to be not so useful. How would you check your understanding? How would you know if you were writing go code which would be frowned upon by industry veterans?

I think it has more to do with the fact that when you offer zero salary for moderators, you have to take what you can get, and it ain't good. I don't really see a connection to the voting mechanic.

My bad. This Wikipedia article has a table of SNR values for 13 different kinds of tape: https://en.wikipedia.org/wiki/Compact_Cassette_tape_types_an...

Did you actually try any searches? Or is this just an excuse to broadcast your feelings about AI?

The author of the Ogg format claims a bit more pessimistic range of bit depth: https://www.youtube.com/watch?v=cIQ9IXSUzuM

Here are some measurements of type I, II and IV:

http://www.ant-audio.co.uk/Tape_Recording/Measurements/HD3_v...

http://www.ant-audio.co.uk/Tape_Recording/Measurements/HD3_v...

http://www.ant-audio.co.uk/Tape_Recording/Measurements/HD3_v...

Here are the specifications of a typical dbx unit: https://www.hifiengine.com/manual_library/dbx/222.shtml

Wow! And Type I are about $2.80 on amazon. That's quite the span!

> but it is really hard to make a good sounding cassette

It is unfortunate that cassettes are the lowest fidelity consumer medium (of modern times). But there is some room to optimize within that space. If you are curious:

The cassettes available today are Type I, Type II ("high bias") and Type IV ("metal"), each being higher fidelity than the last, but not all portable players supported these types of tape.

Dolby B/C noise reduction could improve the dynamic range of tapes a bit, but again not all portable players supported this.

The ultimate was "dbx", which dramatically improved noise reduction and dynamic range ("tape hiss" was essentially inaudible), but now you're in the territory of needing dedicated rack-mount equipment to record and play your tapes.

My dad was a bit of an audio buff, so I got to experience these things as a kid.

Edit: according to gemini AI:

* Type I had a dynamic range of about 50bB (roughly 8 bits)

* High quality tape with Dolby B, C and dbx yielded roughly 65, 75, and 85dB SNR (about 11, 12.5, and 14 bits)

So you could get pretty close to CD quality, but not quite.

Based on how universally horrible their video playback performance is (even in the iOS app), I can only assume incompetence.

This is a satisfying narrative but I feel like you are overestimating the technical competency and/or malice of these companies. The more likely explanation is that they have simply bitten off more complexity than they can chew.

Of the tech companies I've worked for, I can't even imagine how the web team would react if they were instructed to intentionally nerf their website.

Sorry, I meant I want to be able to do it faster. I don't want to be held up by an automatic progression.

Yes, I would also remove the automatic progression entirely. This should be driven by user input only.

This sort of pedantic need for correctness at the cost of clarity seems to also crop up as businesses become increasingly corporate and expand their offerings.

“The best tires” becomes “the best vehicular solutions”

Starting with an Atari 2600 is charming :)

> Orbital Mechanics Sim

Here's a little toy I made. Try to keep the comet on-screen by clicking to spawn a planet: https://ssl.pepas.com/gravity/gravity.html

Written in C / SDL 1.2: https://ssl.pepas.com/gravity/

A one-sentence description would be a great addition to these projects. "SOV|APP|VIDEO|SOURCE" doesn't really invite a click.

Took a minute to track that down (Oran is spelled Oram?) https://www.oreilly.com/library/view/beautiful-code/97805965...

Is it possible for an mp3 or mp4 to contain malware?

If it were such an easy problem to fix, don’t you think they would have done so rather than rewriting in Swift?

Nice project. Some of the workflows could be more keyboard friendly. I started an issue: https://github.com/kanbn/kan/issues/3

The real problem is when you have hundreds (or thousands) of fully discharge roboports, which will peg your power satisfaction to zero for quite some time during a black restart.

During that time, you are producing power, but none of the inserters work, none of the miners work, etc. and the distributed nature of the roboports means it isn’t straightforward to simply disconnect them.