robinson7d

None of the old Natsume Harvest Moon games allowed same-sex marriage or romance. The more recent Story of Seasons games do: the Friends of Mineral Town remake (2019/2020) does, and pioneers of olive town does.

Both are more recent than the BioWare examples, and of course more recent than Stardew Valley, which is more in line with the Harvest Moon genre.

I don’t have stats to speak to the validity of their claims, but I think that we parsed their comment in different ways:

- number of “tornadoes due to Niña/Niño“ (my reading)

- “number of tornadoes” (total for the year), with Niña/Niño being why it’s that way (sounds like your reading, since those numbers are the overall)

While editing one GitHub comment I may be writing another. If you must, implement it as a link, but all else equal I’d prefer keeping the other state alive when canceling one comment-edit. Doing both is cool too, but people don’t typically want to implement a feature twice.

It’s not just because it’s associated with summer, quite the opposite: many of us just feel that sunset 30 minutes after work in the winter will be less depressing than the sun setting while we’re in the office. And then even more so during the days where it moves from 5:30 to 6:30, that’s enough to actually get out and do an activity.

I get that there are good reasons for morning light too, I’m just saying that I don’t think it’s just an association with summer.

I think usually they rave about Novamin, which, at least in Canada, isn’t in the Pronamel line IIRC but in other Sensodyne branded toothpastes.

_EDIT: “repair and protect”_

Do you have numbers for that? The graph in the article says 21.31% by their analysis

Loopholes are by definition legally allowed.

Do the example functions (isObject, isNumber, differenceDeep, randomUUID, debounce), along with the name (“SuperUtilsPlus”), and sentences saying “utility library” and “JavaScript” really not give enough context to get an idea of what this library is for?

And so if Lodash is what they’re trying to replace, is that not enough info to infer what Lodash might be?

The pharma ad comparison seems more than a little hyperbolic to me.

I’m not a huge fan of his, and maybe you’re only talking about more recent films, but Terminator and Titanic have more than “minimal cultural heft” as far as Hollywood movies go.

Didn’t downvote (can’t even downvote, wouldn’t anyway), but if I were to guess it’s that the article talks about it fairly extensively.

It depends on what one considers useful.

E.g. they were also first to support the `:has()` selector/pseudo-class, which I think can be useful for avoiding JS in some cases.

But it’s not core functionality, it’s just a convenience.

Making it more convenient for everybody equally is an admirable goal, but should a trivial change that makes life a bit easier for many people be scrapped just because making it easier for everyone else is difficult? Specifically here where the experience doesn’t significantly regress for anyone.

What a throwback. Somebody asking whether another used ATI graphics. Another person asking whether they should support PPC Macs.

(The following comment agrees with you, it is not intended as an argument against what you’re saying):

Technically being able to contain the content and actually being able to boot the game from the disc (after transferring to the console hard drive) are two separate things. Even without counting Day 1/Day 0 patches. Some games refuse to run without downloading additional content that isn’t on the disc, others require talking to a server even if you’ve just downloaded the latest updates, others. A patch to fix bugs and add content is one thing, refusing to play entirely is another.

Semantic nit: STC is a type checker, SWC already compiles TypeScript well. TSC does both (unless flagged to do one or the other) so it depends on what needs replacing.

Why it matters: in GP’s case it sounds like compiling is the problem, so migrating to using SWC as the compiler but keeping TSC as the checker (noEmit flag) in a lint step may ease that pain a bit. Though it might be nicer to migrate both in parallel.

I’ve started again. I stopped for a while because they stopped feeling novel, but when scrolling through older photos from 5+ years ago, the photos of people that had Live enabled bring me a lot more emotions.

Worst of all: the first seniors get to refactor the professor’s code.

Thanks! Donkey Kong Country felt truly next gen at the time, it makes sense that Nintendo would offer reward deals afterwards.

You’re absolutely correct, but I’d love to hear more about why Rare is an exception. Is it just because they mostly made games for SNES before N64? If so my recollection was that SquareSoft and Enix (separate at the time, IIRC) were similar until PlayStation enticed them, and in our 20/20 hindsight (FFVII and all) we wouldn’t bundle those Nintendo companies like we might consider Rare.

