151–160 of 191 posts
Yay for finally having a default text editor that works over ssh. Managing windows servers over ssh is a bit of a pain without. They could just have packaged nano, but oh well.
Earlier quoted context omitted.
That just feels like scope creep. Notepad would also be neat with some better keybinding support, plugins, lsp, ... - but then it wouldn't be notepad, and theres countless not notepads out there. Tools like nano (well, pico) exist to provide a reliable and always available minimum feature set. If you expand it, then you end up with something that is neither the minimum nor capable enough to sensibly compete with full…
No, it would still be notepad, but a higher quality one where especially users who don’t know better wouldn’t have to suffer as much from bad/lacking functionality
Earlier quoted context omitted.
Can you say more about the chain of trust issue? Does Rust also not have that problem? Or are you using mrustc to bootstrap rustc?
Indeed, we have our own bootstrapped Rust toolchain internally. I think this has to do with (legal) certifications, but I'm not entirely sure about that.
https://bootstrappable.org/ https://lwn.net/Articles/983340/ https://github.com/fosslinux/live-bootstrap/blob/master/part... https://stagex.tools/
Earlier quoted context omitted.
This might be the most obvious use case: https://learn.microsoft.com/en-us/windows-server/administrat... I'm a powershell bigot and spend most of my windows admin life in a terminal (or vscode) so my take is to simply use psremoting but ssh is there if you need.
I prefer SSH because it fits into a standard workflow with far larger ecosystem (my file manager and editors can browse SSH directly, traffic can easily be routed over SSH in either direction), and is already what I'd use for the majority of servers and machines. psremoting would be limited specifically to remote PowerShell on windows, which is comparatively limited. Even if I was purely a Windows admin I'd consider…
Posh remoting works well because it's posh and you get all the nice object-oriented things that come from that. You do miss features like tunneling so I have SSH to fall back on where needed (and also for non-windows workloads etc). Right tool for the job and all that, and if you're not a heavy posh user the ssh option makes a lot more sense.
"Edit". Really? Was that the only name available? I am sick of these companies repurposing very common computing terms for their mediocre products.
Yay for finally having a default text editor that works over ssh. Managing windows servers over ssh is a bit of a pain without. They could just have packaged nano, but oh well.
They could've just shipped YEdit, which is open source: http://www.malsmith.net/edit/ but there is NIH syndrome in MS.
It had some problems however with handling unicode (iirc). Basically, shipping yedit would have required a huge re-write of its underlying text buffer. In the end the discussions we had with Malcom concluded that just writing a new one was probably easier and more maintainable in the long run.
Earlier quoted context omitted.
1. What do you like about Zig more than Rust? 2. How did you ensure your Zig/C memory was freed properly? 3. What do you not like about Rust?
> What do you like about Zig more than Rust? It's been quite a while now, but: - Great allocator support - Comptime is better than macros - Better interop with C - In the context of the editor, raw byte slices work way better than validated strings (i.e. `str` in Rust) even for things I know are valid UTF8 - Constructing structs with .{} is neat - Try/catch is kind of neat (try blocks in Rust will make this roughly e…
Earlier quoted context omitted.
No, it would still be notepad, but a higher quality one where especially users who don’t know better wouldn’t have to suffer as much from bad/lacking functionality
There are already: Notepad3 ( https://sourceforge.net/projects/notepad3/ ) or metapad ( https://liquidninja.com/metapad/ ).
Earlier quoted context omitted.
No, it would still be notepad, but a higher quality one where especially users who don’t know better wouldn’t have to suffer as much from bad/lacking functionality
More features ≠ higher quality.
> While it is relatively simple to learn the magic exit incantation, it’s certainly not a coincidence that this often turns up as a stumbling block for new and old programmers. What’s even simpler is changing the awful defaults and adding the menu to make this a non-issue at a tiny fraction of the time it would take to write a new editor. > we decided that we wanted a modeless editor for Windows (versus a modal edito…
New users accidentally end up in the wrong mode because they press the wrong key, and then get stuck because they don't know what a "mode" is. There's really no reason for a basic lightweight text editor to have modes. If you as a power user want one, Vim can be installed as needed.
No they wouldn't, if you believe there are so many terminal editor users that can't be taught what modes are, you simply guard it via settings so that unless you enable it explicitly you can't press the wrong key
> There's really no reason for a basic lightweight text editor to have modes
There is - having the power in every single Windows installation, including all the VMs and other people's machines.