Earlier quoted context omitted.
This is how the article looks like on 1280x800: https://i.imgur.com/L07L4ce.png Sticky header/footer, cookie consent covering the menu, not a single line of the content visible. You consider this design good? I might be wrong with this specific site on the JS - it only loaded 121KB Javascript. The actual HTML of the entry is 30. WordPress nowadays upgrades itself to minor version - security patches - without touching…
1280x800 means you can have ad blocker at least (or tampermonkey). Block bottom bar and make header scrollable for this site once. Phones lack this, sadly.
Our experience launching a paid, proprietary product on Linux
111–120 of 395 posts
Re: Our experience launching a paid, proprietary product on Linux
#112Earlier quoted context omitted.
This is how the article looks like on 1280x800: https://i.imgur.com/L07L4ce.png Sticky header/footer, cookie consent covering the menu, not a single line of the content visible. You consider this design good? I might be wrong with this specific site on the JS - it only loaded 121KB Javascript. The actual HTML of the entry is 30. WordPress nowadays upgrades itself to minor version - security patches - without touching…
Having the blog post outside Medium doesn't guarantee them all looking better. On the other side, it is easier to fix one site using custom CSS than it is to fix a bunch. An on the other other side Firefox's reading mode makes this whole discussion irrelevant.
It really doesn't. It doesn't fix it for non-firefox and non-power users.
Re: Our experience launching a paid, proprietary product on Linux
#113The big thing I see missing from all this analysis is the home vs. work distinction. You have people saying "Linux users choose FLOSS because of philosophy, and proprietary software goes against this", you have users saying "I'd have tried it if it were FLOSS and I could just download it and try it", etc., but the problem is: this is a product for working with an Exchange server. How many individual users have a need…
Re: Our experience launching a paid, proprietary product on Linux
#114Re: Our experience launching a paid, proprietary product on Linux
#115The big thing I see missing from all this analysis is the home vs. work distinction. You have people saying "Linux users choose FLOSS because of philosophy, and proprietary software goes against this", you have users saying "I'd have tried it if it were FLOSS and I could just download it and try it", etc., but the problem is: this is a product for working with an Exchange server. How many individual users have a need…
A part for that I pay for: - Skype credit - gitkraken (thanks electron!)
And i would pay and pay and pay for a design software like sketch.. I have a lot of hope on figma.. Let see..
Re: Our experience launching a paid, proprietary product on Linux
#116Earlier quoted context omitted.
This is how the article looks like on 1280x800: https://i.imgur.com/L07L4ce.png Sticky header/footer, cookie consent covering the menu, not a single line of the content visible. You consider this design good? I might be wrong with this specific site on the JS - it only loaded 121KB Javascript. The actual HTML of the entry is 30. WordPress nowadays upgrades itself to minor version - security patches - without touching…
1280x800 means you can have ad blocker at least (or tampermonkey). Block bottom bar and make header scrollable for this site once. Phones lack this, sadly.
Re: Our experience launching a paid, proprietary product on Linux
#117Completely unrelated to the contents: Please, publishers, I beg you: walk away from medium. It's terrible for us, your readers. Set up a static blog, with a domain, go WordPress, Grav, Typo3, anything, but without stupidly large sticky header/footer and without heavy javascript . EDIT: apparently 121KB javascript is not heavy. I still believe it's an overkill for 30KB content.
What I can't believe is how poor the experience is reading comments.
Re: Our experience launching a paid, proprietary product on Linux
#118The big thing I see missing from all this analysis is the home vs. work distinction. You have people saying "Linux users choose FLOSS because of philosophy, and proprietary software goes against this", you have users saying "I'd have tried it if it were FLOSS and I could just download it and try it", etc., but the problem is: this is a product for working with an Exchange server. How many individual users have a need…
I do. I work with Linux and on my company we use exchange.. A part for that I pay for: - Skype credit - gitkraken (thanks electron!) And i would pay and pay and pay for a design software like sketch.. I have a lot of hope on figma.. Let see..
Re: Our experience launching a paid, proprietary product on Linux
#119> Turns out there aren’t a lot of email clients for Linux users that work with Exchange / Office 365 Has Linux on the desktop really fallen so far in the last years? When did the decay really set in? How does open source friendly Microsoft not see Linux email clients support falling behind at least as a problem in MS documenting its APIs, if not an opportunity to participate in the major open source clients and influ…
Office 365 comes with a very good web verison of Outlook, which supports more modern features than most email clients do (such as Office 365 Groups). I suspect it doesn't bother them hugely that desktop client support is falling behind on any platform. edited to add: Oddly I can't find much marketing by Microsoft of the browser Outlook, otherwise I'd link it here, but I'd say it's about 85-90% feature complete compar…
Re: Our experience launching a paid, proprietary product on Linux
#120Earlier quoted context omitted.
Having the blog post outside Medium doesn't guarantee them all looking better. On the other side, it is easier to fix one site using custom CSS than it is to fix a bunch. An on the other other side Firefox's reading mode makes this whole discussion irrelevant.
> An on the other other side Firefox's reading mode makes this whole discussion irrelevant. It really doesn't. It doesn't fix it for non-firefox and non-power users.
The "Shitty design is fine because I personally know a way to get around it" school of thought never made sense to me.