Intel and Nokia partnered around 2007 .. 09 to introduce x86 phone SoCs and the required software stack. Remember MeeGo? Nokia engineers were horrified by the power consumption and were convinced it wouldn't work. But Nokia management wanted to go to a dual supplier model instead of just relying on TI at all cost.
MeeGo proceeded far too slowly and Elop chose his former employers' Windows instead in 2011. Nokia's decline only increased and Intel hired many Nokia engineers.
Soon Nokia made no phone anymore and Intel did not even manage to make their first mass-selling product.
ARM-based SoCs were 10 years ahead in power saving. The ARM ecosystem did not make any fatal mistakes, Intel never caught up.
I used it as my first phone some 10 years. I type this message on one. I like their perseverance, but the truth is it's declining in practical usability.
Edit: In EU, so (lack of) bands are not an issue for me.
Depopulated sounds like nobody is living there, something like Pripyat. This town is said to have lost over 50% of its former 53,000 so still over 25,000 left. And apartments in GDR were rather small.
Not a native speaker, but is depopulated really the right word here or just clickbait? At least I was expecting something else. Heavily shrunk of course.
I guess the difference between "unpopulated" and "depopulated" is the former means no one at all, while the latter just means the population had a (meaningfully significant) decrease.
yes, as I said, it means a decrease, but the question of to what degree is unspecified. The assumption that it means to a near-zero degree is erroneous.
Not a web programmer, so know cross-domain only for hearsay :(
It does not seem to hinder e.g. Google using google.com, youtube.com, gmail.com, and several (many?) others to collect your data. Do you say security and privacy work differently here?
In those cases, the company controls all of the code running on those sites, so it's desirable for them to share data and cookies in particular. (e.g. any google.com site can read your login cookie)
In the case of user data domains, intentionally in the design of the service or via a security hole, users may be able to execute code and read cookies (e.g. in JavaScript on a page hosted on githubusercontent.com) and that's undesirable.
Sure, I see why as a company you don't want user data in your domain.
But if the different domain name gives good protection / isolation, why does Google still use completely different domains for different services with content controlled by them. I cannot believe they are interested in protecting users from data collection.
YouTube was an acquisition that they didn’t rebrand. Google Video was on google.com. gmail.com redirects to mail.google.com, and only email addresses use the gmail domain to avoid appearing to be google employee emails.
One reason why you should never think or say ghcr, but always github container register, even if that is longer. You should have enough time for not getting trapped.
Root cause a stupid FLA of course. For several months I thought it means Google whatever register.
I wrote my own init system in C from scratch some 13 years ago. It was more work than anticipated by myself and the manager who approved it. It served the purpose to bring up a Linux GUI and some backend for it on not so capable hardware in n seconds (don't remember n, but it was impressive).
It was a nice programming exercise. Wouldn't be suprised if even back then something like that already existed and the whole effort just demonstrated a lack of insight of what is readily available.
Probably the code still exists on some backup I should not have. Have not looked back and don't know... The company who owned the rights has gone out of business.
Edit: After typing this it came to my mind a colleague of mine wrote yet another init in the same company. Mine had no dependencies except libc and not many features. The new one was built around libevent, probably a bit more advanced.
Technically I have no big doubts about S3 Glacier.
But what happens if you don't use that stuff for a long time. You are in hospital when the bill needs to get paid. Your credit card gets stolen and the number needs to changed. Whatever personal crisis that you are not able to take care of life as usual for some weeks. They will just delete your data before you are back in business.
Does anyone know how long it takes, how many warning mails will come? I have very little data in AWS, but I more or less constantly feeling it might happen to me. Maybe not because of such big crisis, but just the simple fact that my bank will reject the automatic payment requiring a PSD2 second factor and I miss the email...
It takes a couple of months for an unpaid AWS account to get it suspended. Then you have 30 days to reactivate it. Then you have 90 days before the data are actually wiped from the Glacier. You have half a year, or maybe more, to get your backup data.
The price of Glacier Deep Archive is roughly $1/mo per terabyte. (I struggled to produce 500 GB of photos in 15 years.) Set up a dedicated AWS account, put $50 on it, set up a yearly auto-payment of $10, and you're likely safe for several years of nonpayment.
Retrieval is not free though, something like $20-40 for retrieval from tape, and about $90 for a terabyte of egress traffic. Okay for the rare occasion of a full restore.
Backblaze B2 is $6/mo per terabyte, and they only give you 44 days of grace period before deletion for nonpayment. But the traffic is free either way, up to 3x the amount stored per month. They are good for frequent full backups, and for doing full restores periodically.
Yeah I stopped paying for my AWS domain, and they kept sending me new invoice every month for 2 years. (last month I paid all ~24 invoices and deleted the domain).
MeeGo proceeded far too slowly and Elop chose his former employers' Windows instead in 2011. Nokia's decline only increased and Intel hired many Nokia engineers.
Soon Nokia made no phone anymore and Intel did not even manage to make their first mass-selling product.
ARM-based SoCs were 10 years ahead in power saving. The ARM ecosystem did not make any fatal mistakes, Intel never caught up.
reply