About 20 year ago I registered {lastname}.name and have dozens third level domains below it. So there are "privately owned" second level domains under .name for quite some time...
I'm working on same for my family since I want to properly degoogle a bit. One thing I think long term - if I give my kids first-name @ last name , that means that I forever hold power over their email. Which isn't great. But what's the alternative? Register one full domain name per kid? Even ignoring the cost, the ergonomics are awful.
Imho email is missing a feature for nameless email addresses for when somebody just buys their full name as a domain name. If I get "firstname-lastname.name", having the email be "firstname@firstname-lastname.name' kinda ruins it.
A child born today sees email like we see the telegraph...
they'll grumpily sign up to gmail just so they can get a verification email, and that'll be all it gets used for. Messaging their irl friends will be done in apps like Discord.
lol I ran a sizeable team around 2020 and I had to educate a couple of our new hires straight from college that they actually needed to check their work email, after they missed important HR related stuff and they had just completely not realized it was an avenue for company communication, with an assumption that everything was available on our heavily used slack.
tbh I'm with the zoomers on this one. Work email is 99% junk. Newsletters from every SaaS product we use, "A meeting started", invitations for calendar events that I can just accept ON the calendar, notifications for every transaction on every system ("X posted a comment on Y,") and spam from salespeople, recruiters, etc. And then 1% of it is actionable important stuff that I don't get through Slack.
Email died because of the junk/spam issue. And it's self-fulfilling - when most emails are junk, nobody sends a love-letter or party invitation by email because the recipient probably won't notice it, which in turn lowers the usefulness even further.
If email was a commercial product, the company would have done something about that. Email died because it was an open platform, with nobody to address this systematic issue.
They probably didn't realize why they needed multiple apps to communicate inside the company.
I was in a situation where we had slack for communication between teams, email for corporate stuff similar you described, zoom for calls, personal messengers like WA for communicating with people in the company who didn't have slack, SMS/phone calls for alerts and various on-call staff. Total nonsense. No surprise I missed something.
Funnily I did exactly this, so the {lastname}.name is now legacy for me and nobody else of my family ever picked up the offer to have {firstname}@{lastname}.name adresses anyway.
Later (but before my name change) I managed to secure {lastname}.de which I stupidly missed during the early internet due to being a stupid teenager with stupid convictions. If I had secured this back in the day I think they would happily started using it but now they are all too settled in their provider/free webmail addresses.
Nice twist: The father of my wife owned {newlastname}.de since the dawn of the internet. So I'm still fine on that front. ;)
Aside: I'm honestly bewildered that Google doesn't have the ability to handle that in gmail accounts. If somebody gets married or otherwise needs to change their name, their answer is "just make a new google account" when all your stuff is still tied to the old account.
They rolled this out in March this year in the US (and December last year in India).
I've successfully renamed an old account with an email address I no longer liked. It works quite well on everything 1st party, but does have the potential of causing issues with OAuth on poorly-coded websites that key on email instead of user ID (ie. most of them). You do get to keep your old email address though, so it still ends up working fine in practice.
The feature is about fifteen years too late for me, unfortunately. By this point I need this feature to let me "merge Google accounts". But then I barely use Google anything anymore anyways.
"Object thinking" by David West was eye opening about this back in the day. The gist is to model the objects not along the line of real world entities, but along the line of "behaviour" like you mention.
It’s ridiculous how far we have fallen behind the Terminal GUIs from the early 90ies. Look at the Turbo Pascal IDE and business apps built with it. Windows, window management, scrolling in windows, rich dialogs. Everything there. While many modern TUIs are just lists with numbers you can select. Everything is pretty rudimentary
I was missing a real terminal GUI library for some software I built. The rudimentary libraries did not work for me.
That‘s why I took Free Vision (the Turbo Vision derivative for Free Pascal) and ported it with the help of Claude Code over to modern Delphi, then modernised the object system and added lots of features and from there we ported it to go.
There are still lots of bugs and oversights (some caused by me not really knowing how original TV worked) that I fix as I go along using it for real projects.
They had bet 100% on it killing PA-RISC and DEC Alpha. They ported HP-UX, OpenVMS and NonStop to it. All 3 of them were tangled up in long running enterprise and government contracts.
They since discontinued HP-UX, offloaded OpenVMS and ported NonStop to x86-64.
Itanium was essentially (incompatible) PA-RISC 3 - it originated as HP project and the direction to totally replace HPPA with Itanium was there from the start.
Non-Stop got ported early on because they needed some hardware and clients were locked down.
OpenVMS customers however balked about shifting to Itanium given that it was often slower than their existing Alpha boxes, leading to HP being forced to finish EV7 work and release another generation of Alpha chips (funnily enough, EV7 might have forked and lived on in Opteron/K8...)
I just built one of those plant sets. I'm use to that modern instructions just place 1 or two bricks per step. But these plant sets took the cake. You had to build identical submodules. From the picture at the box you could see that it's essentially 8 times the same submodule. But the way the manual presented it was, that you build one submodule 2 times, fit it to the base, then build it 2 times again (same illustration!) and put them on the other side of the base. Then you start building the top and build the same submodule 2 times again, fit it to the top and then 2 times again and fit it to the other side of the top.
IIRC the Apple website used to use (client side image maps) them. But I suspect that was Mai my so they could do some research where users actually click on their screen.
Yes, but because CLIs came before TUIs/GUIs, I thought it only caught with CLIs until Unity (2011) adopted it for GUIs. Turns out there's been some GUIs that have used the term since Windows 3.1 and a TUI in 1988.
German here and me and my wife almost exclusively use Apple Maps, mainly because it looks and feels nicer. The differences in navigation are miniscule, but if we want to really check the traffic before we start we do a quick glance at Google maps.
One difference in navigation we noticed is, that Apple Maps gives some small local streets - those just one revel above "Feldwege" (agricultural/forestry roads) - more weight than they should have. They are not really "single track" (almost unheard of in Germany) but come close, with no lane delineation dashes, etc.
This is about what device you use to verify this. Currently, the ausweisapp on android allows you to authenticate to your authorities. However, this can also be done with a TAN generator and a user name and password like banks do.and them you dont need to depend on a trusted mobile phone.
reply