kenferry

Er, I'm not sure what exactly you're getting at, but the stop market drop was not because of his value-add to the company, it was because of the signal it sends by the CEO quitting.

So… I guess you could make an argument that that merits higher pay, but it'd be saying it's due to his blackmail power.

This article is doing comparisons with the same subjects and lighting…

I… guess? I'm not sure why this was posted. None of these changes seem important.

A lot - title could probably use editing. The language has no heap, only stack memory, so the only deallocation is returning from a call stack frame.

> Everything looks like a problem solvable by reduce. (I'm often wrong on that, but I quite enjoy learning why by trying).

I agree, but I think that’s kind of the objection. It can be tempting to write your code as little brainteasers but…

I’m not a fan of this kind of “fancy” optimization anyway.

It’s too fragile. I may make some innocuous change, now the compiler cannot recognize the pattern and performance falls off the cliff.

I’d rather have the reliabile performance than the absolute fastest possible result. Then if there’s an issue I can catch and fix it reliably with profiling, not deal with a heisenbug based on whether the compiler can match the pattern.

That's true enough, but I don't think the conclusion is "don't regulate".

Try it, iterate, figure it out. It'll be painful but so be it.

I think the big difference here is that it's opt-in, off by default, and also not included with shared images by default.

This is a feature because you use it when you WANT to be able to demonstrate an image wasn't altered / was yours, like for a journalist.

This is an actual question, not a dig: what do you mean by non-removable?

You want there to be separate lines for "how long do you want your stems"?

Looking forward to your 18 SKU product matrix of decisions people have to make that they don't know what answer to choose.

The materials cost between those buns is practically nothing. OP is reaching.

I don't know. AI are basically trained to tell you what you want to hear, including when they're disagreeing with you. If you come off of your conversation with AI with a stronger belief than when you went in, is that merited?

"AI Advice Suppresses People’s Willingness To Say “I Don’t Know”, Even When The Advice Is Wrong And Accuracy Is Incentivized" https://osf.io/preprints/psyarxiv/5y6m4_v1

You sort of side stepped the author's point, though.

> In medicine you have the modern labs which automate a lot and you have the old labs. These 'neolabs' are better because of intelligence.

The author is not denying that a lab can be more effective with intelligence, they're arguing that this entire phase of the process of improving health is not the bottleneck.

There are areas of academia where I definitely worry about this kind of thing, but not really database research (and in general CS is a lot less worrisome than most fields).

It's a good thing when industry is a competitively attractive environment for research, which is how I read this.

I was there too, but this blog post agrees with my memory.

I agree with you that Snow Leopard was billed as no USER VISIBLE features. But people did NOT just fix niggling bugs, it was an architecturally huge release. E.g., it introduced GCD. And unless I’m confusing the year, it rewrote the Mail backend to use it and mail hasn’t had reliable search since.

My memory is that quality was so low that we pushed back the release. With the extra time we did manage to fix enough bugs that it was well received. But internally it was more destabilizing than most releases due to the amount of architectural churn.

100%. Author's point is more like "don't vibe code if you have to maintain it".

The code is your responsibility, and it's your responsibility to understand it and maintain it (using the tools your have available).

Strange article. If their point was "…but vibe coding is really tempting, so you have to exercise a lot of discipline" I'd be on board.

Inside joke. Apple's marketing guy used the word "courage" as an explanation when removing the headphone jack.

They weren't banned, but adult websites were not why people bought the original iPhone. Neither the military nor porn were the drivers of smart phone adoption.

I don’t think either of those drove smart phone adoption.

On what platform? It invoked WebKit always on iOS in the early days, html or not. On Mac, AppKit could import html to attributed strings before WebKit existed.

I mean, is it political when you write a paper that concludes that vaccines are effective or that fish die when streams are polluted?

The answer seems to have become "yes", so this is a rhetorical question, but ideally _information_ would be apolitical.

We also see the current administration politicizing things like the federal reserve, which has tried VERY hard to be apolitical.

I mean, I don't think we should legalize Fentanyl.

I wasn't close enough to that to know how long a world build took. Didn't seem like it was too crazy though. Incremental (non-world) builds of the OS come out every day.

I have this impression because I know the native controls are terrific at rich text, so for some reason that support isn't done in a way the author wants to use. The source code of the TextEdit app on Mac is actually published as an example project for the frameworks. Everything in there is provided by the native framework controls.

It would make sense, for example, if you wanted to allow editing of the rich text and have the markdown be directly accessible by the user. The conversion of markdown -> attributed strings -> markdown would not produce the same raw text, which is a problem if the user can directly edit or view the markdown. The user hitting cmd-B in the text view to make something bold might end up scrapping some explicit formatting they did to the raw markdown.

Er, I agree it's incredibly old, but also has been treated as societal ill and subject to regulation for its entire history.

I enjoyed FiveThirtyEight back in the day, but does anyone actually go back and look at the old posts? They were very much of the moment. I'd imagine the vast vast majority of the traffic to them is robots.

I can see why they wouldn't be a priority to keep up. For archival purposes, I'd think everything is still in the internet archive?

Nate seems to try to justify this a touch, saying he personally was looking for a specific article. Kind of a special case there…

You’re confusing iOS and Mac OS here.

The Mac never used WebKit for NSTextField rendering. When iOS was first written, WebKit was used as the text renderer everywhere initially, including in UIKit controls (the “sweet solution”). This proved to be too heavyweight / cumbersome and the coretext/appkit text rendering approach was brought over.

The native Apple libraries are terrific at rendering rich text, it’s one of their strongest assets.

The poster’s issues seem to be specifically because they want to use markdown as the backing. The native rich text backing for native Apple views is attributed strings. They could translate the markdown to attributed strings, but seems like they don’t want to.

I worked at Apple for a long time. The OS gets fully recompiled regularly.

A simultaneous total world build is relatively rare (is that needed here?), but it does happen. Sometimes new compiler versions or features need this.

Most people making this argument aren’t saying they were incapable of doing the project without AI, they’re saying the cost benefit equation was unfavorable because it would take too long.

Ok, but not what this article is about at all. Six figures is for undergrads. The issue here is that PIs don’t have the money to support graduate students, who are typically fully supported.