kenshi

I wrote an explainer for monads because I think they are typically explained in a terrible way for the working programmer.

Would love any feedback on this.

Thanks for posting this!

I've started looking into the history of Postscript because I was looking into the idea of "sending a program not a data structure".

Some thoughts so far: https://krishna.github.io/posts/send-a-program-not-a-datastr...

This sounds cool. You mentioned Swift's macros - would you mind talking a bit how you are using them?

Yes, you can use SPM to package up Objective-C code.

I should have included the following information in the blog post (will update it later!):

I usually have:

- 45g of air popped popcorn (64 calories).

- 5 to 10g of butter (37 - 74 calories).

- couple of garlic cloves (10 cals).

Most people are consumers, not creators.

Probably my favourite book on programming. Thanks for posting it here - I'll have to make time for a re-read of it.

Information arbitrage is one helluva social media drug.

The thing that's "holding back" the iPad isn't hardware. It's the economics of the App store.

I'm sure Apple are very happy with the niche the iPad dominates in - it leaves plenty of room for Mac laptop sales.

Maybe you just aren't going to be able to afford everything and will just have to make a choice about what you consume.

I suspect Apple knows the developer experience for Swift is terrible (even if the Apple developer community at large is in mass denial about this).

The number 2 item on Swift Core Teams goals for Swift 6 is "Create a fantastic development experience". See: https://forums.swift.org/t/on-the-road-to-swift-6/32862

Whether anyone at Apple cares about documentation any more is another matter. A really sad state of affairs, because once upon a time, Apple had some of the best documentation out there. Of course, that was when they actively needed to court a developer community, and couldn't just announce something half-baked at WWDC and get mass adoption from enthusiastic developers.

Could you talk a bit about the kinds of things you had to fight the compiler on?

Can you identify any idioms or approaches that seem normal or natural in other languages, but which are problematic in Rust?

You are dealing with a lot, in a compressed period of time.

Try to remember that your first priority and responsibility is looking after your own mental, physical and spiritual (I don't mean this in a religious sense) well being.

In your situation, work really should be the lowest priority that you can afford to make it. If you can afford to take extended time off to deal with everything you need to, I would highly recommend that you give it serious consideration.

It's only technically impossible if the system software and/or hardware can't be compromised/exploited.

If you are just going by the intent and marketing of any platform vendor, plenty of things are technically impossible. But exploits and flaws in software and hardware exist, and the resources a nation state can bring to bear to find and use them are significant.

There is a reason vendors run bug bounty programmes, why the jailbreak scene is still a thing, and cybercrime in general is booming.

No one vendor has solved computer security.

I’d call you a person of taste and sophistication.

But more objectively, it is always a pleasure to come to some open source code base and know you have few worries about language churn incurring a maintenance cost.

Why be a "staunch <Company X> supporter" at all?

It's one thing to admire the work/output of a company, but once you identify as a "Company X" supporter you are just closing yourself off to being critical of "Company X".

I cringe at every WWDC session when people applaud for minor features (new themes in Xcode!) and long overdue bug fixes.

I am embarrassed whenever someone online talks about a problem they have with Apple hardware or software, and they are met with passive-aggressive replies along the lines of "I've never seen that problem, what are you doing wrong..."

I develop for and use Apple platforms. I really like some things they have done, but I'd never consider myself an "Apple supporter".

I'm the customer, they are the vendor. They are here to support me.

If they don't do a good job at that, I'll try to find another company to take their place.

Also companies change, as do their priorities. There was once a period in when MS were making the best internet browser (really)...

If it quacks like an alpha, is documented like an alpha, and is unreliable like an alpha... it's production ready because the vendor took the beta label off it.

Edits: typos

> Flutter has its own layout rendering engine, and uses low level APIs in the browser to circumvent the default rendering.

Does this mean that Flutter on the web is really Flutter on Chrome? Or does is support other web browsers well?