Earlier quoted context omitted.
Probably. But I got over it 25 years ago. I think of it as “dotnet” in my head which seems better.
Do people say .net in some way other than "dotnet"? Or did I misunderstand?
Heroku Support for .NET 10
41–48 of 48 posts
Re: Heroku Support for .NET 10
#42I 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…
Re: Heroku Support for .NET 10
#43.net is probably one of the top 10 worst names in history or is it only me?
No, that's Microsoft's other work in the XBox line. Try saying "Xbox Series X" and "Xbox Series S" and "XBox One S" to ten normal people and asking them to find the correct matching product in a store.
Re: Heroku Support for .NET 10
#44.net is probably one of the top 10 worst names in history or is it only me?
Some fun ones: - Colgate Kitchen Entrees - Ayds Diet Candy - Gerber in Africa (in many regions, it is customary for labels to show what's inside. Having a baby on the bottle is just weird) - Chevrolet Nova (no va means "don't go") - Clairol Mist Stick (in Germany. In German, Mist means manure) - Pee Cola (Ghana) - Puffs Tissues (Germany) (in German slang, Puff means brothel) - Nokia Lumia (prostitute in Spanish slang…
Re: Heroku Support for .NET 10
#45Earlier quoted context omitted.
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 -…
.NET Framework was always called .NET Framework and not renamed from NET 4 to .NET Framework. There was a time where .NET was applied as a prefix/suffix to everything Microsoft released. Microsoft Windows Server .NET. that had nothing to do with the framework/CLR/programming platform but with Internet connected features.
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.
Re: Heroku Support for .NET 10
#46Earlier quoted context omitted.
$1 per function call is possible. /s
Isn't that what make.com tries to achieve? Already at 1c per node invocation...
Re: Heroku Support for .NET 10
#47I lament what could have been with heroku. I did some back of the envelope calculations for what it would have cost for my own startup to run on it and it came out to significantly more than what it costs us on aws INCLUDING our dedicated devops guy. They really killed its utility for anything bigger than a hobby project.
As the founder of a local cloud very similar to Heroku, I understand Heroku's limitations. It's a balance between control and convenience. The simpler everything is, the better it's suited for small projects, but the less control you have for complex projects. Unless you're just running a hobby project, you'll be using Kubernetes and similar services with full control and the complexity that comes with it. Heroku use…
Re: Heroku Support for .NET 10
#48I lament what could have been with heroku. I did some back of the envelope calculations for what it would have cost for my own startup to run on it and it came out to significantly more than what it costs us on aws INCLUDING our dedicated devops guy. They really killed its utility for anything bigger than a hobby project.