FranOntanaya

I guess trash bags can/could be produced with biodegradation in mind, while shopping bags may prioritize being able to stay in stock for years and to hold dyes, etc. It's not necessarily a 1:1 replacement.

I'm sure energy and agricultural water are easier to manage environmentally than plastic pollution.

You are comparing a framework to a language though. Escaping in PHP is usually handled by the templating component, you don't go around writing htmlentities() everywhere.

TED Talks for example has a community of volunteer subtitlers that get credit for their work. A lot of them move on from there to professional captioning.

I still use a fanless NC10 to run an IRC bot after a few years lent to my parents for writing emails. Removed the dead battery, replaced the disk with a small SSD and set it to power saving so it never goes above 60ºC while being completely silent. Best bang for the buck I've had with hardware.

I'd personally just avoid using film spec terms for TV and computers and just stick to the old FullHD, Ultra Wide, UltraHD terms. Film tech is always a bit of an island doing their own thing for encoding, captions, hardware, etc.

Attaching terms like "2K" to a computer screen invokes legacy compatibility horror feelings for me.

One issue that was talked about some years ago and has sort of fallen off the news cycle was overcapacity for maritime transport. That could have contributed to it, or maybe it's another symptom of the underlying cause.

https://unctad.org/en/pages/newsdetails.aspx?OriginalVersion...

You seem to be outraged about culture itself.

The enjoyable cars and the context where they are driven e.g. tracks, events, may not change that much.

The boring utilitarian combustion engines the large majority of humanity has ever experienced probably won't be missed, though. Boring cars were still boring a decade ago.

That works better when the land isn't 100 miles wide with ocean on both sides. Miami City has a better ring than Miami Keys.

They aren't supposed to be anymore. Dodd-Frank requires banks to have a living will for unwinding in case of crisis. Wells Fargo's was approved last year.

I assume it'd never be triggered from above due to "a series of scandals" as long as operations remained viable.

#1) The need for a large ellipse of flat plains with a minimal amount of hazardous rocks/slopes. Landing accuracy is constrained by our knowledge of the Martian atmosphere. Odd features tend to be on the opposite end of the ground hazard spectrum.

#2) Planetary protection. Mars his a Category V target: it has potentially habitable niches, it has an atmosphere able to carry biological contamination anywhere, and we want to return samples from it to Earth. Chances of contamination are much lower when we stay far away from water ice and active gullies. Modern landers and rovers are much more delicate and intricate than the original Vikings and we can't just bake off all the contamination.

#3) Communications. Equatorial plains have a better view of the relay satellites.

#4) Close up, most interesting features on Mars are still a rocky desert. The Phoenix Lander landed on top of permafrost, which was unintended as it was thought to be just another rocky desert.

#5) Odd features are often complex geologically and characterizing the area near the rover may not say much about Mars nor provide useful context for future, more detailed missions.

#6) Perhaps, a tiny bit of backlash from Viking's ambiguous chemical experiments. It's easier to get conclusive science and write solid papers from old, stable parts of Mars.

> originally REST was all about self-reporting and discoverability

I don't think this is accurate. Discoverability was the bonus score piece, the most fundamental parts were statelessness and caching.

A lot of grievances in early web development came from state breaking when people browsed back, reloaded pages, did other things between requests, or got hit by pretty aggressive caching.

Nothing intrinsically REST-blocking in the original zero JavaScript, form-based apps, they were just that messy and expected people to follow a linear path on a single browser window.

People where solving these problems for the first time (for the web), and they actually needed to be told to care for state.

As someone that grew through the 00's — I commend the ability to package the feeling of the era into a style, and some of the things back then (like your first time opening a Basic interpreter) were neat... but, boy, the cliparts and Encarta era is not something I'd be nostalgic of.

We had a glimpse of all the information that was out there, but still couldn't access more than a little bit of it. It was frustrating more than anything else. Personally I had gladly archived it in the back of my mind till it started to surge back as vaporwave.

Our Moon has "sort of" dust storms of ionized dust. They are driven by electric charge from ionizing solar wind rather than an actual atmosphere.

JPL has a recording of the 13th press conference here:

https://www.youtube.com/watch?v=fIKxdRFx2Wo

Good old unsanitized HTML. Brings memories of the first bulletin boards.

I reckon with Amazon IPs being thrown indiscriminately in the bucket with Telegram they aren't keen to seeing a repeat of the same situation.

WASM for SQL

There aren't a whole lot of cases where Planetary Society aren't doing the better job. Two that come to mind for me are Marc Rayman's Dawn journal https://www.jpl.nasa.gov/blog/author/marc-rayman/ and HiRISE's outreach https://hirise.lpl.arizona.edu/

I almost added autocorrection to a translation pipeline once. Curated a subset of unambiguous safe cases to reduce the manual workload. I parked it away because I didn't see a way to reliably convey this was just lowering the number of manual corrections needed.

A bad part about user-end autocorrection is that the end user is looking only at the case they have in front, not the overall average — if they have a case where it worked very well, they'll start overly trusting it and failing at producing good results. If they have a case where it wasn't useful, they'll be annoyed by it and feel they are doing more than they should. In all cases someone is going to be unhappy.

If I can't expect all ends to understand the value I'd mostly just look for pipelines where a-c could be an internal process and there was no need for the data provider and end user to be aware that it's happening. But then, ascertaining this is a problem on its own.

Thunderbird already supports feeds.

Same here. Even soldering and replacing switches couldn't keep it going. The switches had a thin metal contact that has to bend to close the circuit and it'd just break after little use.

I just wish irssi supported other scripting languages. I don't particularly dislike Perl and it's not like it needs to do very complex stuff, but it'd be fun to tinker with it with my language of choice.

In the whole area. Where I spent time people still use coal heating and you had garbage pick up once a week (and you had to tip), so even tho burning garbage in the stove is illegal you surely knew when a neighbor was doing it. Part of my coming back home culture shock was not seeing cars covered in sooth.

Guess you never got lost in the purple level!

I would also bet nobody publishes research on games AI didn't perform well at.

Oh man, rich kids had a D: drive. The rest of us had to make do with A: and C:

It was a lot harder to be discouraged as a young adult. Some year you'd feel you were outgrowing your happy QBasic hacking and pick up a massively thick Turbo Pascal book and feel a bit humbled, but that was once in a blue moon. Now you are always one search away from some harrowing design pattern depths or cryptic industry standard source code.

That'd be survivor bias. My average jeans a decade or two ago would start tearing off at the buttonhole or taint seam after a year or so.