Hacker Newsnew | past | comments | ask | show | jobs | submit | throwaway11205's commentslogin

Fractional scaling works perfectly well on Xorg Linux and Windows, but looks blurry on Wayland Linux. Maybe it's not micrometer-scale crisp, but I can't see that. Text on Wayland is very visibly blurred.

And it's not just text, but UI controls too. It looks like Wayland just renders the lower integer scale factor and then stretches the resulting bitmap image. That's bullshit.


I have the exact opposite experience: fonts are crisp on Wayland and blurry crap on xorg.


Doesn't macOS do it the other way, rendering at the next highest integer scale factor and then downscaling to fit the display?

If you can't render fractional factors natively for tech debt reasons then that's the least bad way to do it.


MacOS way is better, text is blurry, but much less. I still don't like it though, but can use it in an emergency.

But there apparently is another way that Xorg and Windows uses. I have perfectly crisp (as far as my eyes can tell) UI and text on both systems at 150% scale (27" 4K display).

> for tech debt reasons

I thought Wayland was supposed to fix the tech debt - so now it introduced some that makes bare basic features impossible?


It does for any app that can't scale; all modern OSX apps can scale natively. I've been using that trick for integer-like scaling for years to deal with fractional scaling while preserving the quasi-aliasing ("crispness") of the source image.

However, Wayland does not prescribe any method for non-integer scaling. Any Wayland WM could choose to do the same thing, and it would be hardware accelerated essentially for free.

Both X11 and Wayland WMs typically don't use this trick, and neither does Windows.


It is exactly (some) Xorg apps that render blurry on Wayland. You are blaming the wrong party for “bullshit”. Xorg scaling sucks, whereas Wayland’s is great.


The Java EE-like OOP mess of later years is no better.


It was sort of necessary for PHP renaissance, to clean up the act, but it's also "not PHP" as-in why bother using PHP if you're going to do it that way, I feel like. The whole joy of PHP is the magic of it just works coupled with a super short path from prototype to prod, but before the component-model that's now the norm and the language clean up it meant a lot of crap foundations. Wordpress is still here to attest to that.

That's why Symfony rose above, and why Laravel is taking over. Laravel is essentially "let's do a code igniter 2 but on top of symfony clean design this time".


In all EU countries an invoice (tax receipt) is a legal document very exactly specified by local law as well as EU regulation, and you can't move a cent without it - you won't be able to claim the expense (subtract from tax base = pay income tax on profit only) if you don't have it.


I'm an American working for an Italian company as a freelancer, and I just print a generic invoice from Harvest (time tracker). I've also seen us pay other freelancers who make simple PDF invoices from web templates.

Have we been doing it completely wrong this whole time...?


No, you haven't done anything wrong. Some people are just paranoid-compliant to the maximum level. Unless a company is doing actual money laundering or financing terrorists, the tax auditors won't give a damn about some wrongly formatted invoices from freelancers, as long as they are based on reality.


Ok, phew, thanks for the reality check! We don't finance any terrorism (unless you count the quality of my code). We're just a small company without a big legal/accounting dept.


PDF invoices are nothing wrong. As long as you're not a VAT payer there are just basic requirements (vendor/customer ID and address, invoice number). Most likely yours is compliant - but you need to provide it.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: