They are still suitable for various small embedded solutions. Not every computing task requires petaflop performance.
I'm not saying that the Raspberry Pi is the ideal solution, but sometimes the most amazing solutions comes out of implementations made on low performance devices while high performance devices instead allows for bloatware.
I think that the abolishing of the Net Neutrality has essentially caused the FCC to get a hard time trying to control the states trying to enforce the Net Neutrality by state.
The end result may be that the FCC loses control completely and that the networks ends up being under state legislation instead.
I don't see a problem when it comes to beta sites, but for full production the site has to be W3C compliant, just use the HTML and CSS validators to ensure that the site follows all standards. But when it comes to JavaScript then it's a headache of its own, primarily on Microsoft browsers where those browsers have a tendency to do things differently.
But a site that depends on JavaScript is in general a pretty crappy site.
At least not with the attack style that works on Intel processors, but I wouldn't be surprised if there are similar methods that works on AMD processors.
But older architectures has other kinds of security gaps instead. So going back isn't going to help either.
And today we essentially only have ARM and x86 architectures to care about. Sparc is a fringe architecture, so is PowerPC and MIPS, which means that it really doesn't matter if these architectures are impacted or not.
This isn't even surprising that the problem exists in almost every CPU since a long time considering that most CPUs share the same type of logic in order to achieve the best performance. But performance and security often comes into conflict.
It all depends on your application if this is going to be a real issue or not. For massive calculation computers already isolated from external influence this is a non-issue but for most computers used for home, office and gaming this is a considerable issue.
And one way around it was to declare the function before it was used - that did help a bit sometimes. Not always, but sometimes - and depending on compiler.
But Pascal, C, Java, C++ and Ada all belong to the same programming paradigm, with or without the object orientation twist.
Then we have Basic and Fortran which sometimes have the paradigms from Pascal et.al. but also other ways not related to them.
Cobol is in turn an animal of itself.
And then you can turn to Erlang, Haskell and Prolog for yet another way to do things.
Different languages allow for different language-specific bugs.
However the worst bugs aren't the language specific bugs - it's system design bugs where the designer don't understand the business case that shall be solved.
The programming language bugs are usually found either by hand or by tools like FindBugs, Splint and other similar tools. But system design bugs are all in the brain of people - and some people have a very strange brain wiring resulting in "perfect solutions on non-existing problems".
Slashdot Mirror
With no network connection it's not possible to do a remote access to log out the users.
And if the visits are frequent enough then it would be pretty stressful.
Remember that the tax authorities always are right even if they are wrong.
How come that I'm not at all surprised by the bikes showing up at Burning Man?
Not to mention the amount of driver distraction it would cause. I'd expect legislation soon to take care of this.
Tell that to the people in Norway that recently turned off the FM net and now only offers DAB.
Even nicer if it was MP/M. Or OS8MT.
In Soviet Russia Olympians makes you.
If you learn to make a solution on a low performance device then you will become a better coder less prone to make inefficient solutions.
You can always make something that works, but to do something efficient takes skill.
They are still suitable for various small embedded solutions. Not every computing task requires petaflop performance.
I'm not saying that the Raspberry Pi is the ideal solution, but sometimes the most amazing solutions comes out of implementations made on low performance devices while high performance devices instead allows for bloatware.
I just tells you to not add any music to your videos. Many videos that have music added is actually pretty annoying.
Good luck with wave form identification on white noise.
I think that the abolishing of the Net Neutrality has essentially caused the FCC to get a hard time trying to control the states trying to enforce the Net Neutrality by state.
The end result may be that the FCC loses control completely and that the networks ends up being under state legislation instead.
How about the PEP mode that the Trailblazer modems had?
These days if you want a modem with some performance you'd have to get a Pactor 4 modem. Or if you want to get really slow, go JT-65.
My broadband supplier is soon upgrading me from 10/100 to 100/100 since that's their lowest offering on media I have. That's sufficient for my needs.
Which means a lot of ATMs out there. Maybe a few voting machines too? Could be fun at the mid term election in the US.
I was waiting for this.
Unpatched Win7 running on Atom? Can it get slower?
I don't see a problem when it comes to beta sites, but for full production the site has to be W3C compliant, just use the HTML and CSS validators to ensure that the site follows all standards. But when it comes to JavaScript then it's a headache of its own, primarily on Microsoft browsers where those browsers have a tendency to do things differently.
But a site that depends on JavaScript is in general a pretty crappy site.
Probably more like "not possible to fix fully with software".
At least not with the attack style that works on Intel processors, but I wouldn't be surprised if there are similar methods that works on AMD processors.
But older architectures has other kinds of security gaps instead. So going back isn't going to help either.
And today we essentially only have ARM and x86 architectures to care about. Sparc is a fringe architecture, so is PowerPC and MIPS, which means that it really doesn't matter if these architectures are impacted or not.
This isn't even surprising that the problem exists in almost every CPU since a long time considering that most CPUs share the same type of logic in order to achieve the best performance. But performance and security often comes into conflict.
Thanks! I got badly confused myself.
It all depends on your application if this is going to be a real issue or not. For massive calculation computers already isolated from external influence this is a non-issue but for most computers used for home, office and gaming this is a considerable issue.
And one way around it was to declare the function before it was used - that did help a bit sometimes. Not always, but sometimes - and depending on compiler.
But Pascal, C, Java, C++ and Ada all belong to the same programming paradigm, with or without the object orientation twist.
Then we have Basic and Fortran which sometimes have the paradigms from Pascal et.al. but also other ways not related to them.
Cobol is in turn an animal of itself.
And then you can turn to Erlang, Haskell and Prolog for yet another way to do things.
Different languages allow for different language-specific bugs.
However the worst bugs aren't the language specific bugs - it's system design bugs where the designer don't understand the business case that shall be solved.
The programming language bugs are usually found either by hand or by tools like FindBugs, Splint and other similar tools. But system design bugs are all in the brain of people - and some people have a very strange brain wiring resulting in "perfect solutions on non-existing problems".