The language api is somewhat inconsistent due to legacy weaknesses and compatibility.
That said, I prefer old-style PHP (like it was written in version 5ish) instead of the new object orienteted/composer/micro-library stuff (that I consider the javascript virus).
Having moved away from PHP a decade ago, I recently had to update some old code (that I had written originally). And even with almost a decade of not using php, the experience was pleasurable enough.
As a senior the TLDR is: The PHP language itself is fine, the actual code base itself means more (and can either be fine or not), but in the end it is the work environment (do you like your coworkers, bosses and are the time constraints reasonable) that mean the most.
Regarding your CV, I would always prefer a candidate with production experiences in (at least) two different environments to a "one trick pony", so I have a hard time seeing that it could hurt you.
I have my own domain (that I share with relatives), and use mailbox.org for hosting it.
I chose them after a rather lengthy search.
Reasons for choosing them(pros)
- multiple "payment accounts" can share the same domain (securely), which was my primary reason for choosing them.
I.e. I cannot access my brother's mail in any way, even if we share the same domain, because he is his own admin.
- you can pay extra for more space (i.e. additional storage on a per gigabyte basis)
- extra "domains" and "aliases" for the mailboxes are possible and free (for a given number dependent on your subscription level)
- German company (i.e. EU company, which I care a lot about).
- They seem like an old-fashioned unix company that respect privacy, so my risk of being data harvested or used for ai training seems miniscule
- They seem to be financially stable and (if I remember correctly) around 40 employees which is a reasonable size
- They have a full online office suit (which I do not use)
Reasons not to (cons)
- you pay per mailbox, not per domain
- their business plans starts to expensive for my taste (so my business domain is at another hoster) as the business is basically revenueless currently. Shouldn't be a problem, if the business is "real".
I want to stress, that I am only a customer, no partner or affiliate or receive any benefit of writing this.
One, in Denmark, we have a system called MitID (basically SSO login for public services (and private services can use it too). Even though there are other options (hardware totp dongle and such), most people have the app installed - I would guess easily over 90% (over the age of 13).
Your reply is (respectfully) analog to : "Why do I care about this ssh security thing? I have always used telnet and it works fine."
In X11, there is the underlying expection is, that no program will misbehave evilly - and THAT has changed in Wayland and hence a lot of wayland is much more complicated and (some of it) unfinished.
A lot of "traffic copping" added, ensuring that the user is queried before privileged access is granted, the ability to capture raw video output of a window for example (through desktop portals) - or the ability to capture raw key strokes from another process windows (think password prompt).
I have been running Sway (on wayland obviously) for 18 months with almost zero issues.
LLM: "... (danefæ refers to good weather or fine days)"
Me: really not, it refers to the law that all significant finds (historically or financially) from the ground belongs to the state, but the finder receives a finder's fee.
I haven't read the articles line by line, just skimmed the headlines and the two above really stands out as really wrong..
I can't read the article due to the paywall, but the correct word in the headline would be "sawdust" (not that it makes any sense without context, it is not a common danish saying).
In Denmark, we have a common login system called MitID (translated: MyID), which is used by all bank, insurance company, the governmental digital mail system (not email, but pdf's in a vault) and it still-alive now-commercial-only predecessor. I believe it is by law.
The system is 2FA with either your phone or a hardware dongle proving your identity.
It is strongly authenticating you as a person, that is precisely identified (but the services are only getting a token, but it can also validate your person-number - think SSN in US context).
It is quite harsh in device security, recently failing on beta versions of Android - on top of afaik always failing on rooted devices...
The phone version also requires you to scan a continuously changing qr-code twice to proceed, which is shown when you need to identify yourself (in an I-frame). This is to ensure you are "physically" present where you are being authenticated (i.e. to block of some phone scams).
Works pretty well and is reasonable secure, whilst still having some flaws..
In the future, I believe this system will work in some/all of the EU due to the coming eIDAS legislation...
