Nokia had the best hardware in the world but a terrible outdated OS. Then Microsoft came and killed the best hardware and replaced the OS with an even worse one.
Depends on what OS you mean - if Symbian then you are right, but Maemo/MeeGo/Harmattan were far ahead of their time.
Yes. I had a N900 and it was brilliant. Then when that OS was killed I got a Jolla.
For still images, there is no more robust way of preserving them than prints. Anything that requires ongoing maintenance is unlikely to survive even a century.
Nokia had the best hardware in the world but a terrible outdated OS. Then Microsoft came and killed the best hardware and replaced the OS with an even worse one.
The 68000 design is lacking the necessary parts for accessing an address and having the OS recover and handle it when it is pointing to void and nothing or just a part of the address map where nothing lives.
The 68010 added the necessary states and instruction to work together with an external MMU to do this.
The other interesting solution was to run _2_ 68000 cpus in lockstep where the hw was designed to detect this and switch to the other cpu to run the offending instruction (there would obviously have to be some cleanup and mapping change before it could do so). Can't remember the name of the system that did it, but it was a Unix-like IIRC. Someone will now find a link to it in 5... 4... 3...
As someone who actually uses SourceForge in the way it was originally intended, i.e. a place to host one of my software projects, this is certainly something I would not want to happen. What is a good alternative? Right now I mostly put release tarballs on SourceForge, the git repository and wiki pages have already moved to GitHub.
Of course, the speed of light in air is faster than the speed of light in fiber. Duh. It still doesn't make a lot of sense, since most of the latency on the Internet comes from buffering and processing in network equipment.
As vi/vim usually comes with the base OS by default (especially Unix - i.e. non-Linux - systems), knowing both editors (as I do) is preferable. For most programming work or complicated file edits, I generally use emacs though - since the late 1980s - my current.emacs config file is from 1990 - and, yes, I'm old.
That's exactly why I switched to vi (not vim at that time) in 1995 after using Emacs exclusively since the 80s: I knew it would be available everywhere. I still use Emacs occasionally.
I'm 50, that's not old.
That's fine, if you want to live in a third-world nation where you can't rely on having power. You know, the kind of place where you can't run a modern, high-tech economy that depends on reliable supplies of electricity.
I save old CDs and DVDs. About this time of year, I take several and drill a small hole near the edge of each disc. Using kite twine, I then hang them from my fruit trees and grape vines to scare birds away.
And the birds go "Aah! The AOL disks are coming! The AOL disks are coming!"
You are costing the website money, as they have to pay to send every byte to you.
Sure, and it costs money to broadcast commercials to TV viewers. That doesn't in any way change the fact that it is the viewers that are the product.
A simple solution for web sites who want to display content only to visitors who also view ads is to use an ad wall that the visitors are forced to endure before they are allowed inside.
You know what ACTUAL theft is? Consuming someone's product (ie. visiting an ad-supported web site) and then refusing to pay (ie. allow the ads to be shown). If you want a moral and ethical ad-blocker, implement a plug-in that refuses to let you visit any site whose ads you don't want displayed, or which allows you to pay micro-payments per visit.
When you visit an ad-supported web site, the web site is not the product, you are. Refusing to be the product is not theft.
Try to compile an OS with a C compiler and see if it fits on a floppy...
Here's my old "Ulric's Router Construction Kit", a single-floppy Linux distribution. Of course, Linux is an OS compiled with a C compiler. At the time there were a bunch of such mini-distributions, I'm not so sure it would be possible today.
http://siag.nu/urck/
I had mod points yesterday, but not today, so here's a reply instead of the "+1 insightful" you deserve. IPv6 does unsolve problems that already have solutions in IPv4. *cough* DHCP *cough* indeed.
I can virtually guarantee if you were inventing the first character set today, with no backward-compatibility constraints and no knowledge of the real world's history of keyboarding, you would not include a tab key.
An indentation level key. I think I would like that. Put it on the list. Scroll Lock on the other hand...
Slashdot Mirror
Nokia had the best hardware in the world but a terrible outdated OS. Then Microsoft came and killed the best hardware and replaced the OS with an even worse one.
Depends on what OS you mean - if Symbian then you are right, but Maemo/MeeGo/Harmattan were far ahead of their time.
Yes. I had a N900 and it was brilliant. Then when that OS was killed I got a Jolla.
For still images, there is no more robust way of preserving them than prints. Anything that requires ongoing maintenance is unlikely to survive even a century.
Nokia had the best hardware in the world but a terrible outdated OS. Then Microsoft came and killed the best hardware and replaced the OS with an even worse one.
This might sound strange, but I sure wish the younger generations would get over themselves and "grow up".
No, I think this more has to do with a combination of hubris and Red Hat capturing a number of open source utility projects.
Yes.
"As usual, Lore Harp McGovern remained fearless: her very next venture pioneered a disposable device that allowed women to urinate standing up."
I thought they were going to drop Artificial Intelligence into cereal.
First level support have a script which their employer tells them to follow. Let them do that or you derail the process.
The 68000 design is lacking the necessary parts for accessing an address and having the OS recover and handle it when it is pointing to void and nothing or just a part of the address map where nothing lives.
The 68010 added the necessary states and instruction to work together with an external MMU to do this. The other interesting solution was to run _2_ 68000 cpus in lockstep where the hw was designed to detect this and switch to the other cpu to run the offending instruction (there would obviously have to be some cleanup and mapping change before it could do so). Can't remember the name of the system that did it, but it was a Unix-like IIRC. Someone will now find a link to it in 5... 4... 3...
Early Apollo workstations.
Are they self-driving?
*whoosh*
As someone who actually uses SourceForge in the way it was originally intended, i.e. a place to host one of my software projects, this is certainly something I would not want to happen. What is a good alternative? Right now I mostly put release tarballs on SourceForge, the git repository and wiki pages have already moved to GitHub.
I'd mod you -1 redundant if I had mod points.
Of course, the speed of light in air is faster than the speed of light in fiber. Duh. It still doesn't make a lot of sense, since most of the latency on the Internet comes from buffering and processing in network equipment.
I don't see how this is any more "speed-of-light" than the light travelling in a buried fiber.
Actually, this program, if anybody remembers it, had Emacs keybindings just because that's what I was used to.
As vi/vim usually comes with the base OS by default (especially Unix - i.e. non-Linux - systems), knowing both editors (as I do) is preferable. For most programming work or complicated file edits, I generally use emacs though - since the late 1980s - my current .emacs config file is from 1990 - and, yes, I'm old.
That's exactly why I switched to vi (not vim at that time) in 1995 after using Emacs exclusively since the 80s: I knew it would be available everywhere. I still use Emacs occasionally. I'm 50, that's not old.
That's fine, if you want to live in a third-world nation where you can't rely on having power. You know, the kind of place where you can't run a modern, high-tech economy that depends on reliable supplies of electricity.
Like Denmark.
I save old CDs and DVDs. About this time of year, I take several and drill a small hole near the edge of each disc. Using kite twine, I then hang them from my fruit trees and grape vines to scare birds away.
And the birds go "Aah! The AOL disks are coming! The AOL disks are coming!"
Software should be distributed as hex code in magazines, to be typed in by the users.
You are costing the website money, as they have to pay to send every byte to you.
Sure, and it costs money to broadcast commercials to TV viewers. That doesn't in any way change the fact that it is the viewers that are the product. A simple solution for web sites who want to display content only to visitors who also view ads is to use an ad wall that the visitors are forced to endure before they are allowed inside.
You know what ACTUAL theft is? Consuming someone's product (ie. visiting an ad-supported web site) and then refusing to pay (ie. allow the ads to be shown). If you want a moral and ethical ad-blocker, implement a plug-in that refuses to let you visit any site whose ads you don't want displayed, or which allows you to pay micro-payments per visit.
When you visit an ad-supported web site, the web site is not the product, you are. Refusing to be the product is not theft.
Try to compile an OS with a C compiler and see if it fits on a floppy...
Here's my old "Ulric's Router Construction Kit", a single-floppy Linux distribution. Of course, Linux is an OS compiled with a C compiler. At the time there were a bunch of such mini-distributions, I'm not so sure it would be possible today. http://siag.nu/urck/
I had mod points yesterday, but not today, so here's a reply instead of the "+1 insightful" you deserve. IPv6 does unsolve problems that already have solutions in IPv4. *cough* DHCP *cough* indeed.
Because code that looks like this is more readable than code that looks like this.
The examples violate the simple rule "tabs for indentation, spaces for alignment".
I can virtually guarantee if you were inventing the first character set today, with no backward-compatibility constraints and no knowledge of the real world's history of keyboarding, you would not include a tab key.
An indentation level key. I think I would like that. Put it on the list. Scroll Lock on the other hand...