bradford (u/bradford)

bradford commented on .NET 10 devblogs.microsoft.com/do... · Posted by u/runesoerensen

DarkNova6 · a month ago

Silly question. If you want the C# experience but more community/OSS driven… why not Java?

bradford · a month ago

I haven't kept aware of changes to Java in the last decade, but the things I didn't like about it then were:

1. The overall architecture (with the JVM) made it slower than the equivalent C# code.

2. C# really started embracing modern language features at a time when Java was kind of languishing (lambda functions, async patterns). Java seems like it's been in perpetual catch-up since then.

(Not OP, disclaimer, I work for Microsoft and this is only my opinion).

bradford commented on Stephen Miller's Quota Likely Drove Korean Arrests in Immigration Raid forbes.com/sites/stuartan... · Posted by u/gok

bradford · 3 months ago

> What do you want for the USA? Completely open borders? Closed borders, but we don't enforce it very well? Something else?

The 2024 bipartisan border bill (https://en.wikipedia.org/wiki/Mexico%E2%80%93United_States_b...) seemed like a good compromise to me. Of course, it wasn't brought to a vote by the house (for reasons that I won't elaborate on), so it's mostly a hypothetical.

And, if I had to choose between the two, I'm more supportive of the Biden era immigration policy than I am of the current Trump policy.

bradford commented on Google will allow only apps from verified developers to be installed on Android 9to5google.com/2025/08/25... · Posted by u/kotaKat

ikiris · 4 months ago

You do realize windows already does this right?

bradford · 4 months ago

Can you explain in what way Windows already does this?

bradford commented on We can no longer run Microsoft Store on 1809/LTSC 2019 github.com/fernvenue/micr... · Posted by u/fernvenue

fernvenue · 7 months ago

Hi, sorry for the late response :)

> The lack of support on LTSC is the least baffling thing going on here but I'm open to the possibility that I'm misunderstanding something....

And yea, you're right, but Indeed, many people need to use the store on LTSC, especially after Microsoft migrated many ecosystem attempts to the store, for example Microsoft Photos and some extensions like HEIC, and now not only UWP applications can enter the store; regular applications can also do so. It actually poses a very big problem that we cannot use the store anymore, at least that's what I think.

Furthermore, it is not just LTSC 2019 that cannot be used; this means that older versions of Windows (at least 1809 or older) are also no longer able to use it. In other words, we can no longer use the store on older versions of Windows. You might say that Microsoft itself didn't intend to provide support for older versions, and yea, I agree, that's true. However, the fact is that many people use Windows largely because of its compatibility advantages. I believe everyone should at least be aware that Microsoft is not as compatible with older programs, especially its own, which is what I want to express.

As for the license, I would like to clarify that it is only to prevent the packaging scripts from being used for commercial purposes and promotion. As you can see, this repository is not specifically intended for hosting store programs, so it does NOT apply to the store programs themselves, but only to the deployment scripts :)

bradford · 7 months ago

Thanks for your response!

bradford commented on We can no longer run Microsoft Store on 1809/LTSC 2019 github.com/fernvenue/micr... · Posted by u/fernvenue

sgjohnson · 7 months ago

> Why doesn't the README file explain what this repository is doing?

It explains exactly what it's doing.

"Microsoft Store package for Windows LTSC."

It provides a Microsoft Store package for LTSC builds, and an install script that allows it to actually work. Windows LTSC builds don't have Microsoft Store preinstalled, and Microsoft offers no official way to re-enable it.

bradford · 7 months ago

Ok, but the brief README links to an actual microsoft.com domain (https://www.microsoft.com/store).

Why would you need a package to wrap a website? Wouldn't the website be accessible on a LTSC build, even if the official package isn't available?

If this is filling a highly useful role that I'm admittedly oblivious to, why are there only three commits in the project history?

(Best I can tell, this is a personal project that somehow made it to HN front page)

bradford commented on We can no longer run Microsoft Store on 1809/LTSC 2019 github.com/fernvenue/micr... · Posted by u/fernvenue

bradford · 7 months ago

Why is a repository called 'Microsoft Store' being hosted on a seemingly random github account?

Why doesn't the README file explain what this repository is doing?

OP, what did you hope to accomplish with this submission?

The lack of support on LTSC is the least baffling thing going on here but I'm open to the possibility that I'm misunderstanding something....

bradford commented on The Gang Has a Mid-Life Crisis chris-martin.org/2025/the... · Posted by u/dralley

argomo · 7 months ago

Nice take. Don't let the DEI lead-in sway you from reading this observation about tech moguls trying to reclaim their glory days.

bradford · 7 months ago

I agreed with a lot in the article, but I was a bit baffled by the DEI name-drop in the opening.

> "... the guys who had big tech startup successes in the 90s and early aughts think that 'DEI' is the cause of all their problems."

Who is the author referring to here?

(I realize that DEI has been rolled back at some companies, and Zuckerberg in particular has derided it, yet I still feel like the author is referring to some commonly accepted knowledge that I'm out of the loop on.)

bradford commented on Pipelining might be my favorite programming language feature herecomesthemoon.net/2025... · Posted by u/Mond_

bnchrch · 8 months ago

I'm personally someone who advocates for languages to keep their feature set small and shoot to achieve a finished feature set quickly.

However.

I would be lying if I didn't secretly wish that all languages adopted the `|>` syntax from Elixir.

```

params

|> Map.get("user")

|> create_user()

|> notify_admin()

```

bradford · 8 months ago

I hate to be that guy, but I believe the `|>` syntax started with F# before Elixir picked it up.

(No disagreements with your post, just want to give credit where it's due. I'm also a big fan of the syntax)

bradford commented on Azure's Weakest Link? How API Connections Spill Secrets binarysecurity.no/posts/2... · Posted by u/hland

IcyWindows · 9 months ago

The caller still needs at least the Reader role, so it was limited to accounts that were added to the Azure subscription as only Readers.

I'm glad they fixed it, but this doesn't seem too scary??

bradford · 9 months ago

Suppose user U has read access to Subscription S, but doesn't have access to keyvault K.

If user U can gain access to keyvault K via this exploit, it is scary.

[Vendors/Contingent staff will often be granted read-level access to a subscription under the assumption that they won't have access to secrets, for example.]

(I'm open to the possibility that I'm misunderstanding the exploit)

bradford commented on Treasury agrees to block DOGE's access to personal taxpayer data at IRS washingtonpost.com/busine... · Posted by u/MilnerRoute

wmf · 10 months ago

Again, it's not a data breach for the government to have access to government data. If it gets outside then it's a data breach.

DOGE has enough real problems that we don't need to cry wolf about its hypothetical (although maybe "inevitable") future actions.

bradford · 10 months ago

> it's not a data breach for the government to have access to government data

This absurd oversimplification needs to be called out.

The 'government' is not a single individual, nor should 'government data' be treated without regards to specifics.

The exact entity doing the accessing, and the exact data that's being accessed, all need to be accounted for, and the appropriateness of the access will change depending on the context.

DOGE hasn't been transparent in any of this, which is my chief complaint at the moment.