hub_

OS/2 comes to mind. Version 1.x was already much more sophisticated than MS-DOS.

TBH I never had that problem on the 9360 (in over 2 years) - YMMV. Knock on wood though as I had to replace the battery and the AC adapter died.

Yep, you need a new battery. Getting one from Dell is harder than actually replacing it.

USB-C as a power connector work great when the proprietary power supply die as you are waiting to get a replacement battery. (true story) (I have a 9360 model, which doesn't like the batteries for the 9350)

Why would that be on the list? Isn't there already a solution? It doesn't need to be GPL licensed for getting FSF recognition - a non copyleft but Libre license is fine.

Does that include open source code for ALL the hardware?

For starter you could restrict the autoplay the next video only if it is the same element.

But then Chrome and Youtube come from the same company. Maybe they should coordinate.

There is a disable autoplay in Firefox as a hidden pref. Enabling it break YouTube (offender number 1) and Vimeo.

Vimeo's take is that it is a bug in the browser hence it should be fixed. But then Vimeo are the same that told use to use Safari on Linux because Firefox "didn't support HTML5" (it did, just not encumbered H264 codec, but when you are lying, do the extra mile).

This is why Firefox download the CISCO binaries at startup... Can't have nice things.

My approach is not to throw away. The changes are incremental and definitely the spirit of the original code is here.

Nope.

ClarisWord never existed — ClarisWorks was the product. Claris had MacWrite II for a time because they were the software spin-off from Apple, and that was their stand alone word processor offering, not much better than Claris Works, which was one application unlike MS-Office.

128KB binary. All written in assembly.

I was in that group. There is so much that can be done just like that.

And Abi as a company was long gone by that time.

I think the OP meant "on Windows".

You know it is hard to order people to do something when they aren't paid. Even project like OpenOffice.org that had commercial venture had hardship with funding. Oracle cancelled it, Novell cancelled it, IBM do whatever they want, etc.

All in all, GNOME Office didn't happen. Some bits did, though. AbiWord was always broader than GNOME. And Gnumeric is great IMHO.

And people see the future in the cloud.

There is definitely lots of improvement to do in that area for AbiWord.

There is a long list of bugs from every side.

Porting to iOS would be easier than to Android. Because on iOS we can simply write the UI code in Objective-C++.

On Android, it involve doing JNI + Java and cross compiling the AbiWord engine. Something like what Firefox for Android is doing.

But neither is in the pipe.

I'm not sure this will go the way one would want. There is nobody to do Windows and the Mac port has also fallen behind. I'd rather continue the bootstrapped Qt port in parallel to Gtk and use that.

nope. Never had eye surgery and I have normal vision without glasses.

It was just a nod a reading stuff with a second set of eyes (ie code I didn't write).

It can read .doc. Never write. When it writes .doc it is actually writing RTF. A kludge, but this is better than always explaining users that saving as .rtf will be fine. And Word did that for a while part of a feature that was removed in an update. The only things were this didn't work is for some proprietary CMS that supported .doc but not .rtf.

I'm personally not super happy about that, but it is still much better than not doing it.

It is not "refused". It is just not a trivial undertaking and with even more limited resources now, it is even less easy.

Just switching to ODF as a default format wouldn't have been a good idea, the difference in data models would have caused problems. I have in mind that to do that we'd have to change the internal model for things like list and tables to not have to convert them back and forth each time with losses.

This is a sad fact of the reality.

BTW one of the glorious hackers from the "LibreOffice side" has implemented a LibroOffice filter to read AbiWord documents.

definitely not.

btw, creating the string with capacity was in my mind at one point. Some contributor submitted a PR already

https://github.com/hfiguiere/leftpad-rs/pull/2

Sadly it has gathered some rust (pun intended !)

I wrote this as a practical joke, following a friend of mine who did that for Go.

(and no I didn't post that to HN either)

there is a big irony in that comment... (very personal to me - that no one can get here)

a PR is more practical if you want me to merge. Thanks !

They are actually working on that. With DRM, DMCA, shitty software, etc. They want you to go back to the vendor to make sure things are fixed. Repairable? Only by authorized service dealers. At a monopolistic cost.

And in the US you can thank the EPA for helping with that.

Or Google Docs...

But they do have exclusive control of the distribution channels of apps for iOS. That's a monopoly.

And they are rightly so to tell people to upgrade to the latest Firefox.