For Microsoft, the first and largest contract mentioned in the table just below the fold on that page is for an IVAS system. Microsoft had been basing this off their HoloLens system but was a distinct product (they weren't just sending over the normal HoloLens and expecting that they were gonna work in the field). This contract was then transitioned to Anduril. But just saying of Microsoft that "they are not defence contractors in any way" is hard to reconcile with the facts of having a large contract to _develop a new product_ for the military ... even if it turned out to never have been used.
EXIF already includes extensive metadata, including phone model and GPS location. For professional cameras, there is often camera and lens serial numbers too.
This has been the case for many years, and so far social media sites never care - they strip that info instead. Why would this change with one more extra piece of metadata?
This link makes it look like it's some event-specific website. It's not. It's an easy way to navigate the confusing mail routing system to military service members, especially those in bootcamp where they can't have phones. But you want to send them a letter which they CAN get, but you don't know their address or you don't want to actually buy stamps and go to the post office and whatever else. It's a convenience service.
Not sure why other commenter suspects people will go apeshit over this, it's just a good business idea?
Weird. A spike in blood pressure maybe? Can you do reproduce it consistently on purpose with an alarm or by holding something as you fall asleep that will make a loud noise when it falls?
> If you take the state of the brain and then run it again, replaying the inputs, you get the exactly same behavior again.
This in itself is a colossal assumption and very far from axiomatic. Roger Penrose disagrees, and his theory of mind may not be in high favor, but it is not nearly so wishy-washy and self-serving as the voodoo horseshit and circular reasoning dispensed by the LLMs-are-sentient crowd.
But they can’t do this unless you agree to enable training on your data. They would never train on raw user data. Only people who have consented and only after de identification.
All of these sites are independently created but viewed as a whole you would think they're all designed by the same group, which is the issue with modern design engineering. The herd mentality on X is quite nuts and I can count on two hands the number of truly unique software artists I know of and respect.
How many light gray, fully rounded buttons with a sans-serif font that darkens on hover can an industry make? How many scroll effects will satisfy you? I would love to see more experimentation within the industry. Unfortunately I don't see AI helping more than hurting here.
There is one thing an airline never wants to have happen and it is a fatal accident. Everything else is secondary. Having one caused by corporate policy would lead to mass exodus of passengers.
Honest question, what are average joes supposed to do? We have no control here. This incessant messaging is going to inspire genuine chaos. What are young adults and parents of young kids supposed to do other than panic?
We’ve abandoned religion and adopted tech consumerism as our new pseudo religion. Is Kubrick our prophet, and 2001 our prophesy?
I built my harness in pi within herdr, I cloned (zipped and downloaded) 0xRichardH/pi-herdr-subagents and went from there, and used pi to build itself, adding gate workflow state control, provider fallbacks (I use many token plans), subagent skill injection, etc.
It is highly custom to my needs and wants, and I think every developer needs to do this. I only talk to my planner which plans, and it subs out to designer, oracle, coders, testers, and reviewers, etc. It is thus highly optimized for correctness. You can TDD or no TDD. You can fast track small changes. I tweak my harness dozens of times as I encounter new edge cases (esp when I switch models and encounter models not as good at following instructions).
As you can start to see, it is better to own the harness because nobody can build something custom that 100% fits your needs or development philosophy.
Also, human developers and AI make different types of mistakes, and take different approaches to debugging. I'm not saying they shouldn't have done that, it's just that a more human-involved approach with AI filling the gaps would probably be a saner bet than 90% AI with some human interference.
Celsius isn't granular enough (people can perceive 0.5˚C changes), and anything above 50˚C is rare or nonexistent. 0-100˚F pretty much lines up with the extremes.
Even if it is, the software on the device could theoretically do whatever it wants with the data before it's encrypted/uploaded, and if it's sent to Apple, they could do whatever they want with it too.
I experienced the same issues but went the other way and migrated from React Native to React. Still one codebase but none of the issues. Performance was better too even though half the code stayed the same.
That is what I always see in wet saunas/bathrooms around me. The bathing room is a main feature so things like main plumbing and water heaters are all placed around that to keep it simple. Recirculation additions after that would then be two simple connections off the back of the tub, probably near where the faucet goes.
I'll put it this way, my argument was pro native. And in the context of the article, if a large company had unlimited resources, they would choose native. I'm not discussing the business case for it, but the end result of it being the better option. It can be seen as "Shopify tried Reactive Native and left it behind the second they could after sinking resources into it for 6 years".
So if Shopify had to do major refactors of all their React Native apps, maybe they could look at what it would take to go back to native Platform APIs.
For the Shop App, this coincided with our next major React Native investment: adopting the New Architecture. That work would have required us to revisit native module integrations, rendering, and the boundaries between shared and platform-specific code. Before committing to this investment, we tested whether coding agents could help us build directly in SwiftUI and Jetpack Compose while keeping product behavior aligned across platforms.
The result of that native platform APIs side project involving six devs converting the app's major user workflows?
- startup time reduced: iOS by 23%, Android by 50%
- crashes - 10x reduction
- app size - iOS increased by 1MB (67MB -> 68MB), Android reduced by 109MB (37.2%)
- build time - Android release build time fell ~75%.
- runtime perf - Android builds could draw at 120fps while scrolling feed and switching screens
Maybe you intended to reply to my comment's parent? I don't necessarily disagree.
But also, according to the Ars article comment describing the Unicode character range, it has been deprecated, so maybe someone involved in the Unicode standard saw problems with it.
I don't for a moment believe that, but apparently arguments that cannot possibly be proven are in vogue nowadays.