Hacker Newsnew | past | comments | ask | show | jobs | submit | sisve's commentslogin

Yeah. For me threatening to invade Greenland was a super red flag. I have not cared about US privacy & security laws. Even if people have talked about it and snowden exposed a lot, over a decade ago.

But by treating Greenland...

I see a real shift in the political environment from the EU [1]

1. https://www.reuters.com/world/europe/eu-is-crossroads-toward...


My _feeling_ is that a lot of EU/European politicians has talked a lot more about the need to be independent from the US after Trump threaten Greenland. At least in the nordic countries. Not only concerning data & privacy, but defence, communications, space etc. All areas. The wheel has started to turn. You will not see it if you look around. But in 10 years time, maybe more, Europe will have stopped depending on the US. And that will hit US hard. We pay a lot of money in services to the US.


The politicians can talk, but they needed to set up an environment that would've let a European company have a decent shot at competing with the best AI models. But they didn't. Should've thought of that before being proud of setting up those strict tech regulations.


That is not how EU does things. If you want no regulation and access to capital you should go to the US.

AI will take over a lot and the biggest AI company will be in US and China. But there will be room for Europe also on the top 10 list.

But there will be an environment that is creating sovereignty from US much more the before. We have learned our lesson


Will there be room for Europe though? Doesn't look like it based on other tech markets.


Even with e/os/ or another u De-googled version of android?

Not directly to you but in general: I do not think (most) of Europe is going the same direction as US. I actually see a lot of hope in response to EU leaders about digital infrastructure, communication & security. we have started to stop realing on America, but it will take 10-20 years before you see the entire crash trump made


Yea sorry I was speaking from the U.S. perspective. But still Europe is still involved in certain things like age gating. That is a clear sign that there are some entrenched interests that want to erode privacy on that front. I hope that moving away from U.S. corps for communication services happens. We (U.S.) really need a kick in the pants. I feel like there is authoritarian agendas everywhere now though.


I would like to see the prompt they are using. I asked CLaude to generate a password and email to a new user and im quite sure he used /dev/urandom in some way. I would expect most llm to do that as long as they have cli access


I think that is a bit to easy. MAY is described ar optional.

SHOULD - Should really be there. It's not MUST, you can ignore it but do not come crying if your email is not delivered to some of your customers ! you should have though about that before.


I moved everything on github to a self hosted foregjo instanse some days ago. I really did not do anything. Created some tokens so that CC could access github and forgejo and my dns API. Self hosting is so much simpler and easier with AI. Expect more people to self host small to medium stuff.


Ironic that that same AI you're mentioning is probably a large part of why this class of outages are increasing. Id highly recommend folks understand their infrastructure enough to setup/run it without AI before they put anything critical on it.


Sure. I can agree with that. At the same time, the reason people aren't doing it is not solely a skill issue. It's also a matter of time, energy, and what you want to prioritise.

I believe I have good enough control over it to fix issues that may arise. But then again, CC will probably do it faster. I will most likely not need to fix my own issues, but if needed, I think I will be able to.

"Critical" plays an important role in what you're saying. The true core of any business is something you should have good control over. You should also accept that less important parts are OK for AI to handle.

I think the non-critical part is a larger part than most people think.

We are lagging behind in understanding what AI can handle for us.

I'm an optimistic grey beard, even if the writing makes me sound like a naive youth :)


Yeah, once you start self-hosting your code, it’s kind of nice having control over everything. Makes you think about moving other stuff, like analytics, to something self-hosted too.


That is 100% true. You cant be fired for picking AWS... But I doubt its the best choice for most people. Sad but true


Schrodingers user;

Simultaneously too confused to be able to make their own UX choices, but smart enough to understand the backend of your infrastructure enough to know why it doesn't work and excuses you for it.


The morning national TV news (BBC) was interrupted with this as breaking news, and about how many services (specifically snapchat for some reason) are down because of problems with "Amazon's Web Services, reported on DownDetector"

I liked your point though!


Well, at that level of user they just know "the internet is acting up this morning"


I thought we didn't like when things were "too big to fail" (like the banks being bailed out because if we didn't the entire fabric of our economy would collapse; which emboldens them to take more risks and do it again).


A typical manager/customer understands just enough to ask their inferiors to make their f--- cloud platform work, why haven't you fixed it yet? I need it!

In technically sophisticated organizations, this disconnect simply floats to higher levels (e.g. CEO vs. CTO rather than middle manager vs. engineer).


You can't be fired, but you burn through your runway quicker. No matter which option you choose, there is some exothermic oxidative process involved.


AWS is smart enough to throw you a few mill credits to get you started.


MILL?!

I only got €100.000 bounded to a year, then a 20% discount for spend in the next year.

(I say "only" because that certainly would be a sweeter pill, €100.000 in "free" credits is enough to make you get hooked, because you can really feel the free-ness in the moment).


Mille is thousand in Latin so they might have meant a few thousand dollars.


Every one of the big hyperscalers has a big outage from time to time.

Unless you lose a significant amount of money per minute of downtime, there is no incentive to go multicloud.

And multicloud has its own issues.

In the end, you live with the fact that your service might be down a day or two per year.


> In the end, you live with the fact that your service might be down a day or two per year.

This is hilarious. In the 90s we used to have services which ran on machines in cupboards which would go down because the cleaner would unplug them. Even then a day or two per year would be unacceptable.


When we looked at this our conclusion was not multi cloud but local resiliency with cloud augmentation. We still had our own small data center


Usually, 2 founders creating a startup can't fire each other anyway so a bad decision can still be very bad for lots of people in this forum


Nope


shame, I remember having a lot of issues getting ts-lint to work with test runners a few years back.


