At this rate Netflix isn’t building a streaming service, it’s building a monopoly starter pack. Give it a few more acquisitions and the “Are you still watching?” prompt will legally qualify as a government notice.
I was flabbergasted driving a 2023 Honda Civic Sport during a trip to Thailand, easily one of the best-balanced cars I’ve driven. Makes me wonder if that model is using the same engine they’re talking about here
Depends on the engine. They had an option for a turbo 1.5l l15 and a 2l k20. Plus a few others I don't know were offered in usdm. No idea about Thailand but if it wasn't a 2 liter, I think it was not a k series.
In a very niche form of motorsport, the civic sport is top in class for a lower tier Street class with the SI being top of another lower tier Street class.
This is fascinating work. Right now it’s mostly focused on near-death experiences, but I’d love to see it grow into a broader map of spirituality, consciousness studies, and related fields. The visual approach has a lot of potential once more domains are added.
Thank you! Yes I want to add more data from different fields and see how the they relate. Possibly Erowid DMT experiences as well since they have a lot of similarities with OBEs.
So hair grows by pulling itself upward? Perfect. I’m just going to stand under a ceiling fan and wait for my hair to pull itself back onto my bald spots. Science has finally given me a plan.
Walrus isn’t trying to replace Kafka, but it does beat Kafka in a few narrow areas. It’s a lightweight Rust-based distributed log with a fast WAL engine and modern I/O (io_uring), so the operational overhead is much lower than running a full Kafka stack. If you just want a simple, fast log without JVM tuning, controllers, or the entire Kafka ecosystem, Walrus is a lot easier to run. Kafka still wins on ecosystem, connectors, and massive scale, but Walrus is appealing for teams that want the core idea without the complexity. Really impressed by the direction here, great work!!.
For this use case it makes sense. cJSON is a general-purpose library, but Redis only needs fast access to a few top-level fields for filters. A tiny purpose-built parser that avoids allocations and skips building a full tree will naturally beat a generic JSON parser here. It’s not “better than cJSON” in general, just better for this very narrow hot path.
I agree with you on SSDs, that was the last upgrade that felt like flipping the “modern computer” switch overnight. Everything since has been incremental unless you’re doing ML or high-end gaming.
I know it's not the same. But I think a lot of people had a similar feeling going from Intel-Macbooks to Apple Silicon. An insane upgrade that I still can't believe.
This. My M1 MacBook felt like a similarly shocking upgrade -- probably not quite as much as my first SSD did, but still the only other time when I've thought, "holy sh*t, this is a whole different thing".
The M1 was great. But the jump felt particularly great because Intel Macbooks had fallen behind in performance per dollar. Great build quality, great trackpad, but if you were after performance they were not exactly the best thing to get
For as long as I can remember, before M1, Macs were always behind in the CPU department. PC's had much better value if you cared about CPU performance.
After the M1, my casual home laptop started outperforming my top-spec work laptops.
> For as long as I can remember, before M1, Macs were always behind in the CPU department. PC's had much better value if you cared about CPU performance.
But not if you cared about battery life, because that was the tradeoff Apple was making. Which worked great until about 2015-2016. The parts they were using were not Intel’s priority and it went south basically after Broadwell, IIRC. I also suppose that Apple stopped investing heavily into a dead-end platform while they were working on the M1 generation some time before it was announced.
It's a lot more believable if you tried some of the other Wintel machines at the time. Those Macbook chassis were the hottest of the bunch, it's no surprise the Macbook Pro was among the first to be redesigned.
I usually use an M2 Mac at work, and haven't really touched Windows since 2008. Recently I had to get an additional Windows laptop (Lenovo P series) for a project my team is working on, and it is such a piece of shit. It's unfathomable that people are tolerating Windows or Intel (and then still have the gall to talk shit about Macs).
It's like time travelling back to 2004. Slow, loud fans, random brief freezes of the whole system, a shell that still feels like a toy, a proprietary 170W power supply and mediocre battery life, subpar display. The keyboard is okay, at least. What a joke.
Meanwhile, my personal M3 Max system can render Da Vinci timelines with complex Fusion compositions in real time and handle whole stacks of VSTs in a DAW. Compared to the Lenovo choking on an IDE.
A lot of this is just windows sucking major balls. Linux distros with even the heaviest DEs like KDE absolutely fly on mediocre or even low range hardware.
I got a lunar lake laptop and slapped fedora on it and everything is instant. And I hooked up 2 1400p/240hz over thunderbolt.
Expensive PCs are also crap. My work offers Macbooks or Windows laptops (currently, Dell, but formerly Lenovo and/or HP), and these machines are all decidedly not 'cheap' PCs. Often retailing in excess of $2k.
All my coworkers who own Windows laptops do is bellyache about random issues, poor battery life, and sluggish performance.
I used to have a Windows PC for work about 3 years ago as well, and it was also a piece of crap. Battery would decide to 'die' at 50% capacity. After replacement, 90 minute battery life off charger. Fan would decide to run constantly if you did anything even moderately intensive such as a Zoom meeting.
To me that reads 3x, not "almost 10x". The main differrence here is probably power. A desktop/server is happy to send 15W to the SSD and hundreds of watts to the CPU, while a laptop wants the SSD running in the ~1 watt range and the CPU in the 10s of watts range.
There's over twice as much content in the first test. It's around 3.8gb/s vs 30gb/s if you divide both folder size and both du durations. That makes it 7.9 times faster and I'm comfortable calling this "almost 10 times".
The total size isn't what matters in this case but rather the total number of files/directories that need to be traversed (and their file sizes summed).
I thought so too on my mini PC. Then I got myself my current Mac mini M4 and I have to give it to Apple, or maybe in part to ARM... It was like another SSD moment. It's still not spun up the fan and run literally lukewarm at most my office, coding and photo work.
The only time I had this other than changing to SSD was when I got my first multi-core system, a Q6600 (confusingly labeled a Core 2 Quad). Had a great time with that machine.
"Core" was/is like "PowerPC" or "Ryzen", just a name. Intel Core i9, for instance, as opposed to Intel Pentium D, both x86_x64, different chip features.
When RAM gets so expensive that even Samsung won’t buy Samsung from Samsung, you know the market has officially entered comic mode. At this rate their next quarterly report is just going to be one division sending the other an IOU.
Overleverage / debt, and refusing to sell at a certain price, are actually very different things though. OpenAI might be a tire fire, but Samsung is the gold pan seller here, and presumably has an excellent balance sheet.
A lot of the time it’s less “nobody checked the security inbox” and more “the one person who understands that part of the system is juggling twelve other fires.” Security fixes are often a one-hour patch wrapped in two weeks of internal routing, approvals, and “who even owns this code?” archaeology. Holiday schedules and spam filters don’t help, but organizational entropy is usually the real culprit.
> A lot of the time it’s less “nobody checked the security inbox” and more “the one person who understands that part of the system is juggling twelve other fires.”
At my past employers it was "The VP of such-and-such said we need to ship this feature as our top priority, no exceptions"
I've once had a whole sector of a fintech go down because one DevOps person ignored daily warning emails for three months that an API key was about to expire and needed reset.
And of course nobody remembered the setup, and logging was only accessible by the same person, so figuring out also took weeks.
I'm currently on the other side of this trying to convince management that the maintenance that should have been done 3 years ago needs to get done. They need "justification".
Write a short memo that saying you are very concerned, and describe a range of things that may happen (from "not much" over medium to maximum scare - lawsuits, brand/customer trust destroyed etc.).
Email the memo to a decision maker with the important flag on and CC: another person as a witness.
If you have been saying it for a long time and nobody has taken any action, you may use the word "escalation" as part of the subject line.
If things hit the fan, it will also make sure that what drops from the fan falls on the right people, and not on you.
It could also be someone "practicing good time management."
They have a specific time of day, when they check their email, and they only give 30 minutes to that time, and they check emails from most recent, down.
The email comes in, two hours earlier, and, by the time they check their email, it's been buried under 50 spams, and near-spams; each of which needs to be checked, so they run out of 30 minutes, before they get to it. The next day, by email check time, another 400 spams have been thrown on top.
Think I'm kidding?
Many folks that have worked for large companies (or bureaucracies) have seen exactly this.
I get the frustration, but I think the npm option actually makes sense here. A lot of users who’d benefit from a fast Rust tool aren’t Rust developers and won’t have Cargo installed. Shipping it through npm lowers the barrier while still giving everyone the performance benefits. It’s not a knock on Cargo, just a way to make the tool more accessible.
Given the fairly shoddy security story with NPM, I genuinely don't understand the hesitation to publish a binary and have a README instruction to curl/wget it into `/usr/local/bin` or `~/.local/bin`. If it's going through NPM that publishing step has to be done already, unless the NPM build is pulling down rust to compile it all as a native extension.
Eventually it'd wangle it's way into homebrew or the unstable branch of another package registry.
But that's me, because I really dislike installing binaries via a language's package manager, because they don't get updated unless I frequently run the upgrade commands for each package manager.
Thing is… who is regularly running `npm update` or `cargo update` to keep local software up to date?
I wouldn’t, because I might be in a repo and it starts upgrading all my local dependencies, and I’m not gonna add a text editor as a dev dependency. I’ll happily take the binary, or a tar.gz with the binary in it, though.
(Btw I love how it’s following the old DOS aesthetic)
> who is regularly running `npm update` or `cargo update` to keep local software up to date?
I do, religiously, as part of my routine to check for updates.
n lts && npm uninstall -g corepack && npm update -g && n prune
Sometimes things break (that's how `npm uninstall -g corepack` became a part of my one-liner), but it is easier to update often than to neglect updates for years.
I'm in the same boat as a JS/TS developer for years to get used to npm install the recent AI command line tools under global scope, it's really weired. Personally I don't event install front end toolchains global as almost all of them work under project scope.
But I totally get the idea behind this, it's greatly combined with the cargo toolchain and is widely installed than cargo (which by the way npm is much easier to install than cargo with my personal experience), npm handles update nicely, and it can handle multiple arch too. I would still prefer npm install because I have installed a lot recently so it's ok.
Does it matter? You are apparently contemplating running a third-party binary on your machine anyway. It seems a bit weird to Worry about npm’s security story, which is all about executing arbitrary code.
Anything that uses npm is fundamentally untrustworthy. I would argue that if you make an editor you should write software for people that want to use and write good software, which isn't anyone that unironically uses npm with anything other than distaste.
Many of them may not be Node developers either, and might not have npm installed. Using a dependency management tool for one language to distribute a packaged application written in an entirely different language seems like a very strange choice.
Why not use the various standard and commonplace packaging and distribution methods for application software? Distro repos, tarballs, Homebrew, AppImage, Flatpak, etc.
Not everyone it's a web developer. Sysadmin and system programmers (and older millenials) don't care and don't want to install anything related to NPM.
reply