They already have an x86 and an x64 translation layer, and it works pretty well TBH. I currently run an M2 Mac with ARM64 Windows 11 within Parallels, and excepting drivers (like for VPN access) all the software I've thrown at it has run well and, frankly, flown - even AutoCAD 2024.

Why is everyone in this thread thinking the device is doing the flashing or transmitting the software?

My hunch is all this device does is triggers the phone to wake up, connect to the store wifi with pre-stored credentials, then run the update as it normally would when activated and shut back down. Sending the update from the device itself, as you say, is a potential exploit path, but if all it does is connect to the wifi and run software update it's no more vulnerable than any other Apple device.

The other thing this does is increase efficiency. Why would they want to occupy said device for the duration of a transfer when there's a perfectly good wifi network *right there*. Hunch is that it sends a particular set of pulses to the wireless charging coil and when the phone senses that it triggers an update-only boot. That way an employee can process these in bulk with a continuously emitting pad. just set the phone on it for 30 seconds to ensure it got the signal and put it back in the racks.

I'm 99% sure this is just a signal to trigger the phone to turn on, connect to the store's wifi, then reach out to Apple's servers for a software update, run it, and shut off.

Sure if you could create a wifi network with the same credentials as Apple's in-store wifi, then run a MITM attack to feed it an update that would have to be signed with Apple's private key so it passes authentication to run you could update it to a hacked version. But uh, there's a *lot* there that is not practical.

This is no different than a phone running and installing an update today - it's just wirelessly triggered.

When Tesla developed their connector (now North American Charging Standard, NACS), the Combined Charging System did not exist. CCS, however, still wasn't developed by the government. The Society of Automotive Engineers issued the charging specifications for the United States as standard J1772; however, this isn't adopted as a national standard. J1772 is where the CCS implementation lies in the US.

When Tesla needed fast Level 2 charging (faster than 6.6kW), they had to develop their own standard. When Tesla needed DC fast charging faster than 50kW and less bulky than the CHAdeMO connector, they had to develop their own. They developed their own connector such that it could do *both* things, and do them well, and be able to extend it in the future with substantial backwards compatibility. Today, a single connector can handle 1.4kW (120@12A) all the way up to 1MW (NACS current max). J1772/CCS1 is a mess, and it's not compatible with the rest of the world's CCS connectors. Tesla was able to extend *their* connector to support CCS by upgrading the hardware on the charge ports and the supercharging stations to add the communications protocol.

And through all of that, they built out a charging network that is larger than the largest CCS network (Electrify America). They have a substantial majority of cars on the road using their network. They've developed a mechanism that allows CCS users to use their stations without having to bring their own adapter. There really isn't incentive to do anything else unless the government wants to declare a specific connector as the standard, which they haven't.

The base RWD available on their website is a Standard Range+ (SR+) that includes basic autopilot for $40k. The additional $7k is for full self-driving (FSD), which most people don't get much added benefit (besides Navigate-on-AP, parking assist, and summon) quite yet since the full FSD functionality is still pending release.

You can still order the off-menu Standard Range (SR) over the phone for $36.2k (up slightly from the original $35k), but that does not include even basic autopilot or traffic-aware cruise control. Although federal rebate for Teslas have been phased out, you can still get state rebates (depending on which state you live in) to bring that price down, possibly to $33k or lower.

I do agree that the article is wrong to say that the base price starts at $33k. Tesla has never claimed the Model 3 had a starting price lower than $35k.

And I don't mean the Fortran version, but the original MDL code (aka, Muddle) which is a much weirder variant of Lisp than ZIL.

ZIL is basically a subset of MDL, so most of the weirdness you've seen in MDL is also there in ZIL. Check out the "maze" files in Bureaucracy, for example - the game reads a text file at compile time and generates pages of gibberish that have to be combined in the right order to solve a puzzle.

The MDL version is included in the same source dump: https://github.com/historicals...

Infocom's compiler hasn't resurfaced, but ZILF works well enough to hack on these games: http://zilf.io/

The linked article does say illegal sales have gone down, and gets into some reasons why they haven't gone away completely:

Business has fallen since the law passed, but enough people think they can score a bargain, or simply donâ(TM)t trust the shiny new stores, to keep things moving.

