I can't remember their names, but there were two programming editors I used on VMS. Both had their quirks - the first wouldn't wrap text that was wider than the terminal screen (72 characters?), nor could it scroll. The second could wrap, but wouldn't allow you to do a "save as", which was a bit of a pain as you could accidentally navigate to a non-existent directory and open a new file by mistyping the name of the directory you'd intended to create the file in. You'd then happily enter a bunch of code, only to discover your navigation mistake when you went to save the file. Cue a bunch of DCL (DEC Command Language - the VMS shell scripting language) to create a 'cd' command that would check for the existence of a directory...
Blimey, just checked the Wikipedia article for Turbo Pascal and it did indeed pre-date the ST. In a weird piece of synchronicity, the article mentions the Nascom computer, since that's where the Turbo Pascal compiler originated. It's the second time in the last few days the Nascom has intruded on my consciousness, as it's the basis of a very rare drum computer that's just been added to the Vintage Synth Explorer.
That's a very Microsoft-centric article, although it does have a passing mention of Smalltalk. Earliest IDE I ever used was the toolset on VMS, which included editor, compiler, debugger and profiler - they were integrated via the shell. If that doesn't qualify, then there was DevPac for assembler and a C development package (Lattice C I think) on my Atari ST, which inclued integrated tools that were far more sophisticated than what was later offered by Turbo Pascal.
I even wrote a small DOS virus in assember myself (never released it, just as a study).
I did an evening course in x86 assembler at a college in the UK many years ago. In our first lesson the tutor showed us how to write a boot sector virus for DOS - I thought it was quite an amusing way to motivate us!
Dear God. I used IRIX on an SGI Indy, and it was the perfect disaster of buggy, unstable software on top opf painfully slow hardware. In comparison, the OpenWindows desktop on my Sun workstation was a thing of reliable elegance.
Linux would not exist without the annoying aspects of GNU and the FSF. They would have made their own kernel in a timely fashion and Linus may never have been motivated to make his own.
Interestingly, the original architect of the Hurd kernel wanted to use 4.4BSD as a starting point, but was overrulled by Stallman who wanted to use Mach.
Ladyada created the brilliant x0xb0x - a faithful recreation of the Roland TB-303 synthesiser and sequencer, but with MIDI and a flashable firmware. It's a a brilliant device, and acknowledged that what made the 303 so good was the combination of synthesiser and sequencer. All previous clones had imitated the sound generation aspects alone.
OS X has user land components and code from both Net and Free. The initial updates to the creaky old OpenStep code base relied on NetBSD as the primary source, but this gradually changed as key FreeBSD developers were recruited by Apple.
Do you know whether Yahoo! is still largely hosted on FreeBSD? I worked there at the very end of the 90's, and it was all FreeBSD - even the developer desktop machines ran it. It was my first exposure to FreeBSD, having used NetBSD and Linux before that.
BSDs have their advantages over Linux, but portability ain't one of them, given that Linux has been ported to far more platforms than NetBSD.
Linux has only been ported to more platforms because of the sheer number of people working on it, but that's no reflection of the portability of the code. NetBSD was designed with portability from the start, whereas Linux was and still is in many areas designed for an x86-centric world. Many Linux ports never reached maturity, and even some of those that did are now broken.
A colleague at work is building a Ford GT-40, a combination of a kit, parts also used on other models of cars and some parts he's had to fabricate himself. Once completed, he can call the car a Ford GT-40 rather than a replica as long as he meets some (very stringent) criteria. I wasn't aware you could do this before, but he explained that to qualify, his car had to be virtually indistinguishable from the real thing (unlike a Lamborghini replica I once saw that had the egine block from a family saloon car).
Rasterman's code is elegant and very readable. From what I remember, he parted ways with the GNOME project because he wasn't particularly interested in working on the GTK libraries as a RedHat staffer.
It's been usable for most of the time it's been in development, and I'm actually running the nightly RPM builds on my laptop at work. I think the lack of a formal stable release just reflects the high rate of change in the underlying libraries, where things are refactored or rewritten quite often. Despite this churn, the window manager itself has remained remarkably stable.
Utter rubbish - in any dynamically typed language you will have many such bugs. I used to code a lot of Perl, and lately I've been forced to use Groovy. There is little chance of refactoring anything, combined with endless cycles of compile, test, fix dynamic language related bug. It's pissing me off so much that quitting my current job and going back to working with Java.
Yes, the UK does have the principle of "contempt of court", and I'd say this is pretty much an example of it as it goes against the spirit and arguably the wording of the court judgement. I just wonder how the court would decide which Apple employees are going to prison for this (and yes, contempt of court invariably means jail time even if it's only overnight).
Amazon is doing something shady and it'll get worked out in court now that it's know[n].
Oh yeah, just like Vodafone and the billions of pounds they avoided paying in tax. In the UK the politicians let big firms get away with crap like this and the Facebook tax dodge in the mistaken belief that it brings jobs to the country. All it does is line the pockets of a few at the cost of a huge amount of tax revenue taht could be used to finance real investment.
I wonder how they manage to support all these different hardware.
One way is automated cross-compiling to ensure that the source at least builds for as many architectures as possible. Think of it as a large scale continuous integration environment.
Yup, they targeted my elderly neighbour and a number of her friends, but I've never heard of them targetting younger people. This suggests to me that they have access to data on people so they can pick the best targets. The only commonality we could find amongst the victims we knew was that they had called British Telecom's broadband support lines in India...
Slashdot Mirror
I can't remember their names, but there were two programming editors I used on VMS. Both had their quirks - the first wouldn't wrap text that was wider than the terminal screen (72 characters?), nor could it scroll. The second could wrap, but wouldn't allow you to do a "save as", which was a bit of a pain as you could accidentally navigate to a non-existent directory and open a new file by mistyping the name of the directory you'd intended to create the file in. You'd then happily enter a bunch of code, only to discover your navigation mistake when you went to save the file. Cue a bunch of DCL (DEC Command Language - the VMS shell scripting language) to create a 'cd' command that would check for the existence of a directory ...
Blimey, just checked the Wikipedia article for Turbo Pascal and it did indeed pre-date the ST. In a weird piece of synchronicity, the article mentions the Nascom computer, since that's where the Turbo Pascal compiler originated. It's the second time in the last few days the Nascom has intruded on my consciousness, as it's the basis of a very rare drum computer that's just been added to the Vintage Synth Explorer.
I thought Turbo Pascal came out around 1988 - 89. That's certainly the timeframe in which I first started to notice people talking about it.
That's a very Microsoft-centric article, although it does have a passing mention of Smalltalk. Earliest IDE I ever used was the toolset on VMS, which included editor, compiler, debugger and profiler - they were integrated via the shell. If that doesn't qualify, then there was DevPac for assembler and a C development package (Lattice C I think) on my Atari ST, which inclued integrated tools that were far more sophisticated than what was later offered by Turbo Pascal.
I also have an integrated dust removal tool. It operates by projecting a high velocity jet of yellow liquid.
Damn. I was hoping he'd answer the question inquiring what it was that he ate from his foot. My money was on a large verruca.
I even wrote a small DOS virus in assember myself (never released it, just as a study).
I did an evening course in x86 assembler at a college in the UK many years ago. In our first lesson the tutor showed us how to write a boot sector virus for DOS - I thought it was quite an amusing way to motivate us!
Dear God. I used IRIX on an SGI Indy, and it was the perfect disaster of buggy, unstable software on top opf painfully slow hardware. In comparison, the OpenWindows desktop on my Sun workstation was a thing of reliable elegance.
Linux would not exist without the annoying aspects of GNU and the FSF. They would have made their own kernel in a timely fashion and Linus may never have been motivated to make his own.
Interestingly, the original architect of the Hurd kernel wanted to use 4.4BSD as a starting point, but was overrulled by Stallman who wanted to use Mach.
The company claims that it's one of the best releases till date
Well, you would rather hope so.
Ladyada created the brilliant x0xb0x - a faithful recreation of the Roland TB-303 synthesiser and sequencer, but with MIDI and a flashable firmware. It's a a brilliant device, and acknowledged that what made the 303 so good was the combination of synthesiser and sequencer. All previous clones had imitated the sound generation aspects alone.
OS X has user land components and code from both Net and Free. The initial updates to the creaky old OpenStep code base relied on NetBSD as the primary source, but this gradually changed as key FreeBSD developers were recruited by Apple.
The "G" in "GTK+" originally stood for "General", not "GIMP".
Do you know whether Yahoo! is still largely hosted on FreeBSD? I worked there at the very end of the 90's, and it was all FreeBSD - even the developer desktop machines ran it. It was my first exposure to FreeBSD, having used NetBSD and Linux before that.
BSDs have their advantages over Linux, but portability ain't one of them, given that Linux has been ported to far more platforms than NetBSD.
Linux has only been ported to more platforms because of the sheer number of people working on it, but that's no reflection of the portability of the code. NetBSD was designed with portability from the start, whereas Linux was and still is in many areas designed for an x86-centric world. Many Linux ports never reached maturity, and even some of those that did are now broken.
A colleague at work is building a Ford GT-40, a combination of a kit, parts also used on other models of cars and some parts he's had to fabricate himself. Once completed, he can call the car a Ford GT-40 rather than a replica as long as he meets some (very stringent) criteria. I wasn't aware you could do this before, but he explained that to qualify, his car had to be virtually indistinguishable from the real thing (unlike a Lamborghini replica I once saw that had the egine block from a family saloon car).
Rasterman's code is elegant and very readable. From what I remember, he parted ways with the GNOME project because he wasn't particularly interested in working on the GTK libraries as a RedHat staffer.
It's been usable for most of the time it's been in development, and I'm actually running the nightly RPM builds on my laptop at work. I think the lack of a formal stable release just reflects the high rate of change in the underlying libraries, where things are refactored or rewritten quite often. Despite this churn, the window manager itself has remained remarkably stable.
Eclipse is the worst IDE I've ever used. NetBeans and IntelliJ are far superior, so much so that I can only wonder at the popularity of Eclipse.
Typing bugs just don't really happen.
Utter rubbish - in any dynamically typed language you will have many such bugs. I used to code a lot of Perl, and lately I've been forced to use Groovy. There is little chance of refactoring anything, combined with endless cycles of compile, test, fix dynamic language related bug. It's pissing me off so much that quitting my current job and going back to working with Java.
Yes, the UK does have the principle of "contempt of court", and I'd say this is pretty much an example of it as it goes against the spirit and arguably the wording of the court judgement. I just wonder how the court would decide which Apple employees are going to prison for this (and yes, contempt of court invariably means jail time even if it's only overnight).
Simple unlock patterns are inherently flawed, anyway. Your password is finger-painted on the screen. Even direction is easy enough to determine.
Particularly if you sweat as much as Jimmy Savile in a primary school playground.
Amazon is doing something shady and it'll get worked out in court now that it's know[n].
Oh yeah, just like Vodafone and the billions of pounds they avoided paying in tax. In the UK the politicians let big firms get away with crap like this and the Facebook tax dodge in the mistaken belief that it brings jobs to the country. All it does is line the pockets of a few at the cost of a huge amount of tax revenue taht could be used to finance real investment.
I wonder how they manage to support all these different hardware.
One way is automated cross-compiling to ensure that the source at least builds for as many architectures as possible. Think of it as a large scale continuous integration environment.
These guys were targeting primarily older users.
Yup, they targeted my elderly neighbour and a number of her friends, but I've never heard of them targetting younger people. This suggests to me that they have access to data on people so they can pick the best targets. The only commonality we could find amongst the victims we knew was that they had called British Telecom's broadband support lines in India ...