The problem is that this reason gets blown out of the water when you start hacking on the code; the reason it's stable is that Sun controlled it, once it's released, that stability is lost.
The main reason most people run Solaris is for the app support, e.g. Oracle. I doubt Oracle will fully support running their apps on OpenSolaris, although it should run just fine.
I'm not going to enter an editor flamewar; I use vi, but gvim is nicer. The main thing is to find one which supports syntax highlighting, it'll help you find that tag you left open which is breaking your page...
Client side scripts aren't bad provided their loss doesn't hamper the site. For instance, input validation prior to submission to the server saves time and your bandwidth, even though you should be checking at the server as well.
As for browsers, validate in Opera, Safari and Konqueror if you can. Depending on your audience, lynx and mobile browser are worth a quick once-over as well.
No they haven't; they're working with Fujitsu to merge UltraSPARC IV and SPARC64 so instead of 2 companies working on different versions of the same chip, they will pool resources.
Yeah, I used to be addicted to MUME based in Middle Earth. However, I found that I became very fast at typing certain commands but the rest of my typing wasn't as hot. I still find the same as I can type certain unix-based things/paths very quickly as I use them every day at work, but normal typing is still OK.
Personally, I learnt typing at school partly out of being a computer geek at that time and it was one of the best things I did as it means I have a fairly decent typing speed and I'm reasonably accurate. My accuracy is also a lot better as I can watch what I type rather than looking at the keyboard all the time...
I always thought this until I started working at a big company and realised just how quick & easy it was to have calendar & mail in one place with todo lists & other stuff.
The capacity is the issue. I didn't get a dedicated MP3 player (iPod, for what it's worth) until the cost/capacity balance was right. Samsung had a phone with 32 or 64MB capacity which isn't too bad. Until we get phones with 1GB at a minimum with decent battery life while still being portable, people will still have seperates. I carry my phone 95% of the time, but I wouldn't want to carry a brick again.
On the other hand, how long ago was it that a decent digital camera was huge and it was inconceivable to get a 3 megapixel camera in a phone? I believe there will be a day when the combined PDA/camera/phone/MP3 player is reasonably cheap, portable and has good battery life, probably within 5 years.
As for Bill's point about running Windows; who knows? Hopefully there will be a variety of OS's with some kind of compatibility between them to keep everyone on their toes, but it'll probably turn into the usual mix of incompatible systems...
Well, I know that 99% of 32-bit apps run just fine under 64-bit Solaris, AIX & HP-UX (the remainder are ones which address the kernel directly like top or lsof). Provided the hardware and the OS is designed correctly (i.e. not like the pain of DOS->Win32), there's no (ok, much less) problem in migrating.
Duration of copyright is a sticky point; I do think it needs to be shorter, but Disney et al will fight tooth and nail to keep it as long as it is no matter how hypocritical it is for them (they've ripped off so many fairy tales and other stories themselves...).
With regards to point 6; there needs to be a form of protection for those kind of things. For example, if someone makes a film of Macbeth, that interpretation is subject to copyrights, but the original work isn't and someone else can put on a play of it, make another film etc.
Using concepts from the film version in your production is a dodgy area.
No, it depends on the law. There are many laws, certainly in the UK that say something to the effect that there is a default position unless the contract overrides it. There are also several laws that say that a contract cannot override the law or at least specific portions of it.
For example, we have the Sale of Goods Act covering sales; this cannot be overriden when selling to an individual and grants the buyer certain rights. However, when selling to a business, rights can be negotiated away, presumably on the basis that the business is in a better position to handle itself.
Smaller binaries = quicker load time (less disk I/O or memory being moved around) and smaller memory footprint. Yes, this is mostly in embedded apps where memory sizes might still be in KB rather than GB, but if you're analyzing performance, memory usage is relevant, even if it may not be your primary concern.
Best bet is bash or zsh with arrow keys; it's more intuitive. Personally, I've gotten used to vi bindings because ksh is the only shell I can guarantee to be on all our servers at work (AIX, HP-UX & Solaris, various versions of each).
I know I had this problem on a "real" modem way back when with some AT command (can't remember what, been so long...). I eventually tracked down the config changes to stop it happening.
I came close to doing rm -rf / as root. I was doing some housekeeping on my desktop box and had some files I wanted to delete. They weren't owned by my user so I figured I'd su to root and remove them; su by default leaves the shell in the same directory, but I did 'su -' out of habit. One rm -r * later caused some errors, so I Ctrl-C'd it, but by that time I'd rendered my system unusable. Luckily it hadn't hit/export/home (Solaris system), so my data wasn't putzed, just the OS on the box. I just reinstalled the OS and the system was fine after that.
Managed that once too here in the UK; bought CD (IIRC; might have been game) from Virgin, walked into Woolworths set of their alarm going in and out; apparently they'd had a few ppl do the same.
Back to the main point, I've set off alarms before and every time they've just re-swiped it or let me go; never had to be searched.
Yes, the logic may be the same, but part of the reason to use a database is to remove the whole clunky data integrity issues from your application. People make bugs in code; fact of life. However, after sufficient testing, the bugs will be removed.
I'd rather rely on the database to ensure my data integrity as I can be reasonably confident it's been tested a lot more than my code. I can say "make that column unique in that table" and be 99.99% sure it will always be unique (let's leave the.01% chance of data corruption or some wacky bug). If I rely on the app to do the same, I have to introduce locking protocols to ensure the uniqueness of that column so I don't get a race condition. Back to my original point: I have a reasonable chance of leaving a bug in my code.
Now, MySQL has had the UNIQUE constraint for some time, but the same logic above can be applied to all the other features such as foreign keys & triggers; use the code in the DB to do your work and leave your app code to be simple and, hopefully, less bug-prone.
Reminds me of washing powder adverts; "New improved Ariel gets clothes even whiter!". We got this for about 10 years and you're wondering about the old Ariel from 10 years ago. What was it, "get some stains out, some of the time"?
Extend that to Windows which has become "faster and more secure" with each iteration; by inference, Windows NT 3.x was klunky, slow and a collander of security holes. Admittedly, that's not far from the truth, but I doubt it was ever advertised that way.
Slashdot Mirror
The main reason most people run Solaris is for the app support, e.g. Oracle. I doubt Oracle will fully support running their apps on OpenSolaris, although it should run just fine.
Client side scripts aren't bad provided their loss doesn't hamper the site. For instance, input validation prior to submission to the server saves time and your bandwidth, even though you should be checking at the server as well.
As for browsers, validate in Opera, Safari and Konqueror if you can. Depending on your audience, lynx and mobile browser are worth a quick once-over as well.
No, they'd never do something as low and underhand as that... That would be like putting an illegal tariff on steel imports...
Personally, I learnt typing at school partly out of being a computer geek at that time and it was one of the best things I did as it means I have a fairly decent typing speed and I'm reasonably accurate. My accuracy is also a lot better as I can watch what I type rather than looking at the keyboard all the time...
I always thought this until I started working at a big company and realised just how quick & easy it was to have calendar & mail in one place with todo lists & other stuff.
On the other hand, how long ago was it that a decent digital camera was huge and it was inconceivable to get a 3 megapixel camera in a phone? I believe there will be a day when the combined PDA/camera/phone/MP3 player is reasonably cheap, portable and has good battery life, probably within 5 years.
As for Bill's point about running Windows; who knows? Hopefully there will be a variety of OS's with some kind of compatibility between them to keep everyone on their toes, but it'll probably turn into the usual mix of incompatible systems...
Well, I know that 99% of 32-bit apps run just fine under 64-bit Solaris, AIX & HP-UX (the remainder are ones which address the kernel directly like top or lsof). Provided the hardware and the OS is designed correctly (i.e. not like the pain of DOS->Win32), there's no (ok, much less) problem in migrating.
With regards to point 6; there needs to be a form of protection for those kind of things. For example, if someone makes a film of Macbeth, that interpretation is subject to copyrights, but the original work isn't and someone else can put on a play of it, make another film etc.
Using concepts from the film version in your production is a dodgy area.
For example, we have the Sale of Goods Act covering sales; this cannot be overriden when selling to an individual and grants the buyer certain rights. However, when selling to a business, rights can be negotiated away, presumably on the basis that the business is in a better position to handle itself.
Depends on (a) local laws and (b) whatever contract you signed. (a) will be the default which may be over-ridden by (b).
Smaller binaries = quicker load time (less disk I/O or memory being moved around) and smaller memory footprint. Yes, this is mostly in embedded apps where memory sizes might still be in KB rather than GB, but if you're analyzing performance, memory usage is relevant, even if it may not be your primary concern.
Best bet is bash or zsh with arrow keys; it's more intuitive. Personally, I've gotten used to vi bindings because ksh is the only shell I can guarantee to be on all our servers at work (AIX, HP-UX & Solaris, various versions of each).
stty erase e
stty intr r
If you know what you're doing, it's fairly trivial to get out of that, but a newbie won't have a chance.
I know I had this problem on a "real" modem way back when with some AT command (can't remember what, been so long...). I eventually tracked down the config changes to stop it happening.
I came close to doing rm -rf / as root. I was doing some housekeeping on my desktop box and had some files I wanted to delete. They weren't owned by my user so I figured I'd su to root and remove them; su by default leaves the shell in the same directory, but I did 'su -' out of habit. One rm -r * later caused some errors, so I Ctrl-C'd it, but by that time I'd rendered my system unusable. Luckily it hadn't hit /export/home (Solaris system), so my data wasn't putzed, just the OS on the box. I just reinstalled the OS and the system was fine after that.
Back to the main point, I've set off alarms before and every time they've just re-swiped it or let me go; never had to be searched.
How else can they convince everyone they need 4GHz CPUs?
We've managed to clone a game that's 10 years old. Fantastic work, guys...
Windows-E - bring up explorer window
Windows-M - Minimise all windows (seems to be same as Windows-D which I didn't know about).
ObReply: Your terms are acceptable.
I'd rather rely on the database to ensure my data integrity as I can be reasonably confident it's been tested a lot more than my code. I can say "make that column unique in that table" and be 99.99% sure it will always be unique (let's leave the .01% chance of data corruption or some wacky bug). If I rely on the app to do the same, I have to introduce locking protocols to ensure the uniqueness of that column so I don't get a race condition. Back to my original point: I have a reasonable chance of leaving a bug in my code.
Now, MySQL has had the UNIQUE constraint for some time, but the same logic above can be applied to all the other features such as foreign keys & triggers; use the code in the DB to do your work and leave your app code to be simple and, hopefully, less bug-prone.
Slashdotted with 0 comments.... *sigh*
Dammit, where's the -1 corny moderator option?
Extend that to Windows which has become "faster and more secure" with each iteration; by inference, Windows NT 3.x was klunky, slow and a collander of security holes. Admittedly, that's not far from the truth, but I doubt it was ever advertised that way.