These are temporary problems, and they don't translate well to other industries. For example, high quality, low tax medical marijuana resold on the black market can easily undercut legal recreational sales. But a black-market brothel can't undercut the legitimate ones as easily, or offer the same level of service -- lower prices tend to mean lower quality, and operating in the open gives the legal ones extra advantages (marketing, health inspection, integration with other businesses).

On T-Mobile at least, they'll gladly let you keep your plan and let you stay grandfathered, but they're not making any plans that are cheaper to let you pay less. That probably means the actual cost per GB that you use is probably a multiple of the cost per GB that I use, though.

Yeah, I'm not sure why they try to force people up in the plans by eliminating the bottom ones or tweaking the prices. However, I'm one that needs as much data as they'll offer, because we don't have access to landline internet at home even though we live in a major metropolitan area (Knoxville, TN) and less than a mile as the crow flies to the city center. My workaround is using a couple of hotspots connected to the same router with WAPs around the house to get the home devices online, combined with cell data. We were doing pretty well with a 22GB general access hotspot, 6GB TV streaming hotspot, and our phones with 6GB each on T-Mobile. Streaming worked well because they don't count that data against you from Netflix/Hulu/Amazon/etc with the plan over 6GB, and using one hotspot didn't work out because when it ran out of data and went to 128Kbps speeds it killed streaming too. I usually got close or ran out of data on my phone because I can't use it at work, but my wife used less than 1GB because she'd do all of her updates and such on wifi at work.

So, the latest changes that T-Mobile made were enough to finally get me to jump with the phone lines to unlimited. It is costing us less for more data (unlimited but also 10GB tethered data per line as well). As a side effect they're also making the hotspot lines tax-inclusive so that will save us some more as well. All said and done our bill will be about $30-40/mo less than last month, with more data.

For that, I'm thankful for the competition, but I can definitely understand folks in your position that have what they need and don't want to pay more.

Each update must be acknowledged and scheduled for installation by the user, although theoretically there might be a backdoor way for them to remotely install updates without user consent. If you ever go a Tesla Service Center you'll need to remember to tell them not to install software updates for you (since they will commonly do that as a courtesy).

However, there will also be a point where features in the older software versions may no longer be supported and capabilities may degrade, particularly if Tesla's server-side communications specific to those older versions are discontinued, particularly around the navigation features. The Tesla Service Center may also say that they are logistically unable to fix or support some issues without upgrading to a current version.

I recently moved into a house that, while 2mi from a major metropolitan area city center (Knoxville, TN), there is no wireline broadband available. Comcast lines stop next door and AT&T installed a cabinet up the street a decade ago for DSL equipment but hasn't populated it. There's a cluster of about 24 houses that have no wireline broadband options.

We do, however, have a solid LTE signal from all carriers here. After burning through 14-18GB the last couple of months between my wife and myself, we just ordered a T-Mobile hotspot, and I'll be pairing it up with a RouterBoard router to supply our wireless network in the house with internet access, and switch to using that while here. I expect that we will see a substantial drop in data usage and have the benefit of being able to stream netflix or Amazon Instant to our TV's unlimited as well.

What some people forget, is that in situations like this, I would much, much rather have a throttled connection for video than to burn through all of our data while at home because CNN/Youtube/everything else wants to serve up my phone with 1080p HD video. As an added benefit, I'm not going to even be charged for much of that usage.

Shouldn't have been less than 3 seconds. Federal Highway Administration Manual of Uniform Traffic Control Devices (FHWA MUTCD) minimum is 3.0 seconds for an approach speed of 30mph (minimum tabulated). If you were contemplating slamming on brakes to make a panic stop, I would make a guess that the intersection was at least a 45mph approach speed, which translates to a minimum yellow phase of 4.3sec.

Most states (excepting CA, UT, TX, MO, IN, MI, OH, MN, MD and DE) have adopted the MUTCD or the MUTCD with a state supplement. The states that haven't have their own standards but are typically in-line with the MUTCD.

If the yellow phase was less than 3 seconds, you probably had a case to protest and win. But in reality it was probably a half-second or second longer than the MUTCD minimum, depending on traffic volume and other factors. People are notoriously bad at estimating time and distance.