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.
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.
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.
(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.
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.
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.
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.