461–470 of 558 posts
Earlier quoted context omitted.
I liked having a simple plain text editor
I can't believe I'm saying this on hackernews of all places... Markdown *is* plain text.
Earlier quoted context omitted.
This is my favorite part of this story. Do you want remote code execution? Because [fixing things that aren't broken] is how you get remote code execution.
I thought it is by introducing an RCE vulnerability that you get an RCE vulnerability. I'm being facetious of course, but this recent rhetorical trend of people confidently vouching for "pet" in "pet vs. cattle" is not a sustainable decision, even if it's admittedly plain practical on the short to medium run, or in given contexts even longer. It's just a dangerous and irresponsible lesson to blindly repeat I think. C…
Earlier quoted context omitted.
It's been so weird to watch over the decades as team sizes, budgets, and timelines have exploded even as we've abandoned once-normal things like native GUI applications as too hard in favor of "more efficient" webshit... even as the aforementioned stuff with growing team sizes, budgets, and timelines have happened.
What's weird is that AI is supposed to make development easy enough that native applications are just as fast to build than web apps Somehow in this timeline AI can only be used to make things worse and sloppier
I don't think that was ever not the case. The popular UI toolkits include a WYSIWYG editor where you can pick widgets and just put them where you want them with the mouse. Sure, that might not be what developers like to use, but invoking a widget constructor is not that hard and gets you a lot more functionality out of the box, that you would need to implement in JS.
Cross-platform GUIs is also more of a problem of theory. It used to be a big thing, because the GUIs don't look native to the platform, but that concern has gone out of the window with websites now. Win32 programs run with WINE, which I guess is not desirable for deploying to ordinary users, but I guess the people who write for Win32 generally do not care much about porting their programs outside of MS Windows. GTK+ and Qt both run on MS Windows. TCL/Tk comes built-in with Python and looks native on MS Windows.
Encoding algorithms is not that much different across C-like (Algol-derived) languages. Registering callbacks also looks kind of the same. I guess what makes a real difference is the ubiquity of async in JS, where you would use threads more in native applications.
I think what is an actual difference is the mindset around styling and layout. This is something that you actually need to adapt. CSS is more declarative, much like writing constraints for sizes, because you just write a formula about e.g. size in relation to other sizes. On native toolkits you would need to implement this stuff imperatively, I guess this looks like a real downgrade coming from the web, but it is really just a different mindset. Also when you run on the actual machine you have actual access to the device/viewport characteristics and can adapt based on that, and don't need to write an abstract layout. The other side of the coin is that the default widget packaging mechanism has been grid based while CSS only gained that later.
What I guess is also easier in JS, is just drawing on a canvas. The native UI toolkits want to nudge you into implementing a custom widget which implements all the required functionality of widgets. That results in a way better interface for the user, but when you just want a raster graphic you can click on, it can feel like a huge waste of time.
Since now native toolkits also support CSS, have JS bindings and Webpage targets, a guess the difference blurs.
Earlier quoted context omitted.
This is my favorite part of this story. Do you want remote code execution? Because [fixing things that aren't broken] is how you get remote code execution.
I think it's more likely that Microsoft is vibe coding slop garbage to replace their core apps that were literally better. Windows 10 explorer.exe is 100x faster than Windows 11 explorer, it's not even close. It also signals the death knell for Windows native apps. Microsoft can't make them anymore. It won't be long until even Excel is a Electron sloplication.
The new notepad is a buggy embarrassment. When you disable the "Continue previous session" option you can very easily lose unsaved changes: 0) Set "When Notepad starts" option to "Start new session and discard unsaved changes" 1) New file 2) Type "abc" - note the "X" to close the file changes to a "O" (pretend that's a circle) to indicate unsaved changes 3) Save file - "O" changes back to "X" 4) Type "def" - "X" chan…
Ironic how Notepad used to be too simple, making it useless as a text editor in many cases. In particular, it didn't support UNIX line endings and files larger than a few MB. The there was a brief moment where it became decent. Still a barebones text editor, but it could actually edit text, what I think most people expected Notepad to be. And now, it is going the other way, with "AI" features no one wanted, and also…
Isn’t it boring when a piece of software is just complete? In fact that’s an unacceptable state for it!
Earlier quoted context omitted.
Well, at least they brought back edit[0] [0] https://github.com/microsoft/edit
Edit is unironically one of my favorite text editors these days. It opens incredibly fast compared to everything else I use, it's easy to use, works fine on Linux. It's not going to replace emacs or VS Code, but it's incredibly handy for basic editing chores.
Yes. Supports .md but when you try to save back to .txt it does something to line endings that you cannot see in notepad but if you grep your .txt files from wsl like, I do all the time, you get page long strings instead of matching lines. It's weird and I haven't dug into the cause as it was easier to save as a new note but pretty sukky for an IT company to miss something like that.
CRLF vs LF?
Maybe Notepad is actually saving LF, but marks the file as CRLF and some WSL translation layer then triggers and removes LF, because they are not CRLF?
Earlier quoted context omitted.
Its not faster bereft of context, its just bloated. If you have enough resource to throw at it, its roughly the same. Theres some specific things that can themselves be slower, the Windows 11 Start Menu has had a lot of words written about its new implementation.
> if you have enough resource to throw at it An i9 with 128GB RAM isn’t enough resources to open a menu?