Live data from Hacker News

.NET Core 3.0 Concludes the .NET Framework API Porting Project

github.com

311–317 of 317 posts

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#311

Earlier quoted context omitted.

Yes, I touch the pad by accident all the time. But why is Apple so good at detecting which touches are accidental, while so many other manufacturers are not?

On Linux this works similarly. ~5 years ago my old laptops did the 'disable touchpad when typing' thing, now with libinput the touchpad has excellent and completely invisible (to the user) anti-false-touch functionality. Apple has invested the time to make great trackpad drivers. People have invested time to make libinput a great driver for Linux (in this regard - it does lack customization possible in older drivers)…

That is fantastic news about Linux. I bought a System76 four or five years ago and the touchpad was terrible. It wasn't just false touches; it was really hard to accurately click on something, the pointer kept making little jumps. Would you say that's better too?

If touchpads are good now, then I might go dedicated Linux again when it's time to upgrade from my aging MBP.

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#312

Earlier quoted context omitted.

On Linux this works similarly. ~5 years ago my old laptops did the 'disable touchpad when typing' thing, now with libinput the touchpad has excellent and completely invisible (to the user) anti-false-touch functionality. Apple has invested the time to make great trackpad drivers. People have invested time to make libinput a great driver for Linux (in this regard - it does lack customization possible in older drivers)…

That is fantastic news about Linux. I bought a System76 four or five years ago and the touchpad was terrible. It wasn't just false touches; it was really hard to accurately click on something, the pointer kept making little jumps. Would you say that's better too? If touchpads are good now, then I might go dedicated Linux again when it's time to upgrade from my aging MBP.

Try making an Ubuntu/Fedora USB and booting from it once on your MBP, that should let you see what it's like. I had to explicitly disable the 'disable touchpad while typing' libinput setting but aside from that everything works great out of the box.

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#313

Earlier quoted context omitted.

That is fantastic news about Linux. I bought a System76 four or five years ago and the touchpad was terrible. It wasn't just false touches; it was really hard to accurately click on something, the pointer kept making little jumps. Would you say that's better too? If touchpads are good now, then I might go dedicated Linux again when it's time to upgrade from my aging MBP.

Try making an Ubuntu/Fedora USB and booting from it once on your MBP, that should let you see what it's like. I had to explicitly disable the 'disable touchpad while typing' libinput setting but aside from that everything works great out of the box.

Cool, thanks!

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#314
post #300
post #257

Earlier quoted context omitted.

Yeah, except I like that Log() isn't already a reserved function name.

I don't think anyone is suggesting the function names should be reserved names. They would still exist in a namespace.

I don't really understand how this is significantly different than having a static class with the function

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#315

Earlier quoted context omitted.

What do you base that on? I have had no problem with F# and asp.net core. Just look at safe stack, it uses saturn or giraffe which in turn runs on asp.net. https://safe-stack.github.io/

That this abstractions exists on top asp.net core to make things more ergonomic proves my point.

No, it only proves that C# and F# are two different languages.

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#317

Earlier quoted context omitted.

Not only that but the new interface is becoming just as complex as the old. By the time they have finished they will be back where they started.

Nah, it's pretty simple these days and people who love scripting can use powershell for everything

Nah, it’s getting just as complex as the old interface, there is nobody with the ability to say no, this is too much.

I’m a big fan of PowerShell, I have embedded it in two products. However it’s not a good justification for a poor user interface.

Post reply on HN