dgritsko

Looks like this might be what you want at least for Node.js: https://nodejs.org/docs/latest-v17.x/api/all.html

Same here, what a nostalgia hit! Immediately got a huge grin on my face the first time I blew myself up by dropping a bomb while upside down - a classic mistake I've done hundreds of times.

It's a great headline that feeds right in to the rest of the OpenAI drama, which is undoubtedly why it's all over the place. But I'm with you - where are the details?

Towards the bottom of the article...

> Could platforms defend themselves? What if the warhead or missile was spinning, etc.? All those questions were answered. The only real barrier at the time was generating very high laser power levels in a way that was logistically practical in the field.

I find it fascinating that the top two comments (at the moment) are essentially saying "this marketing video is great" and "this marketing video is terrible". Would it be this polarizing if it wasn't Google?

The idea of asking it to produce an "ouroboros prompt" that can be fed back into itself summarizing everything already learned is very clever; definitely going to use that in future ChatGPT sessions of my own.

A favorite of mine has been to say with a straight face that "it's important to make sure that there are no kinks in your cables, because the 0's pass through easily but the sharp edges of the 1's get caught on things" and seeing if anyone catches on.

"Those praying for its awakening (basically, everyone in real estate) need office workers to return."

That includes the author, who is a partner at a real estate firm. The livelihood of these people is very much dependent on making sure their buildings are occupied - but for the would-be occupants, what's the benefit?

I have a private office already; it's in my house. It's quiet and comfortable. I don't have to deal with a commute or noisy coworkers, and I'm able to be extremely productive. My quality of life has improved tremendously as a direct result of working from home, and no "carrot" of private offices or "stick" of a forced return will cause me to give it up.

This is a great comment. It takes a lot of humility to admit you were wrong, and it sounds like it was a great learning experience.

The way an SMS message is displayed in iMessage (sent from a non-Apple device, as opposed to a "blue bubble" for iMessage-to-iMessage messages).

I agree, it feels like this technology is progressing by leaps and bounds almost by the day.

I think it boils more down to this:

"I was uncomfortable with how he played because he has a history of cheating so I quit"

Which is entirely reasonable, if you think that cheating is an "existential threat" to chess itself.

The video in question: https://www.youtube.com/watch?v=Cq56o0YH3mE

The subtle inaccuracies that are often present in AI-generated images really work for the creepy/trippy vibe here. Pretty awesome stuff.

I have to say, I wasn't expecting to see the Fermi paradox brought up in the final paragraph. I think that's the first time I've heard AI described as an existential threat not because of malevolence, but because of its potential to collectively dumb down all of humanity due to over-reliance on it.

Reminds me of this recent Scott Alexander post about DALL-E 2 to design stained glass windows, it's a pretty interesting exploration of how various phrases are interpreted. https://astralcodexten.substack.com/p/a-guide-to-asking-robo...

I'm really curious as to what Apple's broader strategy is with live sports, since that's typically been one of the last big reasons to keep a cable subscription. However, given that Apple TV Plus is going to have at least some MLB games[1] and is rumored to possibly be the new home for the NFL Sunday Ticket[2], they could be seeking to make it the must-have subscription for fans of live sports.

https://www.apple.com/newsroom/2022/03/apple-and-mlb-announc...

https://www.tomsguide.com/news/apple-tv-plus-could-become-ho...

I felt the same way. I scrolled down to see what the author's proposed solution was, and the post just... ends.

No, unfortunately he did not survive:

> After helping me with the chute, Mitchell said he’d check on Jim. He climbed into his helicopter, flew a short distance away and returned about 10 min. later with devastating news: Jim was dead. Apparently, he had suffered a broken neck during the aircraft’s disintegration and was killed instantly. Mitchell said his ranch foreman would soon arrive to watch over Jim’s body until the authorities arrived.

Tailwind support would be awesome. I often use Tailwind Play (https://play.tailwindcss.com/) when I'm "sketching out" the look of a new component since it's so quick to iterate and get immediate visual feedback, as you well know.

I recently had a conversation with an "absolute beginner" and it was a stark reminder just how much knowledge I take for granted. It really is extremely challenging to try and build up a base of knowledge starting with no prior experience, and it's great to see examples of this done right.

I'm still learning TypeScript and didn't know about "assertion signatures" prior to reading this article. They were added in 3.7. For any other TS users who also aren't familiar: https://www.typescriptlang.org/docs/handbook/release-notes/t...

True. Approximate skill of the golfer could also be an important factor - the article even mentions three LPGA golfers getting holes-in-one in the same tournament. Presumably they were quite a bit more talented than your average entrant.

> The cost to insure against a hole-in-one is dependent on 3 factors:

> 1. The number of golfers in the tournament

> 2. The length (yardage) of the contest hole

> 3. The cash value of the hole-in-one prize

> Once a client provides this information, Gilmartin plugs it into an algorithm that computes the odds, factors in his risk and margins, and spits out a dollar amount per golfer.

This seems like it could work as a simplified example of how all insurance pricing works, although with many, many more variables involved I'm sure. It'd be fascinating to look at the details of one of these algorithms.

I've heard "propagating" the exception used as well.

I don't have any need for one of these. But this review makes me want one, it looks like a lot of fun. Anybody here have one yet? How does your experience compare?

> The price for the two-hour-up, two-hours-gliding, and two-hour-down voyage, which ends with an ocean splashdown, is significantly less than Virgin Galactic tickets

No mention of the prices in the article, but from here (https://www.space.com/space-perspective-selling-seats-strato...) it looks like they're $125,000 apiece.

> Apparently I am crazy to draw with these outdated tools but I like the hand-drawn look and feel.

I've never heard of this person or seen their illustrations, but after reading the article and viewing the finished artwork it's hard to argue with - clearly, he enjoys the process and has no desire to change it, and the end result looks great.

One obvious downside is that polling at a fixed interval is going to be less efficient than having an event "pushed" to your client as soon as it's available. If your events are low-volume, then there will be periods where your polling requests return no new data, but you still have to make those requests anyway in order to determine that. And conversely, if your events are high-volume, then your polling interval represents an arbitrary amount of delay that you're introducing into the system. That might not be big deal for some applications, but it's worth mentioning as a potential downside in situations where you want the behavior to be as near-instantaneous as possible.

> I don’t think you can introduce a recommendation algorithm without it having a negative effect on the content it’s supposed to aid discovery of.

This feels like it ought to be a corollary to Goodhart's Law ("When a measure becomes a target, it ceases to be a good measure"), or perhaps a specialized application thereof.

https://en.wikipedia.org/wiki/Goodhart%27s_law

I agree. I think organizational scalability is an important benefit of microservices that doesn't always come up in these discussions. Having smaller, more focused services (and repositories) allows your organization to scale up to dozens or hundreds of developers in a way that just wouldn't be practical with a monolithic application, at least in my experience (I'm sure there are exceptions).