10 interesting stories served every morning and every evening.
Skip to content
You signed in with another tab or window. Reload to refresh your session.
You signed out in another tab or window. Reload to refresh your session.
You switched accounts on another tab or window. Reload to refresh your session.
You must be signed in to star a gist
You must be signed in to fork a gist
Embed this gist in your website.
Save bretonium/291f4388e2de89a43b25c135b44e41f0 to your computer and use it in GitHub Desktop.
Embed this gist in your website.
Save bretonium/291f4388e2de89a43b25c135b44e41f0 to your computer and use it in GitHub Desktop.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
You can’t perform that action at this time.
...
Read the original on gist.github.com »
There is a certain kind of computer review that is really a permission slip. It tells you what you’re allowed to want. It locates you in a taxonomy — student, creative, professional, power user — and assigns you a product. It is helpful. It is responsible. It has very little interest in what you might become.
The MacBook Neo has attracted a lot of these reviews.
The consensus is reasonable: $599, A18 Pro, 8GB RAM, stripped-down I/O. A Chromebook killer, a first laptop, a sensible machine for sensible tasks. “If you are thinking about Xcode or Final Cut, this is not the computer for you.” The people saying this are not wrong. It is also not the point.
Nobody starts in the right place. You don’t begin with the correct tool and work sensibly within its constraints until you organically graduate to a more capable one. That is not how obsession works. Obsession works by taking whatever is available and pressing on it until it either breaks or reveals something. The machine’s limits become a map of the territory. You learn what computing actually costs by paying too much of it on hardware that can barely afford it.
I know this because I was running Final Cut Pro X on a 2006 Core 2 Duo iMac with 3GB RAM and 120GB of spinning rust. I was nine. I had no business doing this. I did it every day after school until my parents made me go to bed.
The machine came as a hand-me-down from my nana. She’d wiped it, set it up in her kitchen in Massachusetts. It was one software update away from getting the axe from Apple. I torrented Adobe CS5 the same week. Downloaded Xcode and dragged buttons and controls around in Interface Builder with no understanding of what I was looking at. I edited SystemVersion.plist to make the “About this Mac” window say it was running Mac OS 69, which is the s*x number, which is very funny. I faked being sick to watch WWDC 2011 — Steve Jobs’ last keynote — and clapped alone in my room when the audience clapped, and rebuilt his slides in Keynote afterward because I wanted to understand how he’d made them feel that way.
I knew the machine was wrong for what I wanted to do with it. I didn’t care. Every limitation was just the edge of something I hadn’t figured out yet. It was green fields and blue skies.
I thought about all of this when I opened the Neo for the first time.
What Apple put inside the Neo is the complete behavioral contract of the Mac. Not a Mac Lite. Not a browser in a laptop costume. The same macOS, the same APIs, the same Neural Engine, the same weird byzantine AppKit controls that haven’t meaningfully changed since the NeXT era. The ability to disable SIP and install some fuck-ass system modification you saw in a YouTube tutorial. All of it, at $599.
They cut the things that are, apparently, not the Mac. MagSafe. ProMotion. M-series silicon. Port bandwidth. Configurable memory. What remains is the Retina display, the aluminum, the keyboard, and the full software platform. I held it and thought, “yep, still a Mac.”
Yes, you will hit the limits of this machine. 8GB of RAM and a phone chip will see to that. But the limits you hit on the Neo are resource limits — memory is finite, silicon has a clock speed, processes cost something. You are learning physics. A Chromebook doesn’t teach you that. A Chromebook’s ceiling is made of web browser, and the things you run into are not the edges of computing but the edges of a product category designed to save you from yourself. The kid who tries to run Blender on a Chromebook doesn’t learn that his machine can’t handle it. He learns that Google decided he’s not allowed to. Those are completely different lessons.
Somewhere a kid is saving up for this. He has read every review. Watched the introduction video four or five times. Looked up every spec, every benchmark, every footnote. He has probably walked into an Apple Store and interrogated an employee about it ad nauseam. He knows the consensus. He knows it’s probably not the right tool for everything he wants to do.
He has decided he’ll be fine.
This computer is not for the people writing those reviews — people who already have the MacBook Pro, who have the professional context, who are optimizing at the margin. This computer is for the kid who doesn’t have a margin to optimize. Who can’t wait for the right tool to materialize. Who is going to take what’s available and push it until it breaks and learn something permanent from the breaking.
He is going to go through System Settings, panel by panel, and adjust everything he can adjust just to see how he likes it. He is going to make a folder called “Projects” with nothing in it. He is going to download Blender because someone on Reddit said it was free, and then stare at the interface for forty-five minutes. He is going to open GarageBand and make something that is not a song. He is going to take screenshots of fonts he likes and put them in a folder called “cool fonts” and not know why. Then he is going to have Blender and GarageBand and Safari and Xcode all open at once, not because he’s working in all of them but because he doesn’t know you’re not supposed to do that, and the machine is going to get hot and slow and he is going to learn what the spinning beachball cursor means. None of this will look, from the outside, like the beginning of anything. But one of those things is going to stick longer than the others. He won’t know which one until later. He’ll just know he keeps opening it.
That is not a bug in how he’s using the computer. That is the entire mechanism by which a kid becomes a developer. Or a designer. Or a filmmaker. Or whatever it is that comes after spending thousands of hours alone in a room with a machine that was never quite right for what you were asking of it.
He knows it’s probably not the right tool. It doesn’t matter. It never did.
The reviews can tell you what a computer is for. They have very little interest in what you might become because of one.
...
Read the original on samhenri.gold »
FARGO — A grandmother from Tennessee is working to get her life back after what she says was a case of mistaken identity that nearly cost her everything.
Angela Lipps spent nearly six months in jail after Fargo police connected her to a bank fraud case in the metro.
It’s a crime she says she didn’t commit. In fact, she said she’s never been to North Dakota.
Lipps, 50, is the mother of three grown children and has five grandchildren, spending nearly her entire life in north-central Tennessee. The extent of her travels is limited to neighboring states.
She’s never been on an airplane in her life.
That changed last summer when police flew her to North Dakota to face criminal charges after facial recognition showed she was the main suspect in what Fargo police called an organized bank fraud case.
“It was so scary, I can still see it in my head, over and over again,” Lipps said.
It was July 14, the day a team of U. S. Marshals arrested Lipps at her home in Tennessee. She said she was taken away at gunpoint while babysitting four young children. She was booked into her county jail in Tennessee as a fugitive from justice from North Dakota.
“I’ve never been to North Dakota, I don’t know anyone from North Dakota,” Lipps said.
Lipps would sit in that Tennessee jail cell for nearly four months. As a fugitive, she was held without bail. Lipps learned, following a Fargo Police Department investigation, she had been charged with four counts of unauthorized use of personal identifying information and four counts of theft in North Dakota.
In Tennessee, she was given a court appointed lawyer for the extradition process. To fight the charges, she was told she would have to go to North Dakota.
Through an open records request, WDAY News obtained the Fargo police file in this case. In April and May 2025, detectives were investigating several bank fraud cases. A woman is seen using a fake U. S. Army military I.D. card to withdraw tens of thousands of dollars.
In an effort to help identify the woman in the surveillance video, court documents show Fargo police used facial recognition software. The software identified the person as Angela Lipps. According to the court documents, the Fargo detective working the case then looked at Lipps’ social media accounts and Tennessee driver’s license photo.
In his charging document, the detective wrote that Lipps appeared to be the suspect based on facial features, body type and hairstyle and color.
Lipps told WDAY News that no one from the Fargo Police Department ever called to question her.
Officers from North Dakota did not pick up Lipps from her jail cell in Tennessee until Oct. 30 — 108 days after her arrest. The next day she made her first appearance in a North Dakota courtroom to fight the charges.
“If the only thing you have is facial recognition, I might want to dig a little deeper,” said Jay Greenwood, the lawyer representing Lipps in North Dakota.
Greenwood immediately asked Lipps for her bank records. Once they were in hand, Fargo police met with him and Lipps at the Cass County jail on Dec. 19. She had already been in jail for more than five months. It was the first time police interviewed her.
Her bank records showed she was more than 1,200 miles away, at home in Tennessee at the same time police claimed she was in Fargo committing fraud.
“Around the same time she’s depositing Social Security checks … she is buying cigarettes at a gas station, around the same time, she is buying a pizza, she is using a cash app to buy an Uber Eats,” Greenwood said.
On Christmas Eve, five days after the interview with Fargo police, the case was dismissed, and she was released from jail.
But, Lipps was now stranded in Fargo.
“I had my summer clothes on, no coat, it was so cold outside, snow on the ground, scared, I wanted out but I didn’t know what I was going to do, how I was going to get home,” Lipps said.
Fargo police did not cover Angela’s expenses to get home after her release from jail. Local defense attorneys gave her money to pay for a hotel room and food on Christmas Eve and Christmas Day.
The day after Christmas, F5 Project founder Adam Martin drove Lipps to Chicago so she could get home to Tennessee. Fargo-based F5 Project is an organization providing services and resources to individuals struggling with incarceration, mental health and addiction.
“I’m just glad it’s over. I’ll never go back to North Dakota,” Lipps said.
For more than a week, WDAY News tried to arrange an on camera interview with Fargo Police Chief David Zibolski to discuss the case. Through a spokesperson the chief declined an on-camera interview. WDAY News brought the issue up on Wednesday, March 11, at Zibolski’s retirement news conference.
“Why did nobody from Fargo Police ever speak with Angela Lipps for the five months she was in jail?” Zibolski was asked.
“Thank you, Matt (Henson), for that question but we are not here to talk about that today,” Zibolski replied.
Lipps is back home in Tennessee now, but is still feeling the impact from the incident. She told WDAY News that no one from the Fargo Police Department has apologized for the incident.
Unable to pay her bills from jail, she lost her home, her car and even her dog.
Fargo police say the bank fraud case is still under investigation and no arrests have been made.
...
Read the original on www.grandforksherald.com »
Willingness to look stupid is a genuine moat in creative workEvery Sunday I go to a coffee shop in Japantown with my laptop to write. And I write! I have no trouble writing. The writing isn’t the problem. The problem is that when I’m done, I look at what I just wrote and think this is definitely not good enough to publish. This didn’t use to happen. A few years ago I used to publish all the time. I’d write something, feel pretty good about it, and then hit publish without a second thought. I knew nobody really cared about what I was writing, so it didn’t matter if it sucked. And honestly, a lot of what I wrote really did suck. But I published it anyway. And yet I’d somehow occasionally write a good post.Fast forward to today: I have no trouble writing, but I’ve now developed this fear of hitting publish. I’m older and objectively a better writer, with supposedly better ideas. So where did things go wrong? Why’s it so much harder to share my ideas now?1.
There’s this unfortunate pattern that happens when someone wins a Nobel Prize. They tend to stop doing great work. Richard Hamming talks about this in You and Your Research:When you are famous it is hard to work on small problems. This is what did Shannon in. After information theory, what do you do for an encore? The great scientists often make this error. They fail to continue to plant the little acorns from which the mighty oak trees grow. They try to get the big thing right off. And that isn’t the way things go. So that is another reason why you find that when you get early recognition it seems to sterilize you. In fact I will give you my favorite quotation of many years. The Institute for Advanced Study in Princeton, in my opinion, has ruined more good scientists than any institution has created, judged by what they did before they came and judged by what they did after. Not that they weren’t good afterwards, but they were superb before they got there and were only good afterwards.Before the Nobel Prize, nobody really cares who you are. But after the Nobel Prize, you’re a Nobel Prize winner, and Nobel Prize winners are supposed to have Good Ideas. Every idea, every paper, every talk at a conference is now being evaluated against the standard of your Nobel Prize-winning work. Everyone is asking, “is this worthy of a Nobel laureate?” It’s a high bar to clear. So instead of trying and occasionally failing, they just… stop trying. The fear of making something bad is worse than producing nothing at all.¹2.
Many good ideas come from young and unproven people. The Macintosh team’s average age was 21. Most researchers at Xerox PARC were under 30. Some of the best research work I’ve seen at OpenAI has come from surprisingly young people. I don’t think young people are smarter than old people. I don’t think they work that much harder either. It mostly just seems that nobody really expects much of young people, so they’re free to follow their curiosity into weird, silly, and seemingly-bad-but-actually-good ideas. They’re not afraid of looking stupid. Good Ideas, and I mean this in the broadest sense — research directions, startup ideas, premises for a novel — almost always sound stupid at first. They often make the person who came up with them look stupid. So if a truly Good Idea always starts out by looking unserious, then the only way to have one is to get comfortable producing stupid things.3.
A few weeks ago my friend Aadil and I were at Whole Foods buying a birthday cake for a friend. We wanted to write something clever on the cake but couldn’t really think of anything. We stood around thinking for a few minutes before Aadil said “Let’s just say a bunch of bad ideas out loud so we can get to the good ones.” And it worked! We all said a bunch of terrible ideas, and eventually we landed on a good one — a pretty clever pun based on our friend’s longtime email address.This sounds silly, but I think it captures the entire creative process well. You start by coming up with bad ideas. You will probably look stupid. That’s inevitable. But once you’re comfortable looking stupid, you can produce the bad ideas which will eventually lead to the good ones. If you don’t have the courage to look stupid, you’ll never reap the reward of having good ideas.It feels like there’s something like a conservation law at work here: the amount of stupidity you’re willing to tolerate is directly proportional to the quality of ideas you’ll eventually produce. I’ll call this Aadil’s Law.4.
Yesterday, I visited the Monterey Bay Aquarium and could not stop thinking about the jellyfish exhibit. They are seriously weird creatures. Jellyfish have no bones, brains, teeth, or blood. Some are bioluminescent for reasons we don’t fully understand. They’re pretty much sacs of jelly contained within a thin membrane, drifting aimlessly at the mercy of ocean currents. Yet somehow, jellyfish have been around for over 500 million years. So by most definitions of evolutionary success, jellyfish are a great idea.But how was evolution able to get to the jellyfish? The evolutionary process is pretty simple: generate a ton of random mutations and then let natural selection filter them. The overwhelming majority of mutations end up being harmful or neutral. An exceedingly small fraction are beneficial. If you could somehow give evolution a sense of embarrassment, so if every time it produced a fish with no fins or a bird with no wings, it felt a deep sense of shame and promised to be more careful next time — evolution would no longer work. It needs to be able to explore the fitness landscape with bad traits in order to produce good traits, and this exploration requires a willingness to produce unfit organisms. The only way evolution could get to the jellyfish was by being willing to produce the countless jellyfish-adjacent organisms which went extinct.5.
There might be a good reason why smart people want to avoid looking stupid. I’ve spent a long time thinking about what this reason could be. The only plausible explanation is that our egos are fragile, and by not sharing any work at all, we never have to risk our egos being damaged. If we never share anything, then nothing bad can ever happen to us. But the flip side to protecting our egos is that we never end up making anything worthwhile.I think there are two very different failure modes here, each at an opposite end of the spectrum:Overshare, but look stupid: You have lots of ideas, and you share them indiscriminately. You look stupid because you don’t really care about what you share, and people eventually learn to tune you out.Undershare, but never do anything interesting: You have lots of ideas, but share almost none of them. You’re afraid of looking stupid, so the exceedingly few ideas that you do share end up being incredibly bland. You never look stupid, but this comes at the expense of never doing anything interesting ever again.Knowing myself, I’m definitely more at risk of undersharing my work. I’d also bet that the most people reading this blog post are prone to undersharing as well.6.
So where do we go from here? I think the answer is actually in that Whole Foods story. Aadil’s implicit goal was to “think of something clever to write on this cake” but none of us could do it because cleverness was the standard and none of our ideas met it. But when Aadil said “Let’s just say a bunch of bad ideas,” he changed the frame entirely. We were now playing a game where the only way to lose was by saying nothing at all.I think that’s the key here. Your goal shouldn’t be to share something good. It should just be to share something at all. Even if it isn’t good. A half-baked blog post. A silly demo. A weird project. I’ve been doing too much selection, and not enough production.7.
I keep thinking about the version of me from a few years ago. He was worse at almost everything. Worse writer, worse thinker, worse at making things. Nobody really knew him and nobody really cared what he had to say. And yet he had so much more courage. He’d write something in an afternoon and publish it that evening and go to bed feeling good about himself. He wasn’t performing for anyone. He was just a guy with a blog, putting his thoughts out into the world, mostly for himself. I miss that guy.Evolution didn’t get to the jellyfish by being careful. Aadil didn’t come up with a good cake idea by trying to be clever. I think it’s just about overcoming fear. Not a matter of talent, taste, or intelligence. Just this: are you willing to look stupid today? That’s it. That’s all there is to it.¹ My favorite counterexample to this is that Alec Radford (the researcher behind GPT-1) is still writing papers on cleaning pretraining data, arguably the most unglamorous thing you could work on in ML research in 2026.Most people will spend decades in chronic pain to avoid a few minutes of acute pain.Maybe making is about matteringWanting to matter might be the most honest reason to create anything.Sometimes the people who need invitations most are the ones who always decline them.The models are powerful as is. But where are the tools?
...
Read the original on sharif.io »
We’re thrilled to announce the stable release of Vite 8! When Vite first launched, we made a pragmatic bet on two bundlers: esbuild for speed during development, and Rollup for optimized production builds. That bet served us well for years. We’re very grateful to the Rollup and esbuild maintainers. Vite wouldn’t have succeeded without them. Today, it resolves into one: Vite 8 ships with Rolldown as its single, unified, Rust-based bundler, delivering up to 10-30x faster builds while maintaining full plugin compatibility. This is the most significant architectural change since Vite 2.
Vite is now being downloaded 65 million times a week, and the ecosystem continues to grow with every release. To help developers navigate the ever-expanding plugin landscape, we also launched registry.vite.dev, a searchable directory of plugins for Vite, Rolldown, and Rollup that collects plugin data from npm daily.
Play online with Vite 8 using vite.new or scaffold a Vite app locally with your preferred framework running pnpm create vite. Check out the Getting Started Guide for more information.
We invite you to help us improve Vite (joining the more than 1.2K contributors to Vite Core), our dependencies, or plugins and projects in the ecosystem. Learn more at our Contributing Guide. A good way to get started is by triaging issues, reviewing PRs, sending tests PRs based on open issues, and supporting others in Discussions or Vite Land’s help forum. If you have questions, join our Discord community and talk to us in the #contributing channel.
Stay updated and connect with others building on top of Vite by following us on Bluesky, X, or Mastodon.
Since its earliest versions, Vite relied on two separate bundlers to serve different needs. esbuild handled fast compilation during development (dependency pre-bundling and TypeScript/JSX transforms) that made the dev experience feel instant. Rollup handled production bundling, chunking, and optimization, with its rich plugin API powering the entire Vite plugin ecosystem.
This dual-bundler approach served Vite well for years. It allowed us to focus on developer experience and orchestration rather than reinventing parsing and bundling from scratch. But it came with trade-offs. Two separate transformation pipelines meant two separate plugin systems, and an increasing amount of glue code needed to keep the two pipelines in sync. Edge cases around inconsistent module handling accumulated over time, and every alignment fix in one pipeline risked introducing differences in the other.
Rolldown is a Rust-based bundler built by the VoidZero team to address these challenges head-on. It was designed with three goals:
* Performance: Written in Rust, Rolldown operates at native speed. In benchmarks, it is 10-30x faster than Rollup matching esbuild’s performance level.
* Compatibility: Rolldown supports the same plugin API as Rollup and Vite. Most existing Vite plugins work out of the box with Vite 8.
* Advanced features: A single unified bundler unlocks capabilities that were difficult or impossible with the dual-bundler setup, including full bundle mode, more flexible chunk splitting, module-level persistent caching, and Module Federation support.
The migration to Rolldown was deliberate and community-driven. First, a separate rolldown-vite package was released as a technical preview, allowing early adopters to test Rolldown’s integration without affecting the stable version of Vite. The feedback from those early adopters was invaluable. They pushed the integration through real-world codebases of every shape and size, surfacing edge cases and compatibility issues we could address before a wider release. We also set up a dedicated CI suite validating key Vite plugins and frameworks against the new bundler, catching regressions early and building confidence in the migration path.
In December 2025, we shipped the Vite 8 beta with Rolldown fully integrated. During the beta period, Rolldown itself progressed from beta to a release candidate, with continuous improvements driven by the testing and feedback of the Vite community.
During the preview and beta phases of rolldown-vite, several companies reported measurable reductions in production build times:
For large projects, the impact can be especially noticeable, and we expect further improvements as Rolldown continues to evolve.
With Vite 8, Vite becomes the entry point to an end-to-end toolchain with closely collaborating teams: the build tool (Vite), the bundler (Rolldown), and the compiler (Oxc). This alignment ensures consistent behavior across the entire stack, from parsing and resolving to transforming and minifying. It also means we can rapidly adopt new language specifications as JavaScript evolves. And by integrating deeply across layers, we can pursue optimizations that were previously out of reach, such as leveraging Oxc’s semantic analysis for better tree-shaking in Rolldown.
None of this would have been possible without the broader community. We want to extend our deep thanks to the framework teams (SvelteKit, React Router, Storybook, Astro, Nuxt, and many others) who tested rolldown-vite early, filed detailed bug reports, and worked with us to resolve compatibility issues. We are equally grateful to every developer who tried the beta, shared their build time improvements, and reported the rough edges that helped us polish this release. Your willingness to test the migration on real projects helped make the transition to Rolldown smoother and more reliable.
Vite 8 requires Node.js 20.19+, 22.12+, the same requirements as Vite 7. These ranges ensure Node.js supports require(esm) without a flag, allowing Vite to be distributed as ESM only.
Beyond the Rolldown integration, Vite 8 includes several notable features:
* Integrated Devtools: Vite 8 ships devtools option to enable Vite Devtools, a developer tooling for debugging and analysis. Vite Devtools provide deeper insights into your Vite-powered projects directly from the dev server.
* Built-in tsconfig paths support: Developers can enable TypeScript path alias resolution by setting resolve.tsconfigPaths to true. This has a small performance cost and is not enabled by default.
* emitDecoratorMetadata support: Vite 8 now has built-in automatic support for TypeScript’s emitDecoratorMetadata option, removing the need for external plugins. See the Features page for details.
* Wasm SSR support: .wasm?init imports now work in SSR environments, expanding Vite’s WebAssembly feature to server-side rendering.
* Browser console forwarding: Vite 8 can forward browser console logs and errors to the dev server terminal. This is especially useful when working with coding agents, as runtime client errors become visible in the CLI output. Enable it with server.forwardConsole, which activates automatically when a coding agent is detected.
Alongside Vite 8, we are releasing @vitejs/plugin-react v6. The plugin uses Oxc for React Refresh transform. Babel is no longer a dependency and the installation size is smaller.
For projects that need the React Compiler, v6 provides a reactCompilerPreset helper that works with @rolldown/plugin-babel, giving you an explicit opt-in path without burdening the default setup.
See the Release Notes for more details.
Note that v5 still works with Vite 8, so you can upgrade the plugin after upgrading Vite.
The Rolldown integration opens the door to improvements and optimizations. Here is what we are working on next:
* Full Bundle Mode (experimental): This mode bundles modules during development, similar to production builds. Preliminary results show 3x faster dev server startup, 40% faster full reloads, and 10x fewer network requests. This is especially impactful for large projects where the unbundled dev approach hits scaling limits.
* Raw AST transfer: Allows JavaScript plugins to access the Rust-produced AST with minimal serialization overhead, bridging the performance gap between Rust internals and JS plugin code.
* Native MagicString transforms: Enables custom transforms where the logic lives in JavaScript but the string manipulation computation runs in Rust.
* Stabilizing the Environment API: We are working to make the Environment API stable. The ecosystem has started regular meetings to better collaborate together.
We want to be transparent about changes to Vite’s install size. Vite 8 is approximately 15 MB larger than Vite 7 on its own. This comes from two main sources:
* ~10 MB from lightningcss: Previously an optional peer dependency, lightningcss is now a normal dependency to provide better CSS minification out of the box.
* ~5 MB from Rolldown: The Rolldown binary is larger than esbuild + Rollup mainly due to performance optimizations that favor speed over binary size.
We will continue monitoring and working to reduce install size as Rolldown matures.
For most projects, upgrading to Vite 8 should be a smooth process. We built a compatibility layer that auto-converts existing esbuild and rollupOptions configuration to their Rolldown and Oxc equivalents, so many projects will work without any config changes.
For larger or more complex projects, we recommend the gradual migration path: first switch from vite to the rolldown-vite package on Vite 7 to isolate any Rolldown-specific issues, then upgrade to Vite 8. This two-step approach makes it easy to identify whether any issues come from the bundler change or from other Vite 8 changes.
Please review the detailed Migration Guide before upgrading. The complete list of changes is in the Vite 8 Changelog.
As Vite moves to Rolldown, we want to take a moment to express our deep gratitude to the two projects that made Vite possible.
Rollup has been Vite’s production bundler since the very beginning. Its elegant plugin API design proved so well-conceived that Rolldown adopted it as its own, and Vite’s entire plugin ecosystem exists because of the foundation Rollup laid. The quality and thoughtfulness of Rollup’s architecture shaped how Vite thinks about extensibility. Thank you, Rich Harris for creating Rollup, and Lukas Taegert-Atkinson and the Rollup team for maintaining and evolving it into something that has had such a lasting impact on the web tooling ecosystem.
esbuild powered Vite’s remarkably fast development experience from its early days: dependency pre-bundling, TypeScript and JSX transforms that completed in milliseconds rather than hundreds. esbuild proved that build tools could be orders of magnitude faster, and its speed set the bar that inspired an entire generation of Rust and Go-based tooling. Thank you, Evan Wallace, for showing all of us what was possible.
Without these two projects, Vite would not exist as it does today. Even as we move forward with Rolldown, the influence of Rollup and esbuild is deeply embedded in Vite’s DNA, and we are grateful for everything they have given to the ecosystem. You can learn more about all the projects and people Vite depends on at our Acknowledgements page.
Vite 8 was led by sapphi-red and the Vite Team with the help of the wide community of contributors, downstream maintainers, and plugin authors. We want to thank the Rolldown team for their close collaboration in making the Rolldown-powered Vite 8 possible. We are also especially grateful to everyone who participated in the rolldown-vite preview and the Vite 8 beta period. Your testing, bug reports, and feedback made the Rolldown migration possible and shaped this release into something we are proud of.
Vite is brought to you by VoidZero, in partnership with Bolt and NuxtLabs. We also want to thank our sponsors on Vite’s GitHub Sponsors and Vite’s Open Collective.
...
Read the original on vite.dev »
The Iran war is reviving remote work across the world — from Denmark to VietnamAsia rolls out four-day weeks and work-from-home as emergency measures to solve a fuel crisis caused by Iran warBeijing’s dominance in rare earth processing leaves others scrambling to close the gap: ’China is the leader, and the U. S. is far behind’LIV Golf CEO Scott O’Neil on how stuck golfers got out of a besieged Gulf: ‘Precise planning, excellent resources and tremendous leadership’ and The Associated Press
‘This cannot be sustainable’: The U. S. borrowed $50 billion a week for the past five months, the CBO saysThe national debt isn’t $39 trillion. One economist says it’s actually $100 trillion’Proceed with caution’: Elon Musk offers warning after Amazon reportedly had mandatory meeting to address ‘high blast radius’ and AI-related incidentsThe U.S. Mint dropped the olive branch from the dime. What does that mean for the country?‘I don’t know if we’re ready’: Governors from each party appalled at 100-year-old federal workforce strategyMorgan Stanley warns an AI breakthrough Is coming in 2026 — and most of the world isn’t ready
© 2026 Fortune Media IP Limited. All Rights Reserved. Use of this site constitutes acceptance of our Terms of Use and Privacy Policy | CA Notice at Collection and Privacy Notice | Do Not Sell/Share My Personal Information
FORTUNE is a trademark of Fortune Media IP Limited, registered in the U. S. and other countries. FORTUNE may receive compensation for some links to products and services on this website. Offers may be subject to change without notice.
...
Read the original on fortune.com »
The sight of a delectable plate of lasagna or the aroma of a holiday ham are sure to get hungry bellies rumbling in anticipation of a feast to come. But although we’ve all experienced the sensation of “eating” with our eyes and noses before food meets mouth, much less is known about the information superhighway, known as the vagus nerve, that sends signals in the opposite direction — from your gut straight to your brain.
These signals relay more than just what you’ve eaten and when you are full. A new study in mice from researchers at Stanford Medicine and the Palo Alto, California-based Arc Institute has identified a critical link between the bacteria that live in your gut and the cognitive decline that often occurs with aging.
“Although memory loss is common with age, it affects people differently and at different ages,” said Christoph Thaiss, PhD, assistant professor of pathology. “We wanted to understand why some very old people remain cognitively sharp while other people see significant declines beginning in their 50s or 60s. What we learned is that the timeline of memory decline is not hardwired; it’s actively modulated in the body, and the gastrointestinal tract is a critical regulator of this process.”
The mouse study showed that the composition of the naturally occurring bacterial population that lives in the gut, known as the gut microbiome, changes with age — favoring some species of bacteria over others. These changes are registered by immune cells in the gastrointestinal tract, which spark an inflammatory response that hampers the ability of the vagus nerve to signal to the hippocampus — the part of the brain responsible for memory formation and spatial navigation. Stimulating the activity of the vagus nerve in older animals turned old, forgetful mice into whisker-sharp whizzes able to remember novel objects and escape from mazes as nimbly as their younger counterparts.
“The degree of reversibility of age-related cognitive decline in the animals just by altering gut-brain communication was a surprise,” Thaiss said. “We tend to think of memory decline as a brain-intrinsic process. But this study indicates that we can enhance memory formation and brain activity by changing the composition of the gastrointestinal tract — a kind of remote control for the brain.”
Thaiss, who is also a core investigator at Palo Alto-based Arc Institute, is a senior author of the study, which was published March 11 in Nature. Maayan Levy, PhD, an assistant professor of pathology and Arc Institute innovation investigator, is the other senior author. Timothy Cox, a graduate student at the University of Pennsylvania, is the lead author of the research.
“Our study emphasizes that processes in the brain can be modulated through peripheral intervention,” Levy said. “Since the gastrointestinal tract is easily accessible orally, modulating the abundance of gut microbiome metabolites is a very appealing strategy to control brain function.”
The call is coming from inside the body
The idea that hundreds of species of bacteria are nestled comfortably in our intestines used to be surprising. But the gut microbiome is experiencing a kind of media heyday as people realize that its function is critical to not just how we digest our food, but also to our overall health. A little more than a decade ago, researchers showed that tinkering with rodents’ gut microbiomes affected the animals’ social and cognitive behaviors. Thaiss and Levy wondered whether a similar process could be responsible for the memory loss and cognitive troubles often associated with aging.
Signals from inside the body to the brain — like those that travel from the intestines to the brain via the vagus nerve — are part of what’s called interoception. In contrast, signals from outside the body, conveyed primarily by the five senses of taste, touch, smell, vision and hearing, are called exteroception.
This study indicates that we can enhance memory formation and brain activity by changing the composition of the gastrointestinal tract — a kind of remote control for the brain.”
—Christoph Thaiss
“Exteroception is basically how we perceive the outside,” Thaiss said. “We have a lot of detailed knowledge about how this works. But we know much less about how the brain senses what is going on inside the body. We don’t know how many internal senses there are, or even all of what they are sensing. It’s clear that our exteroception capabilities decline with age — we grow to need eyeglasses and hearing aids, for example. And this study shows that aging also affects interoception.”
To test their theory that the gut microbiome plays a role in the “senior moments” many of us experience, the researchers housed young (2-month-old) mice together with old (18-month-old) mice. Living (and pooping) in close proximity exposed the young mice to the gut microbiomes of the old mice and vice versa. After one month, the researchers examined the compositions of the microbiomes of the old and young animals.
They found that the shared digs caused the microbiomes of the young mice to more closely resemble that of the older animals. When they compared the abilities of the mice to recognize a novel object, or to find the exit in a maze, the young mice with “old” microbiomes performed significantly more poorly than their peers — showing less curiosity about the unfamiliar object and bumbling about the maze in ways similar to that of old animals.
When the researchers compared young mice and old mice raised in a germ-free environment since birth (meaning neither group had gut bacteria), the young mice maintained their ability to form memories. But when they transplanted young, germ-free mice with microbiomes from old mice, the young mice again performed like older animals in the memory and cognition tests. Interestingly, the germ-free old mice did not experience a loss of memory and cognition as they aged, performing as well as 2-month-old animals.
Strikingly, treating young mice with “old” microbiomes (and, therefore, faltering cognitive abilities) with broad-spectrum antibiotics for two weeks restored the animals’ cognitive abilities, causing them to avidly investigate unfamiliar objects and scamper through the maze as well as their control peers.
“The object recognition test is like cognitive recognition tests in humans, where you are shown a series of images, then have to remember which ones you’ve seen before after some time passes,” Thaiss said. “And the maze test is like people trying to recall where they parked their car at a large shopping center. What these tasks have in common, in mice and in people, is that they are very strongly dependent on activity in the hippocampus, because that is where memories are encoded.”
What’s different in their guts?
Digging deeper, the researchers identified specific changes that occur in the composition of the gut microbiome of mice as they age. In particular, the relative abundance of a bacteria called Parabacteroides goldsteinii increases in old mice and is directly associated with cognitive decline in the animals. They showed that colonizing the guts of young mice with this bacterial species inhibited their performance on the object recognition and maze escape tasks, and that this deficit correlated with a reduction of activity in the hippocampus.
When they treated old mice with a molecule that activates the vagus nerve, however, the cognitive performance of the animals was indistinguishable from that of young animals.
Further experiments showed that the increasing prevalence of the Parabacteroides goldsteinii bacteria correlated with an increasing amount of metabolites called medium-chain fatty acids, and that these metabolites cause a group of immune cells in the gut called myeloid cells to initiate an inflammatory response. This inflammation inhibits the activity of the vagus nerve, the activity of the hippocampus and the ability to form lasting memories.
“The GI tract is arguably the first organ system to evolve during human evolutionary history, so the evolution of cognitive processes in the brain has undoubtedly been shaped by signals coming from the intestine,” Levy said.
“It’s likely that signals from the GI tract play an important role in contextualizing memory formation.”
Thaiss added, “Basically, we’ve identified a three-step pathway toward cognitive decline that starts with gastrointestinal aging and the subsequent microbial and metabolic changes that occur. The myeloid cells in the GI tract sense these changes, and their inflammatory response impairs the connection between the gut and the brain via the vagus nerve. This is a direct driver of memory decline. And if we restore the activity of the vagus nerve, we can restore an old animal’s memory function to that of a young animal.”
The researchers are now investigating whether a similar gut microbiome and brain activity pathway exists in humans, and whether it also contributes to age-related cognitive decline. Importantly, vagus nerve stimulation is approved by the Food and Drug Administration as a treatment for depression or epilepsy and to aid stroke recovery. The researchers are also interested in developing ways to non-invasively monitor, and perhaps even control, the activity of peripheral neurons to affect memory formation and cognition.
“Our hope is that ultimately these findings can be translated into the clinic to combat age-related cognitive decline in people,” Thaiss said.
Researchers from Monell Chemical Senses Center in Philadelphia; the University of California, Irvine; University College Cork, Ireland; Calico Life Sciences LLC; and the Children’s Hospital of Philadelphia contributed to the work.
The study was funded by the Arc Institute, the National Institutes of Health (grants NIH DK019525, T32AG000255, F30AG081097, T32HG000046, F30AG080958, DP2-AG-067511, DP2-AG-067492, DP1-DK-140021, R01-NS-134976 and R01-DK-129691), the Burroughs Wellcome Fund, the American Cancer Society, the Pew Scholar Award, the Searle Scholar Program, the Edward Mallinckrodt Jr. Foundation, the W. W. Smith Charitable Trust, the Blavatnik Family Fellowship, the Prevent Cancer Foundation, the Polybio Research Foundation, the V Foundation, the Kathryn W. Davis Aging Brain Scholar Program, the McKnight Brain Research Foundation, the Kenneth Rainin Foundation, the IDSA Foundation and the Human Frontier Science Program.
...
Read the original on med.stanford.edu »
We can go through most of our lives holding out hope of one day seeing in reality such works as van Gogh’s Sunflowers, Monet’s Haystacks, a clay tablet containing actual cuneiform writing with our own eyes, or the ancient Egyptian Temple of Dendur. We can actually come face to face — or rather, face to surface — with all of them, temple included, at New York’s Metropolitan Museum of Art, which contains all those and more artifacts of human civilization than any of us could hope to examine closely in a lifetime. But even if we did, we might only feel tempted to look at them more closely still, even to touch them. That may be an improbable hope, but we can at least get closer than ever now thanks to the Met’s new archive of high-definition 3D scans.
“Viewers can zoom in, rotate, and examine each model, bringing unprecedented access to significant works of art,” says the Met’s official announcement. “The 3D models can also be explored in viewers’ own spaces through augmented reality (AR) on most smartphone and VR headsets, as a resource for research, exploration, and curiosity.”
Highlights include “a marble sarcophagus with lions felling antelope (3rd century); a statue of Horus as a falcon protecting King Nectanebo II (360–343 BCE); Kano Sansetsu’s Old Plum (1646); and a house model by Nayarit artist(s) (200 BCE–300 CE).” Or perhaps you’d prefer an intimate view of an eighteenth-century tile depiction of Mecca, a nineteenth-century marble sculpture of Perseus with the head of Medusa, or a suit of armor belonging to King Henry II of France?
Browsing this archive of more than 100 digitized historical objects, you’ll also notice pieces from Japan like seventeenth-century screens by the artists Kano Sansetsu and Suzuki Kiitsu. These must have been priorities for the Met’s institutional partner in this project, the Japanese television network NHK. It all came about “as part of the public broadcaster’s initiative to produce ultra-high definition 3D computer graphics of national treasures and other important artworks,” with “further educational programming and potential content using these cutting-edge, best-in-class models” in the offing. For now, though, the archive offers us more than enough to behold from any possible angle. To do so, just click the “View in 3D” button below the image on the page of your artifact or artwork of choice. It may not be the same as holding the object in your hands, but it’s as close as you’re going to get — unless, of course, you find yourself inspired to pursue the dream of becoming a curator at the Met.
Take a New Virtual Reality Tour of the Metropolitan Museum of Art
See Vermeer’s Girl with a Pearl Earring in 3D in a New 108-Gigapixel Scan
The Earth Archive Will 3D-Scan the Entire World & Create an “Open-Source” Record of Our Planet
Based in Seoul, Colin Marshall writes and broadcasts on cities, language, and culture. He’s the author of the newsletter Books on Cities as well as the books 한국 요약 금지 (No Summarizing Korea) and Korean Newtro. Follow him on the social network formerly known as Twitter at @colinmarshall.
...
Read the original on www.openculture.com »
Alpha notice: Code export is not functional yet. We’re actively working on it — check back soon.
Design once, generate production-ready code for your framework of choice. Switch targets without touching your design.
Alpha notice: Code export is not functional yet. We’re actively working on it — check back soon.
Design once, generate production-ready code for your framework of choice. Switch targets without touching your design.
Everything you need to know before hitting download.
A TUI (Text User Interface) is an interactive application that runs entirely in the terminal — like htop, lazygit, or k9s. Instead of a web browser or native window, the UI is built from characters, colors, and ANSI escape codes. TUIStudio lets you design these visually instead of hand-coding every layout.
Will macOS or Windows block the app?
With no code-signing configured, each platform behaves differently:
macOS
Gatekeeper blocks the app immediately. You’ll see either “TUIStudio cannot be opened because it is from an unidentified developer” or “TUIStudio is damaged and can’t be opened” on newer macOS after quarantine flags the binary.
To get past it: right-click the .app → Open → Open anyway — or go to System Settings → Privacy & Security → “Open Anyway”.
Windows
SmartScreen shows “Windows protected your PC”. Click More info → Run anyway. Less fatal than macOS, but still alarming to non-technical users.
Linux
No such gate. dpkg -i TUIStudio-amd64.deb or double-click in a file manager — just works.
Why are exports not working?
TUIStudio is currently in Alpha — exports are not functional yet. We’re actively working on it.
When ready, the following 6 frameworks will be supported:
Switch export targets at any time without touching your design.
TUIStudio is currently in early access. The core editor is free to download and use. A pro tier with team features, cloud sync, and priority support is planned for later.
Can I save and reopen my designs?
Yes. Projects are saved as portable .tui JSON files you can open from anywhere, commit to git, or share with your team. No account or cloud required.
...
Read the original on tui.studio »
For a decade, I have been working with AWS and third-party security teams to resolve bucketsquatting / bucketsniping issues in AWS S3. Finally, I am happy to say AWS now has a solution to the problem, and it changes the way you should name your buckets.
Bucketsquatting (or sometimes called bucketsniping) is an issue I first wrote about in 2019, and it has been a recurring issue in AWS S3 ever since. If you’re interested in the specifics of the problem, I recommend you check out my original post on the topic: S3 Bucket Namesquatting - Abusing predictable S3 bucket names. In short, the problem is that S3 bucket names are globally unique, and if the owner of a bucket deletes it, that name becomes available for anyone else to register. This can lead to a situation where an attacker can register a bucket with the same name as a previously deleted bucket and potentially gain access to sensitive data or disrupt services that rely on that bucket.
Additionally, it is a common practice for organizations to use predictable naming conventions for their buckets, such as appending the AWS region name to the end of the bucket name (e.g. myapp-us-east-1), which can make it easier for attackers to guess and register buckets that may have been previously used. This latter practice is one that AWS’ internal teams commonly fall victim to, and it is one that I have been working with the AWS Security Outreach team to address for almost a decade now across dozens of individual communications.
To address this issue, AWS has introduced a new protection that works effectively as a “namespace” for S3 buckets. The namespace syntax is as follows:
For example, if your account ID is 123456789012, your prefix is myapp, and you want to create a bucket in the us-west-2 region, you would name your bucket as follows:
Though not explicitly mentioned, the -an here refers to the “account namespace”. This new syntax ensures that only the account that owns the namespace can create buckets with that name, effectively preventing bucketsquatting attacks. If another account tries to create a bucket with the same name, they will receive an InvalidBucketNamespace error message indicating that the bucket name is already in use. Account owners will also receive an InvalidBucketNamespace error if they try to create a bucket where the bucket region does not match the region specified in the bucket name.
Interestingly, the guidance from AWS is that this namespace is recommended to be used by default. Namespaces aren’t new to S3, with suffixes like .mrap, –x-s3, and -s3alias all being examples of existing namespaces that AWS previously used for new features; however, this is the first time AWS has introduced a namespace that is recommended for general use by customers to protect against a specific security issue.
It is AWS’ stance that all buckets should use this namespace pattern, unless you have a compelling reason not to (hint: there aren’t many). To this end, AWS is allowing security administrators to set policies that require the use of this namespace through the use of a new condition key s3:x-amz-bucket-namespace, which can be applied within an Organization’s SCP policies to enforce the use of this protection across an organization.
This doesn’t retroactively protect any existing buckets (or published templates that use a region prefix/suffix pattern without the namespace), but it does provide a strong protection for new buckets going forward (okay, so it’s dying, not dead). If you wish to protect your existing buckets, you’ll need to create new buckets with the namespace pattern and migrate your data to those buckets.
While AWS has introduced this new namespace protection for S3 buckets, the other major cloud providers handle things slightly differently.
Google Cloud Storage already has a namespace concept in place for its buckets, which is based on domain name verification. This means that only the owner of a domain can create buckets with names that are of a domain name format (e.g. myapp.com), and they must verify ownership of the domain before they can create buckets with that name. Bucketsquatting is still possible with non-domain name formatted buckets, but the use of domain name formatted buckets is Google’s solution to the issue.
For Azure Blob Storage, storage accounts are scoped with a configurable account name and container name, so the same issue does apply. This is further exacerbated by the fact that Azure’s storage account names have a maximum of 24 characters, leaving a fairly small namespace for organizations to work with. (h/t vhab for pointing this out)
There is a new namespace for S3 buckets. The namespace protects you from bucketsquatting attacks, and you should use it for any S3 buckets you create.
If you liked what I’ve written, or want to hear more on this topic, reach out to me on LinkedIn or 𝕏.
...
Read the original on onecloudplease.com »
To add this web app to your iOS home screen tap the share button and select "Add to the Home Screen".
10HN is also available as an iOS App
If you visit 10HN only rarely, check out the the best articles from the past week.
If you like 10HN please leave feedback and share
Visit pancik.com for more.