Wow, the way Upwork is handling this seems really bad. They announced the layoffs today, but nobody will know who is being let go until next week! Sheesh.

Our first year on Vercel, the bill was $40,000. When our management went back to negotiate the second year, Vercel wanted $120,000! Vercel wasn't offering 3x the features, mind you, they just knew we were locked in. Our management got it down to $60,000 (still a 50% cost increase, year over year).

Our app is small beans, too. We don't even have that many users. To borrow a favorite term from DHH, Vercel are "merchants of complexity."

But they're only half the problem. Our management is the other half. They can't be bothered to grow a spine and move away from Vercel. So we'll just keep paying, and eventually some people will "be affected" by a "reduction in force."

Now do OpenAI...

Read the article.

The display has a refresh rate of 120hz when needed. The low refresh rate is for battery savings when there is a static image.

Variable refresh rate for power savings is a feature that other manufacturers already have (apple for one). So you might already be an early adopter.

My wife and I canceled Netflix a while ago and went back to DVDs. An FYE store in our area recently had a store closing sale, so we bought three DVD players and snapped up all our favorite DVDs for a few bucks each.

No subscription, no mid-movie ads, and no worrying about this or that service losing the streaming rights to whatever.

Wait until you discover the local library! DVDs for days, and they let me check out a Netflix device now and then.

I never actually type semicolons in my JavaScript / TypeScript. In work projects, my IDE adds them for me thanks to the linter. In personal projects, I just leave them out (I don't use a linter, so my IDE does not add them), and I've never had a problem. Not even once.

Semicolon FUD is for the birds.

I occasionally run into problems with JS weird parsing rules. My favorite is:

    return
        x 

Which does not return. It returns undefined.

Typescript helps a lot with that. A linter will probably flag it as well. Still, JS went way out of its way to accept just about anything, whether it makes sense or not.

That is what I lament too. So I've started to use the comma-operator to make sure my return statements don't care about line-breaks. I often write:

return 0,

x;

I find this a mildly amusing discovery for myself because it took me a long time to figure out a useful use for the comma-operator.

Cormack McCarthy proved to me that when structured correctly conversive language does not need any quotation marks (while remaining entirely comprehensible).

But " " still exist (for us/mere mortals) because few can write so clearly.

I know nothing about coding (beyond changing others' variables to fit my installation), but would imagine this parallels many coding environments (e.g. yours).

The AOL version missed an opportunity: After connecting it should have said, "You've got mail!"

It does, maybe try again, the MP3 may have failed to load in.

it 100% does already

Somebody else must've already read mine.

AI also makes you bored.