Shog9

Yes indeed! Glad to see you over on Codidact; I suspect small, bespoke q&a will be the future of the form, at least after Facebook implodes.

I was writing like a robot before robots could write, dammit!

This sounds plausible - I grew up in the Midwestern US, and thus "vaguely passive-aggressive" is pretty much my native language. The hardest part of the job for me was remembering to communicate in an overtly aggressive manner when necessary, developing a habit of drawing a sharp line between "this is a debate" and "this is how it is."

Sometimes I put that line in the wrong place.

That said... I can't take credit for any major change in direction (or lack thereof) at SO. To the extent that SO succeeded, it did so because it collectively followed through on its mission while that was still something folks valued; to the extent that it has declined, it is because that mission is no longer valued. Plenty of other spaces with very different people, policies, general vibes... Have followed the same trajectory, both before SO and especially over the past few years.

With the benefits of hindsight, probably the only thing SO could have done that would have made a significant difference would have been to turn their Chat service into a hosted product in the manner of Discord - if that had happened in, say, 2012 there's a chance the Q&A portion of SO would have long ago become auxillary, and better able to weather being weaned from Google's feeding.

But even that is hardly assured. History is littered with the stories of ideas that were almost at the right place and time, but not quite. SO's Q&A was the best at what it set out to do for a very long time; surviving to the end of a market may have been the best it could have done.

Nail guns are great. For nails that fit into them and spaces they fit into. But if you can't hit a nail with a hammer, you're limited to the sort of tasks that can be accomplished with the nail guns and gun-nails you have with you.

This is the way with many labor-saving devices.

There was definitely a bit of Pournelle's Iron Law of Bureaucracy [0] at work. I worked there during a lot of the drama you allude to, and... It sucked, for everyone. But also...

For most of SO's history, the vast majority of visitors (and this questions, answers) came in via Google. Not "search engines"; Google. This was pretty much baked in right at the start, and it effectively served as the site's primary user interface for years. And it worked. It worked pretty well! Until it didn't.

At some point, Google started surfacing fewer "tried and true" Q&A examples and more unanswered, poorly-answered or moderated examples. This broke the fundamental assumption that sat behind SO's moderation - that curating a smaller set of posts was preferable to encouraging more, and newer. Suddenly, Google wasn't a very good UI for SO anymore.

...and SO didn't really have a fallback. Heck, for a while during this period they actually stopped showing questions on their homepage unless you were already logged in; the core assumption remained that there was a never-ending spring of new people feeding the thing. LLMs weren't the start of the problem, they were the end - the final wake-up call.

I don't know that a site like SO can exist without the old Google, the old Internet; it is a product of all that, in the same way that mass-market TV shows were a product of 20th-century broadcast technology, or trade paperbacks of a particular intersection of printing tech and reading habits.

[0]: https://www.jerrypournelle.com/reports/jerryp/iron.html

It's a solution. There are better solutions, and far worse solutions (anyone who has worked to get a deposit back on a college rental has probably developed a few of their own), and most of them are all still fine because drywall isn't (shouldn't be) structural.

Crucially, even if you are completely unwilling to take a stab at a fix yourself, hiring a local handyman to patch a hole via some good enough technique should still be far cheaper in most places than buying a nice new TV.

But nothing is gonna ever beat buying a 2nd-hand framed picture or plaque or movie poster or grabbing a flyer from the junkmail on your porch and tacking it over the hole... And if you're determined to fix holes with a TV, you can probably find one used for about as cheap / free as any of the other choices. Which is what makes this such a stupid example - the cost of TVs, like framed images or furniture, spans from $0 to "as much as you're willing to pay". Hiring someone can also be arbitrarily expensive, but can by definition never be 0. So the comparison is rhetorical trickery and demonstrates nothing.

...other than, apparently, Andreessen's dissatisfaction with paying tradespeople.

Android works great - lets you select the # and then gives you a context menu with the option to call (or copy, or search).

...unless someone made the phone # a tel: protocol link, in which case it has the selection behavior of any other link. Which is mostly fine, since "copy" is a context menu option for tel: links... unless some jerk put a tel: URL in that isn't the same number as what is shown in the text of the link, in which case it's time for some crazy hoop-jumping to either copy OR call the number.

FWIW, you can generally figure out what's allowed fairly quickly by checking the content model for a given element[1]. Some browsers might be more or less restrictive, but for normal usage this'll be more than enough to avoid unexpected behavior.

[1]: https://html.spec.whatwg.org/#the-button-element:concept-ele...

It does not. What it does do is submit the form, so if you trigger some fast change to the page or async behavior from the click event, you may never see it because the submission happens and the page reloads (or a different page loads if form action is set to a different URL). If you're relying on event bubbling, the click handler may run after the form is submitted, which is even less likely to do what you intend.

If you aren't expecting this (and don't know how to discover it e.g. by examining browser dev tools, server logs, etc.) then you'll assume the button is broken and... probably try something else.

