jdub

Literally in the first sentence of the new volume type intro: "… at the same price as the existing io1 volumes".

Funny bit of Ubuntu history: It was almost "Canonical Linux" by the company "Ubuntu", but it didn't take much for the founding employees to convince Mark that it should be the other way around. I don't think any of us had heard of it before, and were absolutely blown away by how similar it was to the way we thought about FLOSS.

That'd be the Debian alternatives system in action.

$ update-alternatives --list editor

Too quick to create a new language?! Rust was started in 2006 and announced in 2010. Its improvements are based on research done before and after C/C++ existed.

If you're the only person smart enough to solve the $64B problem so everyone can start writing safe and backwards compatible code in C/C++, please, go right ahead.

Are we only looking at little ones that have their own user interface? If not, Snowplow is the prime mover of web and event tracking.

https://github.com/snowplow/snowplow

It's a twist ending to the first five minutes of the film.

If you think we could get this right in C (48 years old) and C++ (35 years old), don't you think we would have done it by now? :-)

Good news: `-Z build-std` is available in nightly and various bleeding edge projects have switched to it

https://github.com/rust-lang/wg-cargo-std-aware

1. You could possibly get closer, but you'd lose a lot. Most of Rust's "nice security features" are wildly incompatible with existing C/C++ code and inherent language features.

2. No. If C/C++ could be made safe* Rust would not exist.

* everyone agrees on this point, including the richest and largest software companies on the planet

A major QEMU contributor suggesting that future work on a specific subset of components (that are prone to vulnerabilities that are difficult to avoid in C) be done in Rust is not naïve. It's the beginning of a community discussion.

The song was released almost a year before UTF-8 was first presented at USENIX, so I think it is reasonable for the lyrics to be expressed using the commonly available technology available of the time.

The units are not spoken, but for clarity they should be notated in the lyrics.

Honeycomb https://honeycomb.io/ is laser focused on this stuff. They built their own datastore (similar to Druid but schemaless) so they could create the experience they were aiming for.

They talk a lot about collaborative troubleshooting, and the user interface reflects that. It's actually fun (?!) to drill down from heatmaps to individual events with Honeycomb's little comparison charts lighting the way.

The semantic difference would be important in a song like Baby Got Back by Sir Mix-a-lot, which includes both speech quotes and imperial measurements.

Spain has states with relatively similar state/federal power to the USA. The EU has nation states with more or less power depending where you look. Australia has states, Canada has provinces...

One aspect of US taxation and funding that seems wildly out of step: Primarily local funding of schools. Way to build inequality into the system!

You'll generally find the rest of the (first) world did 1.0 too. But they invest in public infrastructure, so also did 2.0 and 3.0.

The USA is a very strange mix of hyper-first-world and second/third-world, and a lot of it has to do with how taxes are raised and spent.

Shift + Command + 5… click "Options" in the bar down the bottom of the screen.

(Also, try hitting space a couple of times in that mode.)

I'd trust Matthias to know when GTK is ready, and it's a signal to the community that it's definitely time for testing and porting. But he can still make micro bumps. :-)

That's less about the version number, more about the time-based release train. If you're not ready to go, you can't get on.

GTK/GNOME started doing time-based releases every six months 18 years ago. Hasn't missed a beat.

Ha ha. waves

GTK is a 22 year old project.

Both GTK and GNOME have used .99-style release candidate micro numbers, and odd/even minor numbers to represent devel/stable (as Linux once did) for a VERY long time. ~18 years ago, GTK/GNOME decided that major number bumps meant breaking changes.

.99 means "we're absolutely serious about this release candidate" because you know you're going to eat it if you ship a three-digit minor. How embarrassment.

Kids, a bit of community tradition won't hurt you. :-)

Naw, that's just his byline. The Microsoft engineeer is Madhavan T. Venkataraman.

There's necessary and well-encapsulated `unsafe` code in the standard library. It's a tool.

But you can read his response to Rust in the linked thread.

One of Tim's previous posts was about breaking up AWS.

NON-system libraries? Lots. e.g. reading through a directory of dynamically loadable plugins

System libraries (depending how Apple defines that)? Unusual.

I retooled a step functions CloudFormation template to create and attach an EFS filesystem to four functions. Took about 25 lines of YAML.

We can't design everything for people who couldn't figure out how to operate a toothbrush.

Open System Information → USB on a Mac with a T2 chip and check out all the stuff attached to it.

Start with the name. That puts it in opposition immediately. They present a lot of that opposition to projects and people, rarely stated kindly.

They could express a positive enthusiasm for simplicity, but that's not the way they go about it.