ripley12

27 ms·

301.
by ripley12 5y ago
As a person who only occasionally writes JS and has zero interest in keeping track of the differences between client-side and server-side JS - fetch has been a big friction point for me in the past, it's big news to me.
302.
by ripley12 5y ago
Personally, I think the appeal of Go has much more to do with the compiler and the tooling than the language. The compiler is blazing fast and you get small fast statically linked executables by default. That's very appealing to me eve
303.
by ripley12 5y ago
It's a mess. If pressed I would say WinForms is the most practical choice for most apps today - even though it sucks, even though it's ugly. It's actively worked on (unlike WPF) and it lets you use the latest .NET version. We
304.
by ripley12 5y ago
Yeah, DDG has become nearly unusable for me since they stopped honoring quotes (a few months ago?). I've found myself instinctively using the !g Google fallback more often than not, and at that point I might as well just switch back to
305.
by ripley12 5y ago
From the outside it seems to be in maintenance mode. It hasn't received new features in a decade (other than the port to .NET Core, if that counts). The Windows team has staffed it with a skeleton crew (a manager and 2 devs last I chec
306.
by ripley12 5y ago
I'm not sure you can comment on this, but: any idea what the long-term plan is for UI in Visual Studio? WPF has been more-or-less abandoned by the Windows team, and that's a little scary since VS uses WPF so much...
307.
by ripley12 5y ago
> More generally, the reason that build tooling in the .net sphere is such a mess is because of historical baggage from VS. This is part of why the .NET hot reload fiasco was such a big deal to me; it felt like doubling down on one of .N
308.
by ripley12 5y ago
FWIW I (a daily VS user and someone who is generally fond of it) don't particularly like the VS folder view. I find it slow to open and a bit clunky; accordingly I often have VS Code or a terminal or Explorer open in addition to VS.
309.
by ripley12 5y ago
Based on everything I've seen in the last year and a half: WebView2 (i.e. Chromium) is getting more investment from the Windows team than any of the "native" UI technologies. I'm not thrilled about it but I'm adjust
310.
by ripley12 5y ago
> Why do they keep doing this? I can speak to the UWP -> WinUI 3 transition a little: it's a hard transition because UWP did so many things its own way. It's often really difficult to migrate concepts from UWP to the Win32
311.
by ripley12 5y ago
Agreed. It's not for lack of investment either; they invested staggering amounts of engineering time in WinRT and UWP and they actually built some cool stuff. But, well... it certainly didn't help that they made it so difficult to
312.
by ripley12 5y ago
> It does seem like things have settled down upon UWP finally They officially cancelled UWP 2 months ago, after a few years of "not quite dead, not actively supported" limbo. I guess it's settled down, but not in a good wa
313.
by ripley12 5y ago
Yeah, developing Office add-ins is a nightmare and the Office team has totally screwed up Office extensibility. FWIW they march to their own drum, they are largely independent of Windows and Developer Division. I would not tar all of Micros
314.
by ripley12 5y ago
> WinForms is "legacy", WPF is the way to go. It’s not that simple. WPF has been mostly abandoned by the Windows team, while WinForms is owned by the .NET team and much better maintained. WPF will probably never be compatible w
315.
by ripley12 5y ago
I’ve been reading this recently to get up to speed with Notcurses, it’s fantastic. Funny, engaging, and a surprisingly good general overview of how terminals work. One thing to note: it was written for an older version of Notcurses. So some
316.
by ripley12 5y ago
Hmm, I wouldn’t say WinForms is in a similar limbo right now. It's maintained by the .NET team and it gets more attention than WPF. Work is happening to make WinForms compatible with NativeAOT and trimming, I think it will land in .NET
317.
by ripley12 5y ago
Seriously? The effort Rick puts into Paint.NET performance is unreal (check out his Twitter sometime). I've found it to be impressively fast, especially for how much functionality it has. FWIW it was only recently migrated to a modern
318.
by ripley12 5y ago
Yeah, it's a mess. Personally I think web UI via WebView2 is the only way forward; Chromium is far and away the most powerful UI framework shipping with Windows these days. Even if "native" UI frameworks were doing everything
319.
by ripley12 5y ago
Paint.NET is probably the best example of a good, fast widely used .NET app.
320.
by ripley12 5y ago
I think that's only partially right. .NET apps can be published with AOT code (ReadyToRun). WPF apps are still pretty slow to launch with ReadyToRun enabled; I haven't profiled it to see why, but I suspect it has a lot more to do
321.
by ripley12 5y ago
Down that path lies madness. Everyone I know who works with XAML Islands despises it. MS doesn't really push it because it's very broken.
322.
by ripley12 5y ago
It's a similar thing IMO. WPF is understaffed to the point where it might as well be dead in my mind. It hasn't received major new features in a decade. It's currently owned by the Windows team (not the .NET team) and they ha
323.
by ripley12 5y ago
Couldn't agree more. I've followed this rough pattern to build a rock-solid offline-first core for a personal application: https://flpvsk.com/blog/2019-07-20-offline-first-apps-event-... It's got some pa
324.
by ripley12 5y ago
So download a binary instead of building it from source?
325.
by ripley12 5y ago
I wouldn't expect much difference in performance. "The on-disk format for the table data is the same." I would expect the additional checks on writes to be negligible in most cases (dwarfed by other bookkeeping and I/O).
326.
by ripley12 5y ago
> the function-or-media switch is atrocious It's so bad. It's unfortunate because it's otherwise a pretty great keyboard; I'd love something similar with an Fn row.
327.
by ripley12 5y ago
It looks like you're not using the new dynamic PGO functionality (the OP is). I've seen throughput gains of ~15% from that.
328.
by ripley12 5y ago
This is lovely. I really like that you can adjust numeric values by clicking and dragging and the visualization updates in real time; reminds me of the demos from Bret Victor's Inventing on Principle.
329.
by ripley12 5y ago
Seems like a handy feature for things like test frameworks. There's more detail in the official C# docs: https://docs.microsoft.com/en-us/dotnet/csharp/language-refe... And in the GitHub issue for the fe
330.
by ripley12 5y ago
> so if you mistype the parameter name in the decoration, there's no warning Mistyping the parameter name results in the following compiler warning, thankfully: CS8963 The CallerArgumentExpressionAttribute applied to parameter &#x27

More ›