Same reasons that IE versions only support certain versions of Windows:
- they want to be able to switch to newer APIs when the underlying OS adds them (though in Edge's case it's more likely it was written from the ground up using newer APIs)
- they quite possibly want to use "you can get the new browser only if you upgrade" as a carrot for OS upgrades (they explicitly did with IE, I haven't seen anything explicit for Edge but it wouldn't surprise me if they're still taking that approach)
The lack of subscription and signup, combined with the pricing, suggest that this is aiming at people who almost never send a fax, and would spend significantly more buying and maintaining a fax machine, compared to a couple dollars on this service.
I do hope you find a service that fits your need, but this is very likely not intending to be it.
Right, but is it a viable business if the average customer spends $1-2/year or less?
A business phone line ($100/month or less -- crap tier VOIP lines work fine for faxes) and a PCI fax/modem (<$50) should let you send hundreds of pages an hour with no paper or other consumables. It certainly seems like a send-only service that charges $0.01/page is more than viable. Even averaging only a page a minute would be $15/day in revenue, a huge profit margin.
It is worse, actually, because it uses GTK, and is only available on Linux and Windows (not macOS, although there have been attempts).
Most of the "big names" who provide modern and contemporary desktop IM apps deliver on the 3 platforms (Linux, macOS, and Windows), and use mostly web "technologies" (sometimes "pure browser", and sometimes with electron-like desktop "packaging")... so as a consequence, it is very native, indeed, but it is a generally consistent and continuous UX (user experience) between mobile/tablet and desktop/laptop.
it's US english, they're referring to Lego the product as a whole, rather than individual Lego pieces (the meaning ends up basically the same, but the distinction does change the grammar)
I see. My impression is that in US film and television "legos" is used almost exclusively. But it's not like I've been taking notes or anything, and I could well be wrong.
Exactly so. It's not strictly correct modern English as far as I know, but it's quite a common slip amongst French speakers (from their names I would strongly suspect at least one of the core Pijul folks fits that category) for whom the native word is indeed "edition".
I've never really gotten into absolute line numbers, but relative ones are a godsend for me since I use <num>j, <num>d, et al a lot but can't really eyeball how many lines away something is once it gets to be more than 2 or 3.
The crucial distinction as far as the OP is using the term seems to be that such a datastore does not require the user's hosting provider to give them an instance of any of the common DB servers, which typically needs a more expensive plan than the usual baseline of "disk space and an httpd [that supports calling out to one or two scripting languages]".
(Basically it should run on anything more complex than a static site host. Though it's also true that sqlite would probably be a cleaner choice for the datastore without losing any of that benefit.)
Assuming I'm reading the parent post correctly, neither of those links actually do what they would've been hoping for when moving browsers, even if they certainly get closer than nothing.
Firefox Sync only syncs with versions of Firefox, and Chrome's sync only syncs with versions of Chrome, so they'd have to switch mobile browsers too just because they switched desktop browser (and unlike on desktop, I've found Firefox for Android to generally be clunkier to use than Chrome for Android).
And that second link is about Chromecasting from Firefox for Android, not the desktop browser. Being able to send stuff from desktop Chrome is definitely a convenience someone could get accustomed to.
I own an iPhone and there's NO firefox on iOS. The benefits of having synced history across every browser I use is pretty useful(Ex: that restaurant I looked up online on my laptop this morning is going to show up pretty quickly on my phone because it's in my Chrome history)
Also, Chromecast is just amazing. It works with Netflix, Hulu, YouTube etc. Browse for videos on the website, because it's usually easier to click than to do weird controller motions => chromecast. Back to coding. DONE.
I have no hard numbers or evidence for performance, but that was just my feeling.
Of course you'd have to switch mobile browsers, since mobile browsers don't currently have the option of installing extensions that would allow cross-browser syncing.
That may be a deal-breaker for you at the moment, but I believe that when Firefox's rendering engine switches to Servo, it's going to blow Chrome away on both desktop and mobile.
- they want to be able to switch to newer APIs when the underlying OS adds them (though in Edge's case it's more likely it was written from the ground up using newer APIs)
- they quite possibly want to use "you can get the new browser only if you upgrade" as a carrot for OS upgrades (they explicitly did with IE, I haven't seen anything explicit for Edge but it wouldn't surprise me if they're still taking that approach)