Even if you do discover it, you may try something that won't quite have the same reliability - at one point it was common to see folks putting preventDefault() or return false in their click handlers to squelch the (correct) behavior, rather than changing the type of button.

Your control for this test should be (and maybe was, you don't say) running the furnace circulation fan without running the burner. CO2 levels are unlikely to be uniform throughout a building, and thus mixing will change (raise, lower) the CO2 levels depending on where you're measuring.

Better variable frequency drives for both fans and compressor is a big part of it (see other comments about being less prone to short-cycling).

This isn't exactly new or unique to heat pumps (and some older heat pumps lack both), but as the technology has gotten cheaper and more reliable, coupled with the drive for better efficiency, it has become commonplace.

Oh sure. 20 years ago I used VMs and that was also a duct tape solution. I'd have hoped for a proper solution by now, but a lighter hack works too

Reproducibility? No.

Not having to regularly rebuild the whole dev environment because I need to work on one particular Python app once a quarter and its build chain reliably breaks other stuff? Priceless.

Digg rather famously did have both followers and "influencers", though not in quite the same sense that those creatures are known today. Arguably its failure to limit the impact of both are what led to the forms we see today.

There's been an awful lot written about all of this over the years, much of it overly simplistic and some of it just straight-up wrong; we all want to believe that we're just plain smarter than the ancients, even when those ancients were us.

If you're interested in (ahem) digging into this, start by searching for things like "Digg voting network".

IOW, a few sharks eat a tremendous number of minnows.

Something I try to remember whenever the urge to "hustle" comes back: taking payoff I got from years of startup work, subtracting taxes and spread across those years... Still put me at just above market rate for those years. But instead of that market rate for 40 hour weeks, it was that rate for 80, 100, 120 hour weeks. I could've been working two bog-standard jobs for normal companies, worked fewer hours, and come out ahead.

Everyone has a reason for gambling. It's rarely ever a good reason. But man, it's easy to lose yourself in rationalizations when you're in its thrall...

Text selection is such a great example precisely because it is incredibly useful to have in many unexpected situations (and a great many more that should be expected), but UI designers as a rule do not think about these situations!

It is so bad that one of the most impressive operating system features to be added in recent years is the ability to select and copy arbitrary text from app UIs, using either accessibility APIs or (more recently) straight-up OCR (because of course accessibility is another thing UI designers forget).

It's not like adding text selection in native apps is even hard; it's just not on the radar, and never has been. The number of old-school apps that added some form of "open log file" to either support instructions or as an actual function in the UI instead of making error messages selectable / copyable is depressing; I've seen programmers spend more time mocking end users for not knowing how to take proper screenshots than it would have taken to implement selectable UIs.

...and by historical accident, this problem is now solved in the vast majority of new applications. A small mercy!

TBF, Turbo Vision was also a better toolkit than most of what was available for '90s GUI systems. Or a lot of '00 GUI systems.

...hell, native apps are still more likely to be crap than not. Good UIs are hard and programmers are lazy; the big advantage of web apps remains the difficulty of an app completely crashing the browser due to sheer developer apathy.

My observation, after using LG TVs at countless hotels (occasionally internet-connected), AirBnBs (usually internet connected) and at home (never internet-connected) is that even in quite old TVs the UI is blazing fast until you connect it to the 'Net. At that point... It spends a painful amount of time waiting on requests with no visible feedback and the whole UI starts to chug, with some apps becoming almost unusable until the thing has been on for long enough for all the background stuff to finish.

Granted... If they aren't 'Net-connected, most "apps" aren't of much use. But, fast access to settings and inputs is sorta nice too.

No.

We don't have a cure for autism.

We don't have a prevention for autism.

We don't have a clear cause for autism beyond recognizing that genetics play a role.

We don't even have a clear picture of the scope; one reason rates appear to be increasing is simply that we've gotten better at recognizing symptoms in previously ignored populations. But... We are probably still ignoring symptoms in some significant populations.

It is completely understandable that, as we learn more and the scope of the problem becomes more apparent, folks are alarmed and clamoring for politicians to Do Something.

...it is less apparent that there is anything productive to be done, beyond continued efforts to better understand the situation.

We (as a society) and Kennedy in particular (within his own family), have ample experience with the harms wrought by efforts to Do Something when no effective solution exists.

Funny you mention fraud... I worked for a company for quite a while that was absolutely dedicated to WFH for engineering - but swore up and down that sales just couldn't work without "bullpen" office setups.

Come to find out at least one entire office was engaged in widespread misreporting and fabrication. Turns out fraud is pretty tempting when you can easily avoid any paper trail.

Which is why companies that tell you what you'll pay up-front (Amazon, eBay) have made life hard for "traditional" sellers. Your sheep are tired of being fleeced.

Which is possibly the bigger deal. Every time I shop at a specialty provider I end up frustrated by their lack of clarity around shipping costs - many will actually force you to go through the entire order process before giving you a shipping estimate, complete with collecting contact information.

Makes it very tedious to price-shop.

I will actually go out of my way to search for some suppliers on Amazon, eBay, Walmart, even Tictok before dealing with buying directly, just so I can rule them out if they're gonna pull a "$10 + $60 s&h" trick.

And... Again, this isn't new; pretty sure Ronco was doing this on TV before the Web.

Even before "online" was an option, folks were fleeing high prices in high rent districts for cheaper goods on the outskirts. Heck, I remember folks banding together to get in on bulk buys decades ago, when that was neither convenient nor quick. High rent will kill retail in an area no matter what; if online also gets you faster and easier, then who would choose anything else?

Bigger, fewer, more chill cells, fairly robust trenchcoat.

(IIRC, these packs are 16 100ah LiFePO4 cells in a steel case w/ built-in fuse, breaker, and BMS that monitors individual cell health and pack temperature, w/ automatic cut-off if any of that goes out of spec. The weakness is primarily the MOSFETs on the BMS potentially failing shorted. Fortunately, they've added some sort of additional fire suppression beyond just "steel case" in recent-ish versions of these packs)

If you want strictness, use a linter or a pretty-printer that follows your preferred style. Adopting an opinionated parser means you can't lint or pretty-print input from those with different opinions (I do not like underscores for emphasis), and thus somewhat goes against the goals of TFA here:

> Markdown files are essentially plaintext with some extra syntax for common elements like sections, bullet points, and links. The format deliberately avoids precise control over display details like font selection. Following the rule of least power, I consider this limitation a feature.

One of my biggest ongoing frustrations has been MDX - a sort of markdown-and-JSX mixture whose spec is now in its third release and which has made very little effort to maintain compatibility with either CommonMark or itself. It is fairly strict and fairly elegant, and moving to a new version requires rewriting all previously-written documents to eliminate no-longer-supported syntax and re-training writers. Both of those things are miserable tasks; it has absolutely killed any tolerance I might have had for a stricter parser.

There are plenty of businesses that can and do compete with online, or do both (using their distributed inventory to reduce the time it takes to ship online orders).

But saddling a retail company with tons of debt makes much, much harder; profits that should be going to restock instead go toward financing the debt.

We don't really need to read tea leaves here to figure out the cause of death.

It's been a while since I've used it, but IIRC this is actually my favorite feature: it encourages the use of stylesheets vs ad-hoc formatting. As annoying as it is in the moment, when it comes time to integrate multiple documents into a consistent whole (or apply entirely new styling), having a stylesheet vs. miles of ad-hoc inline styles makes it fairly painless.

Sadly... The rich text editor I mostly use these days (Google Docs) goes in the complete opposite direction; trying to apply a new stylesheet is mostly a waste of time. Which is why for any non-trivial document, I mostly rely on Markdown -> HTML + CSS.

The battery life is probably not an issue in practice; the author estimates 5 hours per charge - assuming a very conservative 2000-cycle life for the pack, that's 10,000 hours of work, which is quite respectable.

Yes, a private owner might keep a tractor for decades, but probably not using it for hours every single day and definitely not without some pretty significant repairs; the cost of a new 200ah battery pack is nothing compared to a diesel engine rebuild.

I... Tend to suspect other parts on these things will be unacceptably worn long before the battery craps out.

As Evan points out in TFA, this has happened before.

I'll add that it has happened more than a few times.

Past response was to shut down inappropriate behavior in the now (folks rambling on about the person in comments under some programming question, etc.) and let the temporary interest die out on its own.

This time... The response seems to be inviting the Streisand Effect.

boldmovecotton.gif

Sadly, ridiculously expensive for fairly limited cargo utility, no doubt due to their ATV heritage ($30k will get you what is essentially a posh ATV that is simultaneously an extremely janky vehicle by kei truck standards.)