Vs just running a binary. So simple.
People put up with Java for a while but it’s declining in popularity.
Part of what was so liberating when Node was emerging is that it's so so so configuration less. Python is still fighting to figure out what a package is & where libraries go, and how does work. That was moot with Node, not an issue, because node_modules is the thing & it's almost always local (Debian valiantly fighting to system wide that). .NET has orders of magnitude more carried assumptions & confirmation than Python.
It's super awesome, a lot of it has great reason & power for being there. But this idea that runtimes are black boxes & we ought not notice or care is a day 1 experience that your day 2 engineers may swear at you at over.
https://microsoft.github.io/garnet/docs/getting-started
https://microsoft.github.io/garnet/docs/getting-started/conf...
But you haven’t, because posting FUD is more important.
But it's presenting the impression that it's a blackbox, that it's just Garnet you have to configure.
But there's a huge vm under the surface of this facade, and you're not showing what the rest of the iceberg looks like in these docs. No vm is free of tuning. Not Java, not node, not .net, and they all have specific learned natures.
It's concerning not encouraging that Garnet doesn't even begin to respect that, that it presents itself as a neutral blackbix binary when there's so much more here.
I'm really shocked at the complainy whiny petulant tone that any remotely critical point of view is met with. I've never seen a group of people so brazenly so aggressively insist we should have no concerns, that showing any appreciation for nuance or difference is met with accusations of FUD. Terribly insulting to be bossed around like this, and I hope the rest of the .net platform advocates aren't think skinned & petulant. I don't think you'll get far trying to win cultural arguments by force.
Garnet looks awesome but this attitude of outrage anyone might for a second pause about .NET & that any concern is invalid and not allowed is absurd.
There's a comment stating that the project requires complex and involved configuration, and it's a problem. A link is provided in response that demonstrates it to be the opposite. Turns out, as a reply states, it is equally an issue, possibly because of an assumption that a VM-based language must come with a significant amount of required configuration ceremony (even though counter-points to this, like Go, exist). .NET is configurable, GC modes can be changed, at startup or on the fly (within certain limitations), compiler options can be adjusted, but the default approach is for the users to do as little input as possible unless something does not perform to their expectations.
> Running .net implies a lot, brings a lot of conventions and configuration with it, that's very dense. Dense and powerful and useful. But is it's own universe.
> that it presents itself as a neutral blackbox binary [0]
> .NET has orders of magnitude more carried assumptions & confirmation than Python. [1]
This was posted without verifying whether these statements are true or not, presented as fact. It is not unreasonable to be upset if it happens every single time. You could compare this to how Ruby community feels that whenever Ruby-related projects are discussed, someone is bound to come and point out how it has terrible performance and is therefore unusable (I was guilty of this as well). Emotional embellishments and holier than thou attitude are insufficient to reframe this. When facts change, I change my mind, and if a statement turns out to be incorrect, I stand corrected, and it has been a great boon for acquiring all kinds of tidbits of technical knowledge here so far. At the end of the day, this is an informal setting, therefore the rules of HN and internet etiquette apply first and foremost.
[0]: instead of easier to use pre-built docker images, quickstart guide ends up pointing to just cloning the source code, and doing build+run (dotnet run -c Release). This is as far as it gets from a blackbox binary.
[1]: it only makes the assumptions that are safe to make, which are the same most other platforms are subject to - that certain POSIX and Linux (or macOS/FreeBSD) APIs and glibc or musl are available, that the runtime is present in the $PATH (or not, if an application is published as self-contained or natively compiled), that sort of thing.
https://learn.microsoft.com/en-us/dotnet/core/deploying/sing...
So simple.
"apt install redis-server" on my server says that the following will be installed:
- libjemalloc2
- liblzf1
- redis-tools
Garnet requires .NET, so...
apt install aspnetcore-runtime-8.0
Acting like Redis works "out of the box" while Garnet requires a whole other paradigm shift is disingenuous. I have no dog in the fight - I use macOS and I don't use Redis or Garnet.
While on the topic of macOS, Swift Library Evolution ABI support is coming .NET for native integration with Swift (particularly for system APIs). I have not tried it yet but it's an interesting feature AFAIK no other language has, well, besides Swift itself.