For now, Homebrew works if you want a cross-distro way to install Nu on x64 Linux.
1,572 karma · joined April 24, 2015
For now, Homebrew works if you want a cross-distro way to install Nu on x64 Linux.
- less verbose syntax
- better cross-platform support (PowerShell is technically cross-platform, but it has some baggage from its Windows-first history)
- way faster to start up
I'm biased (I'm a member of the Nushell core team), but those are all things that drew me to start contributing to Nushell.
On the other hand, Nushell is certainly less mature+stable than PowerShell. And if Windows administration is your main use case, PowerShell can't really be beat.
I tend to follow a "clone first, figure out lifetimes later if profiling shows that it would be worthwhile" rule. If I always did the optimal thing with lifetimes, I'd never actually finish anything.
I'm unsure what problems with DPI scaling you're referring to. Last time I was working on a WinForms app (admittedly not an especially big one) I think I just needed to set the DPI awareness in the manifest and it worked OK. https://learn.microsoft.com/en-us/dotnet/desktop/winforms/hi...
I would bet good money that a theming overhaul won't happen this year or next. WPF's currently staffed by a skeleton crew, and they have not demonstrated an ability to deliver features anywhere near that size.
My wild speculation: they'll put some effort into a .NET Core WPF migration and also build out some new features piecemeal in web UI.
tl;dr: WinForms is well supported if you don't need it to be pretty. WPF is complex but mature. WinUI 3 might be ready someday but it's not there yet.
I don't want to suggest Electron, but there are valid reasons why people use it...
I could not disagree more. That might be true for you, if you are a person who has already spent a long time learning WPF. It is not true in general; WPF is complex.
In a past life where I had to deal with a lot of .NET libraries from awful enterprisey vendors, it was often easier to pull down versions uploaded to NuGet by 3rd parties than use the official installers. In retrospect this was pretty dumb of me from a security perspective...
No it isn't. I think you know the answer to the question "are transit riders more or less affluent than drivers on average?"
> And those twee little bicycle-lane-only traffic lights? Cute, right? Those are basically tombstones for your local art scene, because that whole block is 'going Vanhattan' (portmanteau of 'Vancouver' and 'Manhattan').
Please name one place where this has occurred in Vancouver (which I am intimately familiar with).
I quit that job because the extensibility story for Excel was so painful (but they had good business reasons for being in the space), sigh.
I can reproduce your issue, I suspect that `filter` is collecting its input when it shouldn't. It's not totally clear why from looking at the code.
If you can file an issue that would be appreciated, if not I'll try to do so later today. We have a tag for streaming issues: https://github.com/nushell/nushell/issues?q=is%3Aissue+is%3A...
Not sure about Debian. We generally rely on the community for distro packaging. Right now Homebrew is the easiest way to install Nu on most Linux distros.
Fish is a wonderful, mature project, but for me it wasn't quite ambitious enough. It breaks from POSIX just often enough to cause friction when adapting instructions written for POSIX shells, but not enough to make CLI UX significantly better than a POSIX shell. Also, scripting often seems like an afterthought in Fish.
Stability (in the sense of not crashing) is decent, it's been a long time since I've crashed Nushell. We do get the occasional crashing bug filed but most of those are in areas like our completion engine rather than interacting with external tools.
OTOH, command design and language are not entirely stable; we are still pre-1.0 and we do make breaking changes fairly often.
(I work on Nushell)
I say this as someone without most of the usual prejudice against VB; I used to work in a large codebase that was half VB.NET and half C#, and didn't mind VB. VB was a little more verbose for some things, but after getting used to the syntax the developer experience was basically the same in each language (yes, with a few small exceptions like XML literals).
Ultimately, that's the problem with VB; it's not different enough from C# to really justify significant investments in 2023. There are some die-hards who really like the VB syntax but they're growing ever rarer.
Left a bad taste in my mouth, doubly so because I turned down another offer assuming that Okta would come through.
I generally think a garbage collector makes sense for 99% of programs out there, but databases often need a bit more control over memory management for performance reasons.
What? No it doesn't, HoloLens 2 runs "Windows Holographic" which is based on Windows Core OS.
Did the developer story for HoloLens ever get better or did it just die a slow death?