Not sure about the C++ problems you mention, but in Python there is Kamaelia and a dozen of other libraries targeted for creating scalable parallel systems.
Btw. an earlier post mentions the upcoming QT concurrency framework - if Trolltech is able to pull this out on all C++ platforms they support, then it kind of justifies Stroustrup's position, isn't it?
The fact that SSL sessions are being proxied shouldnt scare anyone away, says Joe Skorupa, an analyst with Gartner. Akamai, for instance, proxies SSL transactions - some of them involving e-commerce - for its customers, he says. Theres precedent for doing it and doing it where significant amounts of money are at risk
The strongest principle in computer security is simplicity.
True, but read the article. Firewalls are much simpler concept than what the author proposes: three layer architecture, ACLs, tickets, virtualization, strong clients, smart admins etc. etc.
I agree with you the trend is worrying, but I don't think shifting the responsibility to customers is the solution. It just shows in what a poor state the industry is today.
There is a full-blown computer in my wireless access point, mobile phone, DVD player. Soon in my TV, my fridge, you name it. I don't want to be the system administrator of my fridge!
Infrastructure, as you say, for distributing and installing security fixes is needed - but manufacturers will never invest into this unless forced to do so. So what we really need is security standards, extended customer protection, all enforced by regulations. NCAP crash tests for the home computer...
I couldn't find any justification for this hack except that the Mozilla MNG decoder is too big - (they say 200 k+.
How about streamlining the existing decoder instead, aiming for MNG-VLC only, a basic subset of MNG, already covered by the MNG standard, and not much different from what's proposed in APNG.
... but you honestly cannot know how much space it will take, how fast it will be, etc. Its sheer folly.
Hard requirements like these can be very valid in some cases. For example "this software has to fit in the DVD player's available flash" or "this video processing can't be slower than 25fps". Or even "we must fit on one CD otherwise packaging is too expensive".
Since you asked... I started Windows programming (with Hungarian Notation) when it was at 2.0. I wrote Windows applications for a living for long years, and I'm glad I don't have to do it anymore.
You are ignoring the context of this "invention". Hungarian Notation was invented to add some kind of type safety to a language (C) which doesn't have much.
But not often, really, and I'm sure you know how to use search & replace.
Search & replace can cause much bigger disasters - consider the case when you have variable names with similar starting/ending.
Newer refactoring tools make it even easier.
Refactoring tools? Man, we are talking about the era of Windows 1.0.
I wrote small and medium sized applications using wxWidgets for Linux and Windows and I really liked it. It's basically the only cross-platform/cross-language toolkit which is using native widgets, so your apps don't look like alien body on your desktop. QT, Fltk, Tk and Gtk are all faking the native look and feel.
Those #ifdefs you mentioned are rarely needed, mostly in cases when you are accessing platform specific features like OLE on Windows.
P.S. The Tk API is not horrible at all. Actually it's one of the most brilliant I ever seen. The canvas and rich text widgets were truly revolutionary at their time.
Not sure about the C++ problems you mention, but in Python there is Kamaelia and a dozen of other libraries targeted for creating scalable parallel systems.
Btw. an earlier post mentions the upcoming QT concurrency framework - if Trolltech is able to pull this out on all C++ platforms they support, then it kind of justifies Stroustrup's position, isn't it?
The kde-redhat guys do a great job keeping KDE up to date on Fedora.
Thanks, but these are three unrelated books. Over time, hopefully...
Needs Shockwave. Thank you, goodbye.
Have you ever been out in the woods on a bright moonlit stormy night?
$ xhost +localhost; su otheruser -c firefox
Just make sure you don't crash the validator!
-1 gram of matter?
Option "z" only works for GNU tar. Many older Unixes don't have it.
No need to deal with system libraries if you are converting the whole system: CPU translation + virtualization of some common hardware, a la VMware.
There is a full-blown computer in my wireless access point, mobile phone, DVD player. Soon in my TV, my fridge, you name it. I don't want to be the system administrator of my fridge!
Infrastructure, as you say, for distributing and installing security fixes is needed - but manufacturers will never invest into this unless forced to do so. So what we really need is security standards, extended customer protection, all enforced by regulations. NCAP crash tests for the home computer...
How about streamlining the existing decoder instead, aiming for MNG-VLC only, a basic subset of MNG, already covered by the MNG standard, and not much different from what's proposed in APNG.
Hacking around standards is so IE-ish...
By functional programming I believe he means functional programming .
Hard requirements like these can be very valid in some cases. For example "this software has to fit in the DVD player's available flash" or "this video processing can't be slower than 25fps". Or even "we must fit on one CD otherwise packaging is too expensive".
Make! Just about time. We would be ants without it.
Since you asked... I started Windows programming (with Hungarian Notation) when it was at 2.0. I wrote Windows applications for a living for long years, and I'm glad I don't have to do it anymore.
You are ignoring the context of this "invention". Hungarian Notation was invented to add some kind of type safety to a language (C) which doesn't have much.
Search & replace can cause much bigger disasters - consider the case when you have variable names with similar starting/ending.
Refactoring tools? Man, we are talking about the era of Windows 1.0.
Another problem is that if you change types, you have to change the names, too. Or if you don't, you end up with a completely misleading code.
I wrote small and medium sized applications using wxWidgets for Linux and Windows and I really liked it. It's basically the only cross-platform /cross-language toolkit which is using native widgets, so your apps don't look like alien body on your desktop. QT, Fltk, Tk and Gtk are all faking the native look and feel.
Those #ifdefs you mentioned are rarely needed, mostly in cases when you are accessing platform specific features like OLE on Windows.
P.S. The Tk API is not horrible at all. Actually it's one of the most brilliant I ever seen. The canvas and rich text widgets were truly revolutionary at their time.
Check out HP's PRM.
- apps