@dmitriid Caching may help with not having to reload those 15MB via the network. But still the browser has to parse some of that JS, possibly quite some. And even "just" a few MB of code to parse unnecessarily is utterly irresponsible. A waste of user time and a waste of energy.
Password Inception. Remember attention to detail? Password was an app people have been begging for for like 10 years and it feels like they threw it together in a weekend. BTW, if you try to autofill one level deeper, it freaks out and you lose the password popover until you restart Passwords.
Alternative universe where capital letters were stored in bottom case and small ones in the top one, so we would develop naming “THIS” lower-case and “this” upper-case
Anyone know what the idea of the first screen is? Whatever you choose, you go to the configurator next, where you can configure anything anyway (second screen).
Actually, it only goes up, so from the leftmost you can get to any configuration, but from the right only to more expensive ones (but they are still the same)
Is it some psychological trick? Like an illusion of choice or smth?
@nikitonsky The idea of the first screen is you get a high level comparison between major models (size, CPU gen.) where the second screen is for configuring your package within that selection, even if you can change that selection from the second
@nikitonsky I think the left one is for the people on a budget. They can quickly see a bunch of configurations with prices right away. The right one is another chance for upsell and for the people who’s not constrained by money and more feature-oriented, know what they want.
@nikitonsky The first screen shows the base configurations. These are the models/prices you see online or at any dealership. They are usually available in stock.
The second screen is where upselling happens. Any hardware modifications you make there, will make it a built-to-order (BTO), causing not only the price go up but also the shipping date.
Fun fact: even authorized dealers need to go through that second page (behind a login), if they want to sell anything else than the base models.
Would anybody care about an "Introduction to Quaternions" article, or are there enough of them on the internet already? I'm thinking of deriving everything up to rotations and slerp in a beginner-friendly-but-still-precise way.
Unfortunately it is an hour long video of a powerpoint presentation so referring back to it is a pain. A text form article that takes notes from this would be amazing to have!
I just realized this absolute banger of a UI, being in Russian, might have escaped wider audiences, so I translated it for you. Originally seen in Yandex.Plus
Founded in 1974, Tandem Computers was a leader in high-availability computing. For decades, if you had an application that absolutely could not tolerate unplanned downtime -- a bank, a stock exchange, a telephone network -- Tandem's "NonStop" computers were aimed at you.
NonStop machines achieved reliability through massive hardware redundancy. A NonStop computer was a cluster of computing modules, each with its own processors, memory, disks. A failure in one couldn't affect the others.
Redundancy made Tandem. So naturally, when they made some coffee mugs, it was important that they feature redundancy too.
Founded in 1974, Tandem Computers was a leader in high-availability computing. For decades, if you had an application that absolutely could not tolerate unplanned downtime -- a bank, a stock exchange, a telephone network -- Tandem's "NonStop" computers were aimed at you.
NonStop machines achieved reliability through massive hardware redundancy. A NonStop computer was a cluster of computing modules, each with its own processors, memory, disks. A failure in one couldn't affect the others.
@jalefkowit Around time of the failed ports of NSK to Alpha and then to Itanium, the redundancy switched from being hardware lockstep to firmware. (None of the commodity processors support lockstep.)
The NSK product line and most of the HP “server” business (and whatever little was left of DEC) was eventually ceded to HPE.
Here is some info on the post-Tandem-hardware commodity designs, from 2008:
@jalefkowit
I encountered Tandem during my 6+ year tenure in the banking industry. Some banks in my country still use these systems, because of the high reliability required.
The SwiftUI/shader method was a bit of a dead-end since it would've meant I had to make a fake Mac window from scratch and then apply the shader. Which is silly and goofy and dumb.
But you know what's even goofier and dumber but more efficient? Abusing private APIs like CGSSetWindowWarp. Making good progress here.
The SwiftUI/shader method was a bit of a dead-end since it would've meant I had to make a fake Mac window from scratch and then apply the shader. Which is silly and goofy and dumb.
But you know what's even goofier and dumber but more efficient? Abusing private APIs like CGSSetWindowWarp. Making good progress here.
btw the window remains almost fully interactive, this does break hit testing for the title bar (but not close/maximize/minimize buttons) and it jumps if you do manage to start dragging it
@dmitriid I'm no fan of Jira, but to be fair to them a lot of these scripts look like they are coming from browser extensions.
If you try this again in a private window (ie. without extensions), do you see the same thing?
@dmitriid Atlassian is preparing the next billing concept: By traffic… 🤓
@dmitriid Caching may help with not having to reload those 15MB via the network. But still the browser has to parse some of that JS, possibly quite some. And even "just" a few MB of code to parse unnecessarily is utterly irresponsible. A waste of user time and a waste of energy.