degenerate

9.9.9.9 with 1.1.1.1 as secondary

exactly - the rejection of short range EVs was when they cost as much as a normal car

if the short range EV is now much cheaper, people will adapt to the restriction because it's an affordable option

The majority of people only skim content before making a post.

The truncated paragraphs are very odd - definitely a mistake.

Replace "Them" with "Coworker" and the point of linking to the site is instantly understood (a LMGTFY-style shaming with a dash of humor to soften the blow)

With "Them" I wasn't sure if you meant the AI companies, some dude I didn't recognize in the avatar, scammers, coworkers, etc...

Misery Map adds two crucial pieces of context: the delays between airports, and rain/snow on the map, which often is the reason for delays. It's nice to see it all together.

From a project management perspective, the 5 examples don't help me understand how/why I might switch from Playwright/Cypress to this framework. It seems like Bombadil is a much lower-level test framework focusing on DOM properties but in the "Why Bombadil?" introduction you say "maintaining suites of Playwright or Cypress tests takes a lot of work" ... I'd like if there was an example showing how this is true, perhaps a 1:1 example of Playwright vs Bombadil for testing something such as notifications clearing when I click clear. Basically, beefing up examples with real-world ones that Playwright users might have written is a good way to foster adoption.

You would likely be interested in the Starcraft BWAPI: https://www.starcraftai.com

You can watch the matche videos from training runs: https://www.youtube.com/@Sscaitournament/videos

I don't think BWAPI has ever integrated modern AI models, but I haven't followed its progress in several years.

Many teams work exclusively in GitHub (ticketing, boards, workflows, dev builds). People also have entire production build systems on GitHub. There's a lot more than git repo hosting.

YouTube design changed almost every year until 2020! Wild.

"empathy" "right" "help" "hope" "same"

None of those words appear in the article. I can deduce that the author of this article would never return a wallet. If they are this perplexed at the good deeds of others, and need to turn to science for a reason, they are as dense as a brick.

Reasons:

- because kind strangers have empathy

- because kind strangers want to do what is right, and help others

- because kind strangers would hope the same thing is done when they lose their own wallet

You would likely enjoy Myst: https://www.gog.com/en/game/myst_masterpiece_edition

Related HN thread: https://news.ycombinator.com/item?id=18058991

Are you testing performance with pgbench or something more custom/advanced?

I briefly searched and couldn't find it either - here is the IMDB for others to reference: https://www.imdb.com/title/tt0605181/

Some teammates agreed to do this, but it's not known what files will be edited ahead of time, so a large job often has formatting edits anyway.

Lines with actual code changes aren't a problem for me, it's the automated IDE indent/spacing/bracketing that really drives me up a wall and fatigues the hell out of me.

But this might only be a problem with those of us working on legacy codebases. The kind of PRs I see in OSS projects I could review 1000 lines at a time - it's so clean!

Better than commenting "paywall blocked" is to provide an archive link: https://archive.is/vH7vF

I imagine some OSS authors don't consider someone visiting the GitHub readme before visiting their website. I can't fathom thinking like that, but it must have never crossed their mind.

Here's the screenshots: https://stellarium.org/screenshots.html

The PDF is worse, so there is no simple answer to this: https://arxiv.org/pdf/2312.12907v1.pdf

At least the HTML version pairs each author with their affiliations, instead of the PDF which has all the names on page 1, and all the affiliations on page 2. That's completely unreadable.

Thanks everyone that replied, I thought I was doing something wrong!

Any advice/ideas/articles/references on using kustomize efficiently?

I love the idea of using a tool bundled with kubectl for zero dependencies, but their examples and tutorials are horrible. I can't figure out how to use it correctly to have 1 copy of YAML that would deploy to 5 different environments. It seems I would need multiple copies of kustomization.yaml in multiple folders, if I have multiple namespaces/pods/etc...

When a user search includes a non-indexed repository, GitHub needs to include a warning message along with the search results, something similar to what you just mentioned:

"One or more repositories of this search is not yet indexed, please try your search later for accurate results."

Likewise for the 2nd case.

navigate the UI disaster to read about the UI disaster...

I don't consider this story a UI disaster. Generating different 4-digit codes across terminals for the same object, and recycling those codes regularly... that's a data handling disaster.

Or for more options use Rufus: https://rufus.ie/en/

If you want to disable Google location history (AND/OR) limit data collection to 3 months, you can do that here:

https://myactivity.google.com/activitycontrols?settings=loca...

I don't mind stale repos when it comes to emulation, because nothing changes (except the host/build ecosystems) so there is less to keep updated. In the case of the NES, the last game released was in 1995.

I hear you, and generally you are correct, but migrating from LastPass to BitWarden (and setting up the extension to work exactly the way I liked LastPass to work) truly did take 30 minutes. I wasn't expecting 100% feature parity but it's there. What took the longest was discovering CTRL+SHIFT+L is the shortcut to auto-populate username/password in forms. Pressing it again will cycle to the next account in the vault.

FYI you can use "glass" selection to build walls/cliffs at the start, so all your sand and stone isn't piling into a hill at the bottom.

I both love this level of optimization (for the novelty) and hate it (knowing all the work involved is being done with JS, on my machine, costing more CPU time than the bandwidth saved)

> In Spring 2018, Epic executives and managers discussed adding a confirm purchase button to prevent accidental purchases. Though employees were concerned that “it is a bit of a dark UX pattern to not have confirmation on ‘destructive’ actions,” Epic feared that adding a confirmation button would add “friction,” “result in a decent number of people second guessing their purchase,” and reduce the number of “impulse purchases.”

> Epic has never allowed users to cancel or undo charges for Battle Passes or Llamas and did not begin allowing users to cancel Cosmetics charges until June 2019. Even then, Epic uses design tricks, sometimes referred to as “dark patterns,” to deter consumers from cancelling or requesting refunds for unauthorized V-Bucks charges.

> On July 20, 2018, an Epic Community Coordinator asked if there were any plans to add a confirmation step for in-game purchases, noting: “This is actually a huge complaints on our side and could remove most of the ‘excuses’ about accidental purchase: ‘I wanted to press Replay, my PS4 was in sleep mode’, etc. This is something I wanted to push forward but didn’t have time to build a real case around, has this already been discussed in the past?”

> In addition, Epic deliberately requires consumers to find and navigate a difficult and lengthy path to request a refund through the Fortnite app. To start, Epic hid the link to submit a refund request under the “Settings” tab on the Fortnite app menu, far removed from the purchase screen, even though requesting a refund is not a game or device setting. The Epic user experience (“UX”) designer who helped design the refund request path reported that he put the link there in an “attempt to obfuscate the existence of the feature” and that “not a single player found this option in the most recent round of UX testing.” When the designer asked whether he should make the feature easier to find, he was told by a superior, “it is perfect where it is at.”

Many more examples in this complaint doc: https://www.ftc.gov/system/files/ftc_gov/pdf/1923203EpicGame...

Nearly all my personal photos were encrypted by the [email protected] ("HELP") variant of Phobos. I've been holding onto the encrypted copies for a while in hopes that some people were working on a crack, and I'm excited to read this update.

Sidecar question: when automating your backups, what's a good way to make sure your rolling backups aren't simply backing up malware-encrypted files? I found out too late that all my backups were encrypted. I only had 1 week retention to save space. Is longer retention and manual checks the only sane strategy? Or has some backup software built in sanity detection for crypto attacks by now?