I don't read the screaming of the Luddites very often, so pardon my ignorance--what APIs do I lose by going to VB.NET, exactly, that aren't duplicated in the.NET framework? The "My" namespace covers a LOT of that stuff, and I can always still use any API call that I'd use in VB6...just find the right DLL, same as always.
Now, if they could just design a simple UI that didn't so many bells and whistles on it that it might have to display a warning for people with epilepsy problems.
Or, rather, I was. Then I downloaded the freebie VB.NET Express.
And these days, I wouldn't go back for any reason. VB6 was quick-and-dirty nice. But the language was gimped. 32KB limits for arrays of types? Guh. Ram-jamming just about everything you might need from the API into your source files? At least C/C++ let you #include it, and most API functions end up with a wrapper in.NET (and those that don't are easier to deal with).
I really liked VB5 and VB6. They were great tools. I wrote a MUD in VB6, and a small RPG. but they're old. They're creaky. They're limited, and they're dying.
Newer Dell laptops are pretty excellent machines. My Inspiron E1505 is a great machine; it's taken some pretty serious abuse and kept on ticking. Dropped it about three feet onto one of the front corners onto concrete (while the machine was on) and it suffered no damage. It's no Thinkpad, but it's a surprisingly great laptop. It is a bit heavy though.
I wanted a Thinkpad or a Mac for college, but I got the same machine as an MBP, minus OSX and the bells and whistles, for only $830. The Thinkpad would have cost a bit more, too. And the Dell looks pretty good, even though I think a silver-and-white computer is a little odd. I can't complain.
Oh, believe me, I know--I agree with you, and liked the positioning of it (though it really doesn't bother me all that much that they added them; I barely notice). I'd prefer a way to switch it back too.
You can set the Windows page file with minimum/maximum sizes, i.e. 256MB at low state, and adding up to 512MB if you need more. That's what that means.
Under Windows it seems it'll swap out whether the free RAM is needed or not, no matter what (there's a registry setting to change this though). Under Linux, you won't swap much anyway unless you need it.
I run a Core Duo laptop with 1GB of RAM and have never swapped out in Linux, no matter what I was doing.
(Disclaimer: I use the Office 2007 beta on my laptop, alongside OpenOffice which I use for ODF documents.)
OpenOffice is bloated. It's heavy, demanding, and slow. Yes, most of it is writing it in Sun's trainwreck of choice. OOo 2 was pig-slow on my 1GHz Pentium III ThinkPad A20m, and while it's better on my Core Duo Inspiron, it's still slow and lurching.
When in Ubuntu, I find myself using KOffice a lot more--and I don't even use the KDE environment. I'd rather take the memory hit of waiting for the KDE libraries to load than deal with OpenOffice's slowitude.
Make it faster and make it grok Publisher documents, then stump it as an Office replacement.
Agreed. I have a widescreen Inspiron at 1280x800 (or something similar, too damned lazy to go turn it on and check) and the ribbon system is pretty sweet.
As for dreading the expiring beta--can you say "zero-day"? (Not that I'll use it; I'll get a free copy from work...)
It's a zipped XML file. I'm a middling programmer at best and I can parse an XML doc. There will be a converter for OO.o two days after release. If Java didn't make me feel slimy inside, I'd write one myself!
Do people REALLY get bent out of shape like this when they get a format that they can open perfectly well--in fact, just about seamlessly with their suite of choice? Does your blood pressure spike when someone sends you a link to a Flash file? (Exceptions for those browsing on Linux, as then it may just not work, eh?)
AbiWord, OpenOffice, KOffice--they all can open DOC-format files, but I hear bitching and more bitching about them. Bitching about DOC isn't going to make ODF (which, as it happens, I like quite a bit, and do think *should* be the standard) any more prevalent.
Get over yourself. Attitudes like yours are why people think Linux is hard and unfriendly, and you're passing the same to the new fad cause of ODF.
Slashdot Mirror
That's ok, it'll get reposted in the next 72 hours.
Slaves have better benefits.
Wouldn't touch anything with Dozois's muddy fingerprints on it, ever.
Heinlein. Card. Asimov. Sturgeon. Ellison.
King's very good, but "the best"?
You want SCO to have them?
Better the devil who owns Windows than Darl McBride.
"Mach 2"'s would be Sensors, you insensitive clod!
Blue pill.
Tolkien wrote the Matrix.
Yeah, well...we were wrong then too.
Yeah...but I'm a geek. I wanted a box that had a Core Duo. Hence, new machineage.
As for trusting the money--some banks offer you throw-away card numbers that you can use only for $X dollars.
I don't read the screaming of the Luddites very often, so pardon my ignorance--what APIs do I lose by going to VB.NET, exactly, that aren't duplicated in the .NET framework? The "My" namespace covers a LOT of that stuff, and I can always still use any API call that I'd use in VB6...just find the right DLL, same as always.
Or am I missing something?
Sorry, you're right. Static limit of 64KB, not 32. My bad.
I don't care a goddamn bit for the way VB6 did dynamic arrays, though. Collections helped, but were clunky. VB.NET improves on it vastly.
Now, if they could just design a simple UI that didn't so many bells and whistles on it that it might have to display a warning for people with epilepsy problems.
They did. It's called WinFLP.
Or, rather, I was. Then I downloaded the freebie VB.NET Express.
.NET (and those that don't are easier to deal with).
And these days, I wouldn't go back for any reason. VB6 was quick-and-dirty nice. But the language was gimped. 32KB limits for arrays of types? Guh. Ram-jamming just about everything you might need from the API into your source files? At least C/C++ let you #include it, and most API functions end up with a wrapper in
I really liked VB5 and VB6. They were great tools. I wrote a MUD in VB6, and a small RPG. but they're old. They're creaky. They're limited, and they're dying.
Newer Dell laptops are pretty excellent machines. My Inspiron E1505 is a great machine; it's taken some pretty serious abuse and kept on ticking. Dropped it about three feet onto one of the front corners onto concrete (while the machine was on) and it suffered no damage. It's no Thinkpad, but it's a surprisingly great laptop. It is a bit heavy though.
I wanted a Thinkpad or a Mac for college, but I got the same machine as an MBP, minus OSX and the bells and whistles, for only $830. The Thinkpad would have cost a bit more, too. And the Dell looks pretty good, even though I think a silver-and-white computer is a little odd. I can't complain.
Oh, believe me, I know--I agree with you, and liked the positioning of it (though it really doesn't bother me all that much that they added them; I barely notice). I'd prefer a way to switch it back too.
Click on the close button of the leftmost tab you want to delete. Keep clicking.
Shazam, man. Shazam.
Google's main market share is still made of Windows clients. So the OMFG APPLE IS GOING TO GET SPESHUL GOOGLE FEATURES speculation can stop *now*.
You can set the Windows page file with minimum/maximum sizes, i.e. 256MB at low state, and adding up to 512MB if you need more. That's what that means.
Don't be a jackass.
Under Windows it seems it'll swap out whether the free RAM is needed or not, no matter what (there's a registry setting to change this though). Under Linux, you won't swap much anyway unless you need it.
I run a Core Duo laptop with 1GB of RAM and have never swapped out in Linux, no matter what I was doing.
I view pages at about 50% size anyway when typing, so it's not like it's a big deal.
Work OR student discount for me...can't decide...
Tried it. KOffice is still a lot faster--and not KOffice-compiled-from-source, but KOffice-from-apt.
Still feels dog-tired and slow.
(Disclaimer: I use the Office 2007 beta on my laptop, alongside OpenOffice which I use for ODF documents.) OpenOffice is bloated. It's heavy, demanding, and slow. Yes, most of it is writing it in Sun's trainwreck of choice. OOo 2 was pig-slow on my 1GHz Pentium III ThinkPad A20m, and while it's better on my Core Duo Inspiron, it's still slow and lurching. When in Ubuntu, I find myself using KOffice a lot more--and I don't even use the KDE environment. I'd rather take the memory hit of waiting for the KDE libraries to load than deal with OpenOffice's slowitude. Make it faster and make it grok Publisher documents, then stump it as an Office replacement.
Agreed. I have a widescreen Inspiron at 1280x800 (or something similar, too damned lazy to go turn it on and check) and the ribbon system is pretty sweet.
As for dreading the expiring beta--can you say "zero-day"? (Not that I'll use it; I'll get a free copy from work...)
It's a zipped XML file. I'm a middling programmer at best and I can parse an XML doc. There will be a converter for OO.o two days after release. If Java didn't make me feel slimy inside, I'd write one myself!
Do people REALLY get bent out of shape like this when they get a format that they can open perfectly well--in fact, just about seamlessly with their suite of choice? Does your blood pressure spike when someone sends you a link to a Flash file? (Exceptions for those browsing on Linux, as then it may just not work, eh?)
AbiWord, OpenOffice, KOffice--they all can open DOC-format files, but I hear bitching and more bitching about them. Bitching about DOC isn't going to make ODF (which, as it happens, I like quite a bit, and do think *should* be the standard) any more prevalent.
Get over yourself. Attitudes like yours are why people think Linux is hard and unfriendly, and you're passing the same to the new fad cause of ODF.