Worktrees are a must if you work with monorepos or just multiple branches in general. Lack of conventions (or rather the braindead defaults) and having to explicitly type out everything is what hinders adoption the most.
I've solved this by running thin bash script wrappers that keep the workflow SVN-like with a root directory that contains per-branch directories and a hidden bare repo).
I think my layout is similar to yours. What do your scripts do?
My branches end up in a tree structure (no shit!), and I rebase and merge up stream as changes land. I guess it could be more automated, but the only tedious part is remembering to remove old worktrees and prune the old branches
worktree add: `git worktree add` that creates a local new branch and a directory with the same name and sets upstream to match; alternatively checks out an existing remote branch.
worktree rm: Removes worktree directory, first checking it is in porcelain state. Then prunes them and removes local branch pointers if they match the remote ones.
These all are handwritten and probably buggy, but still less prone to errors than typing out `git worktree add -b foo-123-fix-missing-semicolon foo-123-fix-missing-semicolon origin/develop` manually every time. One pass with Claude or Codex would probably do wonders.
I was looking for some CNATRA (US naval aviation) unclassified, non-distribution-controlled training manuals and noticed that the newest ones had been deindexed when they were put behind authentication.
You can install one on the balcony below the railing level.
The housing company is responsible for the exterior surfaces and thus also responsible for whatever happens to fall on bystanders when it will inevitably happen.
AC installers are also notoriously bad at following placement guidelines.
I've had one placed like this in the balcony of a XVth century palazzo turned museum plus hotel, straight in the historical heart of Verona. If they can do it, everybody can do it as well.
Google has a computer making decisions that affect humans, and then they then have humans defending the decisions a computer did. We live in a dystopia. I hope "Karen" sees the irony in the day job she is doing.
A COMPUTER CAN NEVER BE HELD ACCOUNTABLE. THEREFORE A COMPUTER MUST NEVER MAKE A MANAGEMENT DECISION.
We had CRT displays that could easily do 100 to 120 Hz. Then we regessed to LCD panels that could do 60 Hz and it somehow became the performance target.
> I mean CRT is inherently bulky, it's hard not to see why LCD panels became popular.
But going from, say, a Sony Trinitron CRT [1] to one the first LCD was a huge step backwards, which is what GP is saying.
I did wait for the first LCD with DVI support before switching: for the difference in crispyness between an analog video cable and a DVI one was night and day (I also won many points when I helped friend set up a startup in southern california and we realized one person out of two had picked the VGA cable instead of the DVI one when setting up its desk / computer: so with the CTO late at night we went through every PC and changed all those with VGA cables to the DVI ones).
We're not saying modern days flat monitors aren't better than old CRTs: we're saying the first flat screens were complete suckage.
[1] even though on a Trinitron you could see two faint horizontal lines (Trinitron were still amazing)
Which of course you could only see in direct comparison. Which most ppl didn't have the opportunity to do, so you needed experience instead to judge that. Which most ppl also didn't have, because they've been exposed to cheap stuff only.
Matrox used to have the best back in the day. Ai were ok and Nvidia were the worst. Even a lay person could see that difference between the tnt out put vs a millenium. It was so great that i used to use an older matrox card think it was the g450 since it worked great under Linux and the pq was amazing.
I also had something by ELSA with a S3 and a translucent blue RAMDAC by IBM. Same thing. But only 2MB VRAM, and PCI. So only useful for testing purposes.
Regarding the usability under Linux, or rather support by XFree86, Matrox accelerated some graphics primitives in the DDX-layer, or whatever that was called then. So did the Voodoo3's! Independently of that Glide stuff for 3D.
Was there a top-down push? In general, people on average never really actually liked CRT displays all that much. They are annoyingly deep; they are heavy; the screen is flickery, or not quite pin sharp, or both; they use up a lot of power; they fail in annoying ways, and they're expensive to fix - and they have magnets in them.
Only SD CRTs make an audible shrieking sound. LCD computer monitors were replacing VGA or better CRTs with a horizontal refresh rate of >30kHZ. Maybe they could annoy your dog but no human could hear it.
I still use a 130kHz CRT monitor sometimes. There's no 15kHz whine, but there's audible harmonics. It depends what you're looking at at and how hard you're pushing it.
To buyers as well. I don't recall the switch to LCDs being particularly pushed, though I was admittedly quite young at the time. Especially keep in mind that people today are generally comparing the absolute top-tier of CRTs which were not what the average person had.
(Another thing to keep in mind is that the systems of the time generally could not drive the kinds of resolutions and framerates that make those CRTs shine in some of today's comparisons. At the time the difference in quality in practice was lower because of this)
> (Another thing to keep in mind is that the systems of the time generally could not drive the kinds of resolutions and framerates that make those CRTs shine in some of today's comparisons. At the time the difference in quality in practice was lower because of this)
For desktop applications, the systems could. For 3D games, keep in mind that CRTs (in opposite to flat screens) could also diplay every other supported resolution sharply. The reason why many people think that CRTs were worse in practice is that many graphics cards of the time simply had a low-quality VGA signal generators built-in.
I owned a 17-inch Trinitron and very much preferred it over the early slow and small LCD panels. I did get a 15-inch Samsung VGA LCD panel for free later, but only kept it as a LAN party display as it folded completely flat for storage and transport.
That thing was at least Trinitron equivalent, if not better, because it lacked the thin wires holding the mask from within.
Now you are talking about the start of all that, OFC there were bad and cheap ones, but there was also very good stuff from the beginning by Eizo, Sharp, NEC, and many more.
I had multiple mediocre-to-crappy CRTs in the 90s and 00s and was glad to move away from them. I think the last one I owned was even one of the fabled trinitrons, and it was acceptable.
Yeah i had a trinitron and i still had bloodshot eyes after a few hours that i never got with LCD screens. Everyone was aware that CRTs sucked terribly for eye strain.
The tradeoffs moving to even the early LCDs was well worth it. I remember people spending effectively double on LCDs at the time over higher specced and larger CRTs and being delighted with the result. eg. early LCDs were just 14inch, low res, low refresh rates when you could get a 17inch CRT higher specced in every way. People were still opting for the early LCDs. Your eyes are important!
Now that you mention it, 60Hz was considered poor on a CRT. 85 was the target.
But that was because of flicker. AFAIK, 60Hz video frame rate was considered acceptable, but on a CRT the video frame rate was also the flicker rate and 60Hz was too low for flicker.
Almost laser pointer brightness at one point on the screen which you don't consciously see because the your eyes and the hold the image for a few milliseconds but do you really want to be looking at a extremely bright point of light all day. Higher refresh rates on CRTs lowered eye strain since that point could be effectively lower brightness, just refreshing twice as fast.
I honestly don't get eye strain on LCDs nearly as bad under any circumstance. 60hz LCD was a massive improvement over the 120hz CRTs.
CRT flicker is equally visible when frame rate is the same as refresh rate as when it differs. 60Hz CRTs were never good. 60Hz was only considered "acceptable" because people didn't know any better at the time. At least you didn't suffer with 50Hz CRTs using the same fast phosphors like the PAL regions did.
For Windows users looking to save space, there's Compactor[1] that uses the NTFS built-in compression opportunistically for only those files that benefit from it. It is not a deduplicator but the basic idea is the same: take an underutilized OS feature and make it usable.
Pretty handy when your flight sim game takes 1.2 terabytes with most of that being sparse terrain mesh data and uncompressed textures. Compressing the whole directory would take over a day according to Microsoft and their infamous progress bar; Compactor gets it done in fifteen minutes.
I've solved this by running thin bash script wrappers that keep the workflow SVN-like with a root directory that contains per-branch directories and a hidden bare repo).
reply