They're using/testing a few different versions. I used the front page title at the time I shared the link (which has now been changed to the first title you mentioned)
Fair enough - I meant that, at least in Microsoft's own communication, they started more consistently referring to .NET Framework 4.x to differentiate it from first .NET Core and later .NET.
While it was always called .NET Framework, it was very commonly referred to simply as .NET (e.g. .NET 4.5) - and the "Microsoft .NET" logo was widely used in .NET Framework branding/marketing.
I wrote this post - for anyone curious, Heroku's .NET support is built on our open source .NET Cloud Native Buildpack (CNB), which is written in Rust and produces standard OCI images.
You can use it anywhere, even locally, for free. The example in the post uses the .NET 10 file-based app feature we added support for today, so if you want to try the same functionality locally, you can do something like this:
# Create a minimal .NET 10 file-based app
echo 'Console.WriteLine("Hello HN");' > Hello.cs
# Build an OCI image using the .NET CNB
pack build hello-hn --builder heroku/builder:24
# Run it with Docker
docker run --rm -it --entrypoint hello hello-hn
# Output:
Hello HN
Might be more confusing when you consider that ".NET 5" is actually the continuation of ".NET Core 3.1", not ".NET Framework 4.x"[0].
Microsoft has historically been pretty bad at naming stuff (sometimes hilariously so, see Microsoft PlaysForSure[1] for an example - spoiler: it surely didn't play for long).
The rebranding from .NET Core 3.1 to .NET 5, and from .NET 4.x to .NET Framework, did make sense to me though - and increasingly so as development continues on ".NET > 5" with yearly releases, while ".NET Framework 4.x" is in maintenance mode.
I usually think of coding and programming as fairly interchangeable words (vs “developing”, which I think encapsulates both the design/thinking and typing/coding aspects of the process better)
That was the point of the lawsuit. But also seems like the law, museum, and lots of people here missed the point too.
The guy was paid less than $6K for his work. He was not handed a "giant pile of cash" either, but he will now have to pay back the cash that the museum (for whatever reason) lent him, along with the legal costs amounting to ~$11K.
Good! And welcome back (after keeping your promise to dang for ~611 days [0] (and counting)) :)
If you have time to elaborate on how you make a little money on it at some point, I’m sure lots of people here would love to hear more details and thoughts on that!
So you dislike the word lobbying being used here, based on a seemingly pretty specific understanding of what that means.
Lobbying can happen in many ways, and have many different implications. It certainly sounds like it didn’t happen as a result of company/executive action (and at least Tavis believes that), and neither parent, gp or ggp claim so (in fact they agree the opposite is the case).
I rarely have casual discussions with friends working at regulatory agencies that come back to haunt other people. I also don’t think the word “lobbied” was used in a harmful or particularly egregious way, especially considering the context in which it was used (and explained).