EbolaFred

EbolaFred t1_jdm4xne wrote

Alexandria Bay in upstate NY is great for a long weekend. Lots of cool/peaceful things to do for a couple. Just about five hours. That time of year should be good as it's right before tourist season, when it gets packed.

1

EbolaFred t1_j9yvqkf wrote

One take is that the general population is still seeing this stuff as a gimmick/fad. We've seen this time again since the dawn of technology - some things start "nerdy" and gain widespread adoption (cars, computers, cell phones, the internet, EVs) and others are always a decade or more away (cold fusion, nanobots, quantum computing, nanotubes, flying cars). AI has always fallen into the latter group, until now.

It doesn't help that most people's experience with modern technology is glitchy as fuck. Smart devices suddenly stop working, Alexa picks up randomly, wifi router needs to be rebooted all the time, cloud synching isn't easy, printing something is hit or miss, etc. etc. etc.

So people tend to focus on the "now", and "my latest tech problem".

What people forget is the incredible infrastructure built around the thing they use everyday that do work seemlessly.

Right now I can navigate to far away park, order a pizza, make a high-quality video call to a relative in Europe (for free!), and have some milk and eggs delivered to my door for when I get home. People, even in the early 2000s, would have thought about this in the same way they are thinking about AI/AGI. Yet here we are, I could do the above without even batting an eye, and it will work just fine 99.9999% of the time.

So if there's a quadrant chart, I think most people see this stuff as "far away, glitchy curiosity", whereas very soon it will be "here, reliable".

1

EbolaFred t1_j9yrqbv wrote

I've been thinking a lot about this lately.

Maybe 10% of the people I interact with are free to let their thoughts wander and generate new ideas. The rest seem to be running an NPC script. I can literally predict their full sentences before they say them with pretty decent accuracy.

Now of course I don't know what they are really thinking. They may have some kind of a safe social filter they've developed to make themselves appear normal and socially acceptable - maybe they've had some bad experiences where they've shared their real thoughts and rocked the boat too much, so they shut that part down. But it's something to think about, now that we have access to recent LLMs and can experience how well next word prediction can work.

3

EbolaFred t1_j3d6pew wrote

Yeah, sorry, you're not thinking of it correctly.

Unix time is the number of seconds since Jan 1, 1970. Which, in 2038, will be 2,147,483,648 seconds. This is the same as what a signed 32-bit integer can hold (10^32-1), hence the problem.

Switching to 64-bit can hold this timekeeping scheme for almost 300 billion years.

Note that this is just how Unix decided to keep time when it was being developed. There are obviously many newer implementations that get much more granular than "seconds since 1970" and last longer.. The problem is that many programs have standardized on how Unix does it, so programs know what to expect when calling time().

2

EbolaFred t1_j3c5g33 wrote

Reply to comment by thetburg in ChatGPT Singularity Joke by vert1s

They are different problems.

Y2K happened because back when memory was expensive, programmers decided to use two digits to encode years to save space. This was OK because most humans normally only use two digits for years. Most smart developers knew it was wrong but figured their code wouldn't be around long enough to cause an eventual problem, so why not save some memory space.

Year 2038 is different. It's due to how Unix stores time using a 32-bit integer, which overflow in 2038.

Most modern OSs and databases have already switched to 64-bit, but, as usual, there's tons of legacy code to deal with. Not to mention embedded systems.

6

EbolaFred t1_j2dxabh wrote

Definitely go mid-week.

I'd start with a "learn to ski" group lesson, and do that until you can get down the bunny hill without falling (your first day or two you will fall A LOT, don't let that discourage you) and are comfortable getting on/off the lift.

Once you have the bare basics down I'd switch to private lessons. Obviously more expensive but when you're a beginner, group lessons suck. There's always one or two people that shouldn't be in your group and they will take all the instructor's attention when they fall down and need help getting up every 10 feet.

As to where to go: when you're starting out, anywhere that has decent snow is fine. This time of year you'll want to read some forum posts to see how conditions are. For example, we just had a deep freeze, last few days we're in the 50s, it's going to get cold again later next week...to me that says any local mountains will be a sheet of ice and I wouldn't bother going. You won't always have great snow, but you want to avoid the sheet of ice because that will immediately make you hate skiing.

Regarding lessons, every mountain will have "learn to ski", group lessons, and private lessons. You'll want to book these online ahead of time.

If you go a few times and decide you like and are good enough to get off the bunny hill I'd strongly encourage you to find some ski pals. Skiing alone is not a good idea, especially for beginners. Bad shit can happen and you'll want a pal to get help if you need it.

And a minor correction: nobody calls it a "ski range". Call it "ski mountain" or just "mountain", or "ski slope" or just "slopes" 😎.

Good luck to you, I hope you enjoy it as much as I do!

3