plaidphantom

Only if the student even cares to proofread for something like that in the middle of a big, probably poorly formatted, block of text pasted into a small-ish text box.

Here's another for the pile. https://youtu.be/GyV_UG60dD4?si=yTB_dICMqnLjqVEi

They explicitly address this in the article:

"Initially, we experimented by building this as an app on Pebble, since it has a mic and I’m always wearing one. But, I realized quickly that this was suboptimal - it required me to use my other hand to press the button to start recording (lift-to-wake gestures and wake-words are too unreliable). This was tough to use while bicycling or carrying stuff."

This interacts directly with the Pebble App, so I would be shocked if the watches never get an equivalent app.

Alternate opinion: these URLs read as "spammy" to me and I would be less likely to click on them.

It would be apropos to at least have an "about" dialog somewhere, or maybe one of those "quick tour" popups.

Winning with a 49.8% popular vote is hardly a "mandate".

And Nativescript.

How about SQL joins? "foo JOIN bar ON foo.id = bar.fooid"

I don't think they're saying that such a range function is itself a ternary, but using that as a lead-in to discussing the Frink ("1 to 100 step 15") and Elixir ("1..10//2") syntaxes.

Dangit, I had finally gotten good at The Game.

For those who don't know, DuckDuckGo provides an app tracking blocker for Android that implements itself as an on-device pseudo-VPN and blocks known tracking services. No containerization/sandboxing, but it's a start.

https://spreadprivacy.com/introducing-app-tracking-protectio...

A harmful attribute on its own can be advantageous when combined with others. Think of it as finding a new "local maxima" in the sum total of evolutionary traits. Being (probably randomly) near-blind may have led to being slow and careful, which was the temperament needed to survive climbing trees, which got them away from ground-based predators and found them a lot of leaves ground sloths couldn't reach.

Evolution is basically a random-walk algorithm to find combinations that work.

I've definitely seen high school seniors get a big head!

I'd guess much of this difference is also due to the fats in the cheese & meats solidifying at cold temperatures, and thus less readily coating taste receptors.

For me, .NET Core has been largely solving this problem over time. In classic .NET Framework it was nearly impossible to make something without Visual Studio's arcane templates. The `dotnet` command simplifies a lot of that, and projects have a lot less boilerplate.