41 karma · joined February 12, 2017
Many cheaper laptops still have replaceable RAM, WiFi, cell modem, SSD, optical drive, battery.
A few models still come with socketed, upgradable CPUs. These days the 14nm desktop CPUs are efficient enough for laptop use.
Last year I had a consulting gig in a Europe based company, with offices next to a big airport. As summer was slow anyway I'd work 30h weeks (invoicing four 7.5 hour work days) Tuesday - Thursday, and spend the other 4 days at a beach in Ibiza, Bulgaria or Cape Verde (with occasional remote login to take care of emergencies).
But in practice, I guess this legacy architecture adds a nanosecond or two to a thread switch. Is that a big deal? How many switches does a desktop PC do in a second? How about an AWS/Azure/GCP server?
I've never experienced lag in a game or app or web server due to slow thread switch. Server side async is on the rise anyway, minimizing number of threads and switches.
The original bacteria CRISPR can only cut off pre-defined sequences, but the artificial gene tech CRISPR can add and edit as well. I'm wondering if the later two modes are the sources of the genome damage.
The thing is I'm often looking at the horses and they are looking at me :)
1. Need investment
2. Have a product to sell
Currently carbon nanotubes firms/departments fill neither case. They have enough money, because of all the hype and they don't have a product, as there's still no known way to mass produce.
In a few years, once price efficient nanotube fabs come online, IMHO we'll see tons of amazing, ground-braking products out.
As most other things it comes to passion. If you literally write C in your dreams and spend every waking hour hacking OS kernels you'll get to be very good.
Even if they could do Maemo, there would've been no apps - Microsoft failed to attract enough devs, given that there were already 10M .NET devs out there.
They were doomed by the Symbian technical debt. When the iPhone came out, a very smart person posted a comment on HN saying Nokia is dead and he was right I guess :)
The same happened in Japan and Europe, their best CS people failed to deliver the promised Prolog AIs.