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

I haven't heard anyone talk about Windows containers in years, and that was actually a good thing. Let's just pretend they never existed.

> When an agent can generate a "scalable event-driven architecture" in 5 minutes

Currently they can't. Anyone with a basic understand of sw engineering will find numerous issues with the result of such a prompt within minutes.


But the product manager who asked for it won't realize that.

Unless you hire good TPMs!


If I would be the interviewer in this kind of situation, I would just follow up with something like this: "that might be a good option, but let's assume you need to build a tool to replace those excel sheets, ..."

Surprisingly often you do get an interviewee who just won't accept the premise of the hypothetical. I've had people get hung up on the equivalent of 'but I'd just use excel' even with prompting/nudging/explanation that this is an exercise.

I'm sometimes wondering if the AI content here really starts trending organically, or if it is somehow pushed by AI companies.

Not necessarily with bots, just posting a few links in a company Slack with the request for everyone to upvote it from their personal account could be enough.


It should be possible to directly compile this library to native code and use it in any other language. Maybe adding some C-style wrappers will be needed.

JSON, just use JSON. Or XML, if you don't like JSON.

JSON brings its own set of problems. for example, look at the python generated JSON below.

    >  >>> json.dumps({ "X" : 1 << 66 })
    > '{"X": 73786976294838206464}'
What's the parsing result in javascript ? What's the parsing result in Java ?

What's the difference to CSV?

  number,73786976294838206464

For CSV, I don't know how this comes out. It depends on the library/programming language. It might be 73786976294838210000 or it might throw an exception, or whatever. I'm just saying JSON will not solve your problems neither.

So it always depends on the implementation.

If you need something unambiguously specified, then XML with XSD is still a valid option. All number types are specified exactly, and you can use extensions for custom number types.


what's wrong with protobuf & friends ?

Nothing. Not a very good data exchange format though.

Switching from Word/Excel to LibreOffice is comparably easy. A lot of other Microsoft Products are much harder to get rid of.

I've never seen a European corporation that doesn't do user management with ActiveDirectory. Some still have it on their own Windows servers, but most browser based applications still go through Entra (Azure Cloud based AD). Just shut off their Entra/AAD and most of their software is blocked because nobody can log in.


This is the elephant in the room that most comments on this page miss. Office may be hard to replace, Teams maybe even harder, but the real pain comes when you touch identity and access management. The usual initial optimism that "yeah but [insert solution name here] does this, problem solved" dissolves very fast as you start going through the inventory of requirements for managing users, devices, authentication, etc.

