Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Broken

tyler.io

Post reply on HN
Print view View original

121–130 of 571 posts

Re: Broken

#121

Post by matwood »

dangus wrote: post #99

All the nightmares are nightmares until they're not nightmares. Weird launch day bugs like the I bug on iOS 11 are distant memories. Yeah, these bugs are bad, but to me articles like this really feel a lot like a broken record. Every September and October, when the major releases come out, there are bugs. And then by the time you're on 10.xx.2 or iOS xx.1.3 a month later they're just a bad memory. If you don't want b…

Yeah. I don't use any 32 bit software so I'm good there. Catalina has actually been the smoothest macOS upgrade I've had in awhile when it comes to all my 3rd party apps working. One annoyance was with some of my CLI programs (like Terraform) where I had to open them from the Finder right click -> open to get them marked as safe to run. That was expected though.

Re: Broken

#122

Post by caust1c »

arboghast wrote: post #30
mherrmann wrote: post #22

Can I just say how happy I am with Xfce. It's a Linux desktop environment that looks like in the early 2000s. It's fast. There are no unnecessary frills. It just gets the job done. Its release cycles are measured in several years, and keep it minimal. I used to be on Windows, then macOS, then Ubuntu and now this. As a developer with soon to be 20 years of experience, it's the best environment I've had.

So was I until I switch to a 4k monitor and realize that there's no real, stable, functional fractional scaling on Linux, even less so on XFCE, unfortunately.

It's actually quite good now using Gnome with Wayland on Arch Linux (latest releases of the various components).

Only a few apps have given me trouble in recent times.

Re: Broken

#123

Post by macinjosh »

I've been using Catalina as a daily driver since the first beta. I did notice some bugs here and there but I have to say my take away was different. I did get the barrage of permission prompts but it was just like that the one time and while it was a bit overwhelming it made me feel good that my OS was keeping tabs on these things. With Apple's emphasis on privacy they had to build these sort of controls into macOS to play catch up with iOS's features in this regard.

Also, I have hard time feeling sorry for someone who is upset that beta system software upset his working environment. Apple specifically says not to put their betas on critical hardware. The author said he did this because it was "simpler". Not sure if breaking your work environment is "simpler" than booting off an external SSD or having a second machine for testing.

Re: Broken

#124

Post by nico_h »

ajsharp wrote: post #90
PragmaticPulp wrote: post #47

> The final (well, first) Catalina release along with the outright awful public beta makes me think one thing. And that is Apple’s insistence on their annual, big-splash release cycle is fundamentally breaking engineering. I know I’m not privy to their internal decision making and that software features that depend on hardware releases and vice-versa are planned and timed years (if not half-decades) in advance, but I…

This reminds me of the fascinating NYT story about the lead up to the original iPhone announcement event: https://www.nytimes.com/2013/10/06/magazine/and-then-steve-s... . A choice excerpt: > The iPhone could play a section of a song or a video, but it couldn’t play an entire clip reliably without crashing. It worked fine if you sent an e-mail and then surfed the Web. If you did those things in reverse, however, it m…

There’s a difference between a golden path for a demo for a product that will ship in 6 month and a public release thats still very buggy.

And a public beta that will mess your files on other devices(!?)

Re: Broken

#125

Post by als0 »

shantly wrote: post #118
als0 wrote: post #91

Earlier quoted context omitted.

While on the subject, on Linux I've also noticed that Xscreensaver (or GNOME screensaver, can't remember which) sometimes goes straight into the desktop after wakeup for a few seconds before the lock screen prompt actually appears. You can even run programs. Really bizarre and feels like this issue has been present for a while now. Has anyone else noticed this or is it just me?

Yeah, saw this the other day on an Ubuntu machine (running whatever the last release was, not LTS) I have hooked up to a TV. Flash of the desktop for a second or so before the login screen. Speaks to something fundamentally wrong with the way the whole thing works, I figure.

