rawfan

.io is the country domain of the British Indian Ocean territories which will soon seize to exist.

So just speaking as a user: Outlook is the crappiest email client on the planet, but it’s the best calendar I have seen so far. I haven’t been able to replicate with OSS, what I experience now in this corporate environment. Everything just works and is well integrated. I can easily see availabilities of co-workers before inviting them to meetings. I can easily share certain aspects of my own calendar with some or all co-workers (only availability, titles, full event content). I can hand my calendar over to be managed by someone else and it will be clear that I did so (A invited you on behalf of B).

All these things just work.

I applaud the work to start a good OSS calendar implementation, but what I‘m actually missing is a corresponding OSS server side that does all these things I‘ve seen in the enterprise.

There is no one here that doubts the renewable future and we‘re quite sure we can finish building the necessary grid until the end of the decade (with around 6 times the capacity of the current European grid).

I also think these features have a place. I'm quite sad that Kong completely destroyed all trust our company had in them.

Generally, though, I always try to get any English layout, instead of a European one and map as I desire. For macs that would be English International.

That is not at all the same as building an iOS client using an API as a one man show (or 1-3) and directly selling that.

So whenever people authenticate using a FIDO2 key as their passkey, they also need to enter its password.

The benefit of passkeys are:

- the Webapps only store a specific public key instead of a hashed password

- a direct connection is necessary for the challenge/response flow so that phishing attacks or MITM are impossible (AFAIK)

Seriously, though, I myself work for an enterprise that runs big parts of the European energy grid and we use Laravel for all sorts of stuff. At a previous job Laravel powered a whole ISP.

Notice when people say Laravel is good for small stuff and early prototypes, they never explain why.

Of course it’s pure luck that these boots fit me perfectly.

The problem IMO is, that on the corporate side, you often don’t have any IT knowledge at all. So they hire consultants to ask them what to do and don’t have any way of confirming if what they are being told is sane advice.

I’m also really shocked by what the likes of McKinsey of Accenture get away with regarding the quality of people they send.

Edit: I guess I misunderstood “high-end” and thought of “large” consulting firms, because those are the ones that pretty much always suck. I’ve had wonderful experiences with small consultancies.

E.g. if you're building some kind of file system access and know you want different "drivers" (e.g. local, Dropbox, Google Drive), using an adapter pattern is fine. If you just need local access right now, don't waste your time. Refactor later if needed.