"combat congestion on its network"...which is more cost-effective than... you know... actually paying for the infrastructure to handle the utilization levels you are selling to customers.
I'm accustomed to clunky GUIs in FOSS. I like the "each tool does one thing well" unix philosophy.
But walking into GRASS thinking you will be getting some GIS work done.... will be a mistake. I mean, a Photoshop power-ish user can pick up Gimp and usually get the job done after the figure out none of the tools, windows, hotkeys, or features work the same or as well. But you can figure it out.
I found the documentation to be less helpful that I'd have hoped. I tried to picture my wife, a wildlife biologist with Arcview skills and a littel experience in R programming, trying to make heads or tails out of it. Each "feature" that someone might want in a GIS software suite, I ended up spending time trying to find it, download it, read the even worse documentation spread across unmaintained websites and dead links, then to find out many of them didn't work. I got the feeling that most modules were for some niche edge case that someone needed for a grad school project. At least I didn't have anyone telling to me to "roll my own then, noob"... so that was a plus.
Maybe it's gotten better since I tried it out? I really hope so.
Bandwidth is above all the term I hate the most. Or "broadband".
Somehow it came to supplant throughput.
I agree about fast vs quick... but I follow the slashdot convention of car analogies. A fast car has a high top speed. A quick car has high acceleration capabilities.
Slashdot Mirror
i'll take a capitalist race to the bottom over a communist forced march to the gulag.
"combat congestion on its network" ...which is more cost-effective than... you know... actually paying for the infrastructure to handle the utilization levels you are selling to customers.
Her Linux Administration Handbook (2nd Edition) was my first college textbook on the subject and I still have it.
It really is a pretty good text book. Even if it is bright purple with cartoon giraffes pondering 1337ness.
Engineering and....
Engineering and....
Engineering and.... smoking the reefer!
I know, right?
Imagine having to PAY to find out you are being attacked by.... "DOMAINS BY PROXY, LLC"
Once upon a time the US Government was THE Consortion for assigned names and numbers. They were THE registrar.
They gave it up.
A car made by GM probably will explode if attacked by hostile parties.
A mushroom stamp to unlock... On The Internets!
[ Patent Approved! ]
That is a VERY fair question.
I'm accustomed to clunky GUIs in FOSS. I like the "each tool does one thing well" unix philosophy.
But walking into GRASS thinking you will be getting some GIS work done.... will be a mistake. I mean, a Photoshop power-ish user can pick up Gimp and usually get the job done after the figure out none of the tools, windows, hotkeys, or features work the same or as well. But you can figure it out.
I found the documentation to be less helpful that I'd have hoped. I tried to picture my wife, a wildlife biologist with Arcview skills and a littel experience in R programming, trying to make heads or tails out of it. Each "feature" that someone might want in a GIS software suite, I ended up spending time trying to find it, download it, read the even worse documentation spread across unmaintained websites and dead links, then to find out many of them didn't work. I got the feeling that most modules were for some niche edge case that someone needed for a grad school project. At least I didn't have anyone telling to me to "roll my own then, noob"... so that was a plus.
Maybe it's gotten better since I tried it out? I really hope so.
I really WANTED to like GRASS.
ESRI is THE 800 pound gorilla in GIS.
The FOSS offerings are pretty cool, but I see no "black swan" like MySQL was to Oracle DB coming along in that space any time soon.
More than cloud, but less than synergistic paradigm.
I have a hard time seing organizing a community that looks down on "tryhards".
Bandwidth is above all the term I hate the most. Or "broadband".
Somehow it came to supplant throughput.
I agree about fast vs quick... but I follow the slashdot convention of car analogies. A fast car has a high top speed. A quick car has high acceleration capabilities.
Have you tried iperf in UDP mode both directions?
I would LOVE to just have ethernet eveywhere. I guess my city isn't as good as yours. Ha!
Douchebag.
For low-latency and lossless point-to-point across town, we couldn't find ANY ISP's connection technology that could beat the T1.
Expensive, but rock solid and quick (vs fast).
In space, no one can hear you Whoosh.
Those liberal votes aren't going to buy themselves.
It all start with "experimentation".
Science. The gateway drug.
So they would make good IP litigation lawyers?
So without an all-powerfull government redistributing money, everyone would starve huh?
And no one ever starved in a Communist country?
Every dollar someone gets without working for is a dollar someone else works for but doesn't get.
You don't see the downside to vote-buying or a dependant population, and you think I need help?
I'll take "stupid" people voting for liberty over "lazy" people voting for a living any day.
It's not just a matter of tedium, but of time.
It's the time and meta-programming overhead of environment, precompiler directives, massive API knowledge it takes to actually GET ANYTHING DONE.
In the small amount of time highschoolers get to actually concentrate on any one topic, you can't really get all that far into it.
Something that lets the kids get the flow in a shorter period of time is critical.
Hookers and coke.
You must be new here.
Slashdot is a Perl implimentation of the Greater Internet Fuckwad Theory, with a twist of nerd rage, leftism, and contrarianism.