coldnose

I was also reminded of one: http://codetojoy.blogspot.com/2008/04/open-source-group-anno... ... didn't know this was an April 1st tradition though

ALGOL and Simula 67 are also great languages for this. In those languages, code can be simply copied from one program into another, thereby imbuing the second program with functionality from the first.

I'm personally fond of Malbolge with Rust-bindings, but that's not quite as popular as React yet.

And don't forget Cyberdog!

Here's the actual Nature letter, for anyone interested. https://www.nature.com/articles/nature25791

I'm glad globe-making is still being practiced. For my money, there's nothing quite as cool as an artisanal globe!

As of the time of writing, the headline was, "Australia could become first country to eradicate cervical cancer" not, "... eradicate HPV". I'm skeptical a form of cancer can ever really be "eradicated".

That's a pretty clickbaity title. It's really an article about increasing HPV vaccination and plummeting cervical cancer rates. But I'm skeptical that you can ever "eradicate" cancer as a form of disease, even a particular type of cancer.

This sounds like moonshot-level complexity. It invokes solar sails, laser communication at 550 AU, as well as "advanced propulsion, lightweight telescopes, membrane mirrors, inflatable/rigidizeable structures, and novel coronagraphic techniques." All that for a telescope you can't aim...

~6 hours after launch

I think the real problem is the battery was itself sealed with an airtight plastic wrapping. If consumers could just pull out the lithium plates, patch new electrolytic material over wherever they were shorting, then zip the battery back up, then they'd be fine.

And another thing! Back in my day, if you had a transistor go bad in a discrete logic unit, you could just pop out the card and solder on a new one. But kids these days with their fancy integrated circuits...

I'm uncomfortable around (and supremely irritated by) human babies, but it's pretty common to let people bring their awful babies into an office. Those babies don't work here, and they have no business being here, but I guess human parents feel they have some legitimate reason to bring them to work. In a fair world, I don't see how dogs are any different.

You may want to check out hypertalk, algol, prolog, and simula 67 too.

Only the WakeMate and all other non-UP devices are covered by patents. Evil, baby-raping patents.

The good people at Jawbone respect the integrity of babies' orifices, and would never dare to file a patent.

And today is the day /usr/bin/gcc changes from "deprecated" to "deleted". I'm glad something finally pushed me over that hump.

http://clang.llvm.org/

* If you're appending data to a string, and the variable-length increases by a byte, will you have to memmove() the entire existing string down 1 byte?

* Is every programmer responsible for detecting this condition?

* (This will make manual string manipulation very complicated and dangerous.)

* Suppose you're concatenating two strings, such that the sum of the lengths requires an additional byte. This could cause a buffer overflow. How would a strcat() function avoid causing a buffer overflow here?

* Does every string need a maximum-length counter too?

* Can you access a random element in the string without having to dereference and decode the length?

On the other hand, if you use a constant-sized length,

* What happens when you overflow the maximum length?

* Can you erroneously create a shorter string by appending text?

* How should string libraries handle this condition? By abort()ing? By returning a special error code? Does every string manipulation need to be wrapped in an if() to detect the special error? How should the programmer handle this condition?

In either case,

* Can you tokenize a string in-place?

* Can an attacker read a program's entire address space by finding an address that begins 0xffffffff and treating it as a string?

Am I mistaken, or is this a whole-cloth Lisa screenshot?

http://www.digibarn.com/collections/screenshots/xerox-star-8...

You broke my record 191 bytes!

http://coldnose-sloth.livejournal.com/1024.html

Kudos, Scientific American!

I performed a little experiment on my MacBook (Core 2 Duo, no hardware acceleration). With flash, rendering 720p h264 routinely eats 100% of the cycles on one of my cores. That same video eats 10-20% in QuickTime.

This isn't very scientific - ignoring cache and lots of other considerations - but memcpy()ing 30fps of 720p video from one buffer to another eats 5%. Decoding h264 in QT, and copying the buffer would take 15-25% total. 25% compares favorably to 100%.

I'm aware that the problem is the way Flash writes into Safari's window. But if Adobe thinks that h264 acceleration would dramatically improve its performance, they'd still have to copy frames into Safari somehow.

(Maybe they mean they want to write directly to the GPU's buffer...)

If Adobe wants access to h264 acceleration, use the QuickTime libraries.

In fact, why isn't Adobe using QTKit? Why are they rolling out their own appalling h264 implementation?