Damn right.
Look at failure scenarios in depth. Despite generally good experiences with Cxxxo gear, they often did not explain failure modes.
For networks, Layer 2 versus Layer 3 load-sharing or failover. Time to restore service.
I once saw a web farm for one of the top news sites fail for 45 minutes because some junior sysadmin configured a Sun box with the switch management IP address in a large Layer 2 domain, and VTP went down.
Little things, like not having enough RAM on a supervisor module caused the box to be down for 2 hours while some poor guy baby-sat an xmodem serial transfer from a laptop.
Note, some things like redundant switch fabrics are really only the cost if you're writing 5 9's SLAs for paying customers.
Ultimately, it takes experienced, senior engineers to know what to buy. Not some $40K MS cert d00d who thinks he can do the job.
-RJ
Re:freenet vs fascist corporations
on
Retro Vision
·
· Score: 1
You don't need to conceal what the _network_ is sharing, just _where_ it's at.
In my mind, Freenet, or Freenet+ (tm) will completely conceal your identity and what you have, while a master (distributed, of course) directory will allways list the current contents. Bits of encrypted files will be stored throughout the network.
Perfect for stifling over-litigious corporations
that won't sell you the content you want, but prohibit any distribution.
I would agree with you in the main, but add these points
QT (and KDevelop / QTDesigner) are really the coolest. Too bad they have priced themselves out of the small developer market.
Borland Kylix C++ uses QT under the hood, but who knows whether Borland will continue that product. It's been a _very_ long time since it was released. With Borland's infatuation with.NET, I don't really think we will ever see a native *Nix Kylix 4.x.
FLTK is really cool, very nice people, but I had concerns with the fact that you could only have static callbacks, and the fact that it did not use sizers or layout managers, and getting some of the panels to size properly is a royal pain in the butt.
WxWindows is the the most mature of the free toolkits, but I walked away. I found that it really did not support Threads, really did not support a integral double-buffered window, and I found a number of gaps in the docs. When I raised the issue of updating the docs, there was a not-very-friendly flame war where everyone hated one or more doc structures, and so nothing was done.
FOX is my chosen destination for now. It has very good drawing (minimal or no flicker), layout managers, and threads (in add-on libs, at least).
The only problem is a GUI RAD tool, and we've almost got something usable with FOX DialogEditor.
>>One area I think where WxWindows is still unsatisfactory is in the RAD department
>>using Python
Dude - do yourself a favor and check out WxGlade -it spits out good Python, and the author is very responsive to suggestions. The rest of the RAD tools for WX did not make the cut for me.
-Don
Slashdot Mirror
For networks, Layer 2 versus Layer 3 load-sharing or failover. Time to restore service. I once saw a web farm for one of the top news sites fail for 45 minutes because some junior sysadmin configured a Sun box with the switch management IP address in a large Layer 2 domain, and VTP went down.
Little things, like not having enough RAM on a supervisor module caused the box to be down for 2 hours while some poor guy baby-sat an xmodem serial transfer from a laptop.
Note, some things like redundant switch fabrics are really only the cost if you're writing 5 9's SLAs for paying customers.
Ultimately, it takes experienced, senior engineers to know what to buy. Not some $40K MS cert d00d who thinks he can do the job.
-RJ
You don't need to conceal what the _network_ is sharing, just _where_ it's at. In my mind, Freenet, or Freenet+ (tm) will completely conceal your identity and what you have, while a master (distributed, of course) directory will allways list the current contents. Bits of encrypted files will be stored throughout the network. Perfect for stifling over-litigious corporations that won't sell you the content you want, but prohibit any distribution.
QT (and KDevelop / QTDesigner) are really the coolest. Too bad they have priced themselves out of the small developer market.
Borland Kylix C++ uses QT under the hood, but who knows whether Borland will continue that product. It's been a _very_ long time since it was released. With Borland's infatuation with .NET, I don't really think we will ever see a native *Nix Kylix 4.x.
FLTK is really cool, very nice people, but I had concerns with the fact that you could only have static callbacks, and the fact that it did not use sizers or layout managers, and getting some of the panels to size properly is a royal pain in the butt.
WxWindows is the the most mature of the free toolkits, but I walked away. I found that it really did not support Threads, really did not support a integral double-buffered window, and I found a number of gaps in the docs. When I raised the issue of updating the docs, there was a not-very-friendly flame war where everyone hated one or more doc structures, and so nothing was done.
FOX is my chosen destination for now. It has very good drawing (minimal or no flicker), layout managers, and threads (in add-on libs, at least). The only problem is a GUI RAD tool, and we've almost got something usable with FOX DialogEditor.
>>using Python
Dude - do yourself a favor and check out WxGlade -it spits out good Python, and the author is very responsive to suggestions. The rest of the RAD tools for WX did not make the cut for me. -Don