News for hackers. Stuff that matters.
Re:Closing a 30 pixel gap between native and web by pjmlp on Wednesday September 28, 2022 @04:47AM (#33005776)
Office is using web technologies because they don't want to rewrite their code for Office 365, so native users get the Web stuff on a Web widget instead of a proper native UI.

Which is kind of tragic, given how Office was the testing ground for many Windows UI components.

Re:Closing a 30 pixel gap between native and web by desindol on Wednesday September 28, 2022 @05:07AM (#33005939)
What are you even talking about the only non native app in the office package is teams…
Re:Closing a 30 pixel gap between native and web by pjmlp on Wednesday September 28, 2022 @05:07AM (#33005944)
Re:Closing a 30 pixel gap between native and web by desindol on Wednesday September 28, 2022 @05:31AM (#33006094)
????? Nobody is saying that there aren’t webviews in office I am saying that your statement that most of the desktop office ui is now non native is false and misleading. After reading your other comments in the thread it seems like more of a personal vendetta than factual statements. lmao
Re:Closing a 30 pixel gap between native and web by pjmlp on Wednesday September 28, 2022 @07:14AM (#33006646)
Nope, you're the one interpreting that way, I only mentioned that they are adopting Web stuff as means to reduce code duplication between Web and desktop, via Webviews exactly.

So unless you're on the Office team and want to tell us anything, please do lmao.

[dead]
Re:Closing a 30 pixel gap between native and web by pjmlp on Wednesday September 28, 2022 @07:35AM (#33006763)
My dear I am quite free, unfortunely many people on this planet cannot enjoy the same freedom.
[dead]
Re:Closing a 30 pixel gap between native and web by pjmlp on Wednesday September 28, 2022 @08:55AM (#33007312)
Where I come from we don't give tips at the coffee table, the servants earn a proper salary.
Re:Closing a 30 pixel gap between native and web by desindol on Wednesday September 28, 2022 @09:06AM (#33007427)
Haha you really are a fucking retard. Just remember overconfidence is a slow and insidious killer.
Re:Closing a 30 pixel gap between native and web by pjmlp on Wednesday September 28, 2022 @09:10AM (#33007466)
I am quite aware of the fragility of human life.
Re:Closing a 30 pixel gap between native and web by desindol on Wednesday September 28, 2022 @09:24AM (#33007597)
Dude you really are the prototype of a German honk. Love it.
Re:Closing a 30 pixel gap between native and web by dang on Wednesday September 28, 2022 @06:17PM (#33013966)
Personal attacks will get you banned here and ethnic/national/racial attacks will also get you banned here, therefore please don't post like this to HN.

https://news.ycombinator.com/newsguidelines.html

Edit: actually, since you've been repeatedly breaking the site guidelines quite badly (e.g. https://news.ycombinator.com/item?id=33007427, https://news.ycombinator.com/item?id=33006693) I've banned this account. Please don't create accounts to break HN's rules with.

Re:Closing a 30 pixel gap between native and web by dncornholio on Wednesday September 28, 2022 @05:29AM (#33006080)
Who cares if it just works? Who cars if it's made in Flash or in COBOL when it just works? What's sad about this? It just works right?
Re:Closing a 30 pixel gap between native and web by hulitu on Friday September 30, 2022 @05:13AM (#33032697)
That's the problem: it does not work. I don't care if the programm is written in assembly or in rust as long as it functions properly. But when the blinking cursor stops blinking, when the scrollbar or window border is so thin that i cannot select it with a mouse, when the title bar is so cluttered with buttons that any click brings up a menu instead of being able to double click or click and hold, then _it matters_.

I stop here in order to not throw profanity at MS engineers.