That's usually because the system that runs those things is independent of the timing of the main game loop. And then when someone finally gets around to implementing the pause screen, they still run even with the main game time stopped. And you look at it and think "eh, you know what - looks cool - we'll leave it".
The reintroduction of Red Kites to the UK has been a huge success. I don't get particularly excited by birds normally, but regularly seeing such large creatures (almost 2m wingspans) curving through the sky is nothing short of majestic. They're almost reminiscent of dragons.
I wonder if I'll get to feel the same about golden eagles soon too.
I have large lungs, and can be very loud, and where I live the eagles ridge soar whilst going from one place to another, at just a bit higher than the tree tops, mostly baldies here with the ocasional golden, and for fun I started, belowing EEEGULL strait up at them, and they do a double take WTF, pull a hard wing over to get a better look and the finnish there turn, and blast off down wind,
so if you get the chance, punking eagles is a blast
Can vouch for the loudness capability of large lungs.
A lady sitting in front of me at the football said she could feel the vibrations in her chest when I was loudly booing at the footy.
I had an x-ray a couple of years ago and was asked if I was a smoker, strangely because of the size of my lungs. Apparently, ironically, smokers lungs are larger than average and I have to assume it's to balance out all the damage that smoking does. I used to be a swimmer, so I figured my lungs must have developed from the requirement of controlled breathing as part of swimming (and the general fitness and therefore additional oxygen processing requirements).
I don't get particularly excited by birds normally
Same. Sometimes one of my deer will get thwacked by a car just hard enough it stumbles up my driveway and falls over. There will be 3 golden eagles and 2 bald eagles fighting over it. The first time I saw them I had a double-take ... I swore at first I saw men sitting on my driveway fence. Golden eagles are massive and quite awe inspiring to watch. When they fight over road kill they stretch their wings out entirely.
Each time I have to make sure I still have an outdoor cat and I have to keep an eye on him until they are done. They seem to only eat the soft bits and leave the muscle meat for the ravens. Then the deer turns into a fly factory which I have to spray.
We have a pair of kites that regularly land in a tree a few meters from my garden. They are beautiful looking creatures (even if not very beautiful sounding). It always lifts my spirits to see them. I hope the reintroduction of Eagles is similarly successful.
When I was a kid in the 80s and 90s we'd go on holiday in mid Wales, and I remember it being a big thing that it was the home of some of the last few red kites in the UK. Now I see dozens of them most times I drive around the south of England. Never gets old.
I used nvm a long time and was very happy to get rid of it and use `devbox` and similar tools instead.
The rule on my machine now is that everything has to be in a per-project sandbox, self-contained to ~/.local/bin or installed by the system package manager.
The question was about global tools, something nvm purposefully does not handle.
The `uv tool` answer by a sibling comment was great; it'd be nice to have something similar for npm.
Seriously, you need a heck of a lot more than a random HN reply to give you Jira alternatives if you've been embedded into its ecosystem for any length of time - and my condolences if you have.
It's fine, just not stellar. It was terrible (UX, speed, consistency) ten years ago. It's better now - mostly gets out of people's way and just works. It doesn't delight me.
We've switched to Jetbrains Youtrack, it doesn't have as many features, but turns out nobody was using most of them anyway.
It's Jira + Confluence bundled together including SSO.
We (~200 devs) migrated from Jira to Youtrack 10 years ago, and its functionality has been more than enough. Honestly, I don't remember anyone ever seriously complaining about it, aside from maybe a few nitpicks. A very solid product.
I think there's definite scope for that being true; not because you can start doing stuff before you understand it (you can), but because you can ask questions of a codebase your unfamiliar with to learn about it faster.
Serious question: what are those things from windows 95/98 I might miss?
Rose tinted glasses perhaps, but I remember it as a very straightforward and consistent UI that provided great feedback, was snappy and did everything I needed. Up to and including little hints for power users like underlining shortcut letters for the & key.
I miss my search bar actually being a dumb grep of my indexed files. It's still frustrating typing 3 characters, seeing the result pop up in the 2nd key stroke, but having it transform into something else by the time I process the result.
Inevitably windows search fails to highlight what I’m looking for almost all of the time, and often doesn’t even find it at all. If I have an application installed, it picks the installer in the downloads folder. If I don’t have an app installed, it searches Bing for it. Sometimes it even searches when I do have the application installed!
Microsoft seems not to believe that users want to use search primarily as an application launcher, which is strange because Mac, Linux, and mobile have all converged on it.
The only one I can think of, literally the only one, is grouped icons.
And even that's only because browsers ended up in a weird "windows but tabs but actually tabs are windows" state.
So yeah, I'd miss the UX of dragging tabs into their own separate windows.
But even that is something that still feels janky in most apps ( windows terminal somehow makes this feel bad, even VS code took a long time to make it feel okay ), and I wouldn't really miss it that much if there were no tabs at all and every tab was forced into a separate window at all times with it's own task bar entry.
It's not like grouped icons wasn't technically infeasible on win95. And honestly, whatever they are more useful is quite debatable. And personally, I don't even have a task panel anymore.
The real stuff not on Win95 that everyone would miss is scalable interfaces/high DPI (not necessary as in HiDPI, just above 640x480). And this one does require A LOT of resources and is still wobbly.
I'm not sure what you mean by "Technically feasible", but it wasn't supported by explorer.
You could have multiple windows, and you could have MDI windows, but you couldn't have shared task bar icons that expand on hover to let you choose which one to go to.
If you mean that someone could write a replacement shell that did that, then maybe, but at that point it's no longer really windows 95.
Could you give a few examples? I'd lean towards adjusting tooling if you can.
My spelling is often horrendous and I know it - but almost every dev I know of prefers to copy and paste anything that might be misspelled just because it's easier than taking the risk.
Similarly - how does does this get anywhere near causing a production outage?
I'd be tempted to view this as a blessing in disguise; this person sounds like they'll trip up more often than the rest, but if one individual can cause a production outage with spelling mistakes something's gone awry with your processes elsewhere. You have an opportunity to fix whatever that is now.
A string value in a json config needed to be updated.
On one prod instance, typo while updating the config by hand. Config validation of the software caught it, software stopped with the appropriate error message, a few minutes later we were up and running again.
We introduced work reviews on prod instances (similar to code reviews) after that.
Later, he then wrote a patch script to avoid making that mistake again.
In the json schema definition used in the script, the name of the property had a typo (how it came to be... no clue, copy paste should have taken care of that).
The script was part of a MR, the reviewer missed the typo. We noticed it in staging.
We introduced tests for config editing scripts after that.
And so it went on and on... The problem is not that it happens and we then refine our processes. It is the frequency.
What I’m seeing here is that you don’t have mature mechanisms to assure the reliability of your services yet. The second paragraph suggests that a misconfiguration was able to make it into production that arguably should have been caught at an earlier stage of the deployment pipeline. Anyone can make these sorts of mistakes; the fact that a particular colleague is more prone to them really doesn’t matter all that much.
Fortify your delivery pipeline and the problem should resolve itself.
They are not, but think of it like learning to play a guitar: at first, the strings cut into your fingers, but then you build up enough calluses and playing it stops hurting. Or, consider a building code: every rule was written in blood, and new buildings get safer over time.
reply