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

Why sqlite3 temp files were renamed 'etilqs_*' (2006)

github.com

Post reply on HN
Print view View original

141–146 of 146 posts

Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)

#141

Post by [deleted] »

pivo wrote: post #129
LeonB wrote: post #116

Earlier quoted context omitted.

Microsoft ends up, wrongly, in the firing line for a bunch of things, similar to the story you told and to the sqlite_ comment in TFA. Notice that on iOS (for example) if an app crashes it just disappears > poof! On Windows when an app crashes (or you kill a non responsive app), you then see a dialog with Microsoft Windows branding saying that it is logging that the app crashed. As nerds we understand why… but the re…

macOS is a better comparison to Windows than iOS is, since iOS is just for iPhones and not desktops. macOS will show you the stack trace of a crashed app in a dialog. This allows more technical people a chance look into the reason for the crash. Users have the option to share the stack trace with Apple.

[deleted]

Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)

#142

Post by remram »

ckolkey wrote: post #70
remram wrote: post #35

Earlier quoted context omitted.

I never knew that. How come they end up in Git repositories then? They shouldn't be visible to Git running on a native Mac filesystem?

They're just a file, so git can see it. Good habit would be to add it to the project's gitignore, or your global gitignore (or both)

So they are not a resource fork, then.

Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)

#143

Post by aldonius »

globular-toast wrote: post #89
ckolkey wrote: post #70

Earlier quoted context omitted.

They're just a file, so git can see it. Good habit would be to add it to the project's gitignore, or your global gitignore (or both)

It's a pet peeve of mine when people put stuff like this in a project's `.gitignore`. The proper place is either your global gitignore (probably appropriate for stupid stuff like this) or in your clone in `.git/info/exclude`. `.gitignore` is for stuff that all developers need to ignore, like compiler output, and should be kept to the bare minimum.

TIL there's a global gitignore, thanks!

Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)

#144

Post by ShadowBanThis01 »

CathalMullan wrote: post #109
ShadowBanThis01 wrote: post #8

Love it. Too bad there aren't enough Mac users to prompt a similar backlash against Macs littering every computer they visit on the network with .DS_Store and other turds.

You can avoid creating .DS_Store files on network and USB volumes like so. defaults write com.apple.desktopservices DSDontWriteNetworkStores -bool true defaults write com.apple.desktopservices DSDontWriteUSBStores -bool true

Good tip, thanks.

Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)

#145

Post by s1gsegv »

globular-toast wrote: post #89
ckolkey wrote: post #70

Earlier quoted context omitted.

They're just a file, so git can see it. Good habit would be to add it to the project's gitignore, or your global gitignore (or both)

It's a pet peeve of mine when people put stuff like this in a project's `.gitignore`. The proper place is either your global gitignore (probably appropriate for stupid stuff like this) or in your clone in `.git/info/exclude`. `.gitignore` is for stuff that all developers need to ignore, like compiler output, and should be kept to the bare minimum.

I can see an argument for this being semantically correct, but in practice I think it's preferable to have the repo checkout in the closest configuration to correct for new developers who will start contributing.

And, for what it's worth, all developers need to ignore .DS_Store files regardless if Finder creates it or it gets placed in when you unzip something created on a Mac, for instance.

In the best case, you spend extra time needlessly denying PRs and bothering people who already likely don't know git well enough to cleanly fix their commit. In the case of a repo large enough that you're not the only person approving PRs, I'd say it's almost inevitable that they eventually slip through.

Just my 2¢ from experience working in the industry.

Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)

#146

Post by ShadowBanThis01 »

chunkyguy wrote: post #133
ShadowBanThis01 wrote: post #8

Love it. Too bad there aren't enough Mac users to prompt a similar backlash against Macs littering every computer they visit on the network with .DS_Store and other turds.

.DS_Store has a origin story though not as entertaining https://www.arno.org/on-the-origins-of-ds-store

Apple's perennial lack of interest in truly fixing Finder shows in the fact that they've left this ridiculous bug in there for 20+ years, despite yet another "ground-up rewrite" that was supposed to (or did) happen at some point in the 2010s.

My other favorite Apple filesystem cock-up is the inclusion of a "Contents" directory in every bundle, which never has any siblings. I mean... what kind of ass thinks that a directory needs a subdirectory to hold the contents of itself?

The one thing Apple fixed in Finder that annoyed the living #$%! out of me for all previous years was that you couldn't sort files WITH FOLDERS AT THE TOP. Of course the fix was incomplete, broken in some places at first, including your Desktop directory. But that did get fixed surprisingly quickly.

Post reply on HN