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

For four years, I photographed, indexed and classified my entire house

katalog-barbaraiweins.com

Post reply on HN
Print view View original

51–60 of 75 posts

Re: For four years, I photographed, indexed and classified my entire house

#51

Post by b112 »

httpsterio wrote: post #45
b112 wrote: post #33

Earlier quoted context omitted.

node is used extensively on frontend. Massive bundles of js libraries. That is indeed part of the webpage. And it doesn't matter how typical or not, I'm referencing the case in point.

I think you're confusing js with node. node typically doesn't run on the frontend, but can be used when developing the front but it won't be running on the users browser.

No confusion here. Node.js is an entire ecosystem, and npm is a child of that mess. It is absolutely famous for the massive gobs of absolutely junk it pulls in to satisfy dependencies a frontend dev could manage with 4 lines of native js.

You may rail on about how npm != node, but everyone considers npm to be 'node package manager', no matter what the initialism actually stands for.

Re: For four years, I photographed, indexed and classified my entire house

#53

Post by kragen »

bboynton97 wrote: post #17
urronglol wrote: post #13

Earlier quoted context omitted.

[flagged]

her

This is a particularly amusing case of assuming male gender. If the first possession you see of a person is a dildo, wouldn't that incline you to double-check before you assumed they were male? Especially if it wasn't a buttplug.

Re: For four years, I photographed, indexed and classified my entire house

#54

Post by HPsquared »

tra3 wrote: post #27
HPsquared wrote: post #10

Earlier quoted context omitted.

Maybe a phone camera could be trained to recognize the objects and locations.

Yeah that would work too. I ended up creating a table in org mode for a limited subset of my gear — camping gear specifically. Using the phone is just too much friction. I print out a checklist and check items off. This is not the flying car future I was hoping for, but it works well enough.

Flying cars, when they come, will probably depend on bash scripts on some level.

Re: For four years, I photographed, indexed and classified my entire house

#55

Post by bavell »

b112 wrote: post #51
httpsterio wrote: post #45

Earlier quoted context omitted.

I think you're confusing js with node. node typically doesn't run on the frontend, but can be used when developing the front but it won't be running on the users browser.

No confusion here. Node.js is an entire ecosystem, and npm is a child of that mess. It is absolutely famous for the massive gobs of absolutely junk it pulls in to satisfy dependencies a frontend dev could manage with 4 lines of native js. You may rail on about how npm != node, but everyone considers npm to be 'node package manager', no matter what the initialism actually stands for.

Node.js is a server runtime, it does not run clientside at all. NPM can be used to download server OR client JS packages. A frontend bundler tool (e.g. webpack) can analyze a dependency graph of your client-side entrypoint and bundle all the NPM deps used, which will then be sent and executed on the client. No Node.js components or code are run client-side at any point (caveat - some packages can work server- and client-side).

HTH

Re: For four years, I photographed, indexed and classified my entire house

#56

Post by zamadatix »

I noticed there is a gray dress in twice with the "same" image (separate files but clearly generated from the same photo). I went to go do an automatic search to get some fun stats on things like that but the site is inaccessible for now :) commenting as a self reminder.

Re: For four years, I photographed, indexed and classified my entire house

#57

Post by davkan »

huehehue wrote: post #38
smokel wrote: post #8

I once made a large pencil drawing of my living room using only words. Each word depicted a "thing" at the position I found it. It taught me a lot about what things are. A chair is obviously a separate entity and easy to list, but what about the floor and the separate floorboards? I listed the wall, but I didn't list the paint on the wall. The bookcase took a lot of effort, because I found that each book in it was a…

This is pretty much Van Inwagen's argument in Material Beings -- recommended if you haven't read it! Copied from wiki: "Every composite material object is made up of elementary particles, and the only such composite objects are living organisms. A consequence of this view is that everyday objects such as tables, chairs, cars, buildings, and clouds do not exist. While there seem to be such things, this is only because…

Vsauce has a great video on that if he’s your style - https://youtu.be/fXW-QjBsruE?si=Ul6FLtlffINuKLrT

Re: For four years, I photographed, indexed and classified my entire house

#58

Post by netsharc »

Pikamander2 wrote: post #18

Some constructive feedback to the site owner: Instead of having the webpage spend several minutes slowly loading thousands of barely-compressed 500x500 JPG images, please consider this advice: 1. Convert the images to WEBP or AVIF or at least run them through something like TinyPNG to compress them better. 2. Save two versions of each images; a 75x75 version that gets used for the 75px thumbnails shown on the page, a…

I'm still dreaming of an image file format where the file begins with the, say, 75x75px image, and then continues with higher and higher resolutions, where the browser can decide when to stop downloading. Ideally they wouldn't be redundant either, e.g. the 2nd block would contain just the data to upscale the 1st block to twice the resolution.. so the "75x75" thumbnail in a hidpi display would just need blocks 1 and 2..

Re: For four years, I photographed, indexed and classified my entire house

#59

Post by BugsJustFindMe »

netsharc wrote: post #58
Pikamander2 wrote: post #18

Some constructive feedback to the site owner: Instead of having the webpage spend several minutes slowly loading thousands of barely-compressed 500x500 JPG images, please consider this advice: 1. Convert the images to WEBP or AVIF or at least run them through something like TinyPNG to compress them better. 2. Save two versions of each images; a 75x75 version that gets used for the 75px thumbnails shown on the page, a…

I'm still dreaming of an image file format where the file begins with the, say, 75x75px image, and then continues with higher and higher resolutions, where the browser can decide when to stop downloading. Ideally they wouldn't be redundant either, e.g. the 2nd block would contain just the data to upscale the 1st block to twice the resolution.. so the "75x75" thumbnail in a hidpi display would just need blocks 1 and 2…

Dream no longer. You just described a progressive JPEG.

Re: For four years, I photographed, indexed and classified my entire house

#60

Post by b112 »

bavell wrote: post #55
b112 wrote: post #51

Earlier quoted context omitted.

No confusion here. Node.js is an entire ecosystem, and npm is a child of that mess. It is absolutely famous for the massive gobs of absolutely junk it pulls in to satisfy dependencies a frontend dev could manage with 4 lines of native js. You may rail on about how npm != node, but everyone considers npm to be 'node package manager', no matter what the initialism actually stands for.

Node.js is a server runtime, it does not run clientside at all. NPM can be used to download server OR client JS packages. A frontend bundler tool (e.g. webpack) can analyze a dependency graph of your client-side entrypoint and bundle all the NPM deps used, which will then be sent and executed on the client. No Node.js components or code are run client-side at any point (caveat - some packages can work server- and cli…

Node.js is an ecosystem. The server is a component.
Post reply on HN