Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cursed Knowledge

immich.app

Post reply on HN
Print view View original

121–130 of 165 posts

Re: Cursed Knowledge

#121

Post by motorest »

whilenot-dev wrote: post #99
motorest wrote: post #84

Earlier quoted context omitted.

Older browsers don't support foreach, so it's not like a polyfill is unheard of https://caniuse.com/?search=foreach

Are you serious here? It isn't a polyfill, it's supposed to work on plain objects which isn't part of the spec at all. Besides that, Array.prototype.forEach is only unsupported in Android Browser 4.3 (from July 2013) and IE8 (from May 2008). Seems like a weird reasoning to add it to packages in 2025.

> Are you serious here?

I am.

If you check the definition of polyfill, you'll eventually arrive at something like the following:

> A polyfill is a piece of code (usually JavaScript on the Web) used to provide modern functionality on older browsers that do not natively support it.

https://developer.mozilla.org/en-US/docs/Glossary/Polyfill

I think we would agree that foreach fits the definition, happy path, and whole purpose of a polyfill.

if you read up on forEach, you will notice that Array.prototype.forEach requires objects to be callable.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

Re: Cursed Knowledge

#122

Post by matheusmoreira »

TheBicPen wrote: post #81
burnt-resistor wrote: post #27

- Windows' NTFS Alternate Data Streams (ADS) allows hiding an unlimited number of files in already existing files - macOS data forks, xattrs, and Spotlight (md) indexing every single removable volume by default adds tons of hidden files and junk to files on said removable volumes. Solution: mdutil -X /Volumes/path/to/vol - Everything with opt-out telemetry: go, yarn, meilisearch, homebrew, vcpkg, dotnet, Windows, VS…

Opt-out telemetry is the only useful kind of telemetry

The usefulness is completely irrelevant. We do not want any data exfiltration to take place under any circumstances and for any purpose whatsoever.

We couldn't care less how much money it costs them.

Re: Cursed Knowledge

#123

Post by Havoc »

motorest wrote: post #98
Havoc wrote: post #82

Earlier quoted context omitted.

Forgive my ignorance of js matters but how does adding packages improve backward compatibility at all?

> Forgive my ignorance of js matters but how does adding packages improve backward compatibility at all? The scheme is based on providing polyfills for deprecated browsers or JavaScript runtimes. Here is the recipe. - check what feature is introduced by new releases of a browser/JavaScript runtime, - put together a polyfill that implements said feature, - search for projects that use the newly introduced feature, - p…

Thanks for explaining!

Re: Cursed Knowledge

#124

Post by daveguy »

motorest wrote: post #117
pushedx wrote: post #113

Earlier quoted context omitted.

