I feel for you. I use *no* MS software whatsoever. And I dont like OO either - its too 'similar' to the MS apps its supposed to replace. I suppose thats a good thing for people weaned on those, in order to allow them the opportunity to get off Windows, but I just cant stand that *type* of app.
I have no use for Powerpoint, or anything like it. I stick with ASCII text, so not much need for a Word or its equivalent. On the very rare occasion I need to do something spreadsheet-like, I use gnumeric.
2. Actually, I dont care so much about the backend storage of it, so much as it is *represented* as 'one file', or 'one stream of ASCII'.
3. If you want to copy just part, then copy(/paste) just part - trivial. The point is, if you need to swap to a hot spare, or duplicate a standard site config to a new device for a new site, instead of having to wade through multiple menus, and compare the default settings in the new device with the ones in the standard config, and change the right ones, switch to the next menu, blah (eg 3com ascend etc), instead you have *ONE* 'stream of ascii' to copy, and you are done.
1. Once you know how to do something, its almost impossible to forget
2. tab-completion in both command-mode and config mode - you dont 'edit' the file, you type the config commands, which are saved as part of the running config. Unless you are copying the entire config, you dont do the whole download/edit/upload - you modify the configuration directly at the cisco CLI. You cant 'forget' to save part of the config, as 'copy run star' (copy running-config startup-config) will copy *every* thing from the currently effective configuration, to the NVRAM 'saved' copy.
3. If you *do* need to copy an entire configuration, between identical (or similar) devices, you copy/paste the entire thing, and bang, you are done.
It doesnt matter.. SCO was charging that Novell was claiming it owned the Unix copyright when it knew for a fact that it didnt - this shows that that is absolutely NOT the case, that Novell full beleived that it did in fact retain that ownership.
It all depends on the frequency - some frequencies penetrate different materials with different effectiveness. I havent checked, but if we're lucky, maybe WiMax uses an NLOS frequency.
At $600/mo they arent going to be getting too many residential customers (nor do they probably expect to). Nor do they want to put up what is probably some expensive connection so they can get all 25 of them that would live in the rural area this would cover. They are targeting businesses who want an alternative to paying for a wired T1.
What *I* want to see, is equipment, affordable to end users, to facilitate point-to-point Megabit-or-faster wireless links over 30+ miles. 802.11 can do this, with the same equipment on both ends. I seriously home WiMax equipment eventually supports that, as opposed to only offering a huge expensive 'head end' to tie to the small end-user units (like DSL and cablemodems currently work)
Oh, those tiny things on the right. Wow. I never really noticed those there:P
Seriously, the ads in gmail are *very* discreet, and have never gotten in the way. I really do barely notice them (but yes, I know they are there)
Personally, I dont care about being able to access the google mailbox via POP, or even IMAP. What I want, is to be able to use the *google* interface, to access mail on other external IMAP accounts. (Or a downloadable version of the gmail interface to install on my own webserver, but Im not holding my breath for that)
Ok I guess it isnt that ludicrous to compress it, or to use zip.
I just had flashbacks to where I was going to get some MP3's from somewhere and *they* were individually zipped - which *IS* insane, becuase the resulting zip's were either larger than, the same size, or less than a dozen bytes shorter than the MP3 files were.
A. They've probably always done this - most registrars do these days. You probably just see it sooner now due to the changes at the.com DNS (immediate updated vs 24-48 hours)
B. The grace period is usually 30 days. Its also something imposed by the registRY - google for 'redemption period' If you let a month go by without noticing your domain has expired, it must not be that important of a domain. If you have so many domains you lose track, perhaps you should get a bit more organized. Make a list with expiration dates, and check it once in a while. Maybe even sort it by date.
Cisco IOS, and its single config file, absolutely rocks. I was just looking at the man page for the config file for this project, and it stuck me as absurd that they didnt use the same syntax.
What I would love would be an IOS or IOS clone that ran on common x86 hardware, becuase, as you note, Cisco HW is expensive, even if you do buy used/refurb.
Ah yes, becuase if there *are* vulnerabilities in the systems, we want to make sure every district has the same vulnerability. Havent we learned anything from the MS monoculture?
I can see standardizing the processes, and the data formats (as long as the standards are open and subject to wide public scrutiny) but not which vendors or brands of equipment.
I think the whole concept of 'primary' elections operated by the state should go away. If its a private party, it should manage (and pay for) its selection of candidate to sponsor, on its own.
The concept of 'parties' as an official concept in the elections should go away as well.
He assumes that if everyone runs away from IE (or MS in general), that they will all be running to the same thing, and create another monoculture.
The idea is to NOT have a monoculture. To have an environment where there are *many* competing platforms and applications, and (becuase they all comply with certain published standards for file and network data formats) any individual (person or business) can choose from among many alternatives, and still be able to communicate with and send and receive data to/from individuals who chose something else.
*Eliminate* the monoculture. The solution is not for MS to fix its bugs. The solution is for MS to not have a monopoly (wether they jump or are pushed)
MS biggest fear is that once they are a monopoly, they will lose *all* market share (and to be honest, IMNSHO, rightfully so, their stuff is crap). MS is desperately afraid of having to compete on the technical merits of their products. Its something they never had to do before.
If you need *me* to provide you with the reasons for my conclusions, you've either been living under a rock or been wearing blinders, for the past few years.
Only an absolute *FOOL* would knowingly choose to use any Microsoft OS for an Internet server. Wether they are a fool because they work for someone that forces them, or becuase they are ignorant, doesnt matter.
If an admin only knows Windows they have no business running an Internet server.
The vast majority of Windows users are either forced, or do so by default and arent aware there are any other options. I pity them. The few who actually CHOOSE to use Windows, especially in any sort of Internet/Server environment are fools. I pity them even more.
I'm not really sure why they bothered porting apache to Windows, to be honest. Sort of like cramming a V8 in a Pinto. I suppose someone decided they wanted to do it, and did.
I suspect its becuase some of the people developing sites for apache wanted to have an apache on to play with at home, but for some reason werent able or willing to install a *nix environment for it to run it.
The point is, for production use, if you are going to use an industrial strength, free (beer and speech) httpd, why on earth would you use a 'consumer' OS, pay license fees thru the wazoo to run it on, instead of linux, freebsd, or some other unix. And if your shop has a Windows-only policy, then most likely the same mindset that made that policy is going to mandate MS apps as well (IIS)
No one in their right mind is going to run a production webserver using Apache on Windows (With the possible exception of residential/hobby stuff)
I would say that anyone that had the sense to use Apache, would also run it on a stable secure platform. (And if they were *required* to run Windows by ignorant PHB's, then most likely they would be required to be 100% MS and use IIS as well)
Slashdot Mirror
If I did website design (which I dont), then I suppose that might be about the only valid reason that would come to mind.
*I do write backend code, but when I do I write it 'plain text', and let someone else do the design work around the result.
I feel for you. I use *no* MS software whatsoever. And I dont like OO either - its too 'similar' to the MS apps its supposed to replace. I suppose thats a good thing for people weaned on those, in order to allow them the opportunity to get off Windows, but I just cant stand that *type* of app.
I have no use for Powerpoint, or anything like it. I stick with ASCII text, so not much need for a Word or its equivalent. On the very rare occasion I need to do something spreadsheet-like, I use gnumeric.
Er, what? Why on earth would I *want* to?
I suppose my attempt at humor was too subtle.. my bad..
Whats this 'Internet Explorer' thing you speak of (google, click).. Oh, I see.. something that only runs on Windows, which I dont use either.
1. It points out that its easy to learn to use.
2. Actually, I dont care so much about the backend storage of it, so much as it is *represented* as 'one file', or 'one stream of ASCII'.
3. If you want to copy just part, then copy(/paste) just part - trivial. The point is, if you need to swap to a hot spare, or duplicate a standard site config to a new device for a new site, instead of having to wade through multiple menus, and compare the default settings in the new device with the ones in the standard config, and change the right ones, switch to the next menu, blah (eg 3com ascend etc), instead you have *ONE* 'stream of ascii' to copy, and you are done.
1. Once you know how to do something, its almost impossible to forget
2. tab-completion in both command-mode and config mode - you dont 'edit' the file, you type the config commands, which are saved as part of the running config. Unless you are copying the entire config, you dont do the whole download/edit/upload - you modify the configuration directly at the cisco CLI. You cant 'forget' to save part of the config, as 'copy run star' (copy running-config startup-config) will copy *every* thing from the currently effective configuration, to the NVRAM 'saved' copy.
3. If you *do* need to copy an entire configuration, between identical (or similar) devices, you copy/paste the entire thing, and bang, you are done.
Is it global warming, due to co2, and the polar regions melting? Or is it this, and the polar regions getting colder?
Or do they cancel each otehr out to some degree?
Sorta figures.
;)
Also, increasing altitude doesnt enable you to not need LOS, it is what *gets* you LOS between two distant points.
It doesnt matter.. SCO was charging that Novell was claiming it owned the Unix copyright when it knew for a fact that it didnt - this shows that that is absolutely NOT the case, that Novell full beleived that it did in fact retain that ownership.
It all depends on the frequency - some frequencies penetrate different materials with different effectiveness. I havent checked, but if we're lucky, maybe WiMax uses an NLOS frequency.
At $600/mo they arent going to be getting too many residential customers (nor do they probably expect to). Nor do they want to put up what is probably some expensive connection so they can get all 25 of them that would live in the rural area this would cover. They are targeting businesses who want an alternative to paying for a wired T1.
What *I* want to see, is equipment, affordable to end users, to facilitate point-to-point Megabit-or-faster wireless links over 30+ miles. 802.11 can do this, with the same equipment on both ends. I seriously home WiMax equipment eventually supports that, as opposed to only offering a huge expensive 'head end' to tie to the small end-user units (like DSL and cablemodems currently work)
Maybe its a font issue. Im running Mozilla 1.7 - I know MS HTML likes to specify specific, MS fonts.
:P
And yes, at least the site is in something that at least looks like HTML, as opposed to a flash-only site, or 'DOC' files.
Oh, those tiny things on the right. Wow. I never really noticed those there :P
Seriously, the ads in gmail are *very* discreet, and have never gotten in the way. I really do barely notice them (but yes, I know they are there)
Personally, I dont care about being able to access the google mailbox via POP, or even IMAP. What I want, is to be able to use the *google* interface, to access mail on other external IMAP accounts. (Or a downloadable version of the gmail interface to install on my own webserver, but Im not holding my breath for that)
Ok I guess it isnt that ludicrous to compress it, or to use zip.
I just had flashbacks to where I was going to get some MP3's from somewhere and *they* were individually zipped - which *IS* insane, becuase the resulting zip's were either larger than, the same size, or less than a dozen bytes shorter than the MP3 files were.
Even funnier - I just went to download an ISO, and its *in a ZIP file*.
ReactOS may well be cool, but *UGH* they really need to find someone that knows how to write HTML.
I wondered why as I hovered over links the font size changed, cusing the entire page to flicker all over the place - then I found why:
From their page source:
meta name="GENERATOR" content="Microsoft FrontPage 5.0"
Friends dont let Friends use MSFP
A. They've probably always done this - most registrars do these days. You probably just see it sooner now due to the changes at the
B. The grace period is usually 30 days. Its also something imposed by the registRY - google for 'redemption period' If you let a month go by without noticing your domain has expired, it must not be that important of a domain. If you have so many domains you lose track, perhaps you should get a bit more organized. Make a list with expiration dates, and check it once in a while. Maybe even sort it by date.
Cisco IOS, and its single config file, absolutely rocks. I was just looking at the man page for the config file for this project, and it stuck me as absurd that they didnt use the same syntax.
What I would love would be an IOS or IOS clone that ran on common x86 hardware, becuase, as you note, Cisco HW is expensive, even if you do buy used/refurb.
Ah yes, becuase if there *are* vulnerabilities in the systems, we want to make sure every district has the same vulnerability. Havent we learned anything from the MS monoculture?
I can see standardizing the processes, and the data formats (as long as the standards are open and subject to wide public scrutiny) but not which vendors or brands of equipment.
I think the whole concept of 'primary' elections operated by the state should go away. If its a private party, it should manage (and pay for) its selection of candidate to sponsor, on its own.
The concept of 'parties' as an official concept in the elections should go away as well.
He assumes that if everyone runs away from IE (or MS in general), that they will all be running to the same thing, and create another monoculture.
The idea is to NOT have a monoculture. To have an environment where there are *many* competing platforms and applications, and (becuase they all comply with certain published standards for file and network data formats) any individual (person or business) can choose from among many alternatives, and still be able to communicate with and send and receive data to/from individuals who chose something else.
*Eliminate* the monoculture. The solution is not for MS to fix its bugs. The solution is for MS to not have a monopoly (wether they jump or are pushed)
MS biggest fear is that once they are a monopoly, they will lose *all* market share (and to be honest, IMNSHO, rightfully so, their stuff is crap). MS is desperately afraid of having to compete on the technical merits of their products. Its something they never had to do before.
As you note, there is nothing to discuss.
If you need *me* to provide you with the reasons for my conclusions, you've either been living under a rock or been wearing blinders, for the past few years.
Only an absolute *FOOL* would knowingly choose to use any Microsoft OS for an Internet server.
Wether they are a fool because they work for someone that forces them, or becuase they are ignorant, doesnt matter.
If an admin only knows Windows they have no business running an Internet server.
The vast majority of Windows users are either forced, or do so by default and arent aware there are any other options. I pity them. The few who actually CHOOSE to use Windows, especially in any sort of Internet/Server environment are fools. I pity them even more.
I'm not really sure why they bothered porting apache to Windows, to be honest. Sort of like cramming a V8 in a Pinto. I suppose someone decided they wanted to do it, and did.
I suspect its becuase some of the people developing sites for apache wanted to have an apache on to play with at home, but for some reason werent able or willing to install a *nix environment for it to run it.
The point is, for production use, if you are going to use an industrial strength, free (beer and speech) httpd, why on earth would you use a 'consumer' OS, pay license fees thru the wazoo to run it on, instead of linux, freebsd, or some other unix. And if your shop has a Windows-only policy, then most likely the same mindset that made that policy is going to mandate MS apps as well (IIS)
No one in their right mind is going to run a production webserver using Apache on Windows (With the possible exception of residential/hobby stuff)
I would say that anyone that had the sense to use Apache, would also run it on a stable secure platform. (And if they were *required* to run Windows by ignorant PHB's, then most likely they would be required to be 100% MS and use IIS as well)