It's not just the technical hurdle which maybe you'll whip your admins into finding workarounds (-keep praying that your admins don't leave because it will be painful to find replacements who understand and can maintain the spaghetti pasta monster your infra ended up being-). In overall non-technical organizations the user experience always ends up hobbled even just by asking people to keep track of multiple identities.

MS is still entrenched because they give a turnkey solution with Eeeeeverything™ and your CTO doesn't need to struggle with any uncertainty. SaaS made it so easy to just "outsource" everything to MS, they'll be responsible and accountable for operations, infra, security, processes, etc. Even less headache for your C-level people. See no evil, hear no evil, you pay MS to take the shit and your job is safe. If you throw a stone out the window you'll hit someone with general "MS administration" skills. And users are usually familiar with MS tools, Windows, Office, so they aren't bothered (you hear a lot of complaints about Teams on HN but not so much from normal users). So this covers the tech, the skills, and the UX.


> Office may be hard to replace, Teams maybe even harder.

It actually depends how you use it. If you use the shared online collaboration features (concurrent editing for example) it might be pretty hard since I do not know any other solution besides Google Workspace that can do that.

And Excel standalone I think is the hardest to replace if you have lots of macros with business logic inside them.

For Teams, as long as you use it for conferencing and chat (no file sharing or editing), you can replace it with Slack or whatever other solution might exist that has some feature parity.

IAM can stay MS, as it is a pretty battle tested solution on-prem and in the cloud. Or you move to something like Okta with a LDAP like backend where you manage users and groups.


> IAM can stay MS

That's leaving the most critical component still with a US company. Doesn't fly if the goal is what the Danish agency is trying to achieve.

> It actually depends how you use it.

Obviously but the larger the company, the more ways to use it, and one of those ways will be a nightmare to tackle. You want one solution, not a patchwork. So the one that does everything gets picked. MS throws everything and the kitchen sink in their ecosystem to fit every need even if sometimes at mediocre or crappy quality.

> For Teams, as long as you use it for conferencing and chat (no file sharing or editing), you can replace it with Slack

Taken in isolation you're right. But in a world of network effects every company, supplier, service provider you work with might use Teams and you can federate. Switch to Slack alone and you make your life harder.

I mentioned this in another comment, if protocols and formats were mandated to be open or interoperable (in practice) to allow usage in the public sector, replacing MS would be a notch or 2 simpler.


> That's leaving the most critical component still with a US company. Doesn't fly if the goal is what the Danish agency is trying to achieve.

Yes, because it is very hard to replace. I said that you could move to Okta or something similar (in this or in another comment), but this requires you have pretty modern apps that can integrate with SAML/OAuth/OIDC.

And, even staying with MS for a few more years while you migrate IAM to something else is not as bad as having the full Office stack. You can't just yank out everything overnight - I mean you could, but you have to spend a ton of money to have a 1:1 solution from the get-go.


> You can't just yank out everything overnight

Yeah, it's that transition period - "it's going to get worse before it gets any better" - that hurts the most and that everyone tries to avoid.


> IAM can stay MS

The idea is to move critical parts away from US companies.

The US shows hostility towards Europe, even threatened a military attack. So the goal is now to remove as much dependence as possible.

To claim Microsoft is a company and doesn't have to follow US government order is naive. US government is now routinely breaking the law, if they threaten Europe with military action, they can also threaten Microsoft with military/police action.


How does that matter? They said the same shit during the Nuremberg trials. You're encouraging bad behavior. You can't be submitting to illegal actions by rouge governments. You make everyone less safe when you do this.


Exactly. And if identity and access management is turned off, then nothing works anymore.

In the past there was a lot of Software directly installed to user's PCs and might have been authenticated without SSO. Also log in to a PC often works without identity management (cached credentials). But nowadays nearly everything is somehow in the browser and requires SSO.


Agreed, and even things like Keycloak/FreeIPA are only partial solutions.

FreeIPA in particular is a beast to maintain, it puts kubernetes-cowboys to shame.


One thing I noticed right away: They never mentioned they would take some inspiration from the submitted design, or acknowledge any specific detail. So they can't get sued for IP infringement later, if they ever build a ride that shares any design details with the "Quadroupler"

A lot of companies and organizations actually reply to letters/emails of any kind. Often very appropriately and not just with some boilerplate text.

I guess they have to deal with so many annoying complaints, so they are really happy if there is something joyful once in a while.


you can get a lifetime fan just by replying to a letter - like you see here. That's a very effective marketing.

I got a rejection letter once from a company I submitted my resume to (online) and I still remember that and in a positive light even though it was a rejection.

Now they just ghost you even if you went through 5 rounds of interviews and spend a bunch of your time.


> you can get a lifetime fan just by replying to a letter

Absolutely. But it doesn't increase next quarter's revenue. Which seems to be the main metric nowadays.


Probably a smart move. Writing and mailing a letter takes a lot more time and effort than a phone call or comment online. If a person took the time to write a letter, they're probably worth taking the time to respond to.

Maybe we need to let go of our auto-scaled 100 pod service mesh for a todo list app, and just deploy it bare metal on 2 servers.


You joke, but I remember seeing a talk by Wunderlist CTO who has pretty much that. Also polyglot company and microservices in random languages. Can't find the talk now, but https://www.infoq.com/news/2014/11/gotober-wunderlist-micros... mentions 60 services at least.

I need to get more ideas for my side project. A todo list app with micro services, but everything in bash scripts. So far it's just 6 services.

https://github.com/andi0b/vibe-todo


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

Search: