Live data from Hacker News

Halfbakery

halfbakery.com

61–68 of 68 posts

Re: Halfbakery

#61
post #16

Earlier quoted context omitted.

There was a pretty successful Kickstarter a while back for a product ("Coffee Joulies") that was exactly that, but for your coffee mug. Little bean-shapes made of stainless steel, filled with material that changed phase at 140F.

There's also Ember [1] (also a kickstarter I think) that just made a mug with a heating element and controller to keep your beverage at a specific temperature. Using materials with specific phase change temperatures sounds like an innovative solution, but it's also grossly engineering a problem that can be solved better by $10 worth of components. [1] https://ember.com/products/ceramic-mug

I don't know, personally I would absolutely hate having to remember to keep my mug charged - although it's a damn cool product, just not for me.

I'm not sure I can agree about a phase-change solution being overengineered, however; while the materials would be more complex, the design itself should be far simpler than an electronic mug, and exactly the same as a vacuum sealed one.

Re: Halfbakery

#62
post #13

Earlier quoted context omitted.

I always wondered why TL;DR requests are being consistently down voted. Sometimes this is not a "too long don't CARE to read" but rather "I'm not sure I'm getting what this is about without investing a few hours into it so please kind Sirs and Ladies, can you sum up in a sentence?". Thanks for responding, responders.

tl;dr on this guy's post?

Funny. Take an upvote :)

Re: Halfbakery

#63
post #28
post #13

Earlier quoted context omitted.

I always wondered why TL;DR requests are being consistently down voted. Sometimes this is not a "too long don't CARE to read" but rather "I'm not sure I'm getting what this is about without investing a few hours into it so please kind Sirs and Ladies, can you sum up in a sentence?". Thanks for responding, responders.

For me, "TL;DR" inevitably implies a certain laziness. If a person really means, "I tried to understand this but I'm not getting it", maybe they could say that. Given that the top reply to this post is a copy and paste from the first paragraph of the about page, I could see why people suspect the querent did not work very hard before posting, and so values their own time more than that of other people here. That migh…

Fair enough. This is the old implicit vs explicit argument.

Re: Halfbakery

#64
post #47
post #37

Earlier quoted context omitted.

Wow! A blast from the past. I started my career in the mid-90s writing software with exactly this same stack.

It's funny—you just need a cgi-bin: 1. with 1777 permissions (sticky bit set); and 2. rsynced between a cluster of systems; and you've got a modern Function-as-a-Service backend.

I think you mean setuid bit. The sticky bit (on binaries) went away when we got VMM/swap.

Re: Halfbakery

#65
post #64
post #47

Earlier quoted context omitted.

It's funny—you just need a cgi-bin: 1. with 1777 permissions (sticky bit set); and 2. rsynced between a cluster of systems; and you've got a modern Function-as-a-Service backend.

I think you mean setuid bit. The sticky bit (on binaries) went away when we got VMM/swap.

No, I'm talking about the sticky bit for directories: see

https://en.wikipedia.org/wiki/Sticky_bit#Usage

and

https://en.wikipedia.org/wiki/Setuid#sticky_bit

Re: Halfbakery

#66
post #13
post #3

TL;DR anyone?

I always wondered why TL;DR requests are being consistently down voted. Sometimes this is not a "too long don't CARE to read" but rather "I'm not sure I'm getting what this is about without investing a few hours into it so please kind Sirs and Ladies, can you sum up in a sentence?". Thanks for responding, responders.

I've seen these kind of requests received better when they're phrased "Is anyone with more experience in the field able to summarise what's cool about this?"

Re: Halfbakery

#67
post #28
post #13

Earlier quoted context omitted.

I always wondered why TL;DR requests are being consistently down voted. Sometimes this is not a "too long don't CARE to read" but rather "I'm not sure I'm getting what this is about without investing a few hours into it so please kind Sirs and Ladies, can you sum up in a sentence?". Thanks for responding, responders.

For me, "TL;DR" inevitably implies a certain laziness. If a person really means, "I tried to understand this but I'm not getting it", maybe they could say that. Given that the top reply to this post is a copy and paste from the first paragraph of the about page, I could see why people suspect the querent did not work very hard before posting, and so values their own time more than that of other people here. That migh…

I skimmed the page up and down and couldn't find what it was all about.

And I redid that same thing before posting the TL;DR;

Re: Halfbakery

#68
post #28

Earlier quoted context omitted.

For me, "TL;DR" inevitably implies a certain laziness. If a person really means, "I tried to understand this but I'm not getting it", maybe they could say that. Given that the top reply to this post is a copy and paste from the first paragraph of the about page, I could see why people suspect the querent did not work very hard before posting, and so values their own time more than that of other people here. That migh…

I skimmed the page up and down and couldn't find what it was all about. And I redid that same thing before posting the TL;DR;

Then that would have been a good thing to say. If you say you didn't read something when you actually did, you can't blame people for taking you at your word.
Post reply on HN