How does that contradict what the parent poster says? I think it's very weird to call something "high performance" when it looks like it's maybe 15-20% of the performance of a simdjson in c++. This is not "going from normal performance to high performance", this going from "very subpar" to "subpar"
Par is different for different stacks. It's reasonable for someone to treat their standard library's JSON parser as "par", given that that's the parser that most of their peers will be using, even if there are faster options that are commonly used in other stacks.
If it is sponsored Ads, then I presumre that parented comments thinks the price is not good enough to actually provide, as it does not provide enough money for creators to not have sponsored ads as well.
It does and most people that used Nomad were very positive about it. But with the turn that Hashicorp have taken I'm not sure that it now stands much of a chance.
I love Nomad but having used it in two different roles and now invested time to understand k8s properly, I would absolutely not recommend it.
Nomad is simple on the surface and could have been a great tool - but it is basically unusable on its own without tighter integration with Hashi’s own tools (eg Vault). Configuring and maintaining all those things is nontrivial and ends up being more annoying (for a lesser end result) than just using a fully managed kubernetes cluster like GKE
You'd imagine that any scheduler that's well integrated with Vault would have a huge advantage over other ones. Surprising that it's not like that for another product from the same company.
Seconded. Hashicorp Nomad has been a breath of fresh air for doing HA deployments for my workloads. Getting a small cluster setup to self host Nomad is so easier than Kubernetes and defining workloads is much easier to understand too IMO.
The only negatives about Nomad is the Hashicorp license drama that has happened recently and persistent storage can be a pain in the ass.
They pulled the rug out on a lot of people and people tend to hold grudges. Community edition is peanuts compared to using an open source tool you _could have_ fixed your own bugs with by creating PRs or adding features with PRs. I used to be a huge hashicorp fanboy... _used to_.
Just to clarify, you can still access the code, submit PRs to add features, etc. The only difference is that during a fixed time period (4 years) you cannot use Nomad to compete with HashiCorp. If you want to do that, you can ask for a license.
From what I understand, Stallman had several role at FSF. One of them was spokesperson, which is basically Public Relationship. Then, he made several actions showing that he does not understand the basis or does not have the skills to work in PR. So, we was asked to step down from this position.
If you hire a front-end developer and later discover that they are not able to do the basis of programming, are you "canceling" the developer if you decide to not continue to work with them because they are not what you need for the job?
(As for MIT, apparently, it's based on a series of incidents. Again, his work requirement included skills that would imply he would not have done those mistakes. Positions a universities obviously includes as requirement basic skills in knowledge communication and ability to work with pairs, that's what universities are supposed to do.)
The guy who just gave a well attended speech to loud applause and is getting gushing well wishes in this very conversation? The guy who is back at the FSF? That guy?
Imo problem with Java is... JVM because it's quite a resource intensive application itself, memory usage is orders of time magnitude worse than most of the language I've used.
Interesting. A Spring Boot webapp (with the runtime dependency injection framework, etc. etc.) serving some static content and exposing some REST endpoints works fine with 32 MB RAM. Is it really orders of magnitude more than other languages, e.g. will a Go-based webapp consume less than 300 kBytes of RAM?
I do believe that number will go down in the coming releases; things like valhalla will allow us to pack data representations much more efficiently after all. the only things that really benefit from object identity are behaviors, not data.
That's almost always a consequence of poor engineering. You need to consider the runtime when developing any program. With Java, that runtime is more than just your CPU and OS, it's the JVM too.
I also use alpine as the main/root environment. But I rarely use any applications from alpine. For that I have Arch, Fedora and Debian rootfs dirs into which I pivot_root with the help of bubblewrap (bwrap) in shell scripts. There is no overhead and the GPU can be easily attached. You can also dynamically attach ro/rw CWD and target paths (`for arg in "$@"`).
Everything that I care about just works and I get a separation of concerns. Use of network namespaces allows further flexibility. For example, I have a netns that is forced through a Tor gateway such that any traffic originating in it can only go through Tor.
This type of setup is not hardened against kernel vulnerabilities, the kernel treats applications running in namespaces as if they are isolated from other namespaces but those applications can still interact with broad surfaces of the kernel and therefore potentially exploit it.
For kernel safety applications must be denied direct access to the host kernel, this is usually achieved with virtual machines.
Not much actually, but for me it’s default settings of Goland vs “you need to setup some small things, plugins and shortcuts in Intellij IDEA Ultimate to work with Go effectively”. Ultimate is also a bit slower if you don’t disable a ton of Java plugins. But if you don’t need Java and disable it anyway, why not to use more streamlined and lightweight Goland?
the go plugin that existed at the time of goland creation and what exists today are very very different things.
the go plugin back then was very simple. The fact that you get most of the goland experience in idea ultmate today is because they are investing into the go ecosystem as an independent profit making endeavor in and of itself, not simply a small value add.
> This package offers the same high level json.Decoder API but higher throughput and reduced allocations