It's been shown to death. The original series has lost its 'camp' appeal. TNG milked all the loyalty out of trekkies it could. DS9, Voyager and Enterprise are all -1:Redundant.
Add to the fact that every movie with the TNG cast sucked, it opened against LOTR:TT, and I'm frankly surprised at his shock.
Not even Wil Wheaton himself could make Star Trek interesting. It's over.
I'd pay to see Short Circuit 3 long before Star Trek 22 (or whatever number they're up to). Johnny 5 is a MANS robot. You hear me, Mr Spiner?
>> An ASCII file could do the job in about 10 bytes depending on the size of the words.
If the words were 4 letters long, sure.
It could do it in 4 bytes if the words were 'a' and 'I'. Including whitespace between the words and EOF marker.
And it would still take up at least 1k on your hard disk, depending on the block size you used when you formatted it. I always forget the default in ext2, 4k?
Anyhow, keep your ASCII files. I like my foreign character sets, fonts and styles, embedded spreadsheets and graphics, and WYSIWIG displays, thanks. Word isn't a hyper-efficient data storage tool, it's a word processor/desktop publishing application. And a pretty good one at that.
supercalifragilisticexpealidocious and antidisestablishmentarianism
and the words are stored in a table? and fonts change after each letter?
Who cares. This is the 21st century. I'd make more of the tons of bloat, custom widgets and statically linked libraries in Open Office than I would of 17k of header data in a Word doc.
Another problem with the hardware support is even how they name the drivers and packages. Take networking for example.
My cheapo "linksys etherfast" cards use the tulip.o module. Because the modules are named after the chipset a card is built around. X servers (last time I bothered with it) still had names like mach64, cl5434, etc. Getting a printer online (let alone shared via samba) is still a chore, and still most non-PS printers (practically every consumer-level model) are only partially supported, if at all.
There's a lot of thankless gruntwork that needs to be done so the less-savvy user doesnt have to figure this stuff out. He just wants the driver for his 'linksys' card and for his new Lexmark Z42 to work.
Rebooting the system just to play or try out a game for a few minutes (or even hours) is a joke. Most people I know who do this spend all their time in Windows, and just have linux there in case a geek happens to be looking.
You cant brag about your months of continuous uptime in linux if you have to reboot just to play a game of $WHATEVER. You also cant tell people about the windows licensing dough they'll save. All you do is complicate their lives with more software they have to figure out.
Office apps will get linux into cubicles. That's what this latest 'desktop consortium' is aiming for.
99.999% hardware supported and a fast, reliable native API for game development (something better than SDL, less generic than OpenGL, and not a DirectX clone) will get it into the home.
Well, this group seeks the standards that would make linux desktops predictable and universal, but I agree with your post and then some.
Even if they succeed, and create the 'one true desktop', it's going to be a dog compared to the latest MacOS and Windows. X is just bloated, inefficient and slow.
We'll probably see linux making some progress in the desktop world, it'll probably find its way into the cubicle labyrinths of big corporations, running the desktop apps that are needed. But it will never rule it.
X11 is like bringing a knife to a gunfight. You might draw some blood, but it's doubtful you'll kill anybody.
>> if you have never goofed up in your personal life, you may criticize me
So you realize that it was you who goofed up, it must just be easier to blame your anti-spam filter?
Lay blame where it's due. Dont make excuses, admit when you're wrong.
People lose e-mails, voicemails and snailmails all the time, you dont need spam-filters to do so. If a relationship cant survive a lost e-mail, it probably isnt worth having in the first place.
You act like the shuttle is a commuter craft that should fly 100% reliably. It is still very much experimental. It is completely rehauled from the inside out every year or so. New electronics, new control systems. The only thing going back into space over and over again is the hull.
The latest I've read today seems to indicate that the fancy new computers could have been to blame, overcompensating when the shuttle pitched on its approach, sending it into a roll which caused it to break up. So it could be the brand new cutting edge components that caused it to break up, not the 30 year old design for the hull.
It's still flown over 120 missions with 2 such failures. That's excellent so far considering how little we know about space flight.
Re:I've used something exatly like this for months
on
Shell Simulation Via CGI
·
· Score: 2, Informative
What I use has a list of commands it's allowed to run.
So you could limit it to ls, rm, mv, and cp with the users security level.
All it does is shell commands and pipe stdout back onto the form.
It's such a trivial script I'm surprised its newsworthy even by/.'s low standards.
It's a form that has a text box. You type in "ls ~/" in the text box, hit enter, the cgi script checks to see if it can execute ls, if so, it shell()'s the command, and pipes the output back to the web page.
Its pretty easy to make it as secure as you want.
If you let it run as root and issue any command under the sun, then its a problem. If you let a user just manage the files in his own home directory, it's as secure (even more so) than telnet/ssh access.
I've used something exatly like this for months
on
Shell Simulation Via CGI
·
· Score: 4, Interesting
I use it to add ipfwd lines to an internal router box around here. Runs in cgi under apache, lets me type sh commands and see the output.
This is just a new version of an old product, and has the same major problem: "applications interacting with the user (those that ask for input from the user), e.g. passwd are still a problem. "
So it's good for doing a chmod or ipfwd line, but you cant run vi or the like.
How hard would it be to get full terminal emulation through a browser applet?
JSRF was a poor followup to the original. It lacks the charm and the fun, and is chock full of bugs.
Eg; you either run around tagging, or are in a 'fight' with a bunch of cops. Not like the original where you're trying to get your tags with the cops and baddies chasing you around. And tagging is now just pulling the trigger, none of the controller gymnastics that made the first a challenge.
I'd wager Sega is making more off it's Monkeyball and Sonic series' for GCN and GBA than all of it's Xbox library put together.
Theres a bunch of little no-name japanese developers pumping out a bunch of stuff for the Xbox. Maybe its not one of the big houses at all, but a bunch of the smaller ones.
All those nickels add up to a dollar, even if MS's support is only by way of free devkits.
You might remember the same situation when Win32s and then Win95 were released. It took a few months for most of the apps to be rereleased in a native 32 bit format. Luckily win16 was (and is) still supported. Such will be the case with 64 bit desktops.
There have been articles in the MSDN about porting existing code to 64 bit windows API for a while.
I've perused them and there's really no major learning curve. Most stuff will just recompile as is, except for a few pointer hyjinks and some more esoteric inlined ASM.
Thing is, the same problems can apply to Linux and other OS code. Sloppy code is sloppy code no matter the social viewpoints of its authors.
Or we're being sarcastic.
Well, at least I was.
Apes is good sci-fi with bad special effects.
ST is bad sci-fi with good special effects.
It's been shown to death. The original series has lost its 'camp' appeal. TNG milked all the loyalty out of trekkies it could. DS9, Voyager and Enterprise are all -1:Redundant.
Add to the fact that every movie with the TNG cast sucked, it opened against LOTR:TT, and I'm frankly surprised at his shock.
Not even Wil Wheaton himself could make Star Trek interesting. It's over.
I'd pay to see Short Circuit 3 long before Star Trek 22 (or whatever number they're up to). Johnny 5 is a MANS robot. You hear me, Mr Spiner?
Then allow me to qualify:
PC hardware.
I was there too. I remember poring over tons of code looking for a couple of bytes to free. Looking for instructions to remove.
You also used to have to stand in front of an automobile and turn a crank to get it to start. Noone misses that either.
>> An ASCII file could do the job in about 10 bytes depending on the size of the words.
If the words were 4 letters long, sure.
It could do it in 4 bytes if the words were 'a' and 'I'. Including whitespace between the words and EOF marker.
And it would still take up at least 1k on your hard disk, depending on the block size you used when you formatted it. I always forget the default in ext2, 4k?
Anyhow, keep your ASCII files. I like my foreign character sets, fonts and styles, embedded spreadsheets and graphics, and WYSIWIG displays, thanks. Word isn't a hyper-efficient data storage tool, it's a word processor/desktop publishing application. And a pretty good one at that.
What if the words are
supercalifragilisticexpealidocious and antidisestablishmentarianism
and the words are stored in a table?
and fonts change after each letter?
Who cares. This is the 21st century. I'd make more of the tons of bloat, custom widgets and statically linked libraries in Open Office than I would of 17k of header data in a Word doc.
I think the 'news' is that another site with nothing exciting to talk about posted an article about it.
Another problem with the hardware support is even how they name the drivers and packages. Take networking for example.
My cheapo "linksys etherfast" cards use the tulip.o module. Because the modules are named after the chipset a card is built around. X servers (last time I bothered with it) still had names like mach64, cl5434, etc. Getting a printer online (let alone shared via samba) is still a chore, and still most non-PS printers (practically every consumer-level model) are only partially supported, if at all.
There's a lot of thankless gruntwork that needs to be done so the less-savvy user doesnt have to figure this stuff out. He just wants the driver for his 'linksys' card and for his new Lexmark Z42 to work.
Rebooting the system just to play or try out a game for a few minutes (or even hours) is a joke. Most people I know who do this spend all their time in Windows, and just have linux there in case a geek happens to be looking.
You cant brag about your months of continuous uptime in linux if you have to reboot just to play a game of $WHATEVER. You also cant tell people about the windows licensing dough they'll save. All you do is complicate their lives with more software they have to figure out.
Office apps will get linux into cubicles. That's what this latest 'desktop consortium' is aiming for.
99.999% hardware supported and a fast, reliable native API for game development (something better than SDL, less generic than OpenGL, and not a DirectX clone) will get it into the home.
Well, this group seeks the standards that would make linux desktops predictable and universal, but I agree with your post and then some.
Even if they succeed, and create the 'one true desktop', it's going to be a dog compared to the latest MacOS and Windows. X is just bloated, inefficient and slow.
We'll probably see linux making some progress in the desktop world, it'll probably find its way into the cubicle labyrinths of big corporations, running the desktop apps that are needed. But it will never rule it.
X11 is like bringing a knife to a gunfight. You might draw some blood, but it's doubtful you'll kill anybody.
>> if you have never goofed up in your personal life, you may criticize me
So you realize that it was you who goofed up, it must just be easier to blame your anti-spam filter?
Lay blame where it's due. Dont make excuses, admit when you're wrong.
People lose e-mails, voicemails and snailmails all the time, you dont need spam-filters to do so. If a relationship cant survive a lost e-mail, it probably isnt worth having in the first place.
That's fine for you, I'm perfectly content with a job that I dont hate, or at best like.
I'd rather have free time to spend with my family than be the company zealot who spends 20 hours a day in the office.
I merely like programming, I love my wife and kids.
You act like the shuttle is a commuter craft that should fly 100% reliably. It is still very much experimental. It is completely rehauled from the inside out every year or so. New electronics, new control systems. The only thing going back into space over and over again is the hull.
The latest I've read today seems to indicate that the fancy new computers could have been to blame, overcompensating when the shuttle pitched on its approach, sending it into a roll which caused it to break up. So it could be the brand new cutting edge components that caused it to break up, not the 30 year old design for the hull.
It's still flown over 120 missions with 2 such failures. That's excellent so far considering how little we know about space flight.
What I use has a list of commands it's allowed to run.
/.'s low standards.
So you could limit it to ls, rm, mv, and cp with the users security level.
All it does is shell commands and pipe stdout back onto the form.
It's such a trivial script I'm surprised its newsworthy even by
It's not really a shell.
It's a form that has a text box. You type in "ls ~/" in the text box, hit enter, the cgi script checks to see if it can execute ls, if so, it shell()'s the command, and pipes the output back to the web page.
Its pretty easy to make it as secure as you want.
If you let it run as root and issue any command under the sun, then its a problem. If you let a user just manage the files in his own home directory, it's as secure (even more so) than telnet/ssh access.
I use it to add ipfwd lines to an internal router box around here. Runs in cgi under apache, lets me type sh commands and see the output.
This is just a new version of an old product, and has the same major problem: "applications interacting with the user (those that ask for input from the user), e.g. passwd are still a problem. "
So it's good for doing a chmod or ipfwd line, but you cant run vi or the like.
How hard would it be to get full terminal emulation through a browser applet?
You didnt miss anything.
JSRF was a poor followup to the original. It lacks the charm and the fun, and is chock full of bugs.
Eg; you either run around tagging, or are in a 'fight' with a bunch of cops. Not like the original where you're trying to get your tags with the cops and baddies chasing you around. And tagging is now just pulling the trigger, none of the controller gymnastics that made the first a challenge.
It really was a let-down, thats my $0.02
I'd wager Sega is making more off it's Monkeyball and Sonic series' for GCN and GBA than all of it's Xbox library put together.
Theres a bunch of little no-name japanese developers pumping out a bunch of stuff for the Xbox. Maybe its not one of the big houses at all, but a bunch of the smaller ones.
All those nickels add up to a dollar, even if MS's support is only by way of free devkits.
If you want to call Shenmue II, Halo, DOA3 etc 'leftovers', sure.
Many good games are available for all three.
There's no point arguing with console fanboys. All 3 have their hits and misses, and are pretty much equal in my book.
I didnt want to miss out on Shenmue, FFX, or Zelda, so I just bought all three. Still cheaper than the average 'gaming' PC these days.
I doubt it.
They would have scored Virtua Fighter 4, Sonic Adventure 2, Shinobi, Ecco and MonkeyBall for the Xbox before ToeJam and Earl and PDO.
For the most part, Segas XBox ports are it's second-tier efforts (excluding Shenmue 2).
Perhaps the defecit has more to do with them launching Live this quarter?
>>Can you generate linux (elf) executable in windows?
yes
Aw heck, I've seen plenty of those same assumptions in OSS code as well. Assuming int is 16 bits, and the such.
Not everyone has the energy to type malloc(sizeof(int)*20)
Bad coding habits are endemic in the free, Free, and proprietary worlds.
Good code will 'just work', bad code will need fixing to work natively.
You might remember the same situation when Win32s and then Win95 were released. It took a few months for most of the apps to be rereleased in a native 32 bit format. Luckily win16 was (and is) still supported. Such will be the case with 64 bit desktops.
There have been articles in the MSDN about porting existing code to 64 bit windows API for a while.
I've perused them and there's really no major learning curve. Most stuff will just recompile as is, except for a few pointer hyjinks and some more esoteric inlined ASM.
Thing is, the same problems can apply to Linux and other OS code. Sloppy code is sloppy code no matter the social viewpoints of its authors.
may not be good for Punky McGarageRock.
I appreciate her point, but you cant generalize about every artist and the entire entertainment industry based on one or two anecdotes.