orf

What specific technical issues are you experiencing with running Bun that would justify a change?

Please make my predictions come out wrong.

Wow, you missed the entire point of the article.

I've invoked it in my job mostly to explain to younger developers why learning vim keybindings+terminal git usage

Interesting - I see it as the opposite: learning the git CLI is pointless. It’s slow, clunky and it doesn’t teach you any of the very interesting inner-workings of Git.

There are much better things to spend time learning, especially if your editor has a native git integration.

US card fraud rate is significantly higher than in the EU. In 2015 it was about 0.042% in the EU, vs 0.1388% for the US. The 2021 rates for the EU fell to ~0.028%.

You get nervous about giving your card to a waiter because you’re in a foreign place with a nonsense payment system worst than most developing countries and it’s not something you’re ever asked to do anywhere else.

I see that, but the adversary wasn’t a low effort one, and didn’t need millions of accounts.

New user registration was stopped on June 11 and then re-enabled after the project added Anubis to try to foil the attacker's mass account registrations. That did not work

This confuses me - why would a proof-of-work anti-scraping system like Anubis prevent registrations?

As a discussion regarding if it’s ethical to ignore restrictions progresses, the probability of someone bringing up a famous case where someone ignored unethical restrictions approaches one

Seems reasonable to me. Substitute Rosa parks with another example of unethical restrictions if you wish - there are many.

Was Rosa Parks unethical for sitting down on a bus?

The point is that the context matters: both the users context and the context of the restriction. It’s not as clear cut as “ignoring restrictions = bad”.

The restriction itself can be unethical, in the same way that bypassing a restriction can be unethical.

Are you making an honest attempt at stating your opinion that there is absolutely no reason to prefer a MacBook over your chosen device?

Or are you just being glib because you’ve got a misplaced superiority complex?

how 99% of the population are not going to afford a setup like that

could or will? much fewer than 1% are going to spend their money on that.

It’s ok to change your point, you don’t need to get combative.

Not that it makes any difference, given their ~10% market share.

That’s not at all what you said though, was it?

99% of the population don’t code using models, local or remote. So that’s a useless metric.

What % of developers could afford an older MacBook model, second hand? Far, far more than 1%.

I wrote something similar with go, but MacOS only.

Creating a worktree became instant, but the bottleneck shifted from that to git needing to build its index. Claude code runs `git status` in the background, meaning any speed gains are instantly gone.

Why? Calling a reasonable thing grim without any follow-up isn’t the hallmark of a good comment either.

postgresql also does not synchronously replicate

By default. Generally your primary database is in a completely different failure category than a kubernetes node running an ephemeral workflow pod.

Yes, but directly using s3 as a key-value database is completely different from using SQLite + litestream.

The caveat is that Litestream replication is asynchronous. A restore can miss the newest local writes if the SQLite volume disappears before they are copied. That is fine for many AI and experimentation workflows

In short: SQLite is not all you need, unless you’re just experimenting don’t actually care about durability, in which case you also need litestream + object storage.

Right.

Google followed in 2010 with Cloud to Device Messaging, then Google Cloud Messaging in 2012, then Firebase Cloud Messaging in 2016

Classic

The essence of a program is all of those things. The omission of any one of them makes a program almost worthless.

The release post for v2.8 is not yet published. Check GitHub releases page for the latest release status of Deno.

Misc thoughts:

Perhaps sharing your take home exercise might be a more useful avenue for feedback?

I’m not sure how large the market is for ASP.NET developers, but the skills you’ve learned so far are more transferable than you think. Try creating some projects with Django or Rails and spread your wings a bit. Don’t be a monoglot.

A portfolio helps, as well as a personal narrative. Being a solo developer for 2.5 years is good and bad depending on the audience. For example it means you don’t have much recent experience working with a team, and I imagine clunky Belfast ASP.NET companies are not exactly hotbeds of entrepreneurial spirit. Maybe look for smaller companies or startups?

Extremely personally, Azure certifications and such things are worthless, bordering on a negative signal depending on the context. But some people/companies may value them.

Saying you think reading “C# in a Nutshell” is a good idea is concerning because you say you’ve got 6+ years of ASP.NET experience. Was this not using C#? Revision is always good, but identifying why you’re not already comfortable with C# is a good starting point.

Build some solo projects with C#, not using ASP.NET, with some artificial constraints (speed, memory, etc). Then smash them. Could be as simple as parsing a 20GB CSV into memory: start dumb and slow then make it as fast as you possibly can. For me this beats a book on data structures.

The entire executable isn’t loaded into RAM.

And are laptops a primary deployment target?

You’re right, I misstated. It’s not 10 million per exploitation, it instead limits the pool of people who can exploit you to those willing and have the ability to spend 10 million+ on an exploit.

That is still quite a small pool, and there are other network effects preventing any Joe blogs with that much capital from launching an exploitation campaign.

We have seen multiple software hacks resulting in >10 million dollar payouts

This sets a nice price bar for exploitation. Is someone willing to pay 10+ million dollars to get access to your phone?

The obvious caveat here is that for a lot less than 10 million dollars someone can be hired to hit you with a metal pipe until you give up your passcode.

click total compromise that can trivially worm to take down hundreds of millions of iPhones simultaneously

Where is the profit motive in doing this? Possibility is one thing, but a realistic threat is another.

So you’re saying that if you append 1GB of junk data to the end of an executable it would be slower to execute?

No? So it’s not purely a function of disk size.

This makes sense if you’re a human-rights journalist working in a dangerous country, with the threat of state-level actors looking to compromise you.

If you’re not then this seems quite paranoid, bordering on LARPing.

SSDs can read at gigabytes per second, and only the used portions are paged into memory.

Anything else?

Why does the on-disk size matter for any of that?

You don't want that as an automatic update because it will break in production for anyone who is actually using it

The problem with this take is that it’s stuck in the early 2000’s, where all servers are pets to be cared for and lovingly updated in place.

It’s also circular: you have the same problem with the current model if you don’t have a test environment. And if you do have a test environment, releases can be tested and validated at a much higher cadence.