Hacker Newsnew | past | comments | ask | show | jobs | submit | chubs's commentslogin

I go to church. Everyone has 3 kids. Thanks for bringing it up!

I remember reading that in certain areas/communities in the USA, it's pretty close to 50:50.

What if computers simply rendered 300dpi PNG files and sent that to the printer?

That's actually what a lot of Brother printers do with their default or generic drivers. Except... it's JPEG, not PNG, so you get artifacting. Drives me crazy.

Installing the specific driver like it's 1999 works well, but most people don't bother these days. And thus the world is a bit more crap.


I recently ported an old brickout clone I made to Sokol (a C header-based game library). The whole executable is 500kb (macos), surely could be smaller with eg symbols stripped, and it has a whole 3d engine (not that i'm using much more than one custom shader to blit the screen, but it is using 3d engine infrastructure nonetheless). I was impressed that in this day and age such efficiency is still fashionable in some corners. The whole game is about 2mb zipped. Are shameless plugs allowed? If you're curious have a peek! github.com/chrishulbert/brickwarrior


To mitigate supply chain attacks like this, I've taken to specifying exact versions in my Rust cargo.toml, and when importing new crates, select the previous-to-latest version. Is this a reasonable mitigation? It bugs me that Swift deprecates the concept of specifying exact versions, it actively pushes you towards semver which leaves the door open to this.


> select the previous-to-latest version

For supply chain attacks that simply bide their time, or for dependencies which involve interacting with other subsystems, it's possible you miss a critical security update by doing this. Of course, the maintainers of the crates should yank known bad releases, but that's putting trust in a third-party that may have already been compromised.


Cargo will still pick the latest for transitive dependencies that aren't explicitly specified in your Cargo.toml. This is what Cargo.lock is for.


Oh good point, I didn't think of transitive dependencies. A lot of languages i've worked with unfortunately have a 'do not check in the lockfile' culture, and a common 'blow away the lockfile when the package manager gets stuck' workflow, so that does concern me. Perhaps Cargo is better than average though, and the lockfile never needs nuking, providing this safety. This sounds like a good reason to check in the lockfile! Thanks for the response.


"All I could think about was how bored I would eventually get" I used to wonder this. I read the religious answer to this relies on the concept of infinitude: what if an infinite god can invent an infinite number of exciting new... things to do?


God as Mr. Roarke?


The traditional concept of an 'embodied' resurrection (as opposed to ghosts playing harps) makes me lean towards: yes (eg the gut is part of the body). Who knows though, it's a fun question!


yeah it is :) Like, do we eat in heaven? If not, then all our little passengers must also be immortal in their resurrected form. But part of the biome is the dead bodies of those critters, and those dead bodies also affect our mood (chemistry doing its thing). So how does this work? Does heaven automatically maintain the correct chemistry in our guts to maintain our emotional and hormonal stability with needing the actual biome? Or does it maintain the biome at the correct chemistry without needing the actual ecosystem? And other parts - do the bugs that live on our hair follicles come with us? Does hair even grow in heaven?

I have questions...


John's vision of heaven in the book of Revelation includes both the wedding feast of the Lamb and the trees of life that will bear 12 different fruits in season. Jesus also ate fish a few times after his resurrection to demonstrate the physicality of his resurrected body. So there is the concept of eating in the resurrected paradise of the new heavens and the new earth.


I believe you resolve it by the concept of spirit/body dualism, where your body/soul degenerates but the spirit is still fine.


Holy moly, that guy in the reddit post needs to see a dermatologist asap and figure out why their skin is emitting acid.



It is within the range of physiology. Nobody has pH-neutral skin, and aluminium is reactive.


I don't understand: Who's lending the $2B in situations like this? Wouldn't they be worried that the above situation (company gutted, then going down the drain) is going to play out and they won't get their $2B back? Or is that the root problem with this whole YC submission: banks are being hit by defaults because of this exact problem?


It's from the rapid exploitation of an asset. If I have a cow, I can milk the cow or kill the cow. If a cow costs $1, maybe I can get $5 worth of milk over the cow's lifespan, or I can kill the cow immediately and get $2 of meat. The man with $100 who buys all the cows in town and kills all of them doubles his money in a short timespan, but now there's a shortage of both meat and milk next season.


That is the exact problem. The people who put up the $2B thought they were safe - after all they were putting up money to buy a successful profitable business.

Problem is they didn’t really understand the business and trusted the PE guys to keep running it well…


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: