Miguel de Icaza Debates Avalon with an Avalon Designer
Karma Sucks writes "In an interesting debate with a Microsoft employee, Miguel points out some crucial flaws in Microsoft's Avalon strategy. Perhaps the most shocking revelation is the absolutely horrendous inheritence hierarchy exposed by the Avalon API. Miguel himself is clearly not amused, saying 'We do not want to waste our time with dead-end APIs as we are vastly under-resourced, so we must choose carefully.'"
here comes timbuktoo!
been trying to read more for a few minutes. first time i see that mesg instead of the story.
post
" I totally agree, this is a huge issue. Phishing attacks, spyware, malware, viruses, and more are out there and probably the largest problem facing computer science today. This isn't a Microsoft, Linux, or Java issue - this is a "good guys" issue. Windows XP SP2 is probably the best response to Miguel's security concerns. The integrated firewall, security center, and dozens of other security related features are really the first line of defense. After the basics are resolved there, I would say that the new enhancements to the security system in Avalon are a great step. Not only is Avalon built from the ground up to be secure, but we are enhancing the security system for better application level security, and simpler more understandable presentation of security decisions to the user (hopefully in most cases this means no decision). As to the specific issue of Phishng that Miguel brings up, that is still mostly a research level issue, which I'd love to see creative solutions to. In Windows today there is the secure desktop, but you must press Ctrl+Alt+Delete to get to it first. "
Creative Demolition
Joe Beda had said that Avalon is going to be more of an advanced UI/Visualization toolkit, while Dx will continue to contain all the other serious stuff.
Now, it looks like Avalon can do 3d on it's own and maybe more too -- what's the idea behind this anyway?
Are they trying to get a fresh new API or something? It seems unlikely, since I remember Joe and Scobles saying that they will probably be using Dx for serious graphics and game development. The redundancy seems strange.
From the presentation --
Avalon 3-D are not a replacement for Direct3D
You will find Avalon 3-D useful if:
- You want to integrate 3-D seamlessly into an Avalon app that also contains 2-D content, controls, etc.
- Platform features like Remote Desktop and multimon are high priorities for you
- You want to easily add 3-D functionality without quickly without needing to learn how the graphics hardware works
You will find DirectX useful if:
- You want access to all of the features provided by the graphics hardware
- You want to have full control over how your scene is stored and managed in memory
- Plan for interop between Direct3D and Avalon
Render Direct3D in a HWND and host within Avalon
So basically it seems to help ease the creation of bells and whistles, more than anything. Weird.
And oh, completely offtopic -- what's the deal with saying, work fine in OOorg -- shouldn't that be works fine with OO? Why the org/.org thingy?
Vastly under-resourced?! This coming from a Microsoft employee too.
As far as I understand, Mr. Icaza is now working for Microsoft, and he spends his energy on porting Microsoft ideas and projects to the Linux platform(s)... So why he criticizes Microsoft plans in the public?
We do not want to waste our time with dead-end APIs as we are vastly under-resourced, so we must choose carefully..
.NET API, he shouldn't bite the hand that feeds him!
Well well well. Isn't it easy to complain about an API when we aren't the ones responsible for creating it? Considering he is the one copying the
unlike the current pixel based 2d rendering system of today.
:)
Not necessarily 3d as in "3 dimmensional" but on the other hand not necessarily restricted to what we can 2d either
Why even waste your time at all on a dead end OS such as Windows? Think of the wasted BILLIONS pumped into one of a thousand projects they have on the burners (front and back). Think of the OS that could have been, if they were not bent on ruling every single aspect of the tech world.
The obviously didnt learn with MFC.
"When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
New news, same story:
- Icaza insults Microsoft policies.
- Nerds rally behind Icaza, he's just so smart to stand up to Microsoft and point out things we already knew.
- Other, more cynical nerds point out flaws in what Icaza said, possibly contradictions to previous comments or connections with MS.
- Mods find this comment flamebait, mod it down.
- No one cares.
?????
- Profit!
Mod this insightful, you insensitive clod.
The Open Source way (Miguel's):
/ Se p-09.html
8 5- 10e3-48ee-a6f5-cc4b886ce668
http://primates.ximian.com/~miguel/archive/2004
Date is included, name of the author, the word "archive", the "html" extensions.. easy to understand at a glance, I have a good ideae what that URL points to. It's not "perfect" (it uses American month names rather than a more generic 2004/09-09.html) but pretty good as far as URLs go.
Now check out the Microsoft dude's URL:
http://www.simplegeek.com/PermaLink.aspx/eb453f
What? I have no idea what that points to. Maybe an insightful bit of commentary, or maybe a gaping anus. Who knows. Any subtelty hidden behind a confusing GUID. Extension is "aspx" which is an add for ASP.NET rather than a meaningful extension.
Ladies and gentlemen, I rest my case.
This is a call to arm, sent out to all sensible /.ers. PLEASE, DO NOT embed senseless links within your story submission.
It goes against the ethics of every data purist out there to have to mouse over words like "interesting" and "debate", carefully examining the status bar URL, to find out WTF that link points to.
Enough already.
Amiga? or the "dying" BSD?
Help fight continental drift.
I've said this before, here and elsewhere: WGHIII[1] has said several times in the past (and was at conferences in the mid '90s when & where he said them): "...people do not want bug fixes - they want new features...". This is frequently borne out by the underlying architecture Microsoft presents in their products. A semi-stable underpinning, capable of supporting certain elements is put into place such that products & features can be built upon that architecture. "Patching Architectural Holes" (Security, Stability, etc.) can be fixed via patches later[2]. Unfortunately, this means users suffer frustration for a semi "feature rich", unstable product, and developers discover situations where they write "three sides around the barn" when the pieces don't fit together as the philosophy would lead one to believe.
. html
There are other companies which spend a lot of time on the architecture - almost to a fault - knowing once it is solid, they can add the users' heavily desired features without worry about the stability beneath it.
All developers know about both scenarios as they either crave and know the the outcome if they are permitted to put the architectural stability in place or they are forced to charge ahead with building on top of wet toilet paper.
[1]William Henry Gates 3rd
[2]Providing a vendor is even willing to do so. And the question begs to be answered: How unstable can an architecture be such that patches can be safely made to it (without risking screwing the pooch) to make an improvement? Remember the "three sides around the barn" development? What happens to developed code if the OS suddenly "works" correctly?
Just remember....
______________________________________
My Trunk Monkey can beat up your Trunk Monkey.
http://www.suburbanautogroup.com/ford/trunkmonkey
- Microsoft talking design and technologies out in the open with other developers who aren't Microsoft employees? Even talking with Free software advocates? Man, that's good to hear, honestly. If this were system-wide, I bet it'd be good for both sides.
- Reading Miguel mention that many APIs (Avalon, Tk, Swing, GNOME, Xview, Motif) at least gives one the impression that he might actually know what he's talking about. Let me give him the benefit of the doubt. It makes me wonder how many Microsoft employees have that much understanding of non-Microsoft APIs. Probably plenty, but the few I have encountered seem so immersed in Microsoft culture that they appear to have little understanding of what's going on outside of the Microsoft sphere.
Now, I should say that I'm no real programmer, but I've done some. The "real" programming I've done is computational code that runs in the console, with a couple of GUI front ends. So, I'm not going to claim any kind of serious perspective on this.Curmudgeon Gamer: Not happy
OpenOffice was renamed OpenOffice.org to avoid a trademarked name conflict iirc.
> Mr. Icaza is now working for Microsoft, and he
> spends his energy on porting Microsoft ideas and
> projects to the Linux platform(s)... So why he
> criticizes Microsoft plans in the public?
It's obvious, he wants to be in the payroll of Microsoft and stop working for them for free. All these years of hard work should be rewarded!
In the finest tradition of Slashdot...
PWN3D!
Karma: Segmentation fault (tried to dereference a null post)
A number of my peers like to bitch about how "Swing is hard to learn" and I get called an elitist for laughing at them. Of course, unlike most of them I have tried to learn other toolkits and have come to the conclusion that Swing's design really is the de facto gold standard for how a GUI toolkit should be arranged for practical development. It is fast, extremely logically structured and the documentation is really straight to the point for when you need to look stuff up.
I could never get used to Windows Forms. It still amazes me that the layout manager concept isn't considered a standard part of the UI toolkit design process now. Developers shouldn't have to automatically manage most GUI layouts.
Click here or a puppy gets stomped!
Since when were 3 commentless blog posts considered a debate?
Chris Anderson replied with the following in regard to ignoring standards.
Interestingly enough, we never "ignored" standards. We spent a huge amount of time understanding and evaluating the existing standards. SVG and CSS both were passed on because they weren't adaquate to meet our needs. WinFX is a platform for the next decade or longer - we can't start with a base that doesn't meet our needs.
What a load of shit. That mentality is where the "embrace and extend" came from. It might not meet Microsoft's needs, but CSS and SVG are the bloody standards that people are using! What do they know about the coming decade that we don't?
What Chris said pretty much flies in the face of the entire paragraph that Miguel wrote! Look:
I understand why someone would invent their own version of SVG or their own version of CSS: those standards can be difficult to implement, and growing your own version is a lot simpler than having to adapt an existing model to a new model.
I would have probably done the same if I had been in their position: its easy. But I would think that Microsoft has a higher responsibility towards the developer base that must create tools that interop with third party components: creating a new standard for graphics just because its `easy' is not really a good answer.
Implementing SVG might have problems and limitations, but the advantages outweight these problems: there are plenty of tools today to produce and consume it and it fits better with the rest of the industry. A benefit that Avalon users will not have and will just partition the industry again for a fairly poor reason.
Standards are there for a reason. If Microsoft doesn't like them they can see figure 1. I have a feeling that Microsoft may not dislike the standards themselves, they just don't like the fact that they're not their standards.
-kidlinux.
And why do we care?
1. embrace & extend svg & xul by anouncing avalon/xaml vaporware
2. sit on hands as svg & xul die
3. profit
Before adopting WHATWG, read the moonlight.NET EULA [http://www.microsoft.com/interop/msnovellcollab/moonlight.mspx]
"Hard core" means "death march."
No, it doesn't! It means things done right. It means things done so that a definitive API with expandability for the furure may be developed that doesn't have to be scrapped and started over because everyone working on the project was brain-dead and so desperate for a quick solution to meet looming deadlines that a poor implementation was chosen over no implementation at all.
Microsoft... where do you want to go today? To hell!
"... Interestingly enough, we never "ignored" standards. We spent a huge amount of time understanding and evaluating the existing standards...."
I guess he is talking about Microsoft's efforts in programming. It is certainly not true elsewhere with MS. Take for instance the new Microsoft online music store. If I use a W3C complient HTTP client that isn't IE (or risk security issuse adding ActiveX to your HTTP client), you can't use or view their site correctly. Hum, no customer HTTP client choice there. And certainly not W3C complient. So tell me about following standards again.
Miguel makes a semi-interesting point, but Mr. Microsoft makes a better one: why on earth would the average programmer be rooting upwards through the class tree 10 or 11 levels?
The whole point of abstraction is that Joe Programmer knows "button" derives from the next highest object. That's it. It's nice to know the other levels when you're learning the language's abstraction model for the first time/creating it, but once you get into down and dirty practical programming, you only really need to look up and down a few levels. If you're going all the way back up to Object and reconfiguring it, you're reinventing the wheel. That was the language designer's job.
...who thinks that murdering innocent women and children is prefectly OK.
Best Buy can have you arrested
Well, yes it is complex. But it only appears complex because of a lack of abstraction. It is a matter of perception.
There has always been a big clash between the simple black box and the gazillion arugument camp
In case you haven't noticed, I favor the simple black box.
Let me just say that the reason why people don't fall over when they walk, or birds do not fall out of the sky when they fly is because of an interface which was designed with a very simple black box interface.
Enuf said. Either you get it or you don't.
"My concerns stem from the fact that we do not want to waste our time with dead-end APIs as we are vastly under-resourced, so we must choose carefully."
So? Does he expect Microsoft to change what it is doing because they don't have the budget to port everything they are releasing? If you don't feel like it is a priority then fine, but I fail to see how that should factor into a analysis/review of the software itself.
Then again it seems to be increasingly rare for people to make unbiased decisions these days, so I guess I shoudln't expect anything less.
"I have a porkchop, you have a porkchop. I have a veal, you have a veal".
If you didn't notice, today's headline pointed out that US troops killed 22 gunmen, and 23 others, many of whom were children.
If you have a "Support Our Troops" sticker on you truck, and you probably do, then you think murdering innocent women and children is perfectly OK too...
I'm waiting for the part where you tell us all how to disarm an enemy soldier without killing anyone, especially when said enemy soldier is hell-bent on killing you.
It's one thing to be an idealist or pacifist; it's quite another to actually implement it. Ask Ghandi's dead Indians how much fun it is to be a pacifist.
Hey guys,
Just wanted to point out that the inflamatory
comments that are being made in my name are someone
else's idea of fun. Some guy decided to squatter
the login `Miguel de Icaza'.
Miguel.
so I will....
after years of programing I have come to the following:
1. Object-C rules. NeXT was the best.
2. Aqua is better thought out then any of this crap!
Just my 2 cents.
Oh, yes I am an Apple Fan Boy and proud of it!
2. Aqua is better thought out then any of this crap!
Except that Aqua is pixel based and cannot handle scaling.
Oh dear God, this needs to be modded up. I'm seriously sick of extraneous linking.
Quote:
"In Windows today there is the secure desktop, but you must press Ctrl+Alt+Delete to get to it first. "
He must be talking about pre-NT days, because he cannot be talking about their worthless taskmanager. Telling the taskmanager to kill a process is like a police officer telling Rodney King to pull his car over. In theory it should work, but most of the time is just ends with a system crash.
Dont believe me?? Well try developing M$ service application's for a living and see how many times you reboot your dev machine because of processes getting stuck in M$'s memory "wonderland". Annoying to say the least...
This guy is doing good things... helping mono is awsome.
I'm not trying to be Xeno Phobic but write in the language that people can best understand your arguments. Miguel's blog is a bunch of off the cuff un-supported arguments.
Un-supported only in the sense that there are no examples and/or references. He may be right but doesn't do a very good job expressing his thoughts.
It would be nice to see a better articulation of why it is that he's so concerned with Avalon, in the section about the developer needing to know a lot of the internals to implement code, he's very short on details of why this is. If your going to go to the trouble of jotting good thougts down in a blog - make them worthwhile.
Isn't this kind of discussion rather lethal? What would stop Microsoft from doing the same thing they did with Sender ID? 'Royalty Free but non-transferrable'. Is that why they are acting more open and saying .NET stuff will be RF patented? Are we sitting on a landmine?
It's all fine and good if Miguel's plan is to license them for use in Mono if needed, but that means it's more useless than Java to the Free Software world.
If you've looked at .NET, you'd see that they have. MFC is dead.
> Perhaps the most shocking revelation is the
> absolutely horrendous inheritence hierarchy
> exposed by the Avalon API.
Good grief. This coming from a GNOME luminary
which said project uses Gtk? Gtk is a piss-poor
toolkit. They should have stuck with the X model
of toolkit implementation. Instead we got stuck
with a toolkit which doesn't integrate well with
X and doesn't particularly stand well on it's
own. Get your own house in order first.
Noooo, Quartz is based on a PDF-like model.
Icons, and the decorations on the widgets (such as buttons) are currently done with bitmaps, but there's no technical reason they couldn't switch to resolution-independent graphics for those elements.
Aqua would scale *now* though certain elements would be somewhat blocky at larger sizes.
I don't know anything about Quartz, so this has piqued my curiosity. By "PDF-like", do you mean to say that Quartz is based on Postscript? And it's fast???
Now, THAT would be a thing to behold.
Please mod this post only if you think others should/n't read this. I have enough ego^H^H^Hkarma. Thanks!
I wonder if it is possible for Rocklyte to implement 3D rendering features like in Avalon in their Athene Desktop.
I have tried out Athene and it is very fast - they claim over 25% speed increase to X11.. This is a complete alternative to X11 but can also run X11 apps.. Try out the free version http://www.rocklyte.com/athene/. You can run games on the desktop using SDL.. they have a version of Doom and Quake available for download as well.
I was very impressed with both the desktop as well as the underlying technologies - the desktop is scripted using an XML-like language called DML..and the engine used is called Pandora.
The graphics driver technology is based on SNAP graphics from SciTech and seems very easy to manage.
My two primary gripes with the system were that the licensing seems a little restrictive.. and also, the package management software seemed very weak (if you are using the OS).
But other than that - a very polished desktop.. and underlying API. Most impressive.. Definitely the most innovative and cutting edge Linux desktop and distribution around.
Also wonder if there is a move to implement Windows Forms (for Mono) using the Pandora Engine SDK.
"This isn't a Microsoft, Linux, or Java issue"
The whole point is that it *is* a Microsoft issue. Java is seldom used to write viruses because it is difficult to do. This is because Sun thought about security when the designed the thing in the first place. Linux is pretty secure, too, partly by design and partly in the nature of OSS model iteslf. Windows is not secure and cannot be (consider, for instance, that any application can post an event in any other applications event queue). To misquote Douglas Adams the reason that the fundamental deign flaws in Windows are seldom experienced is because they are entirely hidden by the superficial ones. SP2 has been largely and extensively debunked for the lipstick on a pig that it is here.
The object hierachy does look horendous for buttons compared to .net 1.1/2.0 which has
System.Object
System.MarshalByRefObject
System.ComponentModel.Component
System.Windows.Forms.Control
System.Windows.Forms.ButtonBase
System.Windows.Forms.Button
I hope .net doesn't go the way of the java framework - complex and unintuitive - as this is what attracted me to .net from java in the first place, the excellent hierachy of the classes, the extra functionality and also the extra bit c# has.
Having said that, Chris Powell does point out that it's not even beta yet...
Nothing costs nothing
From the simplegeek (Microsoft) guy.
.doc, but in this case it is much more than a music experience taking place.
'I actually really do understand some of the technical and political reasons why everyone (Real, Microsoft, Apple, etc.) participate in these format wars, but in the end it is consumers that pay. '
Well, it pays your salary!
A lot of developers for Linux don't care for formats. They just make everything work the same - xine, mplayer vlc.
Then some app is build upon this technology - and bazaam, both Ipod, CD's and music players can 'play' every format.
Why? Because the developers wanted it. In Microsoft and Apple it would be a disaster if they suddenly had support for the other standard (their own standard would loose).
So get your ass out Chris - com*friggin*plain to your Boss. If you think it is hurting you - a technology expert, how do you think the rest of the world is feeling towards Microsoft?
It is the same problem with
As Miguel said - please start to cooporate, in the long run it is best for both of you.
Blind fanboyism doesn't get you anywhere ...
With NT 4.0, they moved the display drivers into the system space, not the entire GUI subsystem. This was for performance reasons.
I knew it was a bad idea, and I'm sure that there are those at Microsoft (Dave Cutler, probably) who thought it was a bad idea too. But it's a tradeoff, and at the time the business risk was considered acceptable because they had a driver certification program, and they were going to make sure that drivers would behave themselves.
Chip H.
Aqua is pixel based and cannot handle scaling.
I infer from the sentence above that you don't really grok what Aqua is.
Aqua is the look & feel of Mac OS X: the shape of the scroll bar elements, the standard window title bars, the way that modal dialogs "slide out" from the window they pertain to, etc. IOW, Aqua is appearance and behavior. To say that it's "pixel based" is meaningless.
-jcr
The only title of honor that a tyrant can grant is "Enemy of the State."
Seems that was the way that Miguel used to see Avalon, and the almost-defunct WinFS (check out ReiserFS4 metadata, btw), but now, surprise, is not!
.NET is killer. It is what Java wanted to do with the Web, but with the channel to deploy it and the lessons learned from Java mistakes."p r-24.html
s s?thread_id=27453
r view_with_miguel_de_icaza_cofounder_of_gnome_ximia n_and_mono.html
Check this out:
"They are all fine points of view, but what makes Longhorn dangerous for the viability of Linux on the desktop is that the combination of Microsoft deployment power, XAML, Avalon and
http://primates.ximian.com/~miguel/archive/2004/A
"Avalon will be a lot easier to write than the previous ActiveX; it's a lot prettier, so when organizations are using Longhorn-based machines, which I assume will be sold everywhere by 2008, it's going to be increasingly hard for the rest of us to get there unless we have an implementation of an equivalent technology."
http://www.theserverside.net/common/printthread.t
"Longhorn has kind of a scary technology called Avalon, which when compounded with another technology called XAML, it's fairly dangerous. And the reason is that they've made it so it's basically an HTML replacement. The advantage is it's probably as easy as writing HTML, so that means that anybody can produce this content with a text editor."
http://news.netcraft.com/archives/2004/04/28/inte
So, what was all that crap that he told us "fear Microsoft, you morons, we need something like they have to have more 'competition' there" about?
A big FUD? A way to try to implement and waste time with, all we know, some probabily vapourware or with a product that does not work well? Think about WinFS. He also used to say that it will be the doom for all the Linux users don't have a stuff like that, but even the Microsoft users will not have a stuff like that, at least the way all the utopic dudes wants to!
Now that the technology owner is in trouble with it, he says that it's a lot of shit? Oh, come on.
The big point here is that, with some effort, you don't need Microsoft programs anymore to do what your company needs to run your computers. And we don't need people trying to convince us that WE NEED THEM if we really don't need. Gimme a break.
just use embed instead.
thank God the internet isn't a human right.
New reply from the Microsoft guy.
Watch great movie opening scenes!
Hmmmm,
OSS has more developers than Microsoft as a whole.
Microsoft has more developers than Mono alone.
Mono is tracking Microsoft APIs.
Would microsoft choose to generate a mass of APIs, wait to see which one MONO follows and then deprecate it?
Nahhh... couldnt possibly do that!
That would be mean!
The key problem with the microkernel debate is that there were few true microkernels around at the time. Mach (the only freely available microkernel at the time) was a perfect example of how *not* to write a microkernel. The microkernel is about as big as Linux itself and it's slow. It's little surprise that Microsoft integrated tons of stuff in to their Mach microkernel. It would be pig slow if they didn't
x OnL4/
If you want an example of how a "microkernel done right" looks like, take a look at the L4 kernel.
BTW, Linux *has* been ported to this real microkernel:
http://os.inf.tu-dresden.de/L4/Linu
It's a bit slower than regular Linux but not noticably so and it gains all the advantages of a microkernel design.
Hmm typical MS blinders. As they have forgotten that there is already a project with this name.Apache Avalon is a API/Framework for java.
I'm a good cook. I'm a fantastic eater. - Steven Brust
I wrote software on a windows platform for years. The problem with MS is that it is first and foremost a marketing driven company. They don't release any software unless it somehow ties you to the operating system.
I don't want to be chasing their tails I like technically driven solutions. If you want to make me a linux developer happy give me this. Take mozilla and make it a real development platform. Put a nice clean api on it and let me use mozilla to write all of my software so it will run fast on anything. This is what I want, doing so would neutralize the platform, the only thing I care about.
Got Code?
You make some good points. But remember a few other things.
NT is (or at least was) a microkernel. That's been compromised considerably with poor decisions later on, but you can't consider it a monolithic kernel - it's really a hybrid kernel that started as a microkernel and then adopted some monolithic practices.
On the other hand, Linux started as a monolithic kernel, and clearly still is, but it's incorporated an awful lot of that 'modular design' logic when it made sense to Linus, and in some ways could be considered closer to a microkernel. You don't see the UI running in kernel space, obviously, while NT, the ostensible microkernel of the pair, does exactly that. Linus started with a monolithic kernel and adopted microkernel-ish logic wherever it made sense to him, whereas MS started with a microkernel and imported monolithic logic where it made sense to them.
So the labels can be a bit confusing when applied to the real world. There isn't just A and B, but all sorts of possible variations and permutations with some features of each.
L4-Hurd, I agree, will be something very sweet, when it's finally ready, but it does seem to be a dish that needs a very long simmering time.
Lastly, I'm not sure who you're listening to, but obviously not people worth listening to, if they're saying that binary-only drivers are a good thing. They aren't. Linus doesn't support them, the Linux development model doesn't support them, they are strictly not to be encouraged. Anything that discourages them is probably a good thing.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Friends don't let friends enable ecmascript.
"My name is Miguel de Icaza. You killed my development environment. Prepare to die."
This space for rent
This reminds me of the kind of debate that goes on in the corp world. Say, two guys (good guy, bad guy) argues the right way of using a product. ... I agree that everybody needs this soap, but it should be used with warm water",
One of the (good guy) says, "Well, Yea
the other guy answers "No, no no no! It can be used with both cold AND warm water!". To add to the cred, the "disussion"
turns ugly (now, this reminds me of the 2 dudes Bush&Kerry) and they start to throw soaps on eachother. Whereupon the good guy proceeded to take
that mittenful of the deadly soap crystals and rub it all into his (bad guy) beady little eyes with a vigorous circular motion hitherto unknown to the people of
this area (this sound familiar), Well he (the bad guy) was very upset, as you can understand And rightly so, because the Deadly yellow snow crystals had
deprived him of his (hang on, yellow snow?? This is a RIPOFF!!).
Ehhrr ok, this has turned a itzy bit OT, so I wish U all a nice holiday!
Cheers.
One of Miguel's complaints is that Avalon exposes too much? This is actually something I *like* about Swing.
Let's say you project that involves storing a little extra info with each character in a text editor. Each character has unique info, so you can't efficiently use the usual sorts of mechanisms...what you really need is to replace the core storage model of the editor, so that each character is 64 bits, with a few extra methods to pull those out.
In Swing, this is easy to do, because it exposes every component of the text editor. The storage object implements a simple interface, so it's easily replaceable. I haven't found any other API that allows this.
IMG was added for Mosaic in one of the first short-sighted decisions which led to the mess that was later called HTML 3.2. When submitted for peer-review (your so-called "proper channels") people suggested that maybe it would be better to make a more general embedding element and that it should be a container so that backward-compatible content could be included inside. The ALT, element, if you think about it, is useless for this because no previous browser knew to look there! Also, it can only support plain text, so more "rich" alternatives such as a link to another document or even just a few paragraphs of text are not an option.
Mosaic developer said "tough luck, I've already written it" and released it as it was. Since Mosaic was the biggest browser at the time people quickly sucked down this new IMG element and everyone was forced to co-operate.
To me, this sounds like exactly what Microsoft is doing. IMG was a quick hack with little forward planning just to get images into web pages as quickly as possible. Mosaic and then later Netscape continued this trend by adding poorly-considered features such as FONT, APPLET, EMBED and framesets which are now, thankfully, deprecated in current W3C specifications in favor of better thought-out and more general features. Sadly, W3C's versions have buggy support in most current browsers. (They haven't replaced frames, but I suspect that's because it was a pretty bad idea in the first place, so the best thing to do is just to avoid it.)
How is something that doesn't provide any evidence or arguments at all considered insightful? ...
Blind fanboyism doesn't get you anywhere
Wow. As they say: "You must be new here". On Slashdot, blind fanboyism (as long as the object of adoration is Linux, Apple, or Kerry/Dems) gets you all the mod points you could want!
i wish someone had the time to separate the facts from this discussion.
microsofts 'avalon' is the 'next version' of software to come out of redmond, ok.
i submit the following tensor:
microsofts' ( avalon ) < Hardened ( Linux + mozilla + openOffice + Apache + mySQL/PostSQL + Perl/PHP/Java/Mono )
Imagining... imagining... nope, can't do it. Must not be possible.
Aqua is appearance and behavior. To say that it's "pixel based" is meaningless.
What I mean is that controls are absolutely positioned. Avalon and Gtk and Qt are container based, controls are positioned based on the containers they are in.
What I mean is that controls are absolutely positioned.
No, they can move and resize based on their resizing attributes.
-jcr
The only title of honor that a tyrant can grant is "Enemy of the State."
- Microsoft apologists mock /. programmer defenses of Icaza
- Mods find mocking funny, mod them up
- Insightful discussion of topic is stifled