Text macros? Are you stupid, or just sadistic - clean up the fraking syntax, add lisp style macros, ok, but text macros suck. Oh, and what do you need #includes for? A Go style package system is far superior. And, AFAIK, Gosling never said to get rid of interfaces, but to separate them, and use prototype object model for implementation.
May I remind you that VMS is probably running the most important systems that affect your life, and doesn't care to go so low as to play you your Justin Beiber videos. The NT kernel design evolved from VMS.
The issues you describe are implementation specific, and AFAIK emacs with a couple of extensions can handle all of that, easily. Vi also has autocomplete extensions - in conjunction with GNU screen and zsh, you will probably find a enhancement in productivity. Just saying.
I think the GPP meant that all options and actions in the GUI should be implemented as commands to the internal application shell (like yum shell), sent on a pipe to stdin, possibly in an MVC pattern (thankfully, Unix implements the data model - byte streams it may be, but it is something you can rely on, not to mention that the command line application shell is going to have such semantics anyway). I, for one, really respect the mandriva control panel, at least, in the shape I used in PCLOS 2007 - when configuring the system, you simply saw the command to be executed take shape in front of your eyes, at the bottom of the window.
How are tweaks going for the garbage collector? Have you considered converting it to a regional garbage collector - that ought to bring the same improvements, if not more, as compared to process per tab- which I think is a tad inefficient - are there any reasonable methods to get rid of duplication - some memory mapping tricks? What is your actual GC tech at this time? Do you plan on making it swap-aware? Do you think that any hot-shot optimizations are possible - say, a optional driver to improve memory management (for windows - linus would anal rape you probably, otherwise - though the MRI project is heading the same way, IIRC. It was set up by Azul Systems).
You'd be surprised at the number of superficial bitches in existence - if there weren't so many, the partnerless slashdotter meme wouldn't hold so much water.
Removed features in euro firmwares: 1. Tethering - AT&T didn't like people flashing euro firmwares on their US phones and tethering without paying their sin tax. Rootkits : Hell, their whole OS is on big rootkit - you don't have root, and you can't without voiding the warranty, and hacking it. Sounds close enough for me, though I'm running fast and loose with the definition.
What in the world do you need unprotected pointer math for? Are you writing an OS, or JIT?
Text macros? Are you stupid, or just sadistic - clean up the fraking syntax, add lisp style macros, ok, but text macros suck. Oh, and what do you need #includes for? A Go style package system is far superior. And, AFAIK, Gosling never said to get rid of interfaces, but to separate them, and use prototype object model for implementation.
Set up a small LCD screen at work (maybe solar powered) for telepresence. With a webcam.
Sound-proof the door. And get your wife and daughter to a therapist.
Your IM software sucks if it can't share a screen. And frankly using it is more lazy than walking over.
Or, you could tell the server OEM to flash coreboot instead of a BIOS, and have that for free. Or do it yourself.
Lock and sound-proof doors - done.
Where do you live? Here in BG you have to have 18 for that purpose.
Bad parents have bedtimes, good parents have wakeuptimes. If there is nothing to do in the morning, who cares?
May I remind you that VMS is probably running the most important systems that affect your life, and doesn't care to go so low as to play you your Justin Beiber videos. The NT kernel design evolved from VMS.
Tiny C Compiler has REPL mode, if you so desire. tcsh is also nice
VLC advanced options pane is pretty close.
Sounds like Eclipse with a lot of extensions.
The issues you describe are implementation specific, and AFAIK emacs with a couple of extensions can handle all of that, easily. Vi also has autocomplete extensions - in conjunction with GNU screen and zsh, you will probably find a enhancement in productivity. Just saying.
And what do they pay the web designer for?
That is why we have greasemonkey and stylish.
I think the GPP meant that all options and actions in the GUI should be implemented as commands to the internal application shell (like yum shell), sent on a pipe to stdin, possibly in an MVC pattern (thankfully, Unix implements the data model - byte streams it may be, but it is something you can rely on, not to mention that the command line application shell is going to have such semantics anyway). I, for one, really respect the mandriva control panel, at least, in the shape I used in PCLOS 2007 - when configuring the system, you simply saw the command to be executed take shape in front of your eyes, at the bottom of the window.
What's wrong with smoking a joint?
Nope- same here.
Funny. I'm using FF4 on a 512MB machine, with 50 add-ons, and a few tabs. Not as snappy as I would like, but tollerable.
How are tweaks going for the garbage collector? Have you considered converting it to a regional garbage collector - that ought to bring the same improvements, if not more, as compared to process per tab- which I think is a tad inefficient - are there any reasonable methods to get rid of duplication - some memory mapping tricks? What is your actual GC tech at this time? Do you plan on making it swap-aware? Do you think that any hot-shot optimizations are possible - say, a optional driver to improve memory management (for windows - linus would anal rape you probably, otherwise - though the MRI project is heading the same way, IIRC. It was set up by Azul Systems).
Expect hand crank generators to become real popular.
You'd be surprised at the number of superficial bitches in existence - if there weren't so many, the partnerless slashdotter meme wouldn't hold so much water.
Use mu Torrent Protocol - it's much lighter on the network.
Removed features in euro firmwares: 1. Tethering - AT&T didn't like people flashing euro firmwares on their US phones and tethering without paying their sin tax. Rootkits : Hell, their whole OS is on big rootkit - you don't have root, and you can't without voiding the warranty, and hacking it. Sounds close enough for me, though I'm running fast and loose with the definition.