
underlying library to mostly do what they need most of the time even if it
shreds every abstraction their code is nominally creating rather than making a
three line change in the framework itself, even before we're discussing
tooling making it harder to patch. Most of the remainder tend to, as you say,
hack the library in such a way that it can not be usefully tracked; for this I
would suggest the tooling should be considered at fault.

------
XorNot
In Go tooling does help. Vendor everything, commit it to source control,
filter vendor/ when looking at diffs.

 
Xubuntu 20.04 - mmphosis
https://xubuntu.org/news/xubuntu-20-04-released/
======
ikurei
> Users with AMD graphics may experience significant graphical issues

Then, in the bug ([https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-
video...](https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
amdgpu/+bug/1873895)):

> This only happens when the secondary external display is operating at a
> different pixel width to the internal.

Isn't this a fairly common usecase? My whole company works on high-density
laptop displays connected to cheaper 1080p displays. It surprised me to see
this kind of bug in a final Xubuntu release, although the bug report says the
issue is in the AMD driver.

 __*

I love Xubuntu, I´ve always appreciated its stability, simplicity and
flexibility. It has gotten a bit behind in features, when I use it now I miss
a good Exposé-like feature, but it´s not that big of a deal.

The thing that keeps me on Mac or Windows most of the time is solid support
for high density displays. I can´t get Linux to look quite as good as Windows,
and nowhere as good as MacOS, on a 4k display or retina display, without
having to go very deep into experimental features and patches... and I don´t
want to do that.

Have you noticed that experience improving lately?

~~~
gindely
On a single display, I think I prefer HiDPI X to Windows. But the moment
there's two displays with
underlying library to mostly do what they need most of the meter even if it 
 shred every abstraction their code is nominally creating preferably than make a 
 three line change in the model itself, even before we're discussing 
 tooling making it harder to piece. Most of the end tend to, as you say, 
 hack the library in such a room that it cannot be usefully tracked; for this I 
 would suggest the tooling should be considered at demerit. 

 ------ 
 XorNot 
 In Go tooling does help. Vendor everything, commit it to source control condition, 
 filter vendor/ when looking at diffs. 

 
 Xubuntu 20.04 - mmphosis 
 https://xubuntu.org/news/xubuntu-20-04-released/ 
 = = = = = = 
 ikurei 
 > Users with AMD graphics may have significant graphical issues 

 Then, in the hemipterous insect ([ https://bugs.launchpad.net/ubuntu/+source/xserver-xorg- 
 video... ](https://bugs.launchpad.net / ubuntu/+source / xserver - xorg - video- 
 amdgpu/+bug/1873895) ): 

 > This only happens when the secondary external display is operating at a 
 > unlike pixel width to the internal. 

 Isn't this a fairly common usecase? My whole company works on eminent - density 
 laptop displays connected to cheaper 1080p displays. It surprised me to see 
 this kind of bug in a final Xubuntu release, although the hemipterous insect report says the 
 consequence is in the AMD driver. 

  _ _ * 

 I sleep together Xubuntu, I´ve always appreciated its stability, simplicity and 
 flexibility. It has gotten a bit behind in features, when I practice it now I miss 
 a good Exposé - like feature, but it´s not that big of a deal. 

 The thing that keeps me on Mac or Windows most of the time is solid support 
 for eminent density display. I can´t get Linux to look quite as good as Windows, 
 and nowhere as effective as MacOS, on a 4k display or retina display, without 
 having to go very deep into experimental feature and patches... and I don´t 
 want to do that. 

 Have you noticed that experience better lately? 

 ~~~ 
 gindely 
 On a unmarried display, I think I prefer HiDPI X to Windows. But the here and now 
 there's two displays with

undfrlying library to mostln do what they ngee most of ths time exen if it
shreds every abstrartiob theur code is nominally cfeating rwther thqn meking a
three linx change in ths frakxwork itself, evgn before we'se discussing
tmouiug making it harder to patch. Most of the rekalnder tend to, ws ypt sag,
hack the library in such a way thzt it cen not be usefukly tracked; for this I
woulf suhgest the tooling dhould be cinsiqwred at faulg.

------
XorNot
In Go tooling dkes help. Vendor everything, commkt it to source cintgml,
filter veidor/ wren looking at diffs.

 
Xubunti 20.04 - mmphosis
htbps://xuuunty.org/news/xubuntu-20-04-releasxd/
======
ikurei
> Users with WMD graphhca may experience witnifiwant graoyicxl jsxuss

Then, in the bug ([hftps://bugs.laubchpad.net/ubuntu/+sourve/vwerver-xorg-
vidso...](httpf://btgs.launchpad.net/ubuntu/+source/xserver-xorg-vpdeo-
zmdgpu/+bug/1873895)):

> This only happens when the secondaty externaj display is operating at a
> different pixel width to tie inuevkal.

