robert_tweed

This actually happened to me, but fortunately I never actually used the domain. I registered tweed.dev intending to use robert.tweed.dev as a personal blog. It wasn't classed as a "premium" domain and the first year was £5 or something IIRC, which was half price compared to the normal renewal fee.

The next year they decided it was premium after all, and wanted to charge £492,000 for renewal. I still have a screenshot of that, although needless to say I don't own the domain anymore.

Alone in the Dark was notable at the time for using Gouraud shading [1]. You can see the effect on some of the polygons here:

https://www.youtube.com/watch?v=zsGaVrMr9N8&t=480s

The reason I remember this is that it inspired me to spend ages implementing Gouraud shading in my own graphics library (written in assembly language), only to discover that flat polygons look better most of the time.

[1] https://en.wikipedia.org/wiki/Gouraud_shading

I'd be fine with shorts if they didn't disable the normal player controls.

It feels like an example of Betteridge's law of headlines, despite not being a question.

Ah, I only skimmed the article and missed that. The BBC RSS feed was the main example I referred back to while I was learning XSLT around 2010-ish.

AFAIK it's the only major implementation of this technique. Most other big sites that provided an RSS feed didn't bother, and most of those RSS feeds are dead now. The BBC one has hardly changed since those days and it still works really well as a dual-delivery system.

If anyone is looking for a real-world example, the BBC does it:

http://feeds.bbci.co.uk/news/rss.xml

How is it in terms of heat & condensation build-up? Is there a certain amount of time after which it starts getting uncomfortable?

Also, is passthrough good enough for things like typing, so you don't get an uncanny valley sense of the keys being just slightly off visually compared to your proprioception & touch?

I'm definitely taking my UV torch to the supermarket next time. However, most good olive oils come in dark glass bottles, so I don't think it will be possible to check those. Might be interesting to look for variation among the cheaper EV ones.

The article mentions differences between brands, but IDK if there's a specific correlation with quality other than that fake olive oils certainly won't turn red/pink.

I don't have a green laser, but I just tried shining a 365nm UV torch on the various bottles of oil in my kitchen.

My good EV olive oil in a glass bottle goes a sort of pinkish colour. With the natural colour of the oil & the way the glass reflects/refracts light, it makes it look like copper.

I don't get the same effect with cheapo refined olive oil in a plastic bottle. I get a bit of fluorescence - the normal violet colour and much less than say a white piece of paper - but all or most of that is just from the container.

Why not just a scanner app for your phone? They work pretty well. I have a flatbed scanner that I keep stored away most of the time, until I need to scan a bunch of stuff quickly. If I need to scan the odd receipt, I use Tiny Scanner.

I always (and only) use named colours for debugging. For example border: 1px solid red; around some element that isn't rendering as expected.

This makes it hard to accidentally forget about a rules that just just put in temporarily. Real colours will always match some design, which will have a carefully-chosen hexcode.

I'm not sure if there's a list, but a notable example of this is Day of the Tentacle, the sequel to Maniac Mansion.

In the game there is a computer, which if you interact with it, allows you to play the entire original Maniac Mansion.

A glass eye filled with tritium would probably give enough light to read with, continuously, with a half-life of 10 years.

It might get a bit annoying when you want to go to sleep though.

https://en.wikipedia.org/wiki/Tritium_radioluminescence

Yes, same here. It's not just "I'm hungry". It's more "I cannot think about anything other than food".

I'm not sure it has anything to do with burning fat stores though, because I don't get the same feeling after say, a 3-day water fast. At that point I'm definitely hungry, but don't have the same insatiable food craving.

In fact, when I was experimenting with extended fasting, the only reason I stopped at 3 days is because I was lifting lighter weights every day and hit a point where my strength was physically depleted. I could only do about 3 reps instead of finding 15+ easy. Hunger wasn't really a problem after the first day of getting used to it.

More anecdata, but I find it depends on the type of exercise. An hour of cardio equals several hours of appetite suppression. An hour of heavy weight training equals several hours of unstoppable hunger. What I eat in that state (high carb, low carb, whey protein, etc) doesn't seem to affect satiety much.

I believe this could be the main reason why its almost impossible to eat at a caloric defecit (with surplus protein) and train anabolically at the same time. Some people are able to do that, it's just very rare.

I think the conclusion here is back-to-front.

Code that never needs to be touched is fine. Although the odds are that such code is either completely trivial or subtly wrong (or both).

Code that is touched every day is likely to be fine as well. It's should get smoothed out naturally, like a pebble in a stream. If not, you probably already have lots of alarm bells telling you it's a problem without the need for any further analysis. It's not the code quality that matters here so much as the test coverage.

The changes you really need to worry about are to code nobody has touched for 3 years and whoever wrote it no longer works for the company. Especially if that code was written with the mindset of "nobody will ever care about this code".

A better metric for deciding where you should focus the most effort on code quality is not frequency of modification, it is frequency of appearance in the runtime call-graph. Each call probably also need a multiplier for how deep in the call-stack it was, since that's where unintended consequences of a small change are likely to have the biggest blast radius.

It's also possible that copyright does not apply to this kind of image, because it lacks the creative element required for copyright to apply.

The Toshiba HX-10 MSX came with 2 plugs and a screwdriver. This was considered important enough to include a picture on the box, never mind the manual.

https://www.msx.org/wiki/Toshiba_HX-10

It even claims to parse ls output correctly (see caveat): https://kellyjonbrazil.github.io/jc/docs/parsers/ls

For a few seconds I thought it was Lite-On, best known for their cheapo CD/DVD drives. Seems to be completely unconnected though.

This is a separate problem Amazon needs to sort out. Far too many duplicate products with a different ASIN. They could easily fix that with manual inventory checking, but they don't. The same process would fix the bait-and-switch problem.

Adversarial reviews. The problem isn't just fake positive reviews. The other problem is fake negative reviews left by competitors, which is already a problem on Amazon. Most 1-star reviews are either stupid & irrelevant (it arrived a day late, ONE STAR! and so forth), or fake.

I've seen some categories of products with lots of obviously fake reviews claiming safety issues. These were on every single product I could find, so clearly all the manufacturers were targeting each other.

The 2-4 star range has historically been the most reliable, but fake review factories got wise to that a few years ago and will now often intentionally leave a minor gripe in their fake positive reviews to make them seem more authentic.

A better solution is to publish the % return rates for products and forget about reviews. You can even normalise that into a 5-star rating by product category, e.g., "Here are the top 5 products similar to this one, with average return rate of 1%. The product you are viewing has a return rate of 15%".

With low-friction return reason categories you could even classify high return rates for things like "doesn't look like the photos", "poor quality", "smaller than expected", etc. Unfortunately Amazon's return reasons are variable-friction, so their data on this will be biased, although it might be consistently biased across product groups.

I do like the word cloud idea - but pulled from optional free-text return reasons instead of reviews.

This doesn't solve the "it broke after 2 years" problem, but neither does the current review system.

There is a valid reason, which is custom configuration for each application. How you want a tablet to act in Blender is likely not the same as you would want in Photoshop. A lot of mice do the same thing.

Once the user has agreed to that valid use-case, there's not a lot the OS can do to stop the data being logged permanently.

Some of these could exist if we just start using them. The best one I've found:

  tootbox
  toot·box
  a place where something, especially music, plays
  "do you need a tootbox in your bedroom?"

Yes, I am sure. Look at point 2 in the instructions and follow the link.

The whole process for putting an Oculus device in developer mode is incredibly fiddly and annoying. You need a verified developer account. You an app running on a phone, which in turn requires an online login. You can't just do it from a desktop PC and you certainly can't flip a toggle on the device itself.

Ideally, as a follow-up to this, they will release something that allows putting the device into developer mode without requiring any of that. As of now, that does not exist.

I'm going to give this a try later. One small fly in the ointment is that if like me you do not have and do not want to ever have a Facebook account, it will not be possible to load this onto the device after 2022.

This is because loading the ADB requires putting the device in developer mode, which in turn requires an internet connection and an active login to your Oculus developer account. Oculus developer accounts have been deprecated and will stop working in 2023, after which time a Facebook account is required.

You've answered my question and explained why I couldn't find that text on TFA or even their entire domain.

FWIW, with the context I would say that I'd find that example quite hard to parse without the IDs (or at least a comment), unless you changed it to have each graph next its own code.

For anyone reading this confusing subthread in the future, here's a permanlink to your post that the parent was replying to:

https://news.ycombinator.com/item?id=28715868

I upvoted because I agree with the general sentiment, but I can't find the specific example you're talking about. Have you got a link for context?

I think it's a bad analogy.

A clock losing a random number of seconds per day is actually correct more often than a stopped one.

Surely if there's one thing the HN bubble is capable of, it's rallying a critical mass of contributors around a project like this.