Hah, that's a blast from the past! You've reminded me of "Ameko", which added a little cat to the Amiga Workbench, walking around over the windows. I think I had it from a magazine coverdisk.
With `tail` you can press enter a few times to put some empty lines after the last line. This is useful e.g. when you trigger a function multiple times and want to easily see line groups from each attempt. It's the only reason I still use `tail` for following when `less` is available.
A visual mark would be nice, agreed. I haven't tried it, but I wonder if you could approximate it with the bookmarking feature that less(1) does have. It wouldn't be visible, but it would scroll to a consistent mark.
I usually use tail when I need to do some ad-hoc log following.
Having to set bookmarks and remember them is a PITA I can usually do without. If I'm looking at "normal" log output, it's usually set up in a nice aggregator somewhere, where I can easily exclude noise and otherwise uninteresting output.
I think it costs less too, whereas a new or used PS5 costs more but doesn't add a lot of value -- there are roughly 15 exclusive games for the PS5 so it's not compelling if you have a gaming PC, but it is a nice package to sit next to your TV that does a lot and can stream games from the gaming PC. Personally I like a PS4 controller better than the Apple TV thing.
The launch edition doesn’t? I’m surprised vendors even sell a bluray drive that doesn’t have that capability. I guess sony wanted to cut every cent off they could…
I’m not sure I understand. You refer to the conditional resource fields normally - without list indices. You just have to make sure the object isn’t null.
There’s some samples in the docs[0] on safe access patterns!
My first concern is that this looks very difficult to remove if the battery begins to swell, as silver-oxide batteries are wont to do. Perhaps that's less likely with single use batteries.
Padding ties up capital, it reduces credibility, it delays deployment, it adds costs through delay. It is bad for organizations. However, it is a great solution if you're a worker in a bureaucratic environment that can tolerate large costs, but is intolerant of 1-day of schedule slips. It's a great solution for complacent management, who are confused about the game they're playing and wants to report that they're "on track", which means "not late".
The agile solution of incremental value delivery is a compromise, and can produce good outcomes for functional changes. But agile has unacceptable failure modes when working on infrastructure and satisfying system constraints. Agile can work okay for programmers, but it's not a solution for engineers. Acknowledging, owning, and managing risk is more scalable, but you have to have leaders who acknowledge that they exist and have the maturity to take on that responsibility.
> Padding ties up capital, it reduces credibility, it delays deployment, it adds costs through delay.
Well done timelines are a negotiation between the stakeholders and engineers. The stakeholders need something done for the business, the engineers give a timeline. If that timeline works for everyone, great. If it doesn't, then the stakeholders will ask if it can be done in a faster time.
A timeline that lands on time, or early, is good. The point of timelines is that teams outside of engineering are resourcing their projects based on your timelines. They may have made outside commitments to customers, they may be lining up marketing, they may have embargoed PR, it may be delivered by someone at a conference, etc.
A project running late can be catastrophic. Bad customer relations, wasted marketing spend, pulling back stories from PR, delays for dependent teams, etc.
You pad to make sure your timelines aren't overly optimistic, because we're all bad at estimating, and it's possible our dependencies are too. By padding, when it comes time to negotiate for shorter timelines, you also have some wiggle room.
Bureaucratic environments tend to be larger companies and they care about schedule slips, because they have more teams being impacted, and those teams are handling larger numbers of overall projects. Schedule slips can lead to cascading failures.
I don't know that it's fair to say Framework don't care much about the software. Their oldest devices are still getting firmware updates. At any rate, Pop!_OS runs very well on Framework Laptops (though I use Arch + Hyprland, w/ Windows on their storage expansion card).
reply