The court awarded $10M in punitive damages in addition to the $13M in compensatory damages. So the options are basically "Huy Fong's lawyers are criminally incompetent" or "Huy Fong absolutely screwed over their supplier".
> Gemini was also unable to find the .dev, even in "Research Mode."
Unsurprisingly, right? Gemini just uses the same back end as Google itself, which - according to OP - doesn't list his site on page 1, not page 2 and not page 5.
Depending on the prompt, it should have gotten the link from the github, but that's like an indirect hint from a secondary source, it probably ranks the Google index quite highly when it does research.
Why would you want to do that? Do you like the hardware that much, and also that much more than just an M2 (soon M3) running Asahi?
Linux in a VM would work with the usual caveats. Periphery like the built-in webcam most likely won't work. Getting codecs and DRM to run will be pain and you'll be back to use macOS for that quickly (but that's just standard pain of ARM Linux).
It's the greed. Apple only makes around 8% of revenue through hardware sales of all Macs combined. "Services" (App Store, iCloud, Music, TV+, ect.) make more than 3x more revenue. Then, profit margin on services is again 3x higher than on Mac hardware. So they really want all Mac users also use Services.
If your proposed change increases Mac sales by 1%, but only 0.1% of users install Asahi, they lose money.
I'm still watching out for Asahi progress, amazing project. USB-C displays and the M3 will come (and I don't care to much for the rest), that makes a refurbished macbook air an attractive proposition.
Interesting article, but I wonder why the journalists didn't go all the way. Sure, Meta isn't going to comment when you ask them what data they have. But this is in the EU, just hit them with a Subject Access Request under GDPR.
Would be really interesting to create a completely new account, use the glasses with all upload settings off for a month, and then SAR request and see what they have...
And they don't want to, because that experiment ran for around 20 years and resoundingly failed. Turns out it's really hard to stop the bottom quintile of users from entering all their credentials into just about any website that looks similar to what they are used to - and then their identity/money is just gone.
Stopping those users without a trusted authority deciding which electron-wrapped websites are genuine is an unsolved problem, I think.
If the app truly just plumbed a webview and cert verification - which has been doable for over a decade - it would be very portable and this wouldn't be a problem.
The apps don't just do that though; they call into and use an awful lot of the system APIs for user tracking / semi-native experience / biometrics and probably a whole host of other things. Its the incompatibility in these that drags compatibility.
> The apps don't just do that though; they call into and use an awful lot of the system APIs for user tracking / semi-native experience / biometrics and probably a whole host of other things. Its the incompatibility in these that drags compatibility.
Both can be true. Many (most?) online banking apps are just shitty wrapped javascript, that also uses an awful lot of system APIs.
I'm using a couple of different banks, and not a single one has anything close to a native app. Because how nice would that be? Responsive interface (since it doesn't need to load every single view from the server), instant search over your transactions (since the DB can be cached locally), instant access to all the PDFs in your inbox... but no.
That's the limit for continuous rated power. The motor's frequently have 600W-750W of peak power output, and can legally use this much for short amounts of time (usually seconds, like accelerating from a stop; but often also for going up a steep hill for several minutes).
No, what the modders do is just disable the velocity dependent power limit on the standard e-bike power controllers. The easiest/hackiest way to do that is to install a pulse rate divider on the tachometer cables - bike goes 30mph, controller thinks it's going 10mph and delivers full power. This messes up the mileage counter and is trivially easy for the cops to spot, but it'll work.
> The power levels required to push a hybrid bicycle to 45mph is north of 3000W
Yeah, 45 mph is hyperbole. 45 kph is very easily doable on a standard 750W e-bike motor with <$1 of additional electronics. At that point it's all aero, so going even faster is mostly about rider position and bike geometry (those scooter looking things are going to be slower than a proper bike on 29" wheels).
> Many e-bikes don't have torque sensors and instead use a cheap rotation sensor so the motor engages almost randomly at certain points in pedal rotation when moving at slow speed.
Today, those are mostly limited to Walmart-tier quality e-bikes. Even the very next step up (still big box store bikes) usually come with torque sensors.
Those are legal, at least in the EU. It's called "push support" or "walk assist", my bike engages it when I long-press the down button. It's purpose is to help you push the heavy e-bike up ramps and hills, but I mainly use it as a throttle when I ride behind my toddler on his balance bike.
It's closer to 3mph than 5mph, and as such needs some slow-riding skills, but it works.
One of my bikes without a thumb throttle has this but there is a bit of delay from the long-press required which I don't like compared to the basically instant response of the thumb throttle. It also requires a bit for attention to press the small button vs the throttle you can keep your eyes on the road.
If you want to compete with LIDAR, you need high resolution 4D (range, velocity, azimuth, and height) RADAR. Those are usually phased arrays with expensive phase sensitive electronics, and behind that a chip that can do a lot of Fourier transforms very quickly.
The cheap RADAR devices you're talking about usually only output range and velocity, sometimes for a handful of rather large azimuth slices. That doesn't compete with LIDAR at all.
reply