Windows 11: Just say no • Hacker News Board

Re: Windows 11: Just say no

#501

Post by scns » Fri, Sep 17, 2021, 1:24 PM UTC

seph-reed wrote: post #319

liquidify wrote: post #287

Earlier quoted context omitted.

How does bitwig do with multi channel audio? I need 32 in and 32 out. I have Merging and RME available as audio devices, but I don't suspect that either of them would actually work with multi-channel recording, despite both of them offering drivers. If someone could guarantee rock solid stability, I *might be willing to switch, even though I'm fairly invested in the Ableton / VST world. 10 years of projects will like…

If you've got a tool you're used to, it's probably best to stick to it. That being said, Bitwig does support Jack, so routing should be pretty open ended. And there's this linux project ( https://pipewire.org/ ) that's been doing really, really well. It (sorta) combines all the different audio servers into one.

Even though i gave suggestions how to try out Linux, i would rate this higher. Stick to your guns, never change a running system/winning team.

There is an amazing (IMSO) producer duo, highly recommend their liveset from Glastonbury, called Booka Shade. They produced a chart topping pop act on PowerMacs (G4 IIRC), which were allready ancient back then.

Re: Windows 11: Just say no

#502

Post by scns » Fri, Sep 17, 2021, 1:32 PM UTC

_xy8h wrote: post #90

Wavelets wrote: post #9

Maybe it has better security, but it has worse privacy. Windows 10 is my last MS OS. Heading back to Linux as my daily driver with a System 76 machine.

Windows 10 was what pushed me to start using Linux full time. It just broke me, how nonsensical it was. Going through several layers of new UI style sidebars, submenu items just to end up... in classic Control Panel with configuration elements divided up between new and old? Windows still has an insanely convoluted installation process whereas Ubuntu boots straight into a usable desktop from installation medium and h…

Installing the OS and browsing the web at the same time? Take my money! Free? Ain't kiddin?

1000x Thank You to all devs, packagers and all i forgot in the Linuxverse.

A happy user since 07

Re: Windows 11: Just say no

#503

Post by scns » Fri, Sep 17, 2021, 1:37 PM UTC

hef19898 wrote: post #34

CitrusFruits wrote: post #30

Earlier quoted context omitted.

Found this out the other day: you can have local only accounts for Windows, although it's pretty hidden nowadays. https://support.microsoft.com/en-us/windows/can-i-sign-in-to... (Search in the page "Switch from a Microsoft account to a local account")

Good call! Too late for me now so, especially since the majority of my Steam library is running just fine under Linux. Maybe for some online stuff, Teams for potential home schooling and so. The fact that local accounts are hidden sucks in itself so. I will keep Windows on my private laptop so, just in case. Not that I am going to upgrade to Win 11 so.

Better switch your wifi to metered connection then, like recommended upthread. Prevents automatic updates and being upgraded involuntarily (hopefully).

Re: Windows 11: Just say no

#504

Post by scns » Fri, Sep 17, 2021, 1:41 PM UTC

blacksmith_tb wrote: post #219

autoliteInline wrote: post #16

Earlier quoted context omitted.

I just fired up a Win10 machine for the first time in some while in order to run specific software. Good gawd. It was finally useful about 4 hours later after all the updates and tomfoolery. Never again.

Well, I am not sure it'd be painless to boot up a macOS machine or an Ubuntu desktop that hadn't been getting updates for months - probably not 4hr, but there'd be some annoyance.

Some anecdata: updating packages on Linux will finish in less than 20 minutes (given a high DL speed), no reboots inbetween, and afterwards you can keep working, unless you want to boot a newly installed Kernel.

Re: Windows 11: Just say no

#505

Post by lou1306 » Fri, Sep 17, 2021, 1:45 PM UTC

hef19898 wrote: post #366

lou1306 wrote: post #361

Earlier quoted context omitted.

It should be in Windows 2000's place. ME was a Windows 9x system, 2000 was part of the NT family.

It is too long ago to properly remember, but during this time when building my desktops I always insisted on getting NT and then Windows 2000 in place of the consumer versions. Had some funny discussions with shops when buying licenses.

I also remember using NT 4.0 (with the "hit Ctrl-Alt-Del to login" quirk) and then 2000 at home as a kid. Dad, being a sysop/dev/IT manager/"tech guy", really liked the stability of NTs. It took the first Service Pack for XP to really start catching on. Good times!

Re: Windows 11: Just say no

#506

Post by johnisgood » Fri, Sep 17, 2021, 1:47 PM UTC

AnIdiotOnTheNet wrote: post #96

GiorgioG wrote: post #76

Earlier quoted context omitted.

> Why do they keep messing with the UI? UX folks don't get paid to leave things alone.

Nobody gets paid to leave things alone and maybe that's a big problem with the world.

Yeah, it is seriously worth thinking about.

Re: Windows 11: Just say no

#507

Post by toss1 » Fri, Sep 17, 2021, 1:50 PM UTC

slategruen wrote: post #325

toss1 wrote: post #140

Taskbar can no longer be moved. That single "improvement" will keep me away for as long as possible. It's the first thing I change when setting up a new Windows environment, and have done it for over a decade. I'm enough not alone that I've seen in mentioned in multiple articles. MS makes all kinds of noise about "reworking the UI from the ground up for true usability" or some such. Yet I have no idea what could poss…

Is there any logical explanation on why they did this?

I wish I knew. I literally cannot think of any rationale.

It isn't like they have any concern about efficient or lightweight code so are stripping out features for that reason (and I know from conversation w/their lead developers decades ago that they have not had any interest in any such optimization for at least that long).

I don't see how it confuses anyone, since it requires no action or knowledge to just leave it in the default position - I've encountered a few people who are surprised to see that it can be moved, so it isn't like the capability will cause problems. If they're concerned that someone might accidentally drag it and be surprised, then leave only the buried radio-button position control to select bottom/top/left/right.

Seems like under-talented developers and product managers who can't think of anything that is actually creative and an improvement, so they just vandalize it to leave their mark.

It is utterly baffling

Re: Windows 11: Just say no

#508

Post by Cyder » Fri, Sep 17, 2021, 2:16 PM UTC

It's Vista all over again.

Re: Windows 11: Just say no

#509

Post by jussij » Fri, Sep 17, 2021, 2:20 PM UTC

Joeri wrote: post #367

jussij wrote: post #253

Earlier quoted context omitted.

At a minimum, for a Win32 application to work correctly with HiDPI it needs to tell the OS it is DPI aware. This is done by marking the application DPI aware using the settings found in the manifest file. The manifest file is then embedded into the resource section of the application, which then lets the OS know the application will be handling it's own DPI. So the reason many of those 'legacy apps' don't work with H…

Applications also have to listen for messages that indicate a dpi change (moving between screens) and recalculate and redraw everything for the new dpi. The legacy codebases which are easily retrofitted to do that are the stuff of myths and legends.

> Applications also have to listen for messages that indicate a dpi change

That is how a well behaved 'DPI Aware' application should work.

However, even for those badly written DPI applications that don't listen for those changes, the work around is to first make the required DPI changes and then restart those badly written DPI applications, as they will then pick up those DPI changes on startup.

Re: Windows 11: Just say no

#510

Post by Jorengarenar » Fri, Sep 17, 2021, 2:43 PM UTC

2muchcoffeeman wrote: post #474

ryandrake wrote: post #252

Earlier quoted context omitted.

It's definitely a big problem with software. This "need to constantly pay developers" is part of the justification for moving towards subscription payment instead of one-time payment. The logic goes: One-time payment won't pay for future changes, and developers are always making changes, and they need to be paid for. But, what if I don't want future changes? For almost all software I've ever paid for, as a user, I ju…

> designers need to perpetually change the UI That's a bit unfair. The iPhone 13 just came out and one of the memes and jokes going around is that it looks the same as the previous phone and users are just buying the same thing again. Even tech people I know are joking about it. So the UI people are always going to be busy because even people in the industry equate looks to changes. If the looks don't change they wil…

I think the main reason for memes is because Apple always markets everything they do as some kind of massive innovation despite either bringing something from the past or just copying what competitors already had long ago. They at least used to pretend they make something different with design changes, but now even this facade fell down.