There's no reason that an LLM couldn't (or isn't) being trained on commit messages. No difference between a git index and any other binary data (like video).

> There's no reason that an LLM couldn't (or isn't) being trained on commit messages. You are arguing that it could. Hypotheticals. But getting back to reality, today no coding assistant supports building system prompts from commit history. This means it doesn't. This is a statement of fact, not an hypothetical. If you post context in commit messages, it is not used. If you dump a markdown file in the repo, it is use…

You seem to be confusing the construction of system prompts with "training". Prompts do not change a model's weights or train them in any way. Yes they influence output, but only in the same way different questions to LLMs (user prompts) influence output. Just because it's not available in current user interfaces to use commit messages as a prompt does not mean the model wasn't trained with them. It would be a huge failure for training from version controlled source code to not include the commit messages as part of the context. As that is a natural human language description of what a particular set of changes encompasses (given quality commits, but quality is a different issue).

Re: Cursed Knowledge

#125

Post by jrasm91 »

thorum wrote: post #24

> npm scripts make a http call to the npm registry each time they run, which means they are a terrible way to execute a health check. Is this true? I couldn’t find another source discussing it. That would be insane behavior for a package manager.

https://docs.npmjs.com/cli/v6/using-npm/config#update-notifi...

https://github.com/npm/cli/blob/5d82d0b4a4bd1424031fb68b4df7...

Re: Cursed Knowledge

#126

Post by jrasm91 »

motorest wrote: post #64
maxbond wrote: post #61

> Fetch requests in Cloudflare Workers use http by default, even if you explicitly specify https, which can often cause redirect loops. This is whack as hell but doesn't seem to be the default? This issue was caused by the "Flexible" mode, but the docs say "Automatic" is the default? (Maybe it was the default at the time?) > Automatic SSL/TLS (default) https://developers.cloudflare.com/ssl/origin-configuration/s...

> This is whack as hell but doesn't seem to be the default? I don't think so. If you read about what Flexible SSL means, you are getting exactly what you are asking for. https://developers.cloudflare.com/ssl/origin-configuration/s... Here is a direct quote of the recommendation on how this feature was designed to be used: > Choose this option when you cannot set up an SSL certificate on your origin or your origin doe…

It was the default at the time so we had no idea this behavior would be applied to a fetch request in a worker. That combined with no other indication that it was happening made it a real PITA to debug.

Re: Cursed Knowledge

#127

Post by accrual »

Fwirt wrote: post #51
accrual wrote: post #19

Earlier quoted context omitted.

I like CCYY-MM-DD because it's also a valid file name on most systems, and using "CCYY" (century + year) instead of "YYYY" feels fancy.

Except this could get confusing because the year 1976 (for example) is actually in the 20th century.

That is a good point. The "ordinal" century doesn't exactly line up with the digits in a "YYYY" format, thus "CCYY" creates some ambiguity depending on how one defines "century".

I conclude my fanciness of using "CCYY" is not useful. :)

Re: Cursed Knowledge

#128

Post by whilenot-dev »

motorest wrote: post #121
whilenot-dev wrote: post #99

Earlier quoted context omitted.

Are you serious here? It isn't a polyfill, it's supposed to work on plain objects which isn't part of the spec at all. Besides that, Array.prototype.forEach is only unsupported in Android Browser 4.3 (from July 2013) and IE8 (from May 2008). Seems like a weird reasoning to add it to packages in 2025.

> Are you serious here? I am. If you check the definition of polyfill, you'll eventually arrive at something like the following: > A polyfill is a piece of code (usually JavaScript on the Web) used to provide modern functionality on older browsers that do not natively support it. https://developer.mozilla.org/en-US/docs/Glossary/Polyfill I think we would agree that foreach fits the definition, happy path, and whole p…

> I think we would agree that foreach fits the definition, happy path, and whole purpose of a polyfill

I think you got that all wrong and strongly misinterpret "modern functionality" as some generic library here...

Runtimes are developed against a certain spec, in this case ECMAScript, and "modern functionality" is meant as addition to iterations of such a spec. As it happens, iterations of specifications and runtimes are seldomly provided by the same entity, so both are moving forward with newly supported features, or more "modern functionality", individually.

This behavior provokes some difficult challenges for developers. For once, they would like to work against the latest spec with its newest features, but, due to the natural dynamic of various entities doing things in different ways, these developers would also need to support older/other runtimes where such a feature is not (yet) implemented natively. Now, to bridge these supported-feature-gaps developers came up with an interesting concept: Instead of waiting and relying on the runtime to support such a new feature, it might be possible to provide an implementation as workaround, hence the "polyfill".

So, if something A isn't currently in the spec, nor B even proposed or in discussion to be in the spec, nor C provided by any current runtime (and relied upon by developers), then I'd conclude that such a functionality is not considered to be a polyfill, as it isn't to be seen as workaround for the supported-feature-gaps due to the difference in runtimes.

Re: Cursed Knowledge

#129

Post by burnt-resistor »

nothrabannosir wrote: post #118
burnt-resistor wrote: post #88

Earlier quoted context omitted.

Yep. Create a case-sensitive APFS or HFS+ volume for system or data, and it guarantees problems.

I’ve done this with my main drive for the last ten or so years and run into not a single problem. I recommend it.

Then you don't use Time Machine, Migration Assistant, cmake, or a host of other development and systems tools that don't work correctly on case-sense APFS volumes.

Sorry, but this is terrible advice unsuitable for all audiences. It might seem to work for now but it's walking in a minefield of nonstandard configuration that could bite anytime in the future.

https://forums.macrumors.com/threads/does-anyone-else-use-a-...

https://forums.macrumors.com/threads/heads-up-currently-impo...

https://apple.stackexchange.com/questions/474537/time-machin...

https://gitlab.kitware.com/cmake/cmake/-/issues/26333

Re: Cursed Knowledge

#130

Post by kirici »

burnt-resistor wrote: post #85
kirici wrote: post #49

Earlier quoted context omitted.

>opt-out telemetry: go By default, telemetry data is kept only on the local computer, but users may opt in to uploading an approved subset of telemetry data to https://telemetry.go.dev . To opt in to uploading telemetry data to the Go team, run: go telemetry on To completely disable telemetry, including local collection, run: go telemetry off https://go.dev/doc/telemetry

Yep, but you're techsplaining to someone who already know this. But still, it's not opt-in. It's always on by default and litters stuff without asking. All that does is create a file but that doesn't remove the traces of all the tracking it leaves behind without asking. This fixes it in a oneliner: # mac, bsd, linux, and wsl only (d="${XDG_CONFIG_HOME:-$HOME/.config}/go/telemetry";rm -rf "$d";mkdir -p "$d"&&echo off>…

Like television and telephone, the "tele" (remote) part is the crucial and defining one. Without it, it's just metry.
Post reply on HN