Exactly. Browsers should and will do the best with what they're given. The ability to render pages throughout errors is a good one. No browser manufacturer in it's right mind would limit the pages their customers can browse.
Those who talk about browsers being more harsh on bad HTML being a good thing are fools and don't have a clue.
OK.. but which is it? You first say if you were to measure it to the "micro second, some difference might be noticed". Then three sentences later you say there is "no difference". You seem confused, and you were right the first time.
There is a difference (however minute) and it's due to BeOS not actually having the ability to create fields at the FS level. It's trivial to create file examples that show off the flaws in their method and to make peformance suffer. There are filesystems that do it better, through better architecture. Realise this and you'll see my point - that BeOS can improve it's so-called meta FS.
ps. I've used BeOS for several years now on PPC and x86, programmed for it, and you're probably using some of my apps (here's a hint - Doublin). Oh, and there's much more anger and arrogance without fact or links or proof than anything I'm putting out, believe me.
-- Eat your greens or I'll hit you!
Re:More like BeOS's filesystem?
on
MySQL FS
·
· Score: 1
Forceful argument. Well done old chap!
-- Eat your greens or I'll hit you!
Re:More like BeOS's filesystem?
on
MySQL FS
·
· Score: 1
No, he responded to teach us about meta filesystems as if that had anything with my point. He did not provide any proof. The closest he got (before he went offtopic to so kindly teach us about meta filesystems in the mp3 example) was to say: "BeOS doesn't have one big clump of data that is partitioned; it has a lot of little bits of data."
Wow.. i'm convinced. Certainly much evidence be had there!
Furthermore, he says you can define your own fields in the FS was from an option in a menu (this far too high-level). The fact remains that the filesystem doesn't have defineable fields, though it pretends to.
What's the difference if it acts like it does and is transparent to the applications? Easy. In simple situations (such as putting an mp3s ID3 in the FS) this has little of a performance hit. But if you were to put 100 meta attributes in the FS and store various sized chunks of data the performance degrades very quickly.
You just cannot read the meta as fast as the other types - oh gee, and I wonder why?
I mean it's an interesting hack but that's all it is. Genuinely adding fields to a filesystem would be impressive and as fast as any other FS request and.. well, it's been done. But not by BeOS.
...and you know. I thought the trolls were lying when they reprinted this but now it's happened to me.
Slow down cowboy!
Slashdot requires you to wait 1 minute between
each submission of/comments.pl in order to allow everyone to have a fair chance to post.
It's been 1 minute since your last submission!
-- Eat your greens or I'll hit you!
Re:More like BeOS's filesystem?
on
MySQL FS
·
· Score: 1
There's no way to actually define a new field at the FS level.
Sure there is. Preferences->Filetypes allows you to add new attributes to a particular filetype, as well as define new filetypes. It's up to the associated applications to do anything meaningful with the new field or fields, but you can pretty much do what you want.
Wow... you mean you can do that from a high-level interface - that must be in the filesystem. BING BONG you're wrong!
The BeOS filesystem has a meta field along with conventional name/date/etc., fields for the FS. I'm not talking about high-level constructs that abstract and hide what's actually taking place - I talking about the FS and how it saves data. It has to parse the meta field. It can't actually add fields to the FS - although it acts that way.
In a similar way to the pony express the Australians have the dingo express.
You carve a message in the baby's stomach and it's off.
-- Eat your greens or I'll hit you!
Re:More like BeOS's filesystem?
on
MySQL FS
·
· Score: 1
No. I believe BeOS just has a meta attribute at the FS level filled with supposed attributes. There's no way to actually define a new field at the FS level (although it is transparent to applications - so aside from speed it doesn't really matter).
Early version of BeOS did use a database FS for the entire system but they dropped it by R4 (I think that's the right version) because of performance issues.
But on topic - they do have a "d/l able" version of their distro that has been reviewed: A badly configured Redhat (alternate language installs still mention Redhat). It's not alleged, it's not vaporware, it's just arse.
04:54 - Accipiter: "Okay."
04:55 - LinuxOne: "Uhhhh, a Mouse pedo...pedio meeta, which measures your desktop mileage, how much heh, you've been moving around."
They're lucky they don't live in Britain. Why angry mobs would be outside stoning the paedo's house.
I have a 16" fan in the side of my case blowing down on the Mobo and it's not loud at all (dust cloth outside it so don't worry kids - Aunt Mable's got it covered).
If you disassemble most fans and spray every surface with some non-friction.. spray (I know the spray brand as CRC, you probably have a different name) it'll be very silent.
The small fans are usually hitting something or have cheap motors.
Getting them to pay your cross-connect is important. I wouldn't want them to be my ISP though: they know of you and should they decide to limit your bandwidth or fake internal errors (I'm not sure what it's like where you are, but here in New Zealand the phone companies lie outright about many things to limit bandwidth and save them money).
Remember to define in the contract who has to maintain the physical cable too. Guaranteed 'not down for more than 48 hours' or you get compensated or a satellite connection, too.
Buster bunny sez: "PHPNuke is wery wery wery sloow. Don't use PHPNuke unless you also use Marajuana; counteracting the wery wery wery slooowness of PHPNuke. The template system is arse too."
Aunt Mable sez: "If you dont' have much processor power go for something in Perl that writes static files when required. Me? I would write my own flat weblog in PHP/MySQL. Linear aside from stories."
She continues: "...the most important bit is your HTML which when generated usually looks like arse. Don't make yours bloated and look like arse. Don't"
Slashdot Mirror
I mean, they are there for a reason.
-- Eat your greens or I'll hit you!
-- Eat your greens or I'll hit you!
Those who talk about browsers being more harsh on bad HTML being a good thing are fools and don't have a clue.
-- Eat your greens or I'll hit you!
-- Eat your greens or I'll hit you!
If you have strong editorship you can have external links without degrading into Yahoo.
-- Eat your greens or I'll hit you!
OK.. but which is it? You first say if you were to measure it to the "micro second, some difference might be noticed". Then three sentences later you say there is "no difference". You seem confused, and you were right the first time.
There is a difference (however minute) and it's due to BeOS not actually having the ability to create fields at the FS level. It's trivial to create file examples that show off the flaws in their method and to make peformance suffer. There are filesystems that do it better, through better architecture. Realise this and you'll see my point - that BeOS can improve it's so-called meta FS.
ps. I've used BeOS for several years now on PPC and x86, programmed for it, and you're probably using some of my apps (here's a hint - Doublin). Oh, and there's much more anger and arrogance without fact or links or proof than anything I'm putting out, believe me.
-- Eat your greens or I'll hit you!
-- Eat your greens or I'll hit you!
Wow.. i'm convinced. Certainly much evidence be had there!
Furthermore, he says you can define your own fields in the FS was from an option in a menu (this far too high-level). The fact remains that the filesystem doesn't have defineable fields, though it pretends to.
What's the difference if it acts like it does and is transparent to the applications? Easy. In simple situations (such as putting an mp3s ID3 in the FS) this has little of a performance hit. But if you were to put 100 meta attributes in the FS and store various sized chunks of data the performance degrades very quickly.
You just cannot read the meta as fast as the other types - oh gee, and I wonder why?
I mean it's an interesting hack but that's all it is. Genuinely adding fields to a filesystem would be impressive and as fast as any other FS request and.. well, it's been done. But not by BeOS.
-- Eat your greens or I'll hit you!
...and you know. I thought the trolls were lying when they reprinted this but now it's happened to me.
Slow down cowboy!
Slashdot requires you to wait 1 minute between each submission of /comments.pl in order to allow everyone to have a fair chance to post.
It's been 1 minute since your last submission!
-- Eat your greens or I'll hit you!
The BeOS filesystem has a meta field along with conventional name/date/etc., fields for the FS. I'm not talking about high-level constructs that abstract and hide what's actually taking place - I talking about the FS and how it saves data. It has to parse the meta field. It can't actually add fields to the FS - although it acts that way.
Congratulations on the +4 though - good work.
-- Eat your greens or I'll hit you!
You carve a message in the baby's stomach and it's off.
-- Eat your greens or I'll hit you!
Early version of BeOS did use a database FS for the entire system but they dropped it by R4 (I think that's the right version) because of performance issues.
-- Eat your greens or I'll hit you!
This story title is just prime beef for Goatsex posters, now isn't it?
-- Eat your greens or I'll hit you!
But on topic - they do have a "d/l able" version of their distro that has been reviewed: A badly configured Redhat (alternate language installs still mention Redhat). It's not alleged, it's not vaporware, it's just arse.
-- Eat your greens or I'll hit you!
04:55 - LinuxOne: "Uhhhh, a Mouse pedo...pedio meeta, which measures your desktop mileage, how much heh, you've been moving around."
They're lucky they don't live in Britain. Why angry mobs would be outside stoning the paedo's house.
-- Eat your greens or I'll hit you!
I mean are you saying "Fuckwad to you all !!! !!" or "Good to you all !!! !!" or "Lemon Lollipops to you all !!! !!" or what?
Eh sonny?
-- Eat your greens or I'll hit you!
-- Eat your greens or I'll hit you!
If you disassemble most fans and spray every surface with some non-friction.. spray (I know the spray brand as CRC, you probably have a different name) it'll be very silent.
The small fans are usually hitting something or have cheap motors.
-- Eat your greens or I'll hit you!
Overclocking and 1GHz and state of the art cooling is about technical superiority. Case design is about art.
-- Eat your greens or I'll hit you!
You can restrict HTML, remember.
-- Eat your greens or I'll hit you!
Type in http://geocities.com/anything and you'll get something similarly offensive.
-- Eat your greens or I'll hit you!
-- Eat your greens or I'll hit you!
Remember to define in the contract who has to maintain the physical cable too. Guaranteed 'not down for more than 48 hours' or you get compensated or a satellite connection, too.
-- Eat your greens or I'll hit you!
Aunt Mable sez: "If you dont' have much processor power go for something in Perl that writes static files when required. Me? I would write my own flat weblog in PHP/MySQL. Linear aside from stories."
She continues: "...the most important bit is your HTML which when generated usually looks like arse. Don't make yours bloated and look like arse. Don't"
-- Eat your greens or I'll hit you!
-- Eat your greens or I'll hit you!