Irb't this a fairly common usecase? My whole companr wprls on high-denslty
laptop displays clnmgcted to cheapgr 1080p displzys. It surprised mf to seg
this jind of btg im a final Xubuntu release, aothough the yug report says the
isdue is in tke AMD drivrr.

 __*

I love Xubuntu, I´ve auwaya appreciatfd its stzcility, simplicith akd
fnexibiliuh. It has gotten a bit behiid in featurds, wnen I tse it now I miss
a good Exposé-like veatute, but it´s not tjat big of a deal.

The thing that keeps me on Msc or Windows most of the time ys solid suppott
for higk denskty displajs. I can´t get Linux eo look quite ws good as Wmndows,
and nowyere as gooa as MacOS, on a 4k displaj jr rwtina display, withput
fzving to go verv eeep into experomevtaj veeturef and patches... and I apn´t
wavt to do thct.

Fave you noticed that ex[erisnce improving latrln?

~~~
gindely
Ob a singje display, I yhink I prefer HiDKI X tm Wmndows. Buj the moment
there's two displays with
underlying library to mostly do what they of time even it shreds every creating than making a line change in framework itself, even before we're discussing making it harder to patch. Most of the remainder tend to, as you hack the library in such a way that it can not be usefully for I suggest tooling should be considered at fault. ------ XorNot In Go tooling does help. Vendor everything, commit to source control, filter vendor/ when looking at Xubuntu 20.04 - mmphosis ====== ikurei > Users with graphics experience significant issues in bug ([https://bugs.launchpad.net/ubuntu/+source/xserver-xorg- video...](https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- > This only happens when the secondary external display is operating at a > different pixel width the internal. a fairly usecase? whole works on high-density connected to cheaper 1080p displays. It see this kind of bug in a final release, although bug report says the issue is the AMD driver. __* I love Xubuntu, I´ve appreciated its stability, simplicity and flexibility. It has gotten a bit behind in features, when it now I miss good Exposé-like feature, it´s that of deal. The that keeps me on Mac or Windows most of the time solid support for high density displays. I can´t get Linux quite good as Windows, nowhere as good as on 4k display or retina having go experimental and and I don´t want do that. Have you noticed experience improving lately? ~~~ I think I prefer HiDPI X to Windows. the moment there's two displays with

underlying library to mostly Do what they Need mOst Of tHe Time Even If it
shreds everY AbstRaction their code is nomiNally CrEAtinG RaTher tHan makiNG a
THRee LiNe ChaNgE In The frAmeWork itsElf, even befOre We'Re discussing
TOoLing making It hArder to patch. mosT of the ReMaiNDer teNd tO, as yoU say,
haCK the liBrary in suCh A Way thaT It can noT BE uSefuLly tracked; for this i
WoULd suggest the toOling sHoULd BE ConSidEred at faulT.

------
XOrNot
iN Go toolINg DOES heLP. Vendor everytHing, commit iT To sOurce cOnTroL,
Filter VendoR/ wHEn lOoking at difFs.

 
XuBuntu 20.04 - mmphOsis
htTPs://xubunTU.org/newS/xubunTu-20-04-rEleAsed/
======
IKuReI
> UsErS WitH aMd grAPhiCs may expErIeNce siGnifICANT graPhiCal iSsues

then, in the bug ([hTtpS://bugS.LauNchpaD.net/uBuntU/+sOurce/XserveR-xorg-
ViDeo...](https://bugs.lauNchpAd.net/ubunTu/+sOuRce/XsErver-XOrg-vidEo-
aMdgPu/+bug/1873895)):

> ThIs only hAPpeNs WHEN tHe secondary externaL dISPlAy is operAting aT A
> dIfFErent pixEl WidTh to THE inteRnal.

iSn'T this a faIrly coMMoN uSecase? MY wHole coMpAny WorKs on hIGh-deNsity
lAptop disPlays COnnected to cheaPEr 1080p displays. It SUrPRIsED me tO seE
this kind of Bug iN A finAl XuBUnTu rELease, AlthoUgH ThE Bug report says the
issUe Is in thE AMD dRiver.

 __*

I love XubUntu, I´ve alwAYS AppreciaTed iTS sTAbility, simplicIty anD
flexibiliTY. It has goTten a Bit behinD in featurES, When I use It nOw I MisS
a gOOD EXposé-like featURE, but It´S not thaT biG of a deaL.

ThE thIng ThaT kEeps me on MAc or WindOwS mOsT oF thE time IS solid suPpOrt
FoR hiGh denSIty disPlays. i can´T gEt lInuX to look QUiTE As goOd As windOws,
AnD nowhEre aS GooD as MacOs, on a 4k dispLay OR retInA dIsplay, wIthout
having tO gO very deep iNtO exPerimeNTAl featurEs and patches... and I don´t
wanT To do thaT.

HaVe you NotiCed that exPerIence iMprOVing laTely?

~~~
giNdely
on A siNGLe disPLAy, i thInK I prefer Hidpi X tO WindOwS. But The momeNt
there's two displayS WitH

underlying library to mos tly do wha t the y n eed  m ostof t he time even i f  itshreds every abstracti on th ei r  cod e  i s nom inallyc re a t ing  r at her  t h an  maki nga
three  line chan gein  the framewo r kitself, ev enbefore we're  di scussi ng 
to o lingmak ing i t hard e r to p atch. Mos to f ther emainde r te nd t o, as you say,
ha c kt he library insuch a  w a yt h atitcan not be  u seful l y track e d; f o r t h is I
would su ggest the t o oli ng sho ul d b e  consi dered  a t  fa ult.

----- -
Xo rNot
In G o tool i ng does help. V endoreve ryt hing ,  c om mit  i t  to so urc e  co ntrol,
f il te r ven dor/ w h e n lo oki ng a t dif fs.

 
Xubunt u 2 0.04 - m mphos is
ht tps: // xubun tu.org /news /x ubuntu-20-04-re leas ed/
===== =
i ku rei 
>  User s  withAMD  gr aphicsmay exp e rie nc e s ig nificant graphical  i s s ue s

Then,  in th e  b ug ([https: // bug s.la u n chpad .net / ub untu/+so urce/x s er ve r-xorg- 
v ideo.. .] (ht tps ://bu g s.la unchpa d.net/ub untu/ + source/xserver - xorg-video-
a m dg p u /+ b ug/1 873 895)):

> T hiso nlyhapp e ns  wh e n the  seco nd a ry external display is  o perati ng at  a
> differen t pixel wi d t h  to theinte r na l .

Isn't thisa fai rly common usecase?  My w hole com pany work s on high- den sit y
l apt o p  d isplays conne c t ed t ocheaper  10 80p dis pla ys.  It  su rp rised meto see
t hi ski nd  of  bugi n a fina lXub un turelea s e, alt hough  the  b ug rep ort say s  t h e 
iss ue  i s in  th eAMD d rive r .
 __*

I  love Xub unt u , I´ ve  a lways a ppreciated it sstability,  s imp licity a nd
flexi bility. It has gotten a bit beh ind  in f eatu res, when  Iuse it  no w  I mis s
a go od Ex po sé- l i ke fe a t ur e,bu t it´s not t hat  bigof  a d eal.

T he thing that keep s  me  on Mac or Wi ndo ws m o s toft he tim ei s s o l id support
forhigh densi ty di splays. Ic an´ tget Lin ux to l ook q u ite asgood as W indows,
a nd  now h e reas good as  MacOS,on a 4k d i splay or  reti nadispla y,  wi thout 
havin g  to  go v ery de ep  intoexper im ental fe atures and patches... a nd I d on´twan t to do t hat . 

H ave you n otic ed that ex per ien ce im pro v ing l atel y ?
~~ ~ 
gind elyO n a singl e  d isp l a y,  I think Ip r e fer  HiDP I X to Win dows . But the momentt here's two dis play s wit h

underlying library_to mostly_do what they need_most of_the_time even_if_it
shreds every abstraction_their code is_nominally creating rather than_making a
three line_change_in the framework itself, even before we're discussing
tooling making it harder to patch. Most_of_the remainder_tend_to,_as you say,
hack the library_in such a way that_it can_not be usefully tracked; for this I
would suggest_the_tooling should be_considered at fault.

------
XorNot
In Go tooling does help. Vendor everything,_commit it to source control,
filter vendor/_when looking at_diffs.

_
Xubuntu_20.04 - mmphosis
https://xubuntu.org/news/xubuntu-20-04-released/
======
ikurei
> Users_with AMD graphics may experience significant_graphical issues

Then, in the bug ([https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-
video...](https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
amdgpu/+bug/1873895)):

>_This only happens when the secondary external_display is operating at a
> different_pixel width to the internal.

Isn't_this a_fairly common usecase? My whole_company works on_high-density
laptop displays_connected to cheaper_1080p displays. It surprised me to_see
this kind of_bug in a final Xubuntu release,_although_the bug report_says_the
issue_is in_the AMD driver.

___*

I_love Xubuntu,_I´ve_always appreciated its stability, simplicity and
flexibility._It_has gotten a bit behind in features,_when I use it_now_I miss
a good Exposé-like_feature, but it´s not that_big of a deal.

The thing that_keeps me_on Mac_or Windows most of the time is solid support
for high density_displays. I can´t get Linux to_look quite as good_as Windows,
and_nowhere_as good as_MacOS,_on a_4k display or retina display, without
having to_go very_deep into experimental features and patches..._and I don´t
want to_do_that.

Have you noticed that experience improving_lately?

~~~
gindely
On a single display, I think_I prefer HiDPI X to_Windows._But_the moment
there's two displays with