News for hackers. Stuff that matters.
Re:Why modern software is slow by jiggawatts on Thursday September 29, 2022 @09:10PM (#33029580)
Oh, this is nothing.

Windows force-updated my Notepad.exe to the new modern UI version.

It is very visibly laggy for basic actions such as opening menus or scrolling through text.

You have to be spectacularly bad at programming to make something so basic so slow in 2022 on a very high-end gaming computer.

Not just bad, but utterly oblivious. Casey Muratori excoriated the Windows Terminal dev team for failing to achieve a consistent 60 fps when displaying fixed-width text, which is such a trivial exercise that Casey whipped up a demo in like two weekends. [1]

Now the Notepad team insisted on following in the Windows Terminal team's footprints and slowing down the other fixed-width text app that needs to be lightweight fast for all sorts of reasons. Nobody needs Notepad to be pretty. Everyone needs it to work.[2]

Just amazing to see something like this happen. It's like a slow motion train wreck, ruining one Windows app at a time.

[1] These videos are especially "shocking" because the code he wrote is terse, straightforward, lightning fast, and more correct than whatever madness Microsoft was doing.

First weekend: https://www.youtube.com/watch?v=hxM8QmyZXtg

Second weekend: https://www.youtube.com/watch?v=99dKzubvpKE

[2] For example, opening a 300 MB log file takes a solid minute of time, which is absurdly slow. It also bloats this to 800 MB of memory usage. For comparison, TextPad opens it in 5 seconds and uses 30 MB of memory. VS Code, an electron application(!) opens in under 2 seconds.

Re:Why modern software is slow by musicale on Thursday September 29, 2022 @09:36PM (#33029800)
> You have to be spectacularly bad at programming to make something so basic so slow in 2022 on a very high-end gaming computer.

I don't understand why desktop app user interfaces aren't blazingly fast and 240fps.

That being said, I think current iOS and macOS can run their UIs at 120fps (and Apple devices still seem to have decent battery life.)

Re:Why modern software is slow by WalterBright on Friday September 30, 2022 @12:00AM (#33030757)
> I don't understand why desktop app user interfaces aren't blazingly fast and 240fps.

Telemetry back to HQ takes resources.

I began to notice my disk drive light flickering regularly even when I was doing nothing with the computer, and the computer started seeming sluggish. I'd look at the process list, and started randomly forcing them to quit. Suddenly, the drive light stopped flashing. I'd found my man.

Googling the name of the process, it belonged to a program I'd bought that served media files to my Roku box. But I wasn't asking it to stream anything at the time.

I didn't know what the hell it was doing, but couldn't justify it, and removed the program.

Re:Why modern software is slow by lelanthran on Friday September 30, 2022 @12:58AM (#33031163)
> Googling the name of the process, it belonged to a program I'd bought that served media files to my Roku box. But I wasn't asking it to stream anything at the time.

Maybe it was indexing.

Re:Why modern software is slow by WalterBright on Friday September 30, 2022 @02:52AM (#33031792)
It doesn't take days to index my hard disk. Besides, I configured it with the path the media files. There's no reason to spy on the rest of the drive.
Re:Why modern software is slow by _Algernon_ on Friday September 30, 2022 @02:59AM (#33031846)
Why would it be indexing if no files are changed?
Re:Why modern software is slow by duped on Thursday September 29, 2022 @09:57PM (#33029952)
GPU accelerated vector graphics rendering is an open problem.
Re:Why modern software is slow by raphlinus on Thursday September 29, 2022 @10:10PM (#33030052)
For now.

Unfortunately, even if you have very fast drawing, there are plenty of other ways to make software slow. But high performance GUI software is the main thing I'm working on at the moment and I expect to have interesting results in the coming months. If nothing else, it should be a data point of how fast GUI software can be.

Re:Why modern software is slow by danielvaughn on Thursday September 29, 2022 @10:18PM (#33030103)
I’m super excited to hear about this. I’ve been working on a programming language for UI designers, and I ran into some massive issues when I tried to build my own renderer. Gave up and now I’m just transpiling to other languages instead.
Re:Why modern software is slow by jahewson on Friday September 30, 2022 @12:28AM (#33030942)
Eagerly awaiting this!
Re:Why modern software is slow by jcelerier on Thursday September 29, 2022 @11:44PM (#33030658)
Maybe basic productivity applications shouldn't try to tackle open research problems and instead just do the thing which has worked fine for the last 30 years which is CPU rendering? Like, do you think notepad is going to burn your battery because it redraws 20x20 pixels on every mouse event ?
Re:Why modern software is slow by jiggawatts on Thursday September 29, 2022 @10:38PM (#33030218)
It isn’t an open problem for text editors or terminals, which is the point Casey made in his videos.
Re:Why modern software is slow by naikrovek on Thursday September 29, 2022 @10:45PM (#33030276)
text editors and terminals don’t render vector graphics though, do they? they rely on libraries to rasterize glyphs of a font into a bitmap once and use the bitmaps over and over.
Re:Why modern software is slow by _gabe_ on Thursday September 29, 2022 @10:56PM (#33030346)
> they rely on libraries to rasterize glyphs of a font into a bitmap once

Unfortunately it's not this simple. Unicode and multilingual support means you can't possibly generate a single bitmap to contain all possible characters. Modern UIs (including text editors and terminals) generally support various zoom levels, which requires re-rasterizing glyphs at different zoom levels. This means you typically have to rasterize vector graphics (your font) on the fly as needed and then update your bitmap.

Edit: Also, emojis and certain scripts require composting multiple glyphs together. This means you have to figure out which glyphs are required for your codepoint and use your font metrics to composite the glyphs appropriately. Then throw in mathematical notation and all bets are off.

My point is, rendering text is not a simple done deal, but it's also not an impossible feat and it can be done efficiently.

Re:Why modern software is slow by naikrovek on Thursday September 29, 2022 @11:11PM (#33030438)
that is a very pedantic argument. you completely overlooked the point i was trying to make.

vector graphics are not rendered directly to the screen. fonts are rasterized first, then the rasterization is what the GPU receives.

Re:Why modern software is slow by rileyphone on Friday September 30, 2022 @12:52AM (#33031126)
> that is a very pedantic argument. you completely overlooked the point i was trying to make.

lmao welcome to HN, if you don't enjoy that experience I don't recommend you try to argue here.

Re:Why modern software is slow by _gabe_ on Thursday September 29, 2022 @11:45PM (#33030661)
> vector graphics are not rendered directly to the screen.

What difference does it make if you're caching the rasterization or not? You're still rendering vector graphics. And you're not just rasterizing once.

Modern font renderers can't get away with rasterizing glyphs once and reusing them anymore than arbitrary vector graphics renderers can. I sure hope my vector graphics editors cache the rasterizations instead of re-rasterizing needlessly.

Re:Why modern software is slow by naikrovek on Friday September 30, 2022 @12:23AM (#33030908)
once, twice, two hundred times, whatever.

it's not every frame. that's my point. that you missed twice because you can't see past details to the point of the statement.

Re:Why modern software is slow by audidude on Thursday September 29, 2022 @11:18PM (#33030489)
a huge amount of emoji are embedded png in font files. newer ones, however, do require more work.

> figure out which glyphs are required for your codepoint and use your font metrics to composite the glyphs appropriately.

this is all done in shaping though, the renderers just see "put this thing there" and (at least in GTK) we just maintain texture atlases that are updated on the fly.

you're correct that it doesn't solve the same glyph at lots of scales though. but glyphy does (and at high FPS too).

Re:Why modern software is slow by kilburn on Friday September 30, 2022 @01:27AM (#33031324)
GTK's implementation of text rendering is is admittedly broken in several subtle ways that nobody seems to know how to properly fix. [1] Also, this is while _not_ supporting fractional scaling, which is something that users definitely want.

To be clear, I'm not bashing on GTK. I'm saying that it definitely isn't as simple as the above comment implies ;)

[1] https://gitlab.gnome.org/GNOME/gtk/-/issues/3787

Re:Why modern software is slow by audidude on Monday October 03, 2022 @11:30AM (#33068905)
That issue is literally why I have a branch integrating GLyphy. But yes, your casual drive by comment is definitely more knowledgeable than the people who work on the stuff.
Re:Why modern software is slow by audidude on Thursday September 29, 2022 @11:14PM (#33030461)
harfbuzz creator made https://github.com/behdad/glyphy/ which i integrated into GTK a while back (but we don't ship currently, because we still do the bitmap stuff).

the bitmap stuff still has major drawbacks though, like maintaining grid alignments and pixel boundaries where as this stuff (mostly) goes away using glyphy.

still work to be done around hinting though (hence not merged).

Re:Why modern software is slow by userbinator on Thursday September 29, 2022 @11:25PM (#33030525)
You shouldn't even need a GPU for basic UI like this, especially with "modern" ultra-minimalist flat UIs.
Re:Why modern software is slow by vladvasiliu on Friday September 30, 2022 @12:39AM (#33031024)
Yeah, but they're not actually completely flat since they're translucent.

Also, on Windows, the "acrylic" thing is a circus show. Every app behaves differently. It also manages to sometimes lag on an RX5600. I know it's an "old" gpu, but still...

Re:Why modern software is slow by rayiner on Thursday September 29, 2022 @11:01PM (#33030377)
But you don’t have to do it every frame. Most apps could just render to bitmaps once and cache the results.
Re:Why modern software is slow by moonchild on Friday September 30, 2022 @12:44AM (#33031051)
It is being worked on (ahem...)

But in most contexts, it is not necessary to render vector graphics 'live'; caching is acceptable, so this should not be a bottleneck for most desktop software.

Re:Why modern software is slow by naikrovek on Thursday September 29, 2022 @10:08PM (#33030026)
is it? MacOS has rendered the entire UI via PDF since OSX was first released.
Re:Why modern software is slow by astrange on Thursday September 29, 2022 @10:47PM (#33030293)
It's not really PDF, it just supports similar operations to PDF. There's more SVG UI elements now.
Re:Why modern software is slow by naikrovek on Thursday September 29, 2022 @11:21PM (#33030498)
but it’s vector graphics, right?
Re:Why modern software is slow by astrange on Friday September 30, 2022 @12:37PM (#33037089)
Only very recently. Like, all that old Aqua stuff wasn't vectors, it was done in Photoshop.

Bitmaps are much faster to draw and can be made pixel-precise up front. With vectors it's easy to have pixel cracks or blurry lines because it's offset .5px.

Re:Why modern software is slow by naikrovek on Friday September 30, 2022 @05:20PM (#33040946)
> Bitmaps are much faster to draw and can be made pixel-precise up front.

yes, but that alone doesn't require that bitmap graphics be used.

> With vectors it's easy to have pixel cracks or blurry lines because it's offset .5px.

only if your renderer or your artwork isn't done correctly; inkscape used to be notorious for floating point rounding errors showing up with very few manipulations of a shape.

it's also been very easy to very quickly rasterize vector graphics for some time. maybe not fast enough in the past I guess, but computers are certainly fast enough now.

I look forward to a time when UIs are just all vector all the time, and it's the monitor itself which rasterizes, thanks to a program that the attached device uploads as it boots up or as the monitor is connected.

it's going to get more and more difficult to continue increasing display resolutions and refresh rates over long inexpensive cables if we continue to rasterize on a computer and push raw pixels to the display device.

Re:Why modern software is slow by danielvaughn on Thursday September 29, 2022 @10:14PM (#33030077)
afaik there just hasn’t been a lot of work done towards leveraging the GPU for vector graphics. The one example I can think of is the Slug library.
Re:Why modern software is slow by ehvatum on Friday September 30, 2022 @12:25AM (#33030921)
> afaik there just hasn’t been a lot of work done towards leveraging the GPU for vector graphic

Sure there has been, in the form of the nvidia path rendering extension. https://developer.nvidia.com/nv-path-rendering

It works great, on nvidia cards. Adobe Illustrator on Windows makes good use of it. Calling the extension from C/C++ and Python is no big deal.

Re:Why modern software is slow by djbusby on Thursday September 29, 2022 @10:22PM (#33030128)
Like? SVG UIs everywhere? Could you make a UI that's like SVG and onclick handlers do the "magic". We could have a VB6 like SVG UI designer and program "actions" in $LANG?
Re:Why modern software is slow by ygra on Friday September 30, 2022 @01:06AM (#33031212)
WPF would probably be that. In any case, modern UI toolkits often are vector-based anyway because of UI scaling. Heck, even ancient ones are, if you look at the Marlett font. That contained scalable UI elements for Windows 95.
Re:Why modern software is slow by thefz on Friday September 30, 2022 @03:45AM (#33032133)
> That being said, I think current iOS and macOS can run their UIs at 120fps (and Apple devices still seem to have decent battery life.)

The same critique for Apple applies all the time, when you are completely vertically integrated and make your own chips up to the very software running on them, it's kinda easier.

That aside, there's no display offering above 60Hz IIRC in the Apple line. Correct me if I am wrong.

Re:Why modern software is slow by shadowfacts on Friday September 30, 2022 @09:01AM (#33034278)
The phone and laptop have had them since last year, the iPad Pro has had them for years and years now.
Re:Why modern software is slow by Kipters on Friday September 30, 2022 @03:57AM (#33032212)
14" and 16" MacBook Pros are equipped with 120 Hz displays
Re:Why modern software is slow by strulovich on Thursday September 29, 2022 @10:06PM (#33030021)
A lot of the speed games get is by having bad load times when starting up.

Keeping startup really fast and all interactions really fast is more challenging than it seems.

This is not the whole story, but one example of the differences in perception.

Re:Why modern software is slow by ehnto on Thursday September 29, 2022 @10:43PM (#33030260)
Streaming in hundreds of assets as you walk around an open world does surely take a different pipeline, but as a show of computing competence it is staggering. You should see how fast some of these truly massive games load nowadays. The fact that the notepad app takes forever to load when all it needs to load is the UI is just a sad state of affairs.
Re:Why modern software is slow by wtetzner on Thursday September 29, 2022 @10:10PM (#33030044)
But games are loading enormous textures, meshes, maps, etc. UIs don’t need any of that.
Re:Why modern software is slow by astrange on Thursday September 29, 2022 @10:45PM (#33030278)
A mesh may have a lot of triangles, but it's still a single object you can memory map. UIs are typically a bunch of heap allocations and pointer jumping all created at runtime. That can be surprisingly inefficient.
Re:Why modern software is slow by 8n4vidtmkvmk on Thursday September 29, 2022 @10:53PM (#33030328)
then make it efficient. overallocate a block of memory and use it for all your tiny ui elements. its exactly what games do.
Re:Why modern software is slow by astrange on Friday September 30, 2022 @02:42PM (#33038904)
Arena allocators only work when everything has the same lifetime.

There are game-like UI libraries (https://github.com/ocornut/imgui) but to use them you have to write your program like you're a gamedev and Conway's Law usually fights that.

Re:Why modern software is slow by thomastjeffery on Friday September 30, 2022 @12:23AM (#33030904)
Most bad loading times fall into 2 categories

1. Avoidable: The main one here is shader caching. Shaders could be precompiled for every supported card/driver, but that's more work than anyone is willing to do. Even so, some games (like Rust) have an excessive amount of shaders, which adds a lot of extra waiting time.

2. Unavoidable: The main one here is textures. If you want it to be quickly accessible in VRAM, then it's going to be uncompressed, which means either having some very large files to copy over, or having some semi-large files to decompress. You can save quite a bit of time by micromanaging the texture resolution of each asset to be just high enough. Apart from textures, you have vertex data and other assets; all of which have basically the same considerations.

When it comes to regular software, most UI designs don't have big assets. They aren't loading billions of triangles or thousands of textures. This means there really isn't much need for long startup times.

Re:Why modern software is slow by userbinator on Thursday September 29, 2022 @09:33PM (#33029771)
Fortunately you can copy the binary from an older version of Windows.

At least you could thank Microsoft for being backwards-compatible.

I've done this with calc.exe since ~Vista.

the Notepad team

That's probably part of the problem --- Notepad is something that could be written by a single person in less than a day (it's not more than a wrapper around a Win32 multiline editbox.) Yet give a whole team of multiple people the task of "modernising" it, and work will magically appear to fill the available resources.

Re:Why modern software is slow by paulmooreparks on Friday September 30, 2022 @12:36AM (#33031002)
As noted in the sibling comment, Notepad does A LOT of stuff, some of it to deal with users who use (abuse?) it to do things it was never intended to do, and MS saw fit to keep it doing those things for compatibility. It did these things prior to the update, and knowing MS I imagine it's had to maintain some compatibility with the older version.

That said, I've not encountered the same slowness issues since updating that are discussed here. I'm not a fan of the menu animations, but it's a minor nitpick. For editing huge texts it is significantly more efficient, in my experience. I remember turning off word-wrap in the old notepad after loading a huge log file, then having to wait minutes for Notepad to become responsive again.

Yeah, I know, anecdata....

Edit: The source code to the older Notepad is rather easy to find online. I won't link to it, but it's an interesting read.

Re:Why modern software is slow by ntauthority on Friday September 30, 2022 @01:00AM (#33031172)
This 'modern' Notepad is actually not 'a wrapper around a Win32 edit box', it's (likely to support additional use cases like macOS TextEdit in the future - most the modernization seems to be to haphazardly 'compete' with arbitrary features from macOS) actually a variant of the Office rich text control, which in some cases actually is more performant.

The WinUI parts and initial launch cost, however, are somewhat hard to forgive.

Re:Why modern software is slow by jpitz on Thursday September 29, 2022 @09:45PM (#33029862)
Re:Why modern software is slow by biryani_chicken on Friday September 30, 2022 @02:03AM (#33031507)
> For example, did you know that you can type https://www.microsoft.com/ into Notepad’s File Open dialog?

I tried it. Everything in the File Open dialog got disabled except for the cancel button for about 30 seconds until it loaded. For comparison, curl took 2.3s (250ms in later runs so probably waiting for curl to load) and my browser took around 250ms with cache disabled as well.

Why does it take Notepad so long?

Re:Why modern software is slow by djmips on Friday September 30, 2022 @12:38AM (#33031019)
software is a gas they say.
Re:Why modern software is slow by foobiekr on Thursday September 29, 2022 @10:59PM (#33030362)
I have a 2000 line markdown file that I edit with the Mac native Markdown+ application. It is so slow that I can type full sentences before it can update. This on an M1 with 16GB of RAM doing nothing else.

2000 lines is nothing. I routinely edited book length texts in Microsoft Word for DOS on a 4.77 MHz 8088.

Re:Why modern software is slow by aldonius on Thursday September 29, 2022 @11:36PM (#33030600)
Not familiar with that specific app, but... I'm guessing it's trying to re-rendering the entire document every keystroke?
Re:Why modern software is slow by KerrAvon on Thursday September 29, 2022 @11:40PM (#33030632)
That’s my guess. Hard to do it any other way for Markdown. However, it could probably do that on a background thread and still be responsive with large amounts of text.
Re:Why modern software is slow by WalterBright on Thursday September 29, 2022 @11:55PM (#33030719)
This can be done without multiple threads. MicroEmacs does it by checking the keyboard input buffer every once in a while while rendering. If there's a key in it, it abandons the rendering to go service the key. When there are no keys in the buffer, it tries rendering again. It works so well you never notice this is happening, you just get instance keyboard response.
Re:Why modern software is slow by rayiner on Friday September 30, 2022 @12:42AM (#33031045)
As I recall GNU Emacs does this too, by default. https://www.masteringemacs.org/article/improving-performance...
Re:Why modern software is slow by WalterBright on Friday September 30, 2022 @02:52AM (#33031795)
I expect this is normal practice.
Re:Why modern software is slow by ComputerGuru on Thursday September 29, 2022 @11:49PM (#33030681)
Forget background threads. People don’t know basic programming principles. The thought of debouncing user input didn’t even occur to them.
Re:Why modern software is slow by rustybolt on Friday September 30, 2022 @12:42AM (#33031041)
What do you mean by 'debouncing' here? I only know it as ignoring keypresses of the same key/button that happen too fast after each other (because they are likely a mechanical or electrical glitch rather than the user actually meaning to press the button/key multiple times).

If you mean that, I don't know how it relates to the comment/article since I never needed to do debouncing in a desktop context (only for embedded stuff with actual push button circuitry attached).

Re:Why modern software is slow by kiawe_fire on Friday September 30, 2022 @01:14AM (#33031284)
That same concept, but one step removed if you will.

The classic example is a data table with a text field that filters/searches the results, pulled from a server.

Let’s say you want the results to update “live” as the user types, without having to click a “search” button. So if the user types “bacon” then she sees all results that contain the word “bacon” in them.

Problem is, if the act of sending the text field input to the server and waiting for the results is relatively slow and blocks the UI from updating, then each key press causes a delay between the search results updating on the screen, and the next letter showing up in the search field.

1. User types “b” and then the app sends “b” to the server, pauses, gets a response of all results with the letter “b”.

2. User types “a”, and the app sends “ba” to the server… pauses… gets results. She types a “c”, the app sends “bac”, etc.

Debouncing, then, means the app waits a short period of time to make sure the user is finished typing before sending the search term.

Usually this means every time the user enters a letter into the search field, the app sets a timer for, say, 500ms. If the user doesn’t enter another letter for 500ms, great - send the search term, wait for the results.

If the user does enter another letter within 500ms, then she must still be typing, so reset the timer back to 500ms and hold off on sending the search term out to the server.

Re:Why modern software is slow by edflsafoiewq on Friday September 30, 2022 @01:13AM (#33031277)
Same idea, debouncing replaces a sequence of "re-render Markdown" events (button pushes) with a single "re-render" event (button push). Googling "debouncing" will turn up a bunch of articles about it.
Re:Why modern software is slow by foobiekr on Friday September 30, 2022 @12:34AM (#33030987)
This. Incredible. Debouncing was done in the early 70s and even someone on;y familiar with more modern similar ideas would note that Nagling was invented in 1984 at the latest...
Re:Why modern software is slow by stingraycharles on Friday September 30, 2022 @12:40AM (#33031029)
Not a UI / frontend developer. Doesn’t denouncing user input increase the latency before changes are rendered onto the screen?

I would expect the changes to be visible ideally in the next frame, but I guess that’s not really an option?

Re:Why modern software is slow by wtallis on Friday September 30, 2022 @01:04AM (#33031198)
Debouncing only has to carry a latency penalty for certain kinds of responses. A good UI should be able to start processing an action as soon as the button goes down, and add/amend the actions later once it's clear whether it was a press and hold, press and release, or double-click. If the appropriate responses to those three options are mutually exclusive to the point that the UI can't respond at all until the user input is fully disambiguated, then the keybindings are probably ill-considered and those unrelated or conflicting functions should not be sharing a button.
Re:Why modern software is slow by ComputerGuru on Friday September 30, 2022 @01:01AM (#33031176)
In the strictest sense, yes. But here clearly rendering is taking longer than 1/60s so it wouldn’t matter.

The compromise would be to always start rendering immediately rather than wait x ms, but if you detect that the previous rendering hasn’t completed when the next input has arrived then you can start debouncing before rendering until you catch up.

Re:Why modern software is slow by torstenvl on Thursday September 29, 2022 @11:59PM (#33030745)
Seems like Markdown could be rendered 1-3 lines at a time, depending on line-height. It isn't like other formats where formatting information is spread all over the place.
Re:Why modern software is slow by eyelidlessness on Friday September 30, 2022 @12:12AM (#33030833)
Type two backticks, everything below is fine. Type one more… the entire rest of the syntax tree is potentially a new tree. Backspace, do the whole thing again.
Re:Why modern software is slow by worthless-trash on Friday September 30, 2022 @12:34AM (#33030990)
Behavior solvable.

When a user inserts to backticks, insert the closing backticks immediately.

Re:Why modern software is slow by MauranKilom on Friday September 30, 2022 @05:17AM (#33032731)
Cool, now explain how to do it for backspace.

And now explain how anyone can ever turn existing text into a code block if every user action is "modified" to not turn existing text into a code block.

Re:Why modern software is slow by worthless-trash on Sunday October 02, 2022 @05:22AM (#33054359)
This may be obvious but if you're trashing the second pair of backticks you obviously want the rest of it to be inside the backticks which required the first re-render so its not a mistake, the user made the request , follow through, render till the next set of bacticks into a block.. no trailing backticks ? Render everything.. thats the choice the user made.

> And now explain how anyone can ever turn existing text into a code block if every user action is "modified" to not turn existing text into a code block.

At no point did I mention that you couldnt wrap code in bacticks, I simply said the default insert would NOT have single pair backticks opening up to a forced re-render of every trailing element.

Re:Why modern software is slow by eyelidlessness on Friday September 30, 2022 @02:12AM (#33031557)
That solves your problem but probably doesn’t solve the user’s.
Re:Why modern software is slow by RhodesianHunter on Thursday September 29, 2022 @11:41PM (#33030639)
I'm not sure if it's the case with this particular app, but with many apps these days you have to seek out and download the version specifically for apple silicon.

IntelliJ was killing me until I figured this out.

Re:Why modern software is slow by foobiekr on Friday September 30, 2022 @12:39AM (#33031025)
The problem here isn't the intel/arm issue, it's that the application amplifies handling a single keystroke into what is basically a massive re-rendering job instead of applying any of dozens of well-known solutions to the problem.

Applications are simply not well written and most developers are incompetent and unaware of how incompetent they are.

Re:Why modern software is slow by KerrAvon on Thursday September 29, 2022 @11:38PM (#33030610)
Sure, but in MS Word on an 8088 you were editing in DOS text mode.

Markdown+ is parsing and rendering your Markdown in real time. It may be slower than it needs to be, I haven’t used it and don’t know, but it’s doing a lot more work than 1982-era MS Word was.

You can still get blazing fast speed for even gigabytes of Markdown if you use instead use something like BBEdit on a current Mac, which would be the equivalent modern user experience.

Re:Why modern software is slow by function_seven on Friday September 30, 2022 @12:00AM (#33030753)
All that parsing and rendering can be done in the background, not grinding the UI to a halt. As soon as I strike a key on my keyboard, the letter should appear. Instantly. (Ok, in 20ms or 40ms or whatever)

If I'm actively editing a markdown file, I do not need for it to fire off a re-render on each keystroke. It can wait 500ms before starting to do it, and cancel if I hit another key in the meantime. If I start typing after it has started rendering, then go ahead and finish that cycle while still showing me what I type in real time.

However these events are scheduled, the appearance of my typed characters on the screen is going to always be the priority. There's no reason to block UI while doing this.

Re:Why modern software is slow by WalterBright on Friday September 30, 2022 @12:37AM (#33031007)
I use Thunderbird mail. It often freezes for several seconds while typing text. This is ordinary behavior for modern software. I'm not excusing it, it's just that it's hardly exclusive to Microsoft.

TB is a multithreaded program, but it isn't very good at using it effectively. I've learned through bitter experience to not touch a key or the mouse when it is getting messages.

Re:Why modern software is slow by vladvasiliu on Friday September 30, 2022 @12:34AM (#33030988)
I've never used Word for DOS. The oldest I've used it "seriously" was word 97 on windows 95 or 98 on a 100 MHz 486. Not book-length documents, but comfortably in the dozens of pages. That thing would fly.

Modern Word lags on a two-page document on an 8 core xeon with 64 GB of RAM. Same PC can run modern games at 4k@60 FPS.

I can agree that maybe modern Word "does more work" than Word 97. But as another commenter said: WTF is that work? And do we even need it?

As a user, all I see is that modern Word's interface has buttons all over the place, taking up half my screen. And when I grab the scroll-bar, it won't scroll until some time after I've released it. Word 97 managed to scroll the contents as I moved the bar just fine.

It also takes forever to start-up on an SSD so fast it can move multiple times the size of that old 486's whole hard drive in one second. WTF is it loading? And once loaded, why is it so slow, since everything can fit in RAM?

Re:Why modern software is slow by tuatoru on Thursday September 29, 2022 @11:52PM (#33030702)
> it’s doing a lot more work than 1982-era MS Word was.

That's the point of gp's comment. The software is doing a lot of "work" that it does not need to do, thanks to poor programming.

Work is activity that helps to achieve a goal. Whatever Win11's Notepad is doing, it is not that.

Re:Why modern software is slow by raphlinus on Thursday September 29, 2022 @11:58PM (#33030736)
Markdown parsing can be quite fast. I just benchmarked pulldown-cmark parsing all the Markdown in my blog (10k lines, 1MB) and writing HTML, and it does that in 14ms. Admittedly that's on an M1 Max.

If indeed premature optimization is the root of all evil, then I have lots to atone for.

Re:Why modern software is slow by djmips on Friday September 30, 2022 @12:36AM (#33031005)
premature optimization is the root of all evil is the root of all evil.
Re:Why modern software is slow by foobiekr on Friday September 30, 2022 @12:36AM (#33031001)
I think my point was lost on you. Word had code to accommodate the realities of what the application was trying to achieve. This app I mention could trivially be hundreds of times faster just by doing basic things that have been done since before most current SWE were born.
Re:Why modern software is slow by abruzzi on Thursday September 29, 2022 @11:50PM (#33030685)
I don't know how it did it, but the old DOS version of MS word actually displayed bold/italic/underline in the DOS terminal. It wasn't WYSIWYG but the display was a bit nicer than Wordstar.
Re:Why modern software is slow by pmontra on Friday September 30, 2022 @12:41AM (#33031035)
For all the 80s (before the first version for Windows) the terminal was the only thing out there, plus the graphic modes. I think that bold/italic/underline only existed in the graphic mode version (EGA.)

https://en.wikipedia.org/wiki/History_of_Microsoft_Word

Re:Why modern software is slow by mickael-kerjean on Friday September 30, 2022 @12:28AM (#33030938)
Ha the DOS terminal, that thing where the fullscreen button wouldn't work and you have to right click -> properties -> layout -> change the window size manually until you have something that work ok.

At least, they have fix it in the most recent version of windows ....

Re:Why modern software is slow by worthless-trash on Friday September 30, 2022 @01:04AM (#33031192)
I imagine the OP means the dos interface.
Re:Why modern software is slow by matheusmoreira on Thursday September 29, 2022 @10:53PM (#33030330)
First they ruined the perfectly functional calculator software by bloating it up to the point it takes several seconds to even appear on screen. Now you're telling me the next time they update Windows at work, the notepad will also be ruined.

It just keeps getting worse. I mean how hard is it to do nothing and leave these old apps alone?

Re:Why modern software is slow by ncmncm on Thursday September 29, 2022 @11:13PM (#33030451)
There's no excuse for 2 seconds. Machines are a thousand times as fast as in the 90s, and a text editor didn't take any 2000 seconds, or even 2 seconds, back then.

Now they load up the monstrous libraries they need to negotiate a way to communicate with the desktop, and then negotiate that. A screen buffer is so yesterday, so I guess they have a scene graph now that some library renders whenever a pixel might have changed, triple-buffered to prevent artifacts.

Re:Why modern software is slow by flenserboy on Friday September 30, 2022 @12:22AM (#33030898)
It's probably time to start all over. Chuck compatibility for usability — no more POSIX & friends, for instance, along with the rush to compile everything on anything new, with all the cruft those efforts inject into a system. Let the new thing be the new thing for a while. As much as I like what I can do with a modern system, I've found myself longing more than once of late for an 80x24 text display with instant responses from the system.
Re:Why modern software is slow by rayiner on Friday September 30, 2022 @12:02AM (#33030767)
MacOS X introduced a fully buffered desktop to prevent artifacts 21 years ago. It was a bit pokey on a 500 MHz G4 but still faster than today’s apps.
Re:Why modern software is slow by sitzkrieg on Thursday September 29, 2022 @10:58PM (#33030354)
overpaid ui designers that should probably be contracts maybe. so much pointless 'work'

there is fogies complaining about change, then there is making things objectively worse for zero gain. christ

and they are releasing a new taskmgr on win11 to boot

Re:Why modern software is slow by vladvasiliu on Friday September 30, 2022 @12:44AM (#33031053)
> and they are releasing a new taskmgr on win11 to boot

Which is borken. In the performance tab, I often see the right-hand side elements cut-off (like RAM size, etc) even though there's still space left in the window. Resizing it brings the text back.

But hey, at least it now supports dark mode!

Re:Why modern software is slow by WesolyKubeczek on Friday September 30, 2022 @06:23AM (#33033093)
What do you want from a company that cannot fit their progress indicator squares neatly into their own progress bars since 1995? (Anyone who has seen scandisk and defrag from Windows 95 will understand)
Re:Why modern software is slow by sitzkrieg on Friday September 30, 2022 @12:44AM (#33031057)
nothing is sacred! go figure
Re:Why modern software is slow by waynesonfire on Thursday September 29, 2022 @11:18PM (#33030485)
And we wonder what 7k employees are doing at Docusign... so many useless positions, people gatta find something to do to pad that promo packet.
Re:Why modern software is slow by naikrovek on Thursday September 29, 2022 @10:06PM (#33030016)
to be fair to Microsoft, the terminal developers didn’t have a lot of experience with approaches like the one Casey used. Casey had 25+ years of game development experience to draw from, and the Windows Terminal team didn’t.

game development is an entirely different paradigm than enterprise software development; they aren’t really comparable, other than they both produce software which successfully executes.

in games, any code which does not directly contribute to the final product is not written, or is removed after it is not needed. in enterprise software, tens of thousands of lines of code are produced simply so the project layout is familiar for everyone working on it, because that’s important, somehow?

Casey was right to complain about the performance, and to show them how it should work. licensing it so that they couldn’t even look at it was both 100% intentional and 100% a dick move, and i will not credit him for that. that code could have been used as a wakeup call regarding performance for a lot of people within Microsoft, but he licensed it so they can’t even look at it.

perfomance of microsoft software isn’t great, i’ll agree. poking fun at them then hiding the code that was easy enough to write for him, but completely not obvious to the Windows Terminal team, doesn’t really make Casey the Software Quality Hero you’ve portrayed him as. Casey writes excellent software, don’t get me wrong. this particular example and series of events is not a high point in his career, to me.

Re:Why modern software is slow by feoren on Thursday September 29, 2022 @10:18PM (#33030108)
Paraphrasing: "To be fair to one of the consistently largest software giants of the last 40 years, with nearly unlimited budget and a reputation for paying its software engineers well, they actually suck ass at writing software".

You seem to roughly agree with this in your 3rd paragraph. Enterprise software is fucking awful despite spending an enormous amount of money on it, and that's because the developers and the development process and the SMEs and the managers and vice presidents are all fucking awful at their jobs. That's the reason. They're fucking shit-ass at making software. Just look at Microsoft Teams. This is not the defense you seem to think it is.

Besides, we're not talking about enterprise software driven by bloat from the demand-side. We're talking about notepad and the console.

Marketing and legal is stellar though.

Re:Why modern software is slow by ClumsyPilot on Thursday September 29, 2022 @10:29PM (#33030162)
> Enterprise software is fucking awful despite spending an enormous amount of money on it, and that's because the developers and the development process and the SMEs and the managers and vice presidents are all fucking awful at their jobs

Enterprise software written 20 years ago still runs and works. I can still install it from an Msi package

Half the android apps I bought 5 years ago don't exist any more.

In Google they would have cancelled, closed, relaunched and cancelled again.

Games are hit and miss, admittedly some run for decades.

But above all, they dont care

Re:Why modern software is slow by the_af on Friday September 30, 2022 @12:04AM (#33030788)
Games can avoid a lot of maintenance patterns that look like cruft simply because many games are fire and forget and not truly expected to have a long shelf life.

PS: you wouldn't believe how many tries it took to get my phone to accept the word "cruft" instead of autocorrecting it to craft. Dammit!

Re:Why modern software is slow by naikrovek on Thursday September 29, 2022 @10:59PM (#33030358)
> This is not the defense you seem to think it is.

it’s not a defense at all, it’s my whole point.

enterprise software is absolutely lost, because following enormous sets of rules and enforcing those rules via management is FAR CHEAPER AND EASIER than hiring skilled people who don’t need those rules to produce good software.

if that isn’t the very definition of bad management and business practices, i don’t know what is.

enterprise software being a total shitshow is my point, because a shitshow is far better for shareholders in the short term. filling seats with dopes you hope to train is easy to measure. carefully harvesting the best talent is slow, expensive, and difficult to measure.

microsoft does that. all large publicly traded companies optimize for short-term gain at the expense of long-term loss.

game companies, the good ones, the smaller ones, don’t operate like that. there are shit managers there, too, but game companies attract the exact talent they need, almost by default. they care about what they create because not caring means bad reviews, low sales, no bonuses, and layoffs.

the punishment for writing shit software at any enterprise company is continued employment, and at worst, an involuntary lateral move to another position where software quality does not matter.

microsoft is an enterprise software developer. they are burdened with that management style just like a lot of our employers are.

Re:Why modern software is slow by WalterBright on Friday September 30, 2022 @12:05AM (#33030790)
> microsoft does that. all large publicly traded companies optimize for short-term gain at the expense of long-term loss.

I hear this claim all the time, but nobody is able to explain why they continue to grow profits.

Re:Why modern software is slow by pid-1 on Friday September 30, 2022 @12:18AM (#33030874)
I'm the "main tech guy" of a financial firm and I can answer this question.

It's because people like me don't care about user experience.

We get Teams for free in our M365 subscription. It's integrated with other stuff, it has APIs for automation and I can't be blamed for choosing MS.

I know this is a shitty argument... but seriously, I have many battles to fight, not wasting my energy choosing the best chat software.

Devs think a lot a about software quality and stuff, but that's often irrelevant for business. GP is wrong, MS knows exactly what they need to do to increase profits.

Re:Why modern software is slow by naikrovek on Friday September 30, 2022 @12:33AM (#33030980)
optimizing for short-term gain is growing profit. what do you think short-term gain is? it's gain!

what it isn't is investing in quality and long-term success; it's betting that you'll be able to find some other short-term optimization in the future, and it relies on the stock market having a memory that lasts no longer than one year

Re:Why modern software is slow by WalterBright on Friday September 30, 2022 @02:51AM (#33031787)
Microsoft has had 35 years of long term growth. How can you say optimizing for short term profit at the expense of long term profit is their strategy?

> and it relies on the stock market having a memory that lasts no longer than one year

If that was true, you could easily make $billions shorting those stocks that you know sacrifice the long term. Let us know how it goes!

Re:Why modern software is slow by naikrovek on Friday September 30, 2022 @08:12AM (#33033822)
Microsoft doesn't do _everything_ with an eye on short-term gain, is why.

Everything Microsoft did in the 1990s was based on returning profit sooner rather than later. That's the whole point of "embrace, extend, extinguish": liquidate this technology and turn it into money as fast as possible.

Every time you make a decision which gives you money or profit today, and that decision is based on money alone, you are optimizing for the short term at the expense of the long term.

It is easier to think about when you think of personal finances. You can have a slightly bigger paycheck every pay period or you can set aside money for retirement. You can maximize profit today if you borrow from your own future.

I should not have said that Microsoft do this exclusively (and at this very second I'm not sure I said that) because they don't do that exclusively. It is a common approach to decisions regarding stock price and "shareholder value" however.

Re:Why modern software is slow by WalterBright on Friday September 30, 2022 @06:13PM (#33041475)
> Everything Microsoft did in the 1990s was based on returning profit sooner rather than later.

Are you aware of what happened to MSFT stock during the 1990s? The claim is not credible.

> It is easier to think about when you think of personal finances. You can have a slightly bigger paycheck every pay period or you can set aside money for retirement. You can maximize profit today if you borrow from your own future.

This is not what "profit" is.

Re:Why modern software is slow by naikrovek on Saturday October 01, 2022 @01:23AM (#33044127)
how in the hell am I this bad at communicating?

optimizing for short term gain IS OPTIMIZING TO MAXIMIZE PROFIT IN THE SHORT TERM.

Re:Why modern software is slow by WalterBright on Saturday October 01, 2022 @01:36AM (#33044186)
If your focus is on optimizing for short term profit at the expense of long term, your company won't last long.

If your company does last long, and grows enormously, you are optimizing for the long term.

Re:Why modern software is slow by naikrovek on Monday October 03, 2022 @05:40AM (#33065276)
those companies don't last long, except for those that get lucky, and continue to find new (or create new) things to quickly liquidate.

being a public company and having shareholders more or less requires you to increase stock price at the expense of almost anything else.

investors do not care if a company goes under, provided they get a handsome return on their investment beforehand.

Re:Why modern software is slow by lmm on Thursday September 29, 2022 @11:01PM (#33030381)
Games developers have a very different tradeoff between bugginess and speed than most developers. Security bugs are completely fine, inconsistent and unreproducible behaviour is mostly fine, especially if it's funny.
Re:Why modern software is slow by seba_dos1 on Friday September 30, 2022 @12:16AM (#33030862)
> are completely fine

Can be fine. There are plenty of computer game genres where security bugs are not fine at all and where you need to be super careful to not introduce nondeterminism as that would break the whole game, all while maintaining performance.

Re:Why modern software is slow by ajdude on Thursday September 29, 2022 @11:21PM (#33030504)
Companies should market their software based on celebrity programmers who wrote it. Similar to Shelby cars or warren Buffett stock pics.
Re:Why modern software is slow by spaetzleesser on Thursday September 29, 2022 @11:59PM (#33030746)
Just look at Teams. It feels more and more like a project run by a few interns that are practicing Agile.
Re:Why modern software is slow by jiggawatts on Thursday September 29, 2022 @10:45PM (#33030273)
> licensing it so that they couldn’t even look at it

https://github.com/cmuratori/refterm/blob/main/LICENSE

It’s just GPL 2.0, what are you talking about!?

Are Microsoft employees vampires that will burn up instantly if they merely glance at GPL code or something?

This is sour grapes nonsense from Microsoft. “We don’t like your tone so we won’t even dignify your argument by considering it.”

At one point an MS employee said they would love to fix their code as suggested by Casey but he refused to even look at the YouTube video!

“I would love to hear your arguments but I refuse to listen to the sound of your voice.” is next-level dismissive.

Re:Why modern software is slow by naikrovek on Thursday September 29, 2022 @11:13PM (#33030455)
> just GPL 2.0

perhaps you are not familiar with what the GPL requires of its users, and how wildly incompatible that is with what a company like Microsoft does.

Microsoft employees are forbidden from looking at GPL code (as well as other virally licensed code) because they may unwittingly reproduce some GPL code they saw in a large Microsoft codebase.

If that happens, and they are taken to trial over it, and lose, that entire codebase is now GPL. This is enough of a risk to them that MS employees have computers which simply can not view GPL code.

that is also why they would not watch the video; it isn’t about his voice, it is about the code visible on stream. additionally, watching a video of GPL code being written could be perceived as an attempt to circumvent the restrictions on viewing GPL code, and would likely get the viewer into trouble.

you not already knowing this bothers me a lot, given all the things you’ve said in this discussion. you are making a lot of assumptions that are just not true and basing your opinions on the belief that those assumptions are true.

this is very similar to why software at microsoft is as bad as it is generally; a lot of people assuming they know things they don’t know, and producing results which are more flawed than they needed to be.

Re:Why modern software is slow by seba_dos1 on Friday September 30, 2022 @12:04AM (#33030789)
There's no reason other than lack of will for something like Windows Terminal to not be GPL compatible. The limits Microsoft places upon themselves are results of their own conscious choices.

Also, Microsoft employees work on GPL2-licensed Linux just fine, so something seems off in your story.

Re:Why modern software is slow by naikrovek on Friday September 30, 2022 @12:38AM (#33031016)
other Microsoft libraries are used in Windows Terminal, optionally in code form. cmd.exe is in the same source tree, and other proprietary code of Microsoft's relies on that code; it's a non-zero portion of the command-line stuff that ships in Windows.

stuff that is not Windows Terminal but that lives in the Windows Terminal repo on GitHub gets shipped with Windows.

so, yes, there are very good reasons they can't license Windows Terminal via GPL.

WSL kernel folks get that repo whitelisted.

Re:Why modern software is slow by seba_dos1 on Friday September 30, 2022 @12:58AM (#33031166)
None of what you said inherently prevents GPL licensing. I'm not sure you understand the implications of GPL license at all.

Also, it's not just WSL people who work on GPL software inside Microsoft. I guess they are magically expected not to subconsciously reproduce any GPL code in their work ever ;)

Re:Why modern software is slow by naikrovek on Friday September 30, 2022 @08:14AM (#33033838)
you're right, nothing i said inherently prevents GPL licensing, but the existing license terms of the code they write themselves and license from others does inherently prevent GPL licensing. I thought that was clear, but apparently I need to be more deliberate with my comments.
Re:Why modern software is slow by jiggawatts on Thursday September 29, 2022 @11:24PM (#33030518)
IF THEY COPY IT VERBATIM.

They're free to look at the approach and simply rewrite it.

They'd have to anyway to fit in with their codebase.

Re:Why modern software is slow by forgotpwd16 on Friday September 30, 2022 @03:50AM (#33032171)
>They're free to look at the approach and simply rewrite it.

If by "look at the approach" you mean the "look at the code", then no. You're giving a step for your code to be considered a derivative work. If by "look at the approach" you mean someone read the code, made a specification, and then someone else that hasn't looked the code, made a program based on the specification, then yes. But arguably this isn't "simply rewrite".

Those aren't even baseless considerations. ReactOS project had paused development due to concerns that derived (read: rewritten) parts of leaked Windows code may have been used. It took years for ReactOS to show that everything was in fact a clean-room implementation (basically doing what wrote above). If they hadn't, they'll have made themselves open to be sued by Microsoft.

Re:Why modern software is slow by naikrovek on Friday September 30, 2022 @08:20AM (#33033882)
can you, as a lawyer for Microsoft, make a guarantee to the business that if allowed, a software developer at Microsoft who works on the Windows source code will not ever reproduce a method they saw in a GPL codebase in the code they write for their job?

You can not. So what do you do to prepare for a lawsuit which alleges that you've copied GPL code into the Windows codebase? You have technical and legal barriers in place so that those developers can't see GPL code where you can control that, and make them promise that they won't do anything to compromise the license of the Windows code that they work on. Technical and legal (read: contractual) measures to prevent this are the defense that one needs to have in order to defend against a case like this, in court.

So, because you, as a Microsoft attorney, can't guarantee that GPL code won't be reproduced verbatim in any quantity in the Windows codebase, you do what you can to dissuade your developers from looking at GPL code.

please think for 2 seconds on your own and I won't have to ELI5.

Re:Why modern software is slow by ikiris on Friday September 30, 2022 @12:06AM (#33030795)
Do you just not understand copyright? That is totally in violation.
Re:Why modern software is slow by the_af on Friday September 30, 2022 @12:13AM (#33030845)
Wait, I'm also confused. I thought completely rewriting the implementation of an algorithm would not violate copyright. It may run afoul of other laws, but not copyright. Am I mistaken?

I don't mean simply renaming variables or changing a couple of lines.

Re:Why modern software is slow by ikiris on Friday September 30, 2022 @12:47AM (#33031082)
It does, but only if you can show its not a derivative work. See also the concept of clean room reimplementation.
Re:Why modern software is slow by kragen on Friday September 30, 2022 @05:15PM (#33040898)
"Derivative work" doesn't mean "a work made with knowledge of another work". WP explains, "In copyright law, a derivative work is an expressive creation that includes major copyrightable elements of an original, previously created first work (the underlying work)." Canonical examples include translations into another language, dramatizations of novels, or phonorecords of sheet music.

Algorithms, being purely functional, are not copyrightable in any country that I know of. So a new implementation that uses the same algorithm as the original, but without copying any of its non-functional aspects, is not a derivative work of the original and does not infringe its copyright.

Cleanroom reimplementation is a defense against allegations of copying, because under, for example, US copyright law, access plus substantial similarity is sufficient to show copying. The "He's So Fine" lawsuit is one of the most extreme examples of this doctrine. Cleanroom reimplementations are a defense against copying by eliminating the access element. But copying the functional aspects of a program does not meet the "substantial similarity" bar.

Re:Why modern software is slow by seba_dos1 on Friday September 30, 2022 @12:20AM (#33030892)
> Am I mistaken?

No.

Re:Why modern software is slow by jcelerier on Thursday September 29, 2022 @11:50PM (#33030691)
Uh, no. You cannot e.g. listen to a Radiohead song and "look at the approach and simply rewrite it" for instance if you want to be entirely clear of copyright liability - same applies for software.
Re:Why modern software is slow by the_af on Friday September 30, 2022 @12:12AM (#33030834)
Isn't copyright about copying verbatim (or with trivial enough changes that it remains recognizably the same) large enough sections of the protected work?
Re:Why modern software is slow by jcelerier on Friday September 30, 2022 @12:20AM (#33030887)
At least not in my country (France). At the very least changing the pitch, and rhythm and interpretation of a melody is not enough to make it an original work there.

To give a very concrete example: french singer Claude François made the song Comme d'habitude: https://youtu.be/avr5nvY4wxg

It was translated and rewritten a few times but he still is recognized as one of the copyright owners on those covers, e.g. https://youtu.be/qQzdAsjWGPg which are definitely not just a mechanical rewrite of the original score

Re:Why modern software is slow by seba_dos1 on Friday September 30, 2022 @02:41AM (#33031715)
There's a difference between creating a derivative work and analyzing how something is done in order to create something new based on that knowledge. You can make songs in style of Led Zeppelin that sound like they could be written and performed by Led Zeppelin without violating any copyrights (and to be able to do that you obviously need to know some Led Zeppelin songs beforehand), but you can't take "Dazed and Confused", change the guitar solo and part of the lyrics and call it done...

Well, at least unless you end up as big as Led Zeppelin was before someone catches you, I guess ;)

Re:Why modern software is slow by jcelerier on Friday September 30, 2022 @08:56AM (#33034220)
> Well, at least unless you end up as big as Led Zeppelin was before someone catches you, I guess ;)

Are you talking about the Led Zeppelin who get entangled in judicial pursuits for plagiarism every couple years? If it was as clear cut as you say it is it would never reach any judge.

There is even one case where someone was condemned for not copying any specific song but the general style of another musician : Pharrell Williams had to pay 5M to the Marvin Gaye estate because of this

https://rpjlaw.com/blurred-lines-copying-songs-musical-style...

https://www.jonesday.com/en/insights/2018/07/blurred-lines-b...

Yes, this is extremely shitty but this is the world we live in

Re:Why modern software is slow by seba_dos1 on Friday September 30, 2022 @09:30AM (#33034586)
> Are you talking about the Led Zeppelin who get entangled in judicial pursuits for plagiarism every couple years?

Yes, I intentionally mentioned a song "by Page – inspired by Jake Holmes": https://en.wikipedia.org/wiki/Dazed_and_Confused_(song)#Led_...

> The Ninth Circuit stated that the appeal was decided “on narrow grounds” and that the “decision does not give license to copyright a musical style or ‘groove.’”

What a pile of bullshit. I wasn't aware of that case.

Re:Why modern software is slow by seba_dos1 on Friday September 30, 2022 @12:09AM (#33030815)
Of course you can. That's what a huge chunk of art ever created does. You're only (potentially) in trouble when you make it obvious.
Re:Why modern software is slow by userbinator on Thursday September 29, 2022 @11:58PM (#33030738)
No, otherwise authors of books would be suing everyone who read them and learned their ideas.
Re:Why modern software is slow by Ygg2 on Thursday September 29, 2022 @10:54PM (#33030334)
> Are Microsoft employees vampires that will burn up instantly if they merely glance at GPL code or something?

More like will legal drain life from developers if they hear they looked at GPL code.

We had to switch DB drivers because legal didn't want to deal with GPL. Imagine writing code based on it...

Re:Why modern software is slow by maxerickson on Thursday September 29, 2022 @10:19PM (#33030113)
It seems perfectly fair to expect Microsoft to throw resources at heavily used apps. "They don't have the experience to make it good" is pretty chickenshit.
Re:Why modern software is slow by naikrovek on Thursday September 29, 2022 @10:32PM (#33030182)
> It seems perfectly fair to expect Microsoft to throw resources at heavily used apps.

yes it does seem perfectly fair, doesn’t it? it isn’t. the amount of work that needs to be done always outscales the ability to do the work, forcing prioritization. the Windows Terminal team is not large, and just throwing people at the team will not make it faster.

> "They don't have the experience to make it good" is pretty chickenshit.

you’re very unpleasant already. second sentence, calling me chickenshit. classy.

how many people do you know who are capable of writing what Casey wrote in two weekends who also DON’T work on games full-time?

i don’t know any people like that. so, where do you think those people go to work? on Windows Terminal? like that’s a common career path for someone like Casey? i would be absolutely flabbergasted if there were someone on the Windows Terminal team who knew how to do what Casey did before he did it. “Hey, come work on the command prompt” does not attract people who understand how to dynamically generate a texture atlas of code points and use that atlas to render a texture representing the console window contents 60/120/144/240 frames per second. the people that know how to do that are already spoken for.

Re:Why modern software is slow by jiggawatts on Thursday September 29, 2022 @11:14PM (#33030463)
> i would be absolutely flabbergasted if there were someone on the Windows Terminal team who knew how to do what Casey did before he did it.

THAT is precisely the problem!

What Casey did was not some unique and special solution known only to dark wizards working on AAA game engines.

It's an obvious solution that has been implemented many times before by many people for many systems. All green-screen and DOS-era terminals work this way, for example.

Admittedly, I'm a former game engine developer, but I went into that career with essentially zero industry experience of any type. I just muddled my way through a C++ textbook and started writing a game engine.

I needed a text console for my game engine, and I also needed to display Unicode text because we were targetting an international market.

Completely naively I wrote a "text engine". It took about a week, and my solution was virtually identical to Casey's. The difference was that I was slower at implementing it, and Casey's is more feature complete, but the approach was identical.

I didn't go to Hogwarts School for Game Development Wizardry. I just thought about the problem and applied the obvious solution.

The difference between people like Casey and the Microsoft team is not necessarily aptitude, but attitude. The Microsoft team has no mechanical sympathy and no interest in quality.

They made arguments not just along the lines of "this is impossible", but also "nobody needs this".

Through every fibre of their being they believe that computers are slow and that this is fine.

Re:Why modern software is slow by naikrovek on Friday September 30, 2022 @12:44AM (#33031054)
> All green-screen and DOS-era terminals work this way, for example

lol no they do not. absolutely not lol

> The Microsoft team has no mechanical sympathy and no interest in quality.

I know people at Microsoft. I have acquaintances on the Windows Terminal team. this is just plain factually incorrect.

Re:Why modern software is slow by salawat on Friday September 30, 2022 @09:54AM (#33034858)
The proof is in the putting sadly. Anyone with a concern about Quality would not have shipped. As they would be inflicting pain rather than resolving it.
Re:Why modern software is slow by kragen on Friday September 30, 2022 @05:32PM (#33041075)
Green-screen and DOS-era terminals don't work by having a custom shader running on a GPU, it's true, but they do have hardware that does the same thing Muratori's custom shader does: generate screen pixels by looking up texture data in a texture atlas indexed by a glyph index taken from a display buffer, which is updated by software. Consequently their display latency averages about 9 milliseconds.

Those character generators don't do rescaling and linear interpolation of the texels, and often they're only one-bit color, but that's extra work refterm is doing that DOS-era terminals weren't doing. It wasn't that Muratori invented a new, more efficient way to do things; he just reproduced the bitmap character-generator approach that was standard from 01975 to 01985, but runs it on faster hardware. So he got about 160 megabytes per second before optimizing, ten times faster than Windows Terminal, and 1600 megabytes per second after he "put in the most basic optimization [he] could think of".

It isn't necessary to do character generation on the GPU to be responsive, either. The Alto running Smalltalk took maybe a second for its ≈0.5 MIPS CPU to redraw a screenful of proportional text, say about 2kB. The original Macintosh took maybe 100 ms using a 1-MIPS CPU and hand-optimized assembly. But the laptop I'm typing this on is about 34000 MIPS so it ought to be able to do the job in ≈3 μs. My word-wrapped proportional-font experiment in http://canonical.org/~kragen/sw/dev3/propfont.c gets 72 MB/s, which works out to ≈30 μs per 2-kB "screenful". Valgrind says it's running about 113 instructions per byte rendered, suggesting my C is closer to Smalltalk performance than QuickDraw. It's still 20× as slow as refterm but it's not using the GPU, but 5× as fast as Windows Terminal. (On the other hand, it doesn't draw to the actual display, just a memory buffer which it outputs to a PNM file at the end.)

My own unoptimized monospace terminal emulator running on the CPU with a full-color font https://gitlab.com/kragen/bubbleos/-/blob/master/yeso/admu-s... takes 6.9 wallclock seconds and 3.1 CPU seconds to display the output of yes {1..90} | head -c 1000000. This is enormously slower, only 145 kilobytes per second or 323 kilobytes per CPU second, a whole 14 milliseconds per 2-kB screenful. (And its screen really is 2 kB.) This is 1000 times slower than refterm and 100 times slower than Windows Terminal, and it still doesn't handle the difficult cases like combining characters, double-width CJK characters, and RTL text. Probably I should optimize it!

Re:Why modern software is slow by maxerickson on Thursday September 29, 2022 @10:55PM (#33030341)
I didn't call you chickenshit, I called giving them leeway chickenshit (by synthesizing a statement that I thought roughly reflected the leeway).

I have no idea who could match what, but Windows is just an utterly massive product, they have the resources to make the whole thing shine, even if people really don't want to work on it and need big bribes.

Re:Why modern software is slow by dev_tty01 on Friday September 30, 2022 @01:30AM (#33031339)
Casey wrote code and made it public. That is helping.

Regardless, this isn't about Casey. This is about MS releasing crap software. Text editors from 30 years ago were faster than WT. Something is horribly broken about the programmer's approach to writing code, or they are being horribly managed, or all of the above.

On the surface, it often feels like there is just an extreme lack of pride in workmanship. In code from lots of vendors I am constantly seeing interfaces with strange glaring issues, with bizarrely convoluted UI paths, with odd render bugs, etc... It feels like there is something unfortunate happening across the industry. Maybe I'm just a cranky older engineer, but seeing so many visual and functional failures being shipped makes me think the issue is far deeper than that.

Re:Why modern software is slow by acrispino on Thursday September 29, 2022 @10:13PM (#33030071)
Is releasing software for free under the GPL-2.0 a "dick move" ?
Re:Why modern software is slow by naikrovek on Thursday September 29, 2022 @10:20PM (#33030117)
> Is releasing software for free under the GPL-2.0 a "dick move" ?

it is when you know that Microsoft employees are forbidden from looking at GPL code because they may unconsciously recall it and use it in a Microsoft codebase.

Casey knew that at the time and admitted to licensing it GPL for that exact reason.

That is a “dick move” to me. maybe i’m wrong. you be the judge, i guess.

Re:Why modern software is slow by phenylene on Thursday September 29, 2022 @10:28PM (#33030157)
As you say, Casey is experienced and his code is valuable. MS should pay him if they want to look at his code! He said as much in his tweets… I mean, why should he be doing charity for MS by fixing their products for them?
Re:Why modern software is slow by naikrovek on Thursday September 29, 2022 @10:34PM (#33030194)
> Casey is experienced and his code is valuable. MS should pay him if they want to look at his code! He said as much in his tweets… I mean, why should he be doing charity for MS by fixing their products for them?

so difficult that he wrote it so he could demonstrate how easy it is.

he gladly showed the rest of us how to do it, and he intentionally took action which prevented anything he did from being used within Microsoft. Microsoft is so shitty because they don’t know [thing] so i’m going to show everyone but them how to do [thing].

he could have chosen to help. he chose to not help. he chose to complain and ridicule while intentionally avoiding doing anything to change the situation he was unhappy with.

Re:Why modern software is slow by yuzuquat on Thursday September 29, 2022 @11:26PM (#33030531)
Casey did choose to help - explaining the issue and potential solution on github. It was only after his solution was dismissed, then catching the microsoft engineers using his solution and making a blog post about it that he complained.
Re:Why modern software is slow by naikrovek on Friday September 30, 2022 @12:51AM (#33031113)
they didn't use his solution. they began to adopt his approach. began to. they are still not even close to done with it all, and the changes they would need to make to fully line up with Casey's approach can't happen because of other things the code does.

they were not caught using his solution. they published a blog entry describing that they were made aware of performance problems and they didn't mention him. it was rabid fans of Casey that started foaming at the mouth then, even though Casey publicly stated he didn't want or need credit, because the idea wasn't his to begin with.

Re:Why modern software is slow by ttybird2 on Friday September 30, 2022 @01:57AM (#33031471)
This version of events sounds too simplified

For anyone interested about the blog post drama check https://twitter.com/cmuratori/status/1522468481135902725 (hn discussion: https://news.ycombinator.com/item?id=31284419)

Personally I think that he owes them nothing, especially after the way he was treated in https://github.com/microsoft/terminal/issues/10362 so I can't comprehend statements which claim that he was an asshole for using GPL.

Re:Why modern software is slow by naikrovek on Friday September 30, 2022 @08:26AM (#33033944)
He owes them nothing, you're right. I made no claim that he does.

I'm saying he could have helped the situation, and he deliberately chose to not only avoid helping, but to hinder anyone at Microsoft who wanted to look at that code and contribute to Windows Terminal. That was a choice he made intentionally.

He could have taken the high road, there. He chose not to. It's his choice, don't get me wrong, he was well within his rights. I just disagree with that choice. that's why I call that a "dick move". And if you disagree with me, that's fine. "Dick move" means different things to different people at different times.

Re:Why modern software is slow by projektfu on Thursday September 29, 2022 @11:30PM (#33030563)
Microsoft hires consultants sometimes to better understand Windows. They hire people to come lecture to them about their own software. (I'm not making fun of them, it's a good idea.) If they can't pony up for a few consulting hours to help their developers learn how to write the software they should have written, that's really on them.
Re:Why modern software is slow by ripley12 on Friday September 30, 2022 @12:35AM (#33030993)
The way Casey handled this issue was... not good. He's been a jerk about it and generally dragged this whole dumb argument on way longer than needed (I can't believe we're still talking about it).

He was right, but he does not seem remotely pleasant to work with and has been remarkably adversarial. Hasn't exactly fostered a "let's hire him as a consultant" relationship.

Re:Why modern software is slow by DrammBA on Thursday September 29, 2022 @10:59PM (#33030363)
it's easy, so Microsoft should write it themselves or pay for it.
Re:Why modern software is slow by naikrovek on Friday September 30, 2022 @12:52AM (#33031127)
and now you've justified all non-free software.
Re:Why modern software is slow by matheusmoreira on Thursday September 29, 2022 @11:01PM (#33030380)
> Microsoft employees are forbidden from looking at GPL code because they may unconsciously recall it and use it in a Microsoft codebase

Isn't that exactly what Copilot does?

Re:Why modern software is slow by naikrovek on Thursday September 29, 2022 @11:17PM (#33030481)
this is a fucking meme at this point, the amount of assumption around this.

no, that is not what copilot does unless you check the box (or fail to uncheck the box) that allows exact matches of code from public repositories.

https://docs.github.com/en/copilot/configuring-github-copilo...

Re:Why modern software is slow by matheusmoreira on Thursday September 29, 2022 @11:25PM (#33030528)
If Copilot can look at GPL code and use that to synthesize new code, why can't a Microsoft employee?
Re:Why modern software is slow by giantrobot on Thursday September 29, 2022 @11:55PM (#33030714)
Because the lawyers haven't caught up with Copilot yet. Legal has been hounding developers for decades at this point.
Re:Why modern software is slow by andreime on Friday September 30, 2022 @12:58AM (#33031165)
bingo
Re:Why modern software is slow by naikrovek on Friday September 30, 2022 @08:38AM (#33034039)
eh not really. it's more about being able to reasonably testify in court that no GPL code was introduced into a codebase that they want to license with a non-GPL license and not be lying.
Re:Why modern software is slow by forgotpwd16 on Friday September 30, 2022 @04:15AM (#33032331)
How is it a meme? Copilot can throw verbatim licensed code.

https://twitter.com/mitsuhiko/status/1410886329924194309

Re:Why modern software is slow by naikrovek on Saturday October 01, 2022 @01:34AM (#33044175)
the meme is that you can turn off the verbatim stuff and no one ever remembers that they are told about this, or that it is in the documentation, or that poking around the copilot settings you will see the setting in question.

actual users of copilot seem to know this little bit of information; commenters who like to make comments about things they have never used always overlook details like this, and perpetually restate the things they learned about the topic months or years prior, even when those details were incorrect at the time, and are still incorrect today.

Re:Why modern software is slow by forgotpwd16 on Saturday October 01, 2022 @06:23AM (#33045484)
>the meme is that you can turn off the verbatim stuff

I see. But the setting (which surprises me that is opt-in) merely checks whether the output is an exact match and forces the system to produce a new output. The system can and does (as seen on the tweet) output verbatim code. So the question that parent commenter asked is legit.

Re:Why modern software is slow by mmsimanga on Friday September 30, 2022 @12:53AM (#33031134)
It is nice to be a dominant position like Microsoft because if they weren't they would have put aside their "feelings" and hired Casey to help them out. But they don't need to. Feelings of Microsoft seem more important than feelings of all their users who will just have to bear with it.
Re:Why modern software is slow by abigail95 on Friday September 30, 2022 @01:06AM (#33031209)
Come on man, the fact he's able to use GPL2 to annoy you is your problem. Just stop hitting yourself.

I will restate what many others have said here, Microsoft has used and interacted with GPL2 code longer than I have been alive. There is GPL2 licensed software in the Windows Store released by Microsoft.

Microsoft is the one doing the "dick move" by requiring special permission for new GPL2 interaction.

If Microsoft can interact with Linux, the biggest GPL2 project ever, they can interact with whatever Casey releases.

Re:Why modern software is slow by naikrovek on Friday September 30, 2022 @01:12AM (#33031265)
come on, man, the windows Terminal repo includes code that ships with windows and is not the windows Terminal application itself. cmd.exe lives in that repo, for example, along with some of the structure which supports all command-line applications on windows.

they can't adopt GPL in that repo and Microsoft has a very strong policy about segregation between developers who can read and write GPL code and those who cannot. those who cannot interact with GPL code get to work on stuff that ships with Windows, like the stuff in the Windows Terminal repo.

so, no. they can't look at GPL code, including Casey's refterm code. Casey knew all of this when he chose the GPL for that project.

Re:Why modern software is slow by ttybird2 on Friday September 30, 2022 @02:05AM (#33031518)
What the repo contains should not be very relevant. Proprietary and GPLed software can be in the same repo/disk/etc. We even see this in the official git repo with non-free firmware. Instead the concern is about what code the terminal application ends up using and what it links with. If his terminal did not link to any weird stuff then it is probably the case that they could avoid it as well. Also don't forget that the GPL contains an exception for system libraries specifically.

As for the segregation policy, it sounds like a self-imposed problem.

Re:Why modern software is slow by Firmwarrior on Friday September 30, 2022 @04:49AM (#33032539)
This argument is pointless. Microsoft doesn't need a YouTube video to teach its engineers how to do their jobs. They have tons of people in house who can code circles around any famous open source engineer, and who'd be happy to explain how to make cmd.exe great again internally

Like others have said, there are organizational issues causing the company's output to be embarrassing trash. Personally, I blame the Ballmer years of "unregretted attrition", but that's just my pet theory as to how it became a dysfunctional bureaucratic treacherous pirate's den

Re:Why modern software is slow by the_af on Thursday September 29, 2022 @11:59PM (#33030747)
> project layout is familiar for everyone working on it

Surely you understand why something like this may be genuinely beneficial for application software even when it's not needed for games?

Re:Why modern software is slow by naikrovek on Friday September 30, 2022 @12:55AM (#33031142)
not when it adds tens or hundreds of thousands of lines of code to a project, and makes understanding everything more difficult, because every single action the code takes is indirect and abstracted thrice.

it's stupid.

Re:Why modern software is slow by the_af on Friday September 30, 2022 @09:18AM (#33034462)
But that's not making the project layout more familiar for maintainers.

You are moving the goalposts.

Re:Why modern software is slow by naikrovek on Saturday October 01, 2022 @01:41AM (#33044213)
have you seen a large project grow ? it's all about organization so no one gets lost. none of it is needed if you have skilled developers, but skilled developers are expensive, so outside of silicon valley, companies hire shit developers and hope that they become semi-productive before their 5th anniversary.

the result is very large projects because no one knows how to write code, and tons of unnecessary abstraction and boilerplate stuck onto EVERYTHING.

just write what you need to solve the problem you need to solve, then stop.

Re:Why modern software is slow by kragen on Thursday September 29, 2022 @11:40PM (#33030633)
They can totally look at it, but if they copy it into Windows Terminal, they need to relicense Windows Terminal under the GPL. That would be a great outcome for everyone. Microsoft is already shipping Linux under the GPL2 as WSL2 so this shouldn't be unthinkable.

Also, though, it does not require 25+ years of game development experience to figure out that you can write a non-laggy terminal emulator, which should be obvious because people have been building non-laggy terminal emulators since at least 01974 and people routinely watch 1080p videos at 60 fps on modern laptops and even modern hand computers.

We had terminal emulators with acceptable, even snappy, performance on X-Windows when I started using it in 01993. In 01994 I would commonly use an IRIS Indigo, which had a 150 MHz R4400, which was not superscalar, so it was maybe capable of 150 MIPS, or 300 MIPS if you count floating-point too. I preferred using it instead of the X terminals because it was faster. I'm typing this on an obsolete laptop whose CPU averages about 100 times faster than that. It's immediately obvious to the most casual observer that there is no excuse for software on this laptop to flub UI tasks the Indigo handled with ease.

The VT50 https://en.wikipedia.org/wiki/VT50 was released in 01974, and its microprogram emulated a Teletype with added features. (See my comment at https://news.ycombinator.com/item?id=32547666.) A service manual for the 01975 version, the VT52, is at https://news.ycombinator.com/item?id=32547666. It had 60 frames per second (in the US), 240 scan lines per frame, 80 characters per scan line (at 15.36 kHz), and I think 8 pixels per character (in each scan line), one of which was always blank. So its output shift register ("VSR") operated at 9.8 MHz, or actually a little bit faster because of the 10-μs HBI, during which it checked the keyboard. Its microprogram, which had to load the appropriate 7 bits into the VSR 80 times per scan line (as well as processing escape sequences and printable characters during, I think, the VBI), had a 1.3 μs instruction cycle time (770 MHz), divided into 18 72-ns clock cycles (13.824 MHz) during which it did different things.

So I think that in most 72-ns clock cycles about a couple of dozen flip-flops would change state.

This laptop typically executes about 2400 CPU instructions in every 72-ns tick of the VT52's clock, 600 per core. You could compile an RTL-level logic simulation of the VT52 into C and compile it with a C compiler, and it would run faster than the original VT52.

But that would be sort of stupid because you have a framebuffer and a GPU with texture-mapping units; your CPU doesn't actually have to generate pixels one at a time to keep the screen refreshed because you have hardware to do that for you. A 1920×1080 video at 60 frames per second is displaying 124 million new pixels per second, which it has to get by decoding H.264 or H.265 or something. That's a bit over 1.5 million VT52 characters per second. But when you're displaying characters on a terminal that isn't very useful because people can only read about 30 characters per second; even updating a full-page 80×66 display at 60 frames per second is only 0.3 million characters per second.

In most cases the computation required to process a character is to verify that it's a printable plain ASCII character, update the screen image, and update the cursor position. Updating the screen image might involve blitting some texture data or, as in Muratori's refterm, updating a glyph index that gets consulted by a shader to figure out what texture data to draw when the time comes to render a frame. We're talking about an amount of computation that's small compared to a typical C subroutine call and return.

Re:Why modern software is slow by naikrovek on Friday September 30, 2022 @01:03AM (#33031185)
> They can totally look at it, but if they copy it into Windows Terminal, they need to relicense Windows Terminal under the GPL. That would be a great outcome for everyone.

no! it would not! the GPL is a truly awful license. "freedom" my white butt. it's a list of requirements, all of which restrict the freedoms and abilities of those who utilize it.

about rendering:

I'm not trying to say that it's hard. I'm trying to say that they believed they knew how to do it, when in reality they did not.

THAT'S ALL.

Everyone is laser focused on the details of what I am saying and completely missing the point of what I am saying, or trying to say. I am apparently speaking a language that is close to English but not actually English.

Re:Why modern software is slow by salawat on Friday September 30, 2022 @10:07AM (#33035009)
>no! it would not! the GPL is a truly awful license. "freedom" my white butt. it's a list of requirements, all of which restrict the freedoms and abilities of those who utilize it.

The only freedom the GPL restricts is the freedom to maintain a captive audience in a state of information asymmetry guaranteed helplessness.

You're not making a good case for yourself here.

Re:Why modern software is slow by naikrovek on Saturday October 01, 2022 @01:46AM (#33044235)
GPL forces code others write for your project to also be GPL. that is a loss of freedom for that contributor.

if I license something with the MIT license, anyone can use it for any purpose, and they can take my code with their modifications private if they want, meaning those entities are free to do what they want, and the code I released is still freely available just like it was before. I lose nothing, and no freedoms were taken from anyone who uses my code.

Re:Why modern software is slow by kragen on Saturday October 01, 2022 @02:10PM (#33048607)
Windows Terminal isn't licensed under any of the various MIT licenses, though; it's licensed under the Windows EULA. The Windows EULA forces code others write for Windows Terminal to never exist in the first place, and it forces the people on the Windows Terminal team to lose access to their own code if they leave Microsoft. So moving Windows Terminal to the GPL2 would be a gain of freedom for all those people. Only Satya Nadella would suffer a loss of freedom.

That sort of simple numerical counting isn't enough for an ethical argument, of course. If my house is converted to a public park, then everyone gains the freedom to drink beer in it, or at least everyone in Buenos Aires does, and only I lose any freedom, like the freedom to sleep in a dry bed when it's raining without raucous beer-drinkers guffawing all around me. But this is still a net loss because the benefits to everyone else are not as important as the loss to me.

In the Windows Terminal case, the situation is the other way around: Nadella would suffer a loss of freedom that affects him only in a de minimis way, while everyone else would gain substantially.

Re:Why modern software is slow by sophacles on Friday September 30, 2022 @02:36PM (#33038812)
> Everyone is laser focused on the details of what I am saying and completely missing the point of what I am saying, or trying to say. I am apparently speaking a language that is close to English but not actually English.

Have you considered that people are disagreeing with you because you are wrong rather than because they don't understand you?

Re:Why modern software is slow by kragen on Friday September 30, 2022 @04:37PM (#33040477)
Well, it's true that I spent a lot of words attacking the claim that making a terminal emulator snappy (in the usual case, maybe not Zalgo cases) would be difficult, and it is also true that naikrovek didn't actually make that claim. Rather, they claimed that the Windows Terminal team didn't know how to do it. Which, I mean, maybe that's true, but it isn't that hard to figure out. I think it's more accurate that they didn't bother and made up rationalizations for their shitty software after the fact.
Re:Why modern software is slow by kragen on Friday September 30, 2022 @01:06AM (#33031206)
Oh, well, I agree that the Windows Terminal team overestimated their own competence. I just think they had to argue some pretty obviously implausible positions in order to do so. You have to dumb pretty hard to start believing that a 3 GHz 2-core superscalar i7 with AVX256, 24 MB of L3 cache, and a SIMT GPU can't handle the load of emulating a VT100.

And having the Windows Terminal licensed under the GPL instead of a Microsoft EULA would strictly increase the freedoms and abilities of its users: they could still legally do all the things with Windows Terminal they do now, plus lots of new things as well. Opt out of undesired updates, for example. Even the Windows Terminal team would have more freedom that way: they could go work at a different employer and keep hacking on the code they wrote as part of Windows Terminal.

Re:Why modern software is slow by nyanpasu64 on Thursday September 29, 2022 @09:43PM (#33029849)
I've had the misfortune of watching Windows 11's Notepad crash on opening a specific text file I was taking notes in.
Re:Why modern software is slow by abruzzi on Friday September 30, 2022 @12:03AM (#33030780)
in fairness the old XP/Server 2003 notepad would frequently freak out on me and suddenly remove all <CR> (or <LF>, I don't really know) from a file I was editing (not a unix or mac generated file, so it was not a <CR><LF> issue.) That would force me to quit and reload the file and start my edits over again. This was almost always on servers, so I never bothered to find a fix or workaround, but it made me never trust notepad. So old notepad sucked, and apparently new notepad sucks.
Re:Why modern software is slow by nyanpasu64 on Friday September 30, 2022 @02:12AM (#33031558)
Windows 10 notepad was good for a brief glorious period, they fixed mixing status bar with line wrap, they made files with LF only render as multiple lines (don't know what happens when you save them). I have no plans to move off Ameliorated 10 to Windows 11 with their botched Notepad, slow store apps, and reduced ability to install explorer and taskbar customizations (though 7 already required patching out signature checks, and 8 through 10 progressively broke Aero Glass and widget controls patching).
Re:Why modern software is slow by newZWhoDis on Thursday September 29, 2022 @11:39PM (#33030620)
That was just the malware owning your system
Re:Why modern software is slow by nyanpasu64 on Friday September 30, 2022 @02:14AM (#33031574)
To be fair, this HP consumer laptops did come with a lot of preinstalled bloatware malware, some which even lacked uninstallers. But IIRC the Notepad crash persisted after a so-called clean Windows reinstall from Settings, which removed most bloatware apps but not advertising shortcuts in the Start menu and etc.
Re:Why modern software is slow by leeoniya on Thursday September 29, 2022 @10:30PM (#33030172)
i had the same experience after they revamped the Windows Calculator. it went from instantaneous to ~2s startup with UI jank.

(highly recommend Notepad3)

i don't miss the ceremony of trying to debloat Windows after every unstoppable auto-update; what a goddamn nightmare that was.

now permanently on EndeavourOS KDE/Plasma and everything "just works, very fast". i do wish that Affinity products where available for Linux, i dont think you can run them with Proton/Wine :(

Re:Why modern software is slow by jiggawatts on Thursday September 29, 2022 @11:09PM (#33030423)
I wrote a rant about the Windows Calculator change as well. They're loading things like Windows 10 Hello for Business login recovery assistant modules, NVIDIA telemetry, creating threadpools, writing multiple log files, and on and on.

If you asked me what a calculator app "should" do, none of those would ever enter into my brain.

Re:Why modern software is slow by yyyk on Thursday September 29, 2022 @11:14PM (#33030459)
I didn't get a chance to use the new calculator yet (I usually use Linux. Windows 11 changes make it unlikely I'll 'upgrade' a VM). Is it this one?

https://github.com/Microsoft/calculator

Re:Why modern software is slow by userbinator on Thursday September 29, 2022 @11:40PM (#33030629)
Yes, that's the horrible telemetry-infested (yes, really!) UWP monstrosity that MS was proud to open-source instead of the good old classic one (whose source got leaked a long time ago...)

https://news.ycombinator.com/item?id=19321217

https://news.ycombinator.com/item?id=26579481

Re:Why modern software is slow by user3939382 on Thursday September 29, 2022 @09:45PM (#33029867)
Someone once explained that MS hires a lot of short-term contractors who then don't own the consequences of the code they write. I wonder if this is still true and responsible for this.
Re:Why modern software is slow by deepsun on Thursday September 29, 2022 @10:01PM (#33029974)
Same thing in other faang companies, even with employees, who got the promotion and got hunting for another one. You won't get promoted for supporting an existing project.
Re:Why modern software is slow by sgerenser on Friday September 30, 2022 @08:38AM (#33034040)
Probably not. Contractors tend to be hired for a lot for non engineering tasks (admin, recruiting, facilities) and the sometimes to fill out a dev team with specific skill sets or to cover some grunt work. In my experience on dev teams (in the US at least) FTEs outnumber contractors by at least 8:1, so I’d be surprised if much was done on Windows Terminal by contractors. (I work for Microsoft but not on anything even adjacent to Windows Terminal).
Re:Why modern software is slow by sixothree on Thursday September 29, 2022 @09:13PM (#33029618)
Nothing annoys me more than having to use notepad when remoted into a server. It is the biggest pile of crap and having something even halfway competent included in a very expensive operating system would be a baseline I could accept.
Re:Why modern software is slow by hackerlight on Friday September 30, 2022 @12:27AM (#33030933)
> It is very visibly laggy for basic actions such as opening menus or scrolling through text.

Some (not all) of the lag in Windows is on purpose by the UI engineers. Google "disable windows animation" for a starting point on how to fix it.

Re:Why modern software is slow by moralestapia on Friday September 30, 2022 @01:06AM (#33031207)
>Casey Muratori excoriated the Windows Terminal dev team for failing to achieve a consistent 60 fps

Oh I remember that!

He even got lectured by some expert nitwits at MS which were making dozens of arguments about how it was allegedly impossible to create a fast terminal (on modern machines, most of them with GPUs in the TFLOPS range, LOL).

I have no idea why those "engineers" weren't fired on the spot.

Re:Why modern software is slow by WalterBright on Thursday September 29, 2022 @11:52PM (#33030704)
My text editor (a version of MicroEmacs) is 55Kb in size, and opens instantly. Of course, it was designed to be performant under DOS.
Re:Why modern software is slow by Stratoscope on Friday September 30, 2022 @12:30AM (#33030960)
It's not just the slowness, but the loss of basic functionality too.

Keyboard shortcuts, for example.

On my machine, Notepad still seems to have the traditional keyboard shortcuts. But in Paint they are completely missing.

Alt-F-A? No Save As dialog for you.

Close the app with unsaved changes? You get something like the traditional "do you want to save your work?" dialog, but the left and right arrow keys do not work in the dialog. And you can't type N or Alt+N for "Don't save".

These do work in the latest Notepad on my machine.

These keyboard shortcuts used to work in every Windows app, and especially in all the standard Microsoft apps. Now it seems to depend on whether the individual developer knows about them.

Re:Why modern software is slow by joe_the_user on Thursday September 29, 2022 @11:20PM (#33030497)
Yeah, I'm using Windows Home at the house of the person I'm working for and It's remarkable how much worse it is than either my Linux laptop or Windows of ten years ago.

Media Player has apparently been replaced by "DVD Player(free)" which is not only intentionally crippled (you have to use the keyboard to access the DVD menu and if the Menu begin with no item having focus, you're SOL) but also crashes 75% of the time upon attempting to play the disk (I spent five starting the thing until I installed VLC).

The entire scheme is apparently to try to leverage the monopoly MS has on low-end systems.

Re:Why modern software is slow by thrdbndndn on Thursday September 29, 2022 @11:03PM (#33030392)
> force-updated my Notepad.exe to the new modern UI version.

> opening a 300 MB log file takes a solid minute of time

But notepad.exe is always slow when opening large files. If anything I think it's better now than it was in XP/7.

Re:Why modern software is slow by userbinator on Thursday September 29, 2022 @11:42PM (#33030647)
If anything I think it's better now than it was in XP/7.

Unless you're using the same hardware, that's probably all hardware improvement.

Re:Why modern software is slow by thefz on Friday September 30, 2022 @03:43AM (#33032121)
> You have to be spectacularly bad at programming to make something so basic so slow in 2022 on a very high-end gaming computer.

With all the telemetry going on in the background, Windows is worse every day. I tried Windows 11 and was amazed at how it completely nullified having a top-tier mobile i7 paired with 32GB RAM.

Take a look at how much a modern install of Windows is thrashing your drive. It's scanning everything, all the time.

Re:Why modern software is slow by johnfn on Friday September 30, 2022 @12:33AM (#33030978)
Casey Muratori is an extremely proficient programmer. Windows probably employs a couple of new grads to work on the terminal. (Even if they aren't, it'd be hard to come close to the breadth of experience that Casey has.) I never understood why this is a surprise at all - "Casey Muratori excoriated the Windows Terminal" basically translates to "L8 smarter than L2".
Re:Why modern software is slow by jiggawatts on Friday September 30, 2022 @12:52AM (#33031128)
Everyone has somehow internalised the "fact" that all performance optimisation is a black art that only "hugely experienced" devs can possibly know.

I'll give you an example.

I've seen developers and DBAs working on databases simply create new indexes on the fly to fix some performance issue. It takes ten seconds, it's fairly safe, and it is relatively easy to gauge the effect. "Before minutes, after milliseconds". Done.

I've seen other places where merely suggesting the use of an index -- no matter how beneficial, trivial, or safe -- resulted in everyone foaming at the mouth in abject terror. Wailing and gnashing of teeth. "How dare you suggest that we touch the mystical black box!? Begone with you, foul wizard!"

This is what I saw with the Casey Muratori vs Windows Terminal team arguments.

Everyone acts like Casey pulled out some dark tome only the most grey haired wizards are allowed to see and spoke secrets that Microsoft isn't even allowed to legally hear.

Do you actually know what he suggested?

Make a grid, just a 2D array. Put the characters in them.

Use the characters to look up small images of individual characters in another grid.

If the other grid is missing a characters, find an empty spot an replace it with the missing character image. (If the second grid is bigger than the first one, this is always possible.)

That's... it. Just array lookups, 2D images, and a hashtable.

This is child's play not wizardry.

Re:Why modern software is slow by johnfn on Friday September 30, 2022 @02:05AM (#33031514)
> That's... it. Just array lookups, 2D images, and a hashtable.

No, that's not all that Casey did. I mean, perhaps from a very reductionist point of view it is, yes, but there's a thousand ways to implement "array lookups, 2D images and a hashtable" that are less efficient than the way that Casey did it (and probably most would be less efficient than the MS team as well...) Do you know the ins and outs of Direct2D in order to write all that out efficiently? I certainly don't.

Re:Why modern software is slow by jiggawatts on Friday September 30, 2022 @07:54AM (#33033677)
Sigh...

Casey demonstrated... and it ought to be obvious... that the "ins-and-outs" of Direct2D don't matter.

If you actually bother to cache the glyphs into sprites, then Direct2D can be absurdly slow (it isn't) and still get something like 1000 fps.

Your comment is almost a parody of what went down.

How can you not see that generating a 16x20 pixel image can't possibly be the bottleneck on a modern PC unless you're doing something spectacularly wrong!?

Re:Why modern software is slow by johnfn on Friday September 30, 2022 @12:50PM (#33037250)
> Casey demonstrated... and it ought to be obvious... that the "ins-and-outs" of Direct2D don't matter.

I don't know what this means. Casey clearly uses Direct2D in his repo. If he were to demonstrate that Direct2D doesn't matter, he shouldn't have used it.

> Your comment is almost a parody of what went down.

There are thousands of programmers out there who haven't built a terminal as fast as RefTerm, and then there's Casey Muratori. If a hundred more Refterms show up tomorrow, I'll happily change my mind. Heck, you can even prove me wrong by coding one up yourself, if you'd like!

Re:Why modern software is slow by jiggawatts on Saturday October 01, 2022 @12:06AM (#33043780)
He artificially constrained refterm to use DirectText specifically, because that's what the Windows Terminal team was using, and Casey wanted to prove that this could be made performant. The specific argument the Microsoft guys were making was that DirectText/Direct2D had inherent limitations that fundamentally prevented certain scenarios running fast, such as a mix of many different colours. Casey proved them wrong, but to do that he had to use the same underlying libraries so as not to be seen as somehow "cheating".
Re:Why modern software is slow by dev_tty01 on Friday September 30, 2022 @01:45AM (#33031408)
Well said. I also like your assertion that performance optimization is believed to be a black art. As you say, it is not. In fact, there are much better tools available for performance monitoring today than there ever have been. How many programmers actually open those tools and look for performance bottlenecks? I would guess not too many, at least based on what we are seeing in shipping products.
Re:Why modern software is slow by jiggawatts on Friday September 30, 2022 @08:04AM (#33033752)
Story time!

When I was something like 23 years old, my boss told me to go help optimise IIS performance at a large dev shop.

Think about how absurd it sounds: A junior tech with essentially no knowledge of IIS performance tuning doing consulting to an entire company of 30-40 year old experienced developers on the finer points of web serving.

I turned up, and it turned out that these guys were writing what seemed like a trivial web app, but if two people submitted a form simultaneously then the page would take a minute to submit.

A minute you ask? I timed it: 60 seconds exactly, plus or minus a few hundred milliseconds.

That's a lock timeout.

I asked to talk to the database team. They told me the scope of works was to look at IIS and "tune it". To put things in perspective, they were using the largest server I had ever seen (8 sockets!) and it couldn't handle two users.

"Maybe we need a 16-socket server, what do you thinkg?"

I told them... no-no-no-no, I need to talk to the DBA team, just trust me.

After some negotiation, I finally sat down next to the "senior" DBA and asked him what database engine he was using.

"Sybase."

Shit. I had heard of Sybase, but had never used it. I had a smidge of experience with SQL Server, and I had heard that Microsoft based it off the Sybase code that they had licensed.

In a mild panic I asked him if Sybase had any performance analyzer tool or somesuch?

"No."

Err... that's not good. Now in a cold sweat, I asked to borrow his mouse for a second so I could click through his Start menu, where I found the Sybase folder, with a "Profiler" tool that was a carbon copy of the "SQL Server Profiler", except for the icon and some color schemes.

It took about 10 minutes to repro the scenario and demonstrate that as expected, the codebase was Deadlock City and the mysterious 1 minute "performance issues" were in fact caused by 60.0 second timeouts as I had guessed.

When I walked away from that two storey building full of "professional" developers, I had a wide-eyed look on my face wondering why literally nobody in the entire database team was even aware of the existence of the database profiler tool... which was in their Start menu the whole time.

Re:Why modern software is slow by Falkon1313 on Saturday October 01, 2022 @08:47AM (#33046204)
Really?

Many of us discovered around the age or 13 or 14 that POKE #B8000 plus a little arithmetic was significantly faster than using OS calls to write text to the screen. We were wrapping those in functions, inlining ASM, and building text-mode UIs as teenagers - not as long-time professionals, not college grads, and without all the information available on the modern internet.

Over the next few years, as graphical stuff became more common, we were trying different algorithms to optimize polygon fills, mouse drivers, custom fonts, etc. That was a part-time hobby for teenagers. Did not require greybeard gurus with lifetime achievement awards and college degrees and the entire internet of information always available.

It was just the basics, the fundamentals, a few decades ago.

Re:Why modern software is slow by ridgered4 on Friday September 30, 2022 @10:29AM (#33035344)
I'm of the opinion that all the telemetry is used to identify the remaining parts of Windows users can still rely upon and so they can be 'improved' by a PM looking to redirect an existing user base onto some new-crap.

In this way, users have nowhere to hide. Any refuge from the new UI changes will be tracked, identified and targeted for termination.

Re:Why modern software is slow by smegsicle on Thursday September 29, 2022 @09:21PM (#33029684)
> excoriated

look at that- with so many wonderful words to chose from, why do people fall back on 'decimated' ?

Re:Why modern software is slow by pessimizer on Thursday September 29, 2022 @09:30PM (#33029753)
To excoriate means to condemn. to decimate means to heavily damage. They are not synonyms.
Re:Why modern software is slow by danielheath on Thursday September 29, 2022 @09:46PM (#33029871)
The Roman punishment of “decimation” was to make each ten-man team in an army murder one of their number (the whole team being killed if they refused).

Practically “Saw”, in real life.

Re:Why modern software is slow by smegsicle on Thursday September 29, 2022 @10:10PM (#33030049)
crap i thought it meant 'skin alive'
Re:Why modern software is slow by ShroudedNight on Friday September 30, 2022 @12:19AM (#33030884)
It apparently does have continued use as an approximate synonym to chafe or flay when used in the appropriate context:

https://www.merriam-webster.com/dictionary/excoriate

https://www.collinsdictionary.com/dictionary/english/excoria...

Re:Why modern software is slow by hnick on Thursday September 29, 2022 @11:57PM (#33030730)
That would be flaying. But in a medical context I think excoriating is skin removal... it's just not being used literally here.
Re:Why modern software is slow by stjohnswarts on Friday September 30, 2022 @12:52AM (#33031123)
Just install notepad++ and associate it with the files you want, it will open instantly and has 100x the capability of notepad, even if you don't need it.
Re:Why modern software is slow by cholantesh on Friday September 30, 2022 @12:40AM (#33031030)
I liked the modern Notepad UI when I tried it, but to be fair I didn't use it for long, having discovered a regedit fix to replace it with N++.
Re:Why modern software is slow by ojr on Friday September 30, 2022 @12:23AM (#33030907)
“electron application”, so many smart people working on optimizing javascript, simplicity wins again
Re:Why modern software is slow by ffhhj on Thursday September 29, 2022 @09:23PM (#33029701)
Clever way to push users from Notepad into OneNote, ruin their previous experience.
Re:Why modern software is slow by samstave on Friday September 30, 2022 @12:48AM (#33031086)
why the fn heck does "notepad" even need an 'update'? An update to do what.

>c:\copy con FILE.txt

F6

Re:Why modern software is slow by robertsdionne on Thursday September 29, 2022 @09:24PM (#33029706)
notepad dot electron
Re:Why modern software is slow by jiggawatts on Thursday September 29, 2022 @09:27PM (#33029736)
The new Notepad uses XAML, probably using Win UI 2 or 3.

VS Code, which is an Electron application, opens text files something like 20 times faster than the new Notepad.

Whoever wrote and shipped the new Notepad should feel ashamed at their failure as a professional software engineer.

This isn't some Github toy project. It's being forced onto billions of users, without the slightest bit of quality assurance or adherence to the basic practices of the art.

Re:Why modern software is slow by abraae on Thursday September 29, 2022 @09:31PM (#33029758)
> Whoever wrote and shipped the new Notepad should feel ashamed at their failure as a professional software engineer.

Steady on old chap. Who's to say the hapless developer isn't embarrassed about things themselves, but is prevented from doing the right thing by some management edict, ancient process etc.

My money's on that rather than one person's incompetence.

Re:Why modern software is slow by jiggawatts on Thursday September 29, 2022 @11:32PM (#33030582)
I would absolutely refuse to ship anything of this piss-poor quality. I would refuse to even participate if I wasn't allowed to achieve at least the existing tool's quality level.

In fact, I have done similar things.

For example, I was asked to develop a protocol-shim for an authentication system used by tens of thousands of people accessing one of the largest SAP systems in the country. I wrote the code, tested it, and said to the PM that the only thing missing for go-live is some HTTPS certificates to make it secure.

He asked me to go to production anyway to meet his deadline, and that the certificates will be fixed up later.

I straight up told him: "No."

The look on his face was hilarious. He called my boss, my boss' boss, and up.

I told all of them: "No."

We waited for the certificates to be issued.

Re:Why modern software is slow by 8note on Thursday September 29, 2022 @10:11PM (#33030062)
That's a difference between developer and engineer. It's part of an engineer's job to not put out the garbage required by bad management, and instead signal to regulatory agents and media that management is attempting to say, put changes into a bridge that will cause it to call down, killing the first people to step on it
Re:Why modern software is slow by anthony_d on Thursday September 29, 2022 @10:21PM (#33030124)
I’m ready to agree with you as long as you understand software engineering isn’t a thing.
Re:Why modern software is slow by umanwizard on Friday September 30, 2022 @10:42AM (#33035544)
Your fantasy of how engineering is supposed to work does not correspond to the reality of the term “software engineer”, at least in the US.
Re:Why modern software is slow by leetcrew on Thursday September 29, 2022 @10:37PM (#33030214)
we're talking about the default text editor on an OS that supports endless alternatives. yes, it's an embarrassment, but (approximately) no one is dying because notepad is janky.
Re:Why modern software is slow by jiggawatts on Thursday September 29, 2022 @11:27PM (#33030543)
There can be late night disaster recovery scenarios where logging into an under-resourced virtual machine and using Notepad to view a huge log file is the difference between success and failure. Failure can mean huge companies going under, life & death, suicides, end of careers, you name it.

The new Notepad is not fit-for-purpose. You cannot use it to open a file several gigabytes in size. It'll just die, take minutes, fill memory, and even if it opens successfully, it'll be unusably slow.

It's the Windows equivalent of 'vi'. It has to work, all of the time.

Re:Why modern software is slow by kajaktum on Friday September 30, 2022 @12:16AM (#33030866)
> No one is dying

I hate this argument so much

It's like being perfectly fine with a universe with as much suffering as long as no one is dying. I am exaggerating of course, but why inflict this suffering to a BILLION people? I feel bad when I annoy someone for a few seconds (like struggling to open a door) and yet people are perfectly nonchalant to create ecosystem that billions of people use everyday for the next decade at least.

Re:Why modern software is slow by dev_tty01 on Friday September 30, 2022 @01:52AM (#33031443)
>no one is dying

Are you sure?

---- "Larry started to explain about some of the places where he thought that he could improve things, but Steve wasn't interested. He continued, "You know, I've been thinking about it. How many people are going to be using the Macintosh? A million? No, more than that. In a few years, I bet five million people will be booting up their Macintoshes at least once a day."

"Well, let's say you can shave 10 seconds off of the boot time. Multiply that by five million users and thats 50 million seconds, every single day. Over a year, that's probably dozens of lifetimes. So if you make it boot ten seconds faster, you've saved a dozen lives. That's really worth it, don't you think?" --- https://www.folklore.org/StoryView.py?project=Macintosh&stor...

Re:Why modern software is slow by donatj on Thursday September 29, 2022 @09:39PM (#33029817)
You put up the stink of your life or you quit. Anything less and you are a coward and shouldn't work in the industry.
Re:Why modern software is slow by __ryan__ on Thursday September 29, 2022 @09:52PM (#33029915)
In this hypothetical, the individual is choosing between possible homelessness and making Microsoft look bad by following Microsoft’s orders and releasing bad software.

And they should choose possible homelessness?

Re:Why modern software is slow by userbinator on Thursday September 29, 2022 @10:03PM (#33029991)
"possible homelessness"? For someone who at least met the bar for getting hired by Microsoft? On the contrary, I think that individual would easily find a job somewhere else.
Re:Why modern software is slow by j-bos on Thursday September 29, 2022 @10:24PM (#33030140)
Who are these software engineer's working at Microsoft in the year 2022 at risk of homlessness?
Re:Why modern software is slow by __ryan__ on Thursday September 29, 2022 @10:41PM (#33030243)
In this hypothetical, the same person who is a “failure as a software engineer”, according to a parent commenter.
Re:Why modern software is slow by Dylan16807 on Thursday September 29, 2022 @10:53PM (#33030332)
You mixed up two scenarios.

The original claim was that they were a failure.

The hypothetical is that they are not a failure, but are "prevented from doing the right thing". In the hypothetical, they should quit and get a new job.

Re:Why modern software is slow by GauntletWizard on Thursday September 29, 2022 @09:59PM (#33029967)
Cowards ship. Shippers get raises and promotions. Software quality declines.
Re:Why modern software is slow by ripley12 on Friday September 30, 2022 @12:36AM (#33031000)
> without the slightest bit of quality assurance or adherence to the basic practices of the art.

You really don't do your argument any favours with exaggerations like this.

Re:Why modern software is slow by naikrovek on Thursday September 29, 2022 @10:14PM (#33030078)
> It's being forced onto billions of users, without the slightest bit of quality assurance or adherence to the basic practices of the art.

whoa there, you don’t know that. you think you do because you’re getting a ton of upvotes and you’re leaning into the feeling you had when you wrote that comment — the anti-Microsoft comment on a site known for its anti-microsoft comments.

if you don’t work at Microsoft, you have very little hope of understanding the motivations of a team, a product manager, or even a single developer within Microsoft. there’s a lot more there than meets the eye, just like there is at any huge company.

Re:Why modern software is slow by jiggawatts on Thursday September 29, 2022 @11:43PM (#33030650)
Famously, Microsoft fired their entire QA team and now relies only on telemetry. They similarly fired their technical writing team, and now beg the public to write their documentation through pull-requests.

I do know what Microsoft is or isn't doing.

The evidence is in the pudding: opening a large text file in the new Notepad is orders of magnitude slower than any other editor on my system. This is a common failure mode that is trivially caught by testing. It's a well understood problem space, much like how databases "get slower" as the data volume increases, but the well understood solution is to use indexing to make this not occur.

The fact that the Notepad team spent months (years?) working on a trivial text editor and never tested it with text files speaks volumes.

If they had ever opened a large text file, they would have immediately noticed that a mistake had been made. Much like how if a database developer runs a query over large amounts of data, the missing indexes are immediately obvious.

It takes a minute for Notepad to open a file that isn't even "huge".

A minute isn't slow. It's broken.

They shipped broken software to the public, at the scale of hundreds of millions or even billions of users.

> understanding the motivations of a team, a product manager, or even a single developer within Microsoft.

Clearly, performance and quality are never motivations at Microsoft.

Re:Why modern software is slow by forgotpwd16 on Friday September 30, 2022 @04:04AM (#33032255)
>if you don’t work at Microsoft, you have very little hope of understanding the motivations of a team, a product manager, or even a single developer within Microsoft

Their motivations are irrelevant for an end-user. Their results are.

Re:Why modern software is slow by naikrovek on Friday September 30, 2022 @08:06AM (#33033765)
It's important to understand that Microsoft are staffed by people just like us, trying to make things better. Except Microsoft get shit on daily simply because they are Microsoft. That stuff adds up and gets to people who work on things.

If you don't think it should, I remind you that you can't take the humanity out of a human.

Re:Why modern software is slow by nik282000 on Thursday September 29, 2022 @10:57PM (#33030351)
> Windows force-updated my

If you don't like how your OS works, pick a different one.

Re:Why modern software is slow by mike741 on Thursday September 29, 2022 @11:27PM (#33030541)
There are also bash scripts to stop Windows from force-updating. Its a lot less work than switching to an entirely new OS and doesn't require giving up video games. But if someone can afford to learn Linux, or any OS that doesn't force updates, then its probably better to do so in the long run.
Re:Why modern software is slow by nik282000 on Thursday September 29, 2022 @11:37PM (#33030603)
With Proton you can run a hell of a lot of your Steam library. It's far enough along that you don't need to be terminal guru any more.
Re:Why modern software is slow by mike741 on Friday September 30, 2022 @12:39AM (#33031022)
I've heard of Proton a few times but last time I checked only 600 out of Steam's 50,000+ games are compatible with it. Not bad by any means but using an older Windows version still seems to offer more at the moment.
Re:Why modern software is slow by thefz on Friday September 30, 2022 @03:48AM (#33032153)
I have 400+ titles in my Steam library and play most of them on a Linux machine. Nowadays it's very rare to find one that does not work out of the box, and in those rare cases, there's always glorious eggroll to try. Check by yourself on protondb.
Re:Why modern software is slow by nik282000 on Friday September 30, 2022 @12:45AM (#33031065)
Using an older Windows version to run Steam is a really bad idea. Steam requires an internet connection, old versions of Windows, are by definition, not up to date.
Re:Why modern software is slow by mike741 on Friday September 30, 2022 @03:34AM (#33032054)
If the first 19,000 updates weren't secure, I don't have much confidence the next one will be. Is Linux any different in this regard?
Re:Why modern software is slow by lmm on Thursday September 29, 2022 @11:02PM (#33030386)
It's a monopoly.
Re:Why modern software is slow by nik282000 on Thursday September 29, 2022 @11:11PM (#33030439)
Unless you are in a REALLY specific field (programming PLCs, interacting with weird hardware), everything is in a browser, an office suite or dev. You can stay corporate and run MacOS, or you could run Linux or BSD.