But really, I wonder why it's not used more ? Price are maybe a bit high for some things ?
But really, I wonder why it's not used more ? Price are maybe a bit high for some things ?
Even now with cross-border selling, there are 27 different VAT codes to follow when transacting within Europe. Sure, you can report and actually settle it to a single national authority (and then that national process separately).
Unless a country will actually defer parts of its company and tax law to Brussels, for companies present in that country - then I just don't really see what this brings over just starting a limited company in another state (even outside of the EU) - as you'll still have to follow national law in the country where you're resident anyway, which could be anything.
(e.g. I start an Estonian OU with E residency, I live in Finland. I am obliged under Finnish law to submit a return for that company in Finland too as a person of control. In Finnish, along with the Estonian return, in Estonian)
I’m hoping they can be creative and find a way to distribute revenues to member states in a way that works for everyone.
For employment taxes, one way could be to tax EU-inc employees as if self-employed in their personal tax domicile.
Now, that may not work in all jurisdictions for reasons of local taxation etc (and you'll have to work out payroll tax, benefits etc) but that's almost never anything to do with the legal entity type!
The amount of founders who choose to domicile their company in Estonia because the ticket rates and ease look attractive and who don't understand that this will still need to be administered in their local market as a CFC (controlled foreign corporation) would probably say differently.
> Just choose a jurisdiction where investors understand how the legals work (Delaware C-corp, UK Ltd is OK too) and there's a finite administrative burden and/or commoditized tooling in place to help you handle it.
That's exactly what EU-INC is trying to provide/solve afaict.
What this means in workflow terms is that the bottleneck has moved, from writing the code to reviewing it. That's forward progress! But the disparity can be jarring when you have multiple thousands of lines of code generated every day and people are used to a review cycle based on tens or hundreds.
Some people try to make the argument that we can accept standards of code from AI that we wouldn't accept from a human, because it's the AI that's going to have to maintain it and make changes. I don't accept that: whether you're human or not it's always possible to produce write-only code, and even if the position is "if we get into difficulty we'll just have the agent rewrite it" that doesn't stop you getting into a tarpit in the first place. While we still have a need to understand how the systems we produce work, we need humans to be able to make changes and vouch for their behaviour, and that means producing code that follows our standards.
This helps both me and the next agent.
Using these tools has made me realise how much of the work we (or I) do is editing: simplifying the codebase to the clearest boundaries, focusing down the APIs of internal modules, actual testing (not just unit tests), managing emerging complexity with constant refactoring.
Currently, I think an LLM struggles with the subtlety and taste aspects of many of these tasks, but I’m not confident enough to say that this won’t change.
In my opinion, not everything requires a native app. AI Chat assistants are completely fine to be used in the web browser. for most used applications like slack, I do have native application( even slack which is website in a shell is completely usable as a desktop application). What i really don't understand is the benefit of a ChatGPT native application other than native widgets instead of web elements.
That said, I'm less and less bothered by an app that's Electron under the hood, but I think that's more to do with the quality bar for native apps slipping over the past few cycles (macOS) and forfeiting their advantage.
> Before the sacred, people lose all sense of power and all confidence; they occupy a powerless and humble attitude toward it. And yet no thing is sacred of itself, but by my declaring it sacred, by my declaration, my judgment, my bending the knee; in short, by my — conscience.
---
In any case, the "en-dash", as you seem to suggest, is not equivalent to the "em-dash", but typically used to express ranges or contrast between two words, i.e. "1990–1992" or "push–pull configuration".
In Robert Bringhurst's The Elements of Typographic style – pretty much a bible amongst typographers – he states:
We should “[u]se spaced en dashes – rather than close-set em dashes or spaced hyphens – to set off phrases.” Bringhurst then adds this devastating indictment:
The em dash is the nineteenth-century standard, still prescribed in many editorial style books, but the em dash is too long for use with the best text faces. Like the oversized space between sentences, it belongs to the padded and corseted aesthetic of Victorian typography.
For example:
* Object storage: lots of horror stories out there regarding flakey performance so hard to justify sticking mission critical stuff there.
* Private networking: Again, too many anecdotes about loss of service. Lots of people just using the public IP6 interfaces to avoid their private networking entirely. And private networks are IP4 only.
* Kubernetes CSI: I've had issues with this where a PV gets in some locked state and I can't remove from console.
I'd love to see more competition here.
The ones I'm affected by seemingly:
Still cheap compared to the performance + unmetered bandwidth, so I'm personally not super upset about it, my monthly bill in total goes up maybe 40-50 EUR in total, not that outrageous.Here is the full list of the updated prices: https://docs.hetzner.com/general/infrastructure-and-availabi...
Seems it's because of increased cost of hardware, and they seemingly tried to avoid increasing the prices but they couldn't. From the email:
> The underlying causes of the increased costs are, among others, the exploding demand for AI-related computing power and for cloud services. In addition, raw material prices and production costs have also generally risen for manufacturers. The costs for RAM and SSDs especially have risen by a large amount. For example, the cost for DRAM memory has increased up to 500% since September 2025. And according to market researchers like TrendForce, this price trend will continue throughout the year.
> We have genuinely tried hard to optimize our costs and to prevent increasing our prices for as long as possible. But we can no longer compensate for the strain that it has placed on our operations. We want to continue to deliver quality products that meet both our standards and your expectations, so we must take this step.