I had the same impression. That general feeling that the screensaver is like an app/overlay that is invoked only once the desktop is active. The speed of invocation also seemed related to how fast your machine is at launching general desktop programs...

Re: Broken

#126

Post by jki275 »

fortran77 wrote: post #27
schappim wrote: post #9

Earlier quoted context omitted.

>> don't try to use the version of Linux under MacOS MacOS is based on Unix not Linux. However, I mostly agree with your sentiment and would extend it to “use the right tool for the job”. Use launchd (although I hear it is on the way out) instead of Cron etc.

It's based on Mach via NeXTStep. Not Unix.

macOS is Unix. It's the only successful desktop Unix that's ever been published.

Re: Broken

#127

Post by gdubs »

dangus wrote: post #99

All the nightmares are nightmares until they're not nightmares. Weird launch day bugs like the I bug on iOS 11 are distant memories. Yeah, these bugs are bad, but to me articles like this really feel a lot like a broken record. Every September and October, when the major releases come out, there are bugs. And then by the time you're on 10.xx.2 or iOS xx.1.3 a month later they're just a bad memory. If you don't want b…

I’ve gotten calls from my mom after she’s done a software update and had a bunch of things break. She’s more careful now, but I think the expectation set for the general public is that when someone announces an update is available, that it’s not going to be Beta.

Re: Broken

#128

Post by jjuel »

dangus wrote: post #99

All the nightmares are nightmares until they're not nightmares. Weird launch day bugs like the I bug on iOS 11 are distant memories. Yeah, these bugs are bad, but to me articles like this really feel a lot like a broken record. Every September and October, when the major releases come out, there are bugs. And then by the time you're on 10.xx.2 or iOS xx.1.3 a month later they're just a bad memory. If you don't want b…

I mean Windows 10 May 2019 release was "deemed safe" only at the end of September. It is no surprise. Companies push to meet deadlines which in turn results in buggy releases. It happens in video games quite a bit too where the full release is nothing more than a buggy beta for a few months.

Re: Broken

#129

Post by Yetanfou »

irq wrote: post #37
arboghast wrote: post #30

Earlier quoted context omitted.

So was I until I switch to a 4k monitor and realize that there's no real, stable, functional fractional scaling on Linux, even less so on XFCE, unfortunately.

This is the biggest thing keeping me from leaving the Mac for Linux, and it hasn’t really improved much in the last 4 years. I don’t think most people care about HighDPI (or whatever you want to call it), particularly Linux devs. But I can’t go back to lower DPI screens.

I do care about high dpi but not in the way most people seem to mean: I want as much text as readable on a screen. One of the many reasons for not using Gnome everything is that it insists on making everything SO BIG with enormous amounts of wasted space around it. Those 1600x1200 pixels on my laptop or 1920x1280 on the monitor are there to be used, not wasted. Firefox used to be another offender in this respect albeit one which is easier to tame - just change layout.css.devPixelsPerPx to something sensible (0.7 works quite well), move all controls to the navigation bar and close all toolbars.

Re: Broken

#130

Post by _bxg1 »

matwood wrote: post #111
_bxg1 wrote: post #98

To throw my own (admittedly niche) Catalina anecdote into the mix: In El Capitan, Apple introduced something called System Integrity Protection (SIP). This is a security layer that prevents you from doing certain things, like modifying system directories, even as root . The idea is that malicious software could gain root permissions and still be unable to do the most egregious stuff. Okay, fine. You can turn it off b…

I can appreciate your problem, but SIP on whole is a good thing along with mounting system directories as read only. It's the only thing that prevented many machines from having to be reinstalled recently. https://mrmacintosh.com/google-chrome-keystone-is-modifying-...

Right, but it's something that technical users should have a clear path for overriding. SIP at least has a semi-clear path for disabling it (though I couldn't find any official documentation of it, only forum posts) but the read-only directory thing was definitely really hard to find.
Post reply on HN