Impressed with what Node is doing the last years, deno and bun has really made Node focus and improve. It was stuck for a while


What are the recent improvements in node itself?

Last actually note-worthy improvement I heard of was properly supporting import/export (although do you still need to use the .mjs hack?), but I've been out of the loop here for sometime so would be nice to know what they've added since.


Here’s a nice overview:

https://kashw1n.com/blog/nodejs-2025/

It doesn’t cover everything, but as an old-school Node user I found several interesting features I didn’t know about.


That is a nice article. It does a great job summing thing up with real examples too.


Small but lovely addition for me is the ability to load .env files natively. There’s more like this; small, focused, real-world-improving features.


> (although do you still need to use the .mjs hack?)

Syntax detection is enabled by default in v22.7.0, v20.19.0:

https://nodejs.org/api/packages.html#syntax-detection

Sounds like the obvious correct solution, making .cjs and .mjs obsolete - unless of course someone uses import() statements exclusively, in which case I need to ask: why?


It is surprising for me to see these features finally being added to Node after such a long time. Especially so when I remember reading discussion after discussion about how something like this wasn't possible. I touched on this in a blog post some time ago [1]. Glad Node is catching up.

[1] https://kilo.bytesize.xyz/an-incorrect-specification


I don't see in your blogpost any sources cited regarding anyone saying that ES modules were infeasible.

Additionally, io.js actually forked off due to internal drama which started with Ben Noordhuis having changed some pronouns here and there and people wanting to cancel him for that, to which he picked up his toys and left the sandbox.

It so happened that aside from being competent himself, he had competent people on his side, which eventually forced those governing Node.js to concede.

Bun is just a cash grab in comparison.


And for a few earlier versions `type: module` in package.json was all that was needed for .js files to be treated as ESM.


using, memory64, undici, async local storage, ESM import improvements, type stripping, local storage / session storage, env file support, built in file watching. Those are just the ones I mainly remember. There is a lot more.


Adding to the list: permissions, CLI styling/colouring, require(esm), globs, test runner.


Do you mean.. node-worthy?


They added type striping, not full TS support.

And the biggest issue with Node IMO is that the standard lib still forces you to rely on endless npm dependencies.

Node is still very much stuck.


> the standard lib still forces you to rely on endless npm dependencies

How? We have async/await file access, a async/await test runner, and even async/await sleep built in. What are you missing?


> What are you missing?

Everything else needed to make a backend app.

At the very least, Node should provide fundamental pieces like database drivers. Currently the best PG driver[1] depends on a single guy.

Bun already provides its own PG driver [2] and Jarred has written they will keep investing into more built-in APIs.

[1] https://github.com/porsager/postgres

[2] https://bun.com/docs/api/sql


> Currently the best PG driver[1] depends on a single guy.

Definitely a problem, but funding good Postgres/MongoDB/SQLite should be handled by AWS, Microsoft, Google, and other orgs that sell database services.


>> Currently the best PG driver[1] depends on a single guy.

> Definitely a problem, but funding good Postgres/MongoDB/SQLite should be handled by AWS, Microsoft, Google, and other orgs that sell database services.

A good chunk of PG development is done by employees of those companies (*). Of course they could (and probably should) always do more. But even if they invest more, it's not obvious that the marginal effort is best invested in some language's drivers...

Disclaimer: I'm paid by one of those big companies.


I’d argue that JS/TS is more popular than ‘some language’ would suggest. If there’s a problem that affects 19% of customers it should be fixed.

I am not saying this problem exists and 19% is a made up number, the grandparent post seems to think there is some kind of problem.


You don't think depending on dozens or even hundreds of NPM packages with a single maintainer is an issue?

Just as an example, Express depends on 25 modules with a single maintainer.

https://npmgraph.js.org/?q=express

Obviously a router is a fraction of what's needed for any non trivial backend project.


It's an issue, but not a new issue and not an issue introduced by NPM or introduced by package managers.

People were cuddling and pasting code from random people on the Internet they didn't understand for many years before package managers where there were zero maintainers. Many people that don't properly understand supply chain issues still are.


Maybe. Doesn't change the fact that the problem is there.


Have them though?

On the projects I am involved, they could even not exist, only node LTS releases matter, and the most recent projects are still node 20.


As a quick aside, “them” is an object pronoun, not a subject pronoun. The correct word you needed is “they”.

You couldn’t phrase your original question as a statement “Them have though.” That’s often a quick test for valid English grammar. With the correct pronoun, it makes more sense: “They have though.”

As another example, take this sentence: “Have you seen them though?”

“You” is the subject of that sentence, and “them” is the object.


Them is fine.

It's short for "Have them [Node bozos improved it], though?"

Or, equally likely it, refers to deno and bun ("deno and bun has really made Node focus and improve", "Have them (deno and bun) really made Node focus and improve, though?")


Your expanded version is also incorrect.


It's a common idiom used in slang and "urban" dialects for decades...

(Also the expansion was meant as a joke in case it went woooosh - I don't mind-read to know what the OP meant)


That is nonstandard English, at best. It's found in some uncommon dialects.

Without the expansion I don't know of any native English speaker who would say it.


22 is LTS. The future is now.


All even versions are LTS btw, maybe what you mean is that version 22 entered in maintenance mode (hence stable) and new features will not be added.


Sure, who is going to budget project upgrade effort of ensuring all dependencies work equally as well?

There is a reason why so many Java, Python, .NET/C#, C, C++,.. projects are stuck several versions behind.


No one said developing software wasn't going to be work.


Work isn't free beer in most places.


Did you do hot updates? I ser that is mention in the post, but I thought the community has walked away from it? Or at least that its mixed feelings about it?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: