标签：#m

Samsung says its next foldables will have less visible creases thanks to its new titanium display tech.

Gidi Littwin's new AI startup, Hemispheric, makes diagnostic brain scans for conditions like depression, PTSD, and Parkinson’s. He wants the technology to be as cheap and easy as a blood test.

An old Oscar Mayer factory in Wisconsin will become America's latest fusion power research and development hub.

The startup has reached a $120 million annualized revenue run rate and more than 200,000 paying customers.

The Home Depot is once again upgrading its 12-foot-tall skeleton to help keep the viral piece of Halloween decor popular as spooky season creeps closer. Skelly is borrowing some of the tech introduced in the smaller 6.5-foot Ultra Skelly last year, including letting you speak through the skeleton's moving mouth using a mobile app. The […]

"I pretty much, at that point in time, gave up on being an astronaut."

Amazing : Researchers from ETH Zurich in Switzerland, however, managed to create a new type of pixel that can simultaneously do both. This hypercharged pixel, called a Fourier pixel, can generate and sense arbitrary light fields and tap into a pixel’s full potential for carrying information by manipulating light’s intensity, oscillation phases, and polarization. The team reported its findings in a paper published yesterday in Nature. We are one step closer to 1984 technology: The telescreen received and transmitted simultaneously. Any sound that Winston made, above the level of a very low whisper, would be picked up by it; moreover, so long as he remained within the field of vision which the metal plaque commanded, he could be seen as well as heard. There was of course no way of knowing whether you were being watched at any given moment...

But with great power comes a great price.

Co-founded by serial entrepreneur Shai Morag, Israeli identity management startup Oak is emerging out of stealth with $60 million in seed funding.

There’s now only one worth buying—but you can still access new features on older models you might already own.

Samsung has unveiled a new flexible display technology for foldable phones that's designed to be slimmer, more durable, and less prone to creasing. The Flex Titanium tech is the culmination of everything that the company has learned over seven generations of foldables, according to Samsung, and will debut with the upcoming Galaxy Z Fold 8 […]

Spotify founder Daniel Ek's body-scanning startup, Neko Health, is setting its sights on the United States after raising $700 million from a star-studded group of celebrities, entrepreneurs, and investment firms. It plans to open its first clinic in New York this year before expanding rapidly across the country. Neko operates private clinics offering full-body scans […]

Hello, I'm Maneshwar. I'm building git-lrc, a Micro AI code reviewer that runs on every commit. It is...

The video game industry is in turmoil. Microsoft and Sony are starting to pivot to their next consoles, but it's not looking great: Prices are soaring, Sony is killing the video game disc, and Microsoft is jettisoning studios ahead of the transition. What could entice people to pay? On the Xbox front, we genuinely can't […]

Various interesting things about sorting data: defaults, performance and determinism (or lack thereof) of paging ;) submitted by /u/BinaryIgor [link] [留言]

This is a submission for DEV's Summer Bug Smash: Smash Stories powered by Sentry . It was 11:14 PM. My friend DM'd me on Twitter: "Your app just hung for 30 seconds, spun indefinitely, and then completely died." I opened the browser DevTools console pointed at production and saw it — the screen flooded in red: GET https://careerpilot-ai.run.app/api/analyze-career net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 (OK) The Server-Sent Events stream powering CareerPilot AI was systematically collapsing on Google Cloud Run. And I had no idea why. Locally on localhost:3000 , the agentic pipeline was a masterpiece. The multi-stage reasoning logs streamed gracefully — Step 1 flowed into Step 6, the final structured JSON payload arrived within seconds, the UI lit up with a complete personalized career roadmap. Beautiful. But once deployed behind Google's Front End (GFE) proxy, the pipeline was a graveyard of broken sockets. The Architecture Under Fire CareerPilot AI runs a six-stage agentic pipeline on every career analysis request. Instead of firing a single long-running prompt to Gemini and making the user stare at a blank screen for 20+ seconds, we designed a Server-Sent Events logging stream to broadcast real-time reasoning steps directly to the browser — giving the interface the feel of a live, active mentor thinking out loud. Once the final stage (Self-Evaluation & Constraint Validation) completed, the backend constructed a massive, nested 15KB JSON payload containing the personalized roadmap: skill weightings, role benchmarks, resource links, and a 30-day milestone calendar. Here was the delivery mechanism — and the landmine hiding inside it: // server.ts — The vulnerable streaming channel app . get ( " /api/analyze-career " , async ( req , res ) => { res . setHeader ( " Content-Type " , " text/event-stream " ); res . setHeader ( " Cache-Control " , " no-cache " ); res . setHeader ( " Connection " , " keep-alive " ); // Stream intermediate reasoning logs per step for ( let st

If you've searched the App Store for a reliable third-party QWERTY keyboard on iOS, you know how that ends. Some are abandoned. Some are ad-riddled. Some feel like they were ported from Android and never touched again. The good ones are the ones that don't ship features so much as they don't crash. The system keyboard is fine. It's fine because Apple has been iterating on it for fifteen years. Nobody else has. Third-party keyboards on iOS are a graveyard. I'm building one that isn't. It's called Diction. Most people know it as a voice keyboard, and that's what I lead with, but under the hood it's a serious low-level QWERTY project too. This post is about that half of it, because that's the half nobody talks about. Why third-party QWERTY on iOS is a graveyard Building a good keyboard extension on iOS is hard. There's a strict memory ceiling. There's a permission dance the user has to opt into. There's no keychain access, no meaningful background work, and the extension can be killed the moment iOS decides it needs the RAM. Most keyboard makers ship a first version to check the box, then abandon it once they see how much work maintaining it takes. The result is what you see on the App Store today. Every third-party keyboard I've tried on iOS fails on at least one of these: Speed. You type a letter, the letter arrives. That's it. If there's a hitch you can feel, the keyboard is broken. Half the ones I've tried have a visible delay on every keystroke. Predictability. If you correct the same word back three times, that word should be yours. The keyboard should stop fighting you. Most never do. You fight the same wrong correction for a year. Recovery. iOS keyboard extensions are memory-constrained. Bad ones freeze under pressure. When you rapid-switch between apps, half the third-party keyboards on the store will lock up until you kill and reopen the host app. Autocorrect that isn't from 2014. Fix the obvious typos. Split words that ran together. Complete contractions. Ge

Most test automation tools look good during a demo. You record a login flow, add an assertion, run it in Chrome, and get a green result. Everyone is impressed. Then the real application gets involved. There are dynamic elements, delayed API responses, test accounts, verification emails, downloaded files, several deployment environments, and a checkout flow that behaves differently on Safari. A few months later, the original test suite has grown from 10 tests to 300. Some failures are product bugs. Others are test problems. A few only happen in CI. Nobody is completely sure which is which. That is when you discover whether you selected a test automation tool or merely a good demo. Creating tests is rarely the main problem When teams compare automation tools, they often begin with questions such as: How quickly can we record a test? Can AI generate the steps? Does it support plain-English instructions? Can a manual tester use it? Does it integrate with our CI pipeline? These are reasonable questions, but they mostly describe the beginning of an automation project. The harder questions appear later: Who updates the tests after a redesign? How do we investigate failures? Can another person understand a test created six months ago? What happens when the original automation engineer leaves? Can we test workflows that involve email, APIs, files, or mobile devices? How much infrastructure do we have to manage? Does the cost increase every time we run the regression suite? The first test tells you whether the tool works. The hundredth test tells you whether the approach works. Maintenance should be part of the evaluation A stable automated test is not a test that never changes. Applications are supposed to change. Buttons move. Components are replaced. Authentication flows evolve. APIs return different data. Product teams redesign entire sections of the interface. The objective is not to prevent tests from changing. It is to make those changes inexpensive and understandable.

There's a specific kind of marketer who should be nervous right now. Not the strategist. Not the writer with a point of view. Not the creative director who can look at forty options and know, instantly, which one is alive and which thirty-nine are furniture. The one who should be nervous is the marketer whose entire job was being a slow version of a machine. You know this person. Maybe you've been this person — most of us have, at some point, in some job. The one whose week was resizing banners, rewording the same caption in six formats, pulling a report nobody reads, and calling a meeting to discuss the meeting. Their output was never brilliant, but it was there, and for twenty years, "there" was enough. Volume looked like value. Busy looked like good. AI just ended that arrangement. Quietly, without a memo. The excuse economy is closing For most of modern marketing, mediocrity had excellent cover. A bad campaign could hide behind timelines. A weak idea could hide behind budget. "We didn't have the resources" was the most useful sentence in the industry, and everyone accepted it, because everyone was using it. Now a two-person studio in Amman or Manila or Medellín can produce, in an afternoon, what used to require a floor of people and a quarter of runway. The drafts are instant. The variations are infinite. The production bottleneck — the thing entire careers were built on managing — is basically gone. Which means the only thing left to judge is the thing that was always the actual point: is the idea any good? That question used to arrive at the end of a long process, softened by exhaustion and sunk cost. Now it arrives immediately, naked, on day one. There's nowhere for a bad idea to hide anymore, because there's no longer a six-week production schedule standing in front of it. What the machine actually can't do Here's what gets lost in the panic. AI can generate. It cannot choose. It can write you a hundred taglines. It cannot tell you which one will make a foun

Getting Comfortable with HTML Attributes When I first started learning HTML, attributes felt like tiny details hiding inside the tags. I understood the basic structure of a webpage, but I didn’t fully understand why some elements had extra words like href, src, or alt. Over time, I realized attributes are what make HTML elements useful. They add meaning, behavior, and context. Without attributes, a webpage would still have structure, but it would feel limited and incomplete. What HTML attributes really do An HTML attribute gives extra information about an HTML element. It is written inside the opening tag and usually has a name and a value. In simple words, the tag creates the element, and the attribute explains something about that element. For example: Here, href tells the browser where the link should go. Why attributes matter Attributes may look small, but they make a big difference in how a webpage works. They can: Connect one page to another using links. Display images, videos, and other media. Improve accessibility for users and screen readers. Help CSS and JavaScript identify elements. Control forms, buttons, and user input. Without attributes, HTML would only show content. Attributes help that content become interactive and meaningful. Some attributes I use all the time href for links The href attribute is used with anchor tags. It tells the browser the destination of the link. src for images The src attribute gives the path to an image, video, or audio file. alt for accessibility The alt attribute describes an image. It is helpful when the image does not load and also important for screen readers. id and class for styling id gives a unique name to an element, while class is used when multiple elements share the same styling or behavior. placeholder and required in forms These attributes make forms easier for users to understand and complete. A few habits that helped me Use lowercase attribute names. It keeps the code cleaner and easier to read. Put attribu