Again though, you aren’t wrong! Rare covers many of the non-Nintendo greats on N64 (GoldenEye! Banjo Kazooie! Donkey Kong 64! Conker, if you were in a fairly narrow range of maturity!), but they did some Sega before N64 and a lot of Xbox afterward, so I just expect there’s probably some interesting details left to expand here :)

If there’s not much to it other than that they were a shining star with a ton of Nintendo investment, all good.

Self-reply: I see that the website links to tldraw under Job, which might be a good example to weigh the shipped size vs the same thing minified, except that it's already minified.

As a tangent: this is a neat tool! :)

Do you have any strong example websites? The website you linked is very simple, I can’t see why most pages on it would benefit from using JS at all except for analytics or similar. It’s a good website, I don’t mean to make it sound otherwise, but it’s not the type that should consider minifying code in the first place.

Minification’s more useful for web applications, along the lines of: MS Office (e.g. Excel), Zappier, UberEats, Photoshop, the reporting side of analytics (e.g. Google Analytics) where you get all the interactive graphs and maps.

I think many of the disagreements on here would dissolve if they were only considering blogs and similarly small websites.

All of the comments on this post that include numbers show that using both is better than just one or the other, mostly when the code’s sufficiently large.

I agree with the recommendation of one good compression algorithm vs combining multiple in general, but is it possible that you hadn’t considered that this is a case where we have a very good lossless compression (gzip) that can get benefits when combined with a lossy compression (minification)? As wonderful as Huffman codings can be, it’s hard to compete with outright throwing “unnecessary” (to many users, maybe not OP and some of us) data away.

You’re right for the large majority of cases, but there are exceptions. These days some use canvas or WebGL, in the past some have used Flash or Java Applets/Swing.

A popular app that some web developers here may use day-to-day recently is Figma, which uses WebGL for rendering.

Did your experience involve the (recommended) build step? It uses, at least last I checked, a purgeCSS step to remove unused rules and decrease the css size.

In fact, I’ve seen an extension several times: senior developers performing code review, and requesting that unnecessary parens be removed. Not excessive parentheses, a single pair in a line or statement.

There’s a short thread by WalterBright in here that explains why: https://news.ycombinator.com/item?id=38199237

The back and forth on that thread seems to result in advocating for what we’ve got: compiler (TypeScript in your example) not caring, but linter caring.

The reason not to in the transpiler is it can be very helpful during testing to block or force some paths.

Fidgeting can make a big difference, at least it’s appeared that way in a couple sources I’ve seen referenced here in the past - failing to have those handy I found this: https://pubmed.ncbi.nlm.nih.gov/15681386/

No idea how accurate it is, but an extra 350 calories burned is a pretty big improvement over _not_ having those burned.

I doubt fidgeting alone is sufficient to keep most people skinny. There’s a lot that impacts our weight. But if somebody’s automatically burning calories because they have a hard time stopping fidgeting, that might ease the load a bit so they could eat a bit more or walk a little less than would be the case without it.

EDIT: it feels worth mentioning that fidgeting can be an all day activity for some people, 8+ hours. Walking 10k steps takes maybe 1.5 hours, more or less depending on the persons speed. It wouldn’t be as much of a workout replacement as a whole lifestyle change.

Ah, no in that case you did misread it. They’re saying that “private information shared with a governmental organisation should stay private” is a popular opinion.

The “unpopular” and “in what world” act like a double-negative.

It’s possible that they’re simply agreeing with it.

That’s for sure why it was discontinued. I’m sad it’s gone, but I do understand I’m a minority in that feeling.

I was just offering it as a counter point (from as recent as last year) to the onscreen keyboards necessitating huge phones that the comment I replied to was suggesting. Plus an option that is still modern enough to use. Using the mini keyboard isn’t much worse than the pro. It’s feasible, these minis type well, I don’t think it’s the reason for bigger, thinner phones with cameras popping out. I’d blame content more.