I can attest to this. People say the Netherlands is among the best countries to be an entrepreneur. The visa policies for starting a business are good. But man, the whole tax system, shares, and holding management—belasting breathing up your neck—is horrible when I am trying to do firefighting. You never know when you might get hit by a tax bill. The tax system is built towards benefitting large organizations, and they can afford expensive tax consultants who can help them dodge it. The VC ecosystem is limited and not risk averse.
Having operated in multiple geographies, US is really business friendly.
>the whole tax system, shares, and holding management
You don't have to set up a holding management structure for your company. It's there if you want to, but why make it complicated if you don't want a complicated structure?
If you're small, a simple eenmanszaak will suffice - which you can fill online, and then complete within an hour at the KvK.
>belasting breathing up your neck
Honestly I never had any issues with the belastingdienst, as long as you file your reports every quarter/year, and you're willing to pay the taxes you owe.
Any time I ever had issues, I just had to talk with one of their inspectors, go over my paperwork, and we sorted it out there. When I had issues with paying, it was one phone call to defer it for 2 years and set a payment scheme.
Compared to modern social media platforms they are eons behind ofc social media has more content and more data ofc.
But their BigData and stuff was bleeding edge in pre-2018 in 2026 they really are 5-8 years behind they have not progressed much from what I can tell in both my usage experience, and their technical outputs over the years.
And yes that's the thing about modern development you fall behind really quickly.
Think about it Google was the company to create modern LLMs but people now dog on their LLMs. Apparently even SpaceX is ahead (I don't exactly know but maybe it is).
Being ahead once doesn't mean you are ahead today.
Netflix excels at maximizing engagement. The idea that you should A/B thumbnails for individual users, for example.
All the world-class data science doesn’t change the fact that the catalog doesn’t actually have many “hidden gem” titles. I find it somewhat hypocritical to argue that naive recommendations skew to the mean, when Netflix will happily pull funding for quirky shows that underperform in front of a general audience.
a nation can emerge as a superpower with advanced infrastructure at one point in time, and still have antiquated infrastructure in the present, no high speed rail and overly complex solutions to make up for it
I am wondering when would you use kubernetes on oxide vs running kubernetes with kubevirt on baremetal?
At first look, it feels like oxide is equivalent to proxmox or some virtualization tool, may be it uses qemu stuff underneath.
Just curious.
The reason I am asking this is that, we have lot onprem scenarios in our business. We are tightly coupled with k8s, to solve this we started building an internal project that is kubernetes API compatible [1] but runs containerd or WASM or our platform natively.
Good question. We use our own hypervisor[0] that's not KVM/QEMU. We don't have nested virtualization today so we don't follow the KubeVirt model, though we are discussing what CRDs like OxideInstance would look like for those that want to operate solely in Kubernetes manifests.
The core primitive on Oxide is the instance (virtual machine). We could support some container primitive, but that's a larger product direction discussion. Our host OS is Helios (Illumos) so there are details to iron out there regarding what abstractions we would build and expose to the users. Not impossible but not something we're currently pursuing either given that we have other immediate product asks.
If you're at a scale where compute density, power efficiency, security, and rack-level API management matters then that's where Oxide makes sense for you.
Could there theoretically be a swappable hypervisor for oxide some day? I'm imagining a oxide Linux distro of sorts running on the hosts, and using kvm for vms, but still oxide control plane bits downstream. Then you get nested virt and gpu support, and could maybe even virtualize a traditional oxide host. Like running multi-host vcenter clusters inside a single esxi, amazingly powerful lab scenarios, teardown is even fun
Switching to Linux and KVM would gain the ecosystem benefits but Oxide would lose control of the host OS which can impact our security stance. Better to tightly integrate at this layer and expose the primitives that are needed. It's not impossible, but we're already maintaining the existing Helios host OS. Adding another wouldn't be beneficial.
You would use Oxide if you hate Dell/HPE/Lenovo/Supermicro. Also most people won't run k8s on bare metal because they want to dynamically provision a bunch of clusters.
Oxide is shipping the baremetal server as well, with integrated hypervisor - so running kubernetes with kubevirt on it makes less sense than integrating with the host hypervisor
Yeah me too. Like I kinda compare oxide to coreweave and coreweave is built on top of k8s afaik. I'm wondering what the underlying tech oxide leans on. If I was doing this I would be using talos and k8s on baremetal and building on top of that. Container first rather than VM first seems like a big advantage imo. Most workloads will be containers.
Yeah, YC also has their own "multiplayer agent", qm (https://github.com/yc-software/qm), though it doesn't seem to be focused on code, which makes a little more sense.
You can do this in lovable too now. But i dont think it gets used a lot. I think it is not very unique, i have seen bunch of providers, some are selling ai workers, some are selling internal tools in different shape and form.
I think the moat for internal tools is not where you think it is. Also, i see self host option, it is a nightmare too, no one will do it just for internal tools now. It was valid before AI era.
I am also seeing non engineering staff actually building tools with claudecode, paas like railway and stuff. People have become more efficient with engineer tools.
Fair, the generation part is commoditized. What we sell is the trust layer around company data. No credentials in the builder's hands, scoped access per tool, forkability etc. CC + Railway works until someone pastes a prod key into an env var.
[1] https://au.finance.yahoo.com/news/many-employees-ibm-2026-la...
reply