![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Phil Cook v2 escreveu:
> And lo On Wed, 22 Sep 2010 11:01:30 +0100, Invisible <voi### [at] dev null> did
> spake thusly:
>> Oh, right. I couldn't tell; my PC was too busy dying. (Perhaps the VM
>> I was running this under has insufficient RAM?) All I know is that
>> Flash was doing that 10 years ago. I still don't see what all the fuss
>> is about.
>
> Because it's using the HTML5 canvas with Javascript so no need for
> Flash; bye-bye plugins and the "You need to download the latest version
> of Flash"
I'm much more excited about getting rid of small plugin windows getting
keyboard and mouse focus and getting embedding of other web techs like
SVG, xforms directly into the page markup.
--
a game sig: http://tinyurl.com/d3rxz9
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 9/22/2010 2:59 AM, Invisible wrote:
> I especially love the way that MS Word is specifically designed to crash
> most often WHILE SAVING YOUR WORK!
Oh. That's nothing. MS Word will silently corrupt your document while
saving, and keep that corruption intact the whole time, keeping it
hidden until its time to reload the file (e.g. after Word crashed) Then
all hell breaks loose and you wind up losing days worth of work on a
document... Documenting APIs before using doc-comments to create help
files sucked. ;)
--
~Mike
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Mike Raiford escreveu:
> On 9/22/2010 2:59 AM, Invisible wrote:
>
>> I especially love the way that MS Word is specifically designed to crash
>> most often WHILE SAVING YOUR WORK!
>
> Oh. That's nothing. MS Word will silently corrupt your document while
> saving, and keep that corruption intact the whole time, keeping it
> hidden until its time to reload the file (e.g. after Word crashed) Then
> all hell breaks loose and you wind up losing days worth of work on a
> document... Documenting APIs before using doc-comments to create help
> files sucked. ;)
I can see know why's it's so widespread and popular: it can reproduce
its own bugs in a way that it's impossible for OpenOffice opening their
documents...
--
a game sig: http://tinyurl.com/d3rxz9
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
nemesis escreveu:
> Mike Raiford escreveu:
>> On 9/22/2010 2:59 AM, Invisible wrote:
>>
>>> I especially love the way that MS Word is specifically designed to crash
>>> most often WHILE SAVING YOUR WORK!
>>
>> Oh. That's nothing. MS Word will silently corrupt your document while
>> saving, and keep that corruption intact the whole time, keeping it
>> hidden until its time to reload the file (e.g. after Word crashed)
>> Then all hell breaks loose and you wind up losing days worth of work
>> on a document... Documenting APIs before using doc-comments to create
>> help files sucked. ;)
>
> I can see know why's it's so widespread and popular: it can reproduce
> its own bugs in a way that it's impossible for OpenOffice opening their
> documents...
now! what's happening to my english skills??! o_O
--
a game sig: http://tinyurl.com/d3rxz9
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 22/09/2010 07:57 PM, nemesis wrote:
> now! what's happening to my english skills??! o_O
Skills?
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 22/09/2010 07:41 PM, Mike Raiford wrote:
> On 9/22/2010 2:59 AM, Invisible wrote:
>
>> I especially love the way that MS Word is specifically designed to crash
>> most often WHILE SAVING YOUR WORK!
>
> Oh. That's nothing. MS Word will silently corrupt your document while
> saving, and keep that corruption intact the whole time, keeping it
> hidden until its time to reload the file (e.g. after Word crashed) Then
> all hell breaks loose and you wind up losing days worth of work on a
> document... Documenting APIs before using doc-comments to create help
> files sucked. ;)
Interestingly, I've seen a Word document which crashes Word every time
you touch it, yet it opens just fine in OpenOffice. Resave it and it
works perfectly in Word again.
Interesting that a group of hackers who don't even have access to the
spec managed to implement it better than the people who invented it, eh? :-P
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 22-9-2010 22:17, Orchid XP v8 wrote:
> On 22/09/2010 07:41 PM, Mike Raiford wrote:
>> On 9/22/2010 2:59 AM, Invisible wrote:
>>
>>> I especially love the way that MS Word is specifically designed to crash
>>> most often WHILE SAVING YOUR WORK!
>>
>> Oh. That's nothing. MS Word will silently corrupt your document while
>> saving, and keep that corruption intact the whole time, keeping it
>> hidden until its time to reload the file (e.g. after Word crashed) Then
>> all hell breaks loose and you wind up losing days worth of work on a
>> document... Documenting APIs before using doc-comments to create help
>> files sucked. ;)
>
> Interestingly, I've seen a Word document which crashes Word every time
> you touch it, yet it opens just fine in OpenOffice. Resave it and it
> works perfectly in Word again.
>
> Interesting that a group of hackers who don't even have access to the
> spec managed to implement it better than the people who invented it, eh?
> :-P
>
You are assuming that there are no documents that crash in OO while
opening nicely in Word. Unless you can show that such cases do not exist
I will simply assume that both implementations are independent and have
a (hopefully) disjunct set of bugs.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
>> Interesting that a group of hackers who don't even have access to the
>> spec managed to implement it better than the people who invented it, eh?
>> :-P
>>
> You are assuming that there are no documents that crash in OO while
> opening nicely in Word. Unless you can show that such cases do not exist
> I will simply assume that both implementations are independent and have
> a (hopefully) disjunct set of bugs.
Dang. If only OpenOffice had been implemented in a programming language
which facilitates operational proofs...
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
> Right, but... why does it run at a crawl and utterly cripple the
> browser? (In the end, I couldn't actually terminate Chrome; I just
> terminated the entire VM - the equivalent of a hard shutdown.)
>
> I'm all for new technology, but this one doesn't seem to enable you to
> do anything interesting, and requires absurd amounts of computer power
> to do what little it does.
I just saw an advert:
"Make the Internet fast. Download Google Chrome, the fast web browser."
Not on the strength of this thing. :-P
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 9/22/2010 3:39 PM, andrel wrote:
> You are assuming that there are no documents that crash in OO while
> opening nicely in Word. Unless you can show that such cases do not exist
> I will simply assume that both implementations are independent and have
> a (hopefully) disjunct set of bugs.
I've had a .docx file that crashed OO before.
--
~Mike
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |