Hacker News new | past | comments | ask | show | jobs | submit | steve_adams_86's comments login

In a sense, yes - but even after adjusting to glasses for 20+ years I still find it far more fatiguing than working without glasses.

I’ve tried all kinds of things but my eyes are bad at working through glasses.

I agree. I haven’t done a lot of fuzzing, but my understanding is that this is how fuzzing can be helpful. Am I wrong? Or is it more complicated than that?

It's a trade-off. Larger input files may slow the fuzzing process, and therefore explore less of the problem space. You usually want to test many different kinds of inputs, not just more of the same.

OTOH file formats often include sizes of fields, which a fuzzer will set to arbitrarily high values. This tests (some) handling of overly large inputs without files being actually that large.

For what it’s worth, I started noticing kids not caring about Facebook around 10 years ago. It was gradual, but evident for quite some time.

And Facebook bought Instagram about 10 years ago. They know where the wind blows.

Oh, you’re right. I recall a lot of people thinking Facebook was in a major decline trying to stay relevant. $1B for Instagram?! What a joke!

Well… it worked out for them alright.

The first time I saw this I was in awe of how far we’ve come, realizing the first 3d rendering I ever did took several seconds and was accomplished within DOS. Now we have things like this in the browser running in real time.

Since then I’ve had my mind blown several more times, but this demo has a special place in my mind. I was so excited at the prospect of WebGL.

Are you talking raytracing or real-time? I loved POVRay in the early 90s for raytracing. It blew my mind. As a little kid in the 80s, John Lasseter was my hero; I had a picture of Luxo Jr I used to eye regularly.

By '92 I had built a whole software 3D renderer in x86 and had the T-Rex from Jurassic Park stomping around in real-time on my 286.

That suddenly brought back a memory of the first 3d rendering code I did - it was written in Basic on an 8086 machine running DOS 2.1. Not only did it take several seconds to render, it was only an unshaded wireframe line drawing. To be fair, there were techniques available at the time to make it quite a bit faster that I didn’t know. But it still blows my mind a little bit every time I think about how far things have come since I was a kid.

Maybe it’s high risk to do mass production with untested components rather than revert to tried and tested components

You’re not kidding. I loved that application. I started my career with it!

Yes, I’ve fixed my animal vacuum in major ways 3 times and it was very easy to do. The vacuum has been running well for a very long time in vacuum years.

I agree. Inedible exciting and rewarding machines, worth the time investment, but it’s still very early. I’m sure I’ll be blown away by what’s possible in ten years or so. Today I’m still babying each print and the machine itself. Jams are the worst.

I believe tailwind ui’s license agreement specifically forbids using it in website generators

It was not really a website generator when in the VSCode extension. It was more of a copy and paste into your editor, with a easier way of viewing the components available (e.g., via dropdown in the editor).

They seem like they’ll be a steady climber. I’m not sure who has the inertia or a compelling enough product to knock them down any time soon.

Having said that, I don’t know anything about this and I only invest for fun/to keep an eye on these things.

WooCommerce is growing at a steady pace, with a YoY growth of 50%-100%

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