The trackpad and trackpoint of my aging linux laptop stop working if the thing gets its lid shut. The touchscreen continues to work just fine, however. It turns out that while two stupid things can’t make a good thing, they can sometimes cancel each other out.

Everyday, big thing in schools.

@V0ldek @youngalfred I’d argue that they’re put in places they shouldn’t be, where tactile feedback is important. Like car interfaces.

To add to the others’ comments, they were much less impressive before we had capacitive touch screens. Older resistive screens needed a good deal of mechanical force to register a press (great for longevity!) and required frequent re-calibration. They just weren’t very satisfying to use compared to any modern smart phone or tablet.

YAML is great if you need to make simple configuration files

… which is why no one uses it for things like Kubernetes /s

Try YAML, the serialization format recommended by four out of five Nordic countries

yeah there are so many fucking crazy footguns in yaml

another I quite like:

❯ ipython -c 'import yaml; d = dict(); d["d"] = d; print(yaml.safe_dump(d))'
&id001
d: *id001

No, that’s not a base64-encoded private key nor a transcript of someone’s editing session in vim, that’s an XPath.

lol

JSON has its issues but at least it’s only the worst of some worlds. Want to make JSON unparsable anyway, for a laugh? Try YAML, the serialization format recommended by four out of five Nordic countries!

fucking

this take is so dangerously real I’m pretty sure uttering it at work will earn you a PIP and a fistfight in the parking lot with the lead data architect

you know, normal startup shit

It didn’t jump out of tech media containment, so it wasn’t a mainstream hype thing, more a techworker hype thing. It was the data serialization standard which would save the web! Second life otoh, did massively jump containment.

(see this for some others)

This article appears to contain a large number of buzzwords. (July 2011)

WP:LOL. WP:LMAO even

Sarvega, Inc., the leading provider of high-performance XML networking solutions, today announced the Sarvega XML Context™ Router, the first product to enable loosely coupled multi-point XML Web Services across wide area networks (WANs). The Sarvega XML Context Router is the first XML appliance to route XML content at wire speed based on deep content inspection, supporting publish-subscribe (pub-sub) models while simultaneously providing secure and reliable delivery guarantees.

it’s fucking delicious how thick the buzzwords are for an incredibly simple device:

• it parses XPath quickly (for 2004 (and honestly I never knew XPath and XQuery were a bottleneck… maybe this XML thing isn’t working out))
• it decides which web app gets what traffic, but only if the web app speaks XML, for some reason
• it implements an event queue, maybe?
• it’s probably a thin proprietary layer with a Cisco-esque management CLI built on appropriated open source software, all running on a BSD but in a shiny rackmount case
• the executive class at the time really had rediscovered cocaine, and that’s why we were all forced to put up with this bullshit
• this shit still exists but it does the same thing with a semi-proprietary YAML and too much JSON as this thing does with XML, and now it’s in the cloud, cause the executive class never undiscovered cocaine

./^ L E G S ^\.

Lot easier to do hype when you pretend the previous iterations didn’t exist. (and still do, and actually have more content).