When were the first 1280x1024? My memory places it about 20 years ago, and I had one.
They were around in 94, but they were relatively expensive and rare. That res usually required a fancier video card too to get a better DAC.
And multi monitors required non mainstream video cards too back then (not anymore).
And my most recent work computer has fewer pixels than that monitor did.
Ouch. My sympathies. Our oldest lowest specced PCs here now have dual monitors with the smallest one at 1280x1024.
But think what your small cheapo monitor costs now in real terms compared to what 1280x1024 did in 1994. Your workplaces relative budgets are very different.
Speak for yourself. You must've been in a very rarified environment.
20 years ago I was AutoCAD drafting at 1024x768 on a flickery 15" monitor. Not pleasant at all, but every one else in the office was on 14" monitors at 640x480 or 800x600 and weren't even aware of higher resoltions - at least they weren't as flickery at those lower resolutions.
Today my 27" 2560x1440 monitor at home cost about the same as that old 15" CRT. And the multicore SSD equipped 15" laptop it's plugged into does 1920x1080. Both screens have way better image quality and zero flicker.
20 years ago I was using VB 3 or 4, VBA, or writing AutoLisp macros in Notepad. Yuck.
20 years ago we were still getting 486s and a Pentium was well out of my employers price range. SMP machines were still exotic things to dream about. Although only a few years after that I was using a dual socket PII 266 with a whopping 128MB (whoa!).
Scala also runs on the JVM, so it's fast as opposed to Python.
It's probably wan't your intention, but you make it sound like it is the running on the JVM part that makes Scala fast, rather than Scalas design and implementation eg static typing etc.
By itself, just running on the JVM is not some magic fairy dust that's enough to make highly dynamic languages run like Scala. ie most of the time Jython is actually slower than CPython.
Date of project/company founding? Date of first public announcement? Date of first public 0.x release? Date of first 1.x release?
As far as I can tell, they both had various milestones before the other and their initial development overlapped somewhat - eg Debian started first and (probably) got prereleases out earlier, but Redhat got to 1.x quicker. But I can't see any way to claim Redhat was around long before Debian.
All these people complaiing about how "horribly corrupt" the US government are are just playing a huge round of "First World Problems". The US is #19 on the Transparency International list.
Changing the topic slightly...
Kim Dotcom's extradition hearings are being held in a country that's first equal on that list. And whose courts are not automatically bending over to take the various government agencies purely on their word. He's getting plenty of opportunity to defend himself.
If he does still get extradited, he's going to have a hard time claiming it was due to corruption. No doubt he will try though.
Not really, there's also Dart, an actually forward-looking systems language with a lot of real thought behind it. But nobody pays attention to that, because it's not by Apple or Google. Far better to keep favoring whatever Google's current ga-ga for
Dart is a Javascript replacement and is by Google. Maybe you meant Rust or something else?
This whole cloud thing will blow over. As someone already noted, if you replace "cloud" with "other people's servers" it sounds a lot less appealing and a lot less manageable.
Isn't the point of deploying OpenStack yourself that "cloud" != "other people's servers"?
Its called exaggeration. If I must spell it out, it was to highlight the absurdity by contrasting the nonfree IIS / schannel (not vulnerable to the biggest security flaw in a decade) with the free OpenSSL (vulnerable).
Well if you're going to exaggerate to the point of bullshit, then you could just have easily made it a 'Free' vs 'Open' ideological argument.
And then your inner RMS would claim that none of the GPL licensed (or dual licensed) libraries (gnutls, polarssl, jsse) leaked private keys while the biggest BSD licensed one did. Thus proving the technical superiority of code written using the GPL.
I like the standard keys. And really, just because one manufacturer happened to use a defective part, we lose them? Key switches have been around for decade and are reliable. Just fix the reliability issue in that one model and that's it.
Another reason I like having an older car with a plain old stainless steel non electronic key. I can just hang it around my neck under my wetsuit when I go surfing and leave the car locked.
Those with newer cars are hiding their keys in wheelwells etc while hoping nobody nefarious is watching, or having to use annoying lockboxes to put their keys in.
Probably not a big deal for the average slashdotter though.
You're 55 and have no kids? You've failed your (biological) purpose in life, which is to have kids. You're too old for that now so you can't make amends once you get truly old and start having regrets about not creating life and instead just spending it all on yourself.
I say this as a parent* myself... fuck off!
There are plenty of perfectly valid reasons for not having kids, and plenty of people that want them but can't have them.
I understand their personal motivations, but everyone has to understand that this does not make the OpenSSL ecosystem safer, it only makes the OpenBSD specific port of OpenSSL safer. The rest of the world will still be subject to any vulnerabilities and shortcomings in the code, because they are not intent on contributing this code back to OpenSSL.
While you are correct (for now), you're not thinking far enough ahead. I reckon a year or two down the road there will be a portable version of this library just like what happened with OpenSSH when they forked SSH for themselves. ie OpenBSD becomes the new upstream for libssl rather than the existing OpenSSL team.
There is a reasonable chance the portable version of the fork could eventually end up taking over from OpenSSL by default on the other BSDs and some Linux distros.
Seriously, could they screw the pooch any harder than they are right now?
Hundreds of commits, after just *DAYS* of testing? I've never seen a faster or more reckless release cycle for code changes, ever.
This just tells me they are putting in hundreds of basically untested code changes, which is what got us into this mess in the first place.
OpenSSL is dead to me now.
Let me guess... someone else who thinks that the OpenBSD team and the OpenSSL team are the same people?
Hint: they're not. This is a fork of the OpenSSL libraries used in OpenBSD and not intended for anyone else. If after some time it stabilises and turns out to be a good move (I'm guessing it will), then some other people are likely going to want to maintain a portable version that can be used on other platforms - just like what happens with openssh plus the odd other project eg openntpd.
I think the grandparent was right. MS now is hugely better than the MS of 10-15 years ago. I'm not going to try and objectively prove that as I don't care enough about MS and probably couldn't anyway.
But the NT4 to XP/2003 era was appalling security wise - but they changed that. IIS went from swiss cheese to one of the tougher web servers to break. You just don't hear any more about the kinds of problems they used to have. If you endured those days or just laughed from the sidelines, you don't need any hard data to see that they have improved a lot.
I found this paper from Theo de Raadt illuminating though. He steps through 10+ years of OS hardening techniques OpenBSD has put in place to prevent badly written applications misbehaving. Towards the end he summarises how other platforms do this stuff - the only other platform that did it all by default was Windows (yikes!).
All this episode does is to remind us that security is hard. Encryption is even harder.
In general maybe. This issue had nothing to do with encryption though (or hard security stuff even).
It was a very basic input checking error in a massively crusty overly obfuscated and badly written/documented codebase that all kinds of people have been tacking 'kitchen sink' style features onto for years. It's almost as if the codebase is actively trying to counteract the 'many eyes' effect.
OpenBSD has already taken on their fork and started stripping out cruft - who knows that fork could end up having a portable version that everyone else starts using (like with OpenSSH).
Companies like Google and RedHat etc are presumably going to be putting some extra resources into OpenSSL to help clean it up. It's importance means they would be crazy not to. Hopefully they also put some resources into funding/helping the OpenBSD fork too as a better longer term option.
Climate change is to actual environmental science while Jenny McCarthy is to Vaccines. The real truth is being subverted by the Al Gore et al bs that serves no one but a few corps.
So... are you saying that climate change claims that actual environmental science causes autism?
Nah, that can't be it - I'm not sure climate change actually claims anything itself. Although Anthropomorphised Global Warming does have a nice ring to it.
Hmmm... thinking about it some more, I suspect you are cleverly using autism as more of a metaphor here (or is that a simile?).
So you must really be saying that the only research that ever backed climate change was a fraudulent discredited study by Al Gore and his corporate conflicts of interest? And a significant percentage of the public is swayed by misguided celebrity followers of Al Gore all the while ignoring the existing research from actual environment science that can't find any evidence of climate change?''
I would think licensing wouldn't be much of an issue. Facebook probably maintain their own internal custom linux distro. GPL incompatibility between ZFS and the kernel presumably wouldn't be a problem as they wouldn't be distributing it to anyone else.
Slashdot Mirror
They were around in 94, but they were relatively expensive and rare. That res usually required a fancier video card too to get a better DAC.
And multi monitors required non mainstream video cards too back then (not anymore).
Ouch. My sympathies. Our oldest lowest specced PCs here now have dual monitors with the smallest one at 1280x1024.
But think what your small cheapo monitor costs now in real terms compared to what 1280x1024 did in 1994. Your workplaces relative budgets are very different.
Speak for yourself. You must've been in a very rarified environment.
20 years ago I was AutoCAD drafting at 1024x768 on a flickery 15" monitor. Not pleasant at all, but every one else in the office was on 14" monitors at 640x480 or 800x600 and weren't even aware of higher resoltions - at least they weren't as flickery at those lower resolutions.
Today my 27" 2560x1440 monitor at home cost about the same as that old 15" CRT. And the multicore SSD equipped 15" laptop it's plugged into does 1920x1080. Both screens have way better image quality and zero flicker.
20 years ago I was using VB 3 or 4, VBA, or writing AutoLisp macros in Notepad. Yuck.
20 years ago we were still getting 486s and a Pentium was well out of my employers price range. SMP machines were still exotic things to dream about. Although only a few years after that I was using a dual socket PII 266 with a whopping 128MB (whoa!).
It's probably wan't your intention, but you make it sound like it is the running on the JVM part that makes Scala fast, rather than Scalas design and implementation eg static typing etc.
By itself, just running on the JVM is not some magic fairy dust that's enough to make highly dynamic languages run like Scala. ie most of the time Jython is actually slower than CPython.
Just curious, how do you figure that?
Date of project/company founding? Date of first public announcement? Date of first public 0.x release? Date of first 1.x release?
As far as I can tell, they both had various milestones before the other and their initial development overlapped somewhat - eg Debian started first and (probably) got prereleases out earlier, but Redhat got to 1.x quicker. But I can't see any way to claim Redhat was around long before Debian.
Changing the topic slightly...
Kim Dotcom's extradition hearings are being held in a country that's first equal on that list. And whose courts are not automatically bending over to take the various government agencies purely on their word. He's getting plenty of opportunity to defend himself.
If he does still get extradited, he's going to have a hard time claiming it was due to corruption. No doubt he will try though.
Dart is a Javascript replacement and is by Google. Maybe you meant Rust or something else?
No, no, no. Try this one instead:
https://www.youtube.com/watch?...
Isn't the point of deploying OpenStack yourself that "cloud" != "other people's servers"?
Pressure is mass per unit area? Sounds like a specification for paper density.
Surely you meant force per unit area?
Well if you're going to exaggerate to the point of bullshit, then you could just have easily made it a 'Free' vs 'Open' ideological argument.
And then your inner RMS would claim that none of the GPL licensed (or dual licensed) libraries (gnutls, polarssl, jsse) leaked private keys while the biggest BSD licensed one did. Thus proving the technical superiority of code written using the GPL.
See? Bullshit works both ways.
Maybe he's a... Libretarian
Hmmm... I'm sensing some level of overstatement here. I can't quite put my finger on it though.
Another reason I like having an older car with a plain old stainless steel non electronic key. I can just hang it around my neck under my wetsuit when I go surfing and leave the car locked.
Those with newer cars are hiding their keys in wheelwells etc while hoping nobody nefarious is watching, or having to use annoying lockboxes to put their keys in.
Probably not a big deal for the average slashdotter though.
I say this as a parent* myself... fuck off!
There are plenty of perfectly valid reasons for not having kids, and plenty of people that want them but can't have them.
* yes I feed trolls offline too!
You weren't asking me, but syntax highlighting in vim is way nicer on the eyes with 256 colours.
That is the only thing I want to have it for though.
Not so fast... most of us Linux users are falling behind in our access to cutting edge vulnerabilities.
Sure we still have plenty of the old ones to play with, so it isn't all bad.
I imagine we'll end up with the Nutrimatics version of that instead.
While you are correct (for now), you're not thinking far enough ahead. I reckon a year or two down the road there will be a portable version of this library just like what happened with OpenSSH when they forked SSH for themselves. ie OpenBSD becomes the new upstream for libssl rather than the existing OpenSSL team.
There is a reasonable chance the portable version of the fork could eventually end up taking over from OpenSSL by default on the other BSDs and some Linux distros.
Let me guess... someone else who thinks that the OpenBSD team and the OpenSSL team are the same people?
Hint: they're not. This is a fork of the OpenSSL libraries used in OpenBSD and not intended for anyone else. If after some time it stabilises and turns out to be a good move (I'm guessing it will), then some other people are likely going to want to maintain a portable version that can be used on other platforms - just like what happens with openssh plus the odd other project eg openntpd.
I think the grandparent was right. MS now is hugely better than the MS of 10-15 years ago. I'm not going to try and objectively prove that as I don't care enough about MS and probably couldn't anyway.
But the NT4 to XP/2003 era was appalling security wise - but they changed that. IIS went from swiss cheese to one of the tougher web servers to break. You just don't hear any more about the kinds of problems they used to have. If you endured those days or just laughed from the sidelines, you don't need any hard data to see that they have improved a lot.
I found this paper from Theo de Raadt illuminating though. He steps through 10+ years of OS hardening techniques OpenBSD has put in place to prevent badly written applications misbehaving. Towards the end he summarises how other platforms do this stuff - the only other platform that did it all by default was Windows (yikes!).
In general maybe. This issue had nothing to do with encryption though (or hard security stuff even).
It was a very basic input checking error in a massively crusty overly obfuscated and badly written/documented codebase that all kinds of people have been tacking 'kitchen sink' style features onto for years. It's almost as if the codebase is actively trying to counteract the 'many eyes' effect.
OpenBSD has already taken on their fork and started stripping out cruft - who knows that fork could end up having a portable version that everyone else starts using (like with OpenSSH).
Companies like Google and RedHat etc are presumably going to be putting some extra resources into OpenSSL to help clean it up. It's importance means they would be crazy not to. Hopefully they also put some resources into funding/helping the OpenBSD fork too as a better longer term option.
So... are you saying that climate change claims that actual environmental science causes autism?
Nah, that can't be it - I'm not sure climate change actually claims anything itself. Although Anthropomorphised Global Warming does have a nice ring to it.
Hmmm... thinking about it some more, I suspect you are cleverly using autism as more of a metaphor here (or is that a simile?).
So you must really be saying that the only research that ever backed climate change was a fraudulent discredited study by Al Gore and his corporate conflicts of interest? And a significant percentage of the public is swayed by misguided celebrity followers of Al Gore all the while ignoring the existing research from actual environment science that can't find any evidence of climate change?''
Is that more like it?
That wasn't a simile face. It was like a simile face though.
That's the way I like it baby
I would think licensing wouldn't be much of an issue. Facebook probably maintain their own internal custom linux distro. GPL incompatibility between ZFS and the kernel presumably wouldn't be a problem as they wouldn't be distributing it to anyone else.
I could be wrong though :)