All those real-time features are antipatterns that do nothing but create anxiety and a false sense of urgency. We use Slack at work, and the typing indicators/presence detection/etc. drive me (and many others) downright insane.
I agree that encryption in transit and rest are important, but there are open and verified solutions like Signal. It seems like extremely poor security hygiene to take Apple's word that their closed-source chat service is actually secure as they claim for it to be.
Those young people are probably doing themselves a favor by disassociating from peers who are shallow and prejudiced enough to exclude someone for, of all things, not using a specific (proprietary!) chat app.
Beeper has caught a ton of media attention in recent weeks but I truly do not understand it. The SMS protocol has been around for decades and works perfectly fine with iPhones. If you want rich media and other bells and whistles, use WhatsApp. How often does someone whine so loudly about insisting on using the closed, Apple-proprietary protocol that their friends need to pay a monthly subscription for a third party interop app?
You and I live in completely different worlds. I will absolutely not complete a purchase if your website is unusable.
In fact, this happened last week--I was trying to purchase a plane ticket and the animations were so excessive and poorly done that it obscurbed a form field that made it impossible to book the ticket. I bounced and booked a ticket from a competing airline.
> Both errors will be mapped into the same Failed to fetch JavaScript error, so we can’t rely on the error type, but we can perform a timing attack. Local networks are fast, so the valid mDNS hostname registered in the network will be resolved in a reasonable time frame, which is significantly faster than the default connection timeout. In the example above, the difference is four milliseconds for a valid address versus five seconds for an invalid one.
This isn't really a "timing attack." A timing attack implies exploitation of an unintended behavior by executing something at some specific time. This just sounds like a workaround for the fact that the Javascript API doesn't expose a way to detect a hostname resolution error, which really should exist.
Python is just the web server. All the truly performance-sensitive components--edge proxy, load balancers, backend services, databases, caches, and storage services--are mostly C++.
There's a ton of hidden bias in this assessment. Have you considered that you either live in a wealthy area or are surrounded by people who are more prone to seeing having iDevices as a status symbol? Because
> People said the AirPods Max were overpriced, and I see it all the time in co-work spaces and libraries.
Is absolutely not true in my experience.
> People said the M1 Pros were overpriced; they're literally everywhere, used by almost all of the professionals I know.
And how many of those laptops are corporate assets that were provided by their employer? How many of those professionals actually use Macs anywhere outside of work?
I'm surprised Docker Desktop drives so much revenue. As far as I know, it is a Mac and Windows-specific tool.
Are FAANG and FAANG-like developers not using Linux machines locally despite deploying production software on Linux servers? Even for enterprise developers who use Mac and Windows, isn't 99% of day-to-day development on a Linux box you SSH into anyways?
I've never really quite grasped the need for Docker Desktop.
A lot of people are claiming that ghostty is "faster." I watched the lightning talk where the author claims that catting files and binaries is faster.
I tried this against ghostty itself after building with zig build -Doptimize=ReleaseFast, using: time cat ghostty.
In GNOME terminal, it took 3.340s. In ghostty, it took 16.947s. I must be doing something wrong?