This is crazy to me as well: half a terabyte (!) of RAM?! How is that even possible lol (I know this is possible, but seems totally overkill, even though I know LLMs eat RAM for breakfast)
I personally don't understand the point of an M4 iPad to begin with, let alone M4 Pro. What kind of CPU-intensive work can you do on an iPad? Video editing, I guess? You can't do any serious programming because there's no proper terminal emulator and you can't compile and run custom code. All you have are interpreted languages like Python and Ruby, but it seems like they still can't use the full power of an M4 because iPadOS doesn't let you spawn threads AFAIK.
Even for photo/video editing, why not use a Mac mini with the same (!) CPU and proper cooling? An iPad doesn't even have a fan, so surely the CPU will throttle.
"A glorified $1000 YouTube machine" is a pretty accurate description of an iPad LMAO
It certainly lets you spawn threads. What it doesn't let you do is spawn processes (which blocks what a typical IDE would like to do, as well as things like the Chrome sandboxing model)
So, is it better (faster, stronger, etc) than iOS 18? Everyone says iOS 26 was not good at all and iOS 27 is much better, but it seems like it's fairly simple to make something that's better than iOS 26. A more interesting question is whether it's better than iOS 18? Does anyone have any experience switching from iOS 18 to, say, some beta of iOS 27?
It's "better" if you like eye candy, animations are more drawn out and deliberate. Otherwise they're functionally identical (and has ever been since iPhone X).
For me 26 absolutely chews through battery compared to 18 (I have the last gen iPhone SE). Hopefully 27 doesn't make that worse, but i'm holding off on upgrading. Really took me by surprise.
Definitely made it worse for me. I'm on 15 pro, and when I have anything intensive open (ranging from youtube video ~ games), the phone starts burning through my hand and the battery in it. I would've kept 18 forever, except the camera on the old one died out and replacement came with 26 :(
That's a nice overview, but it seems to compare iOS 27 to iOS 26. Isn't iOS 26 known to be terrible, though? I'd like a comparison to a "known-good" iOS version. Basically I skipped iOS 26 (so I have zero experience with it) and am now wondering whether iOS 27 is any good
That's dramatically overstating it. iOS 26 was just... alright. It wasn't great. It also wasn't the devil incarnate in a phone. iOS 27 has been legimately good since the early public betas.
> The good news is there are some places where things are just better across the board. In general, iOS 27 feels peppy. I know, we always talk about snappiness, but given the time Apple has spent on improving performance and removing bugs with this release, it’s reassuring to see that it’s borne out by my experience. Apps launch quickly, photos sync faster via iCloud, AirDrop transfers are especially rapid, browsing my NAS via the Files app was downright speedy compared to earlier versions.
"Better" is subjective. I've been using iOS 27 beta and other than a few bugs it hasn't been that bad. I only had some minor downgrades in Safari UI, but those are minor and personal.
One thing I hated was a downgrade in Photos app on iOS 26 though, that hasn't improved in 27. Unfortunately it seems I was the only one loving Photos on iOS 18.
I did jump from macOS 18 to macOS 27 beta though and Safari's UI is abhorrent.
> The good news is there are some places where things are just better across the board. In general, iOS 27 feels peppy. I know, we always talk about snappiness, but given the time Apple has spent on improving performance and removing bugs with this release, it’s reassuring to see that it’s borne out by my experience. Apps launch quickly, photos sync faster via iCloud, AirDrop transfers are especially rapid, browsing my NAS via the Files app was downright speedy compared to earlier versions.
I didn't see a single reference to iOS 18 in that article. So while I understand it would be faster than 26, those of us wondering about the comparison to iOS 18 are still in the dark.
Well, it's fast. Perhaps "they" want me and everyone else unemployed, but it's not immediate and not particularly certain. However, I can use uv here and now to greatly simplify my workflows, so I use it.
Sure, but these ten characters let you treat columns as values and do math on them, which is super intuitive, in my opinion. I've been using Pandas for quite some time and always kinda sucked at it. One day I decided to give this new library Polars a try. Now I can do things I couldn't even dream of with Pandas! And it's fast, too!
I think of `pl.col` as delayed evaluation: I want to do math on the vector of values of this column. But wait, let me just refer to the name of that column and build the expression that I want to compute. Then I hand this expression to Polars and it retrieves the actual values of the columns my expression refers to and executes the operations.
IMO, it would've been great to just do math on strings, like `"Amount" * "Price" - "Losses"`, but programming languages either don't allow math on strings or that math is actually string concatenation, which is not what we want. So we have to wrap the name of the column into some object. This is just an API thing.
As a side note, it's such a pity that there's basically no Polars for the Julia language! There is some wrapper package, but it seems old and unmaintained. I can't seem to properly learn DataFrames.jl for some reason, I always miss Polars when I use Julia.
How is, say, `age = 5; print(f"Age: {age} years old")` not easy for beginners? IMO it's as easy as it gets: you want the value of `age` printed {HERE}, so you just put it where you want it, surrounded by curly brackets.
I'm a HUGE fan of f-strings and I think they should be added to more or less every language in existence. (This is just to show how much I like f-strings, not to be taken literally) `printf`-style format strings seem outdated: why use format strings when I can put my variables IN THE STRING? I want the result of `x+y` to be put {HERE} in this string. Well, just write `"This is here: {x+y} blah"` — it makes perfect sense and immediately lets me see what the resulting strings generally look like.
Basic usage is a no-brainer: write your string, put variables or short expressions in curly braces, add `printf`-style format specifiers after the colon. This is also great because it's a natural extension of `printf`-style format strings.
Of course you can write complicated and confusing f-strings. But then you can write complicated and confusing... anything, really. Many programming languages have extremely weird quirks and cases where basic syntax can be transformed into an unreadable monstrosity, like C syntax for pointers to functions and arrays.
Sure, this increases the language's complexity, but you don't have to use all of it to reap the benefits.
Because these are used for locale-specific configuration data. `"This is here: {x+y} blah"` on the other hand isn’t a string (mere data), it’s a program, because you can have arbitrary expressions inside the braces. You don’t want to repeat the `x+y` in each localization file.
I have nothing against ergonomic program constructs for composing strings, but please let’s not confuse such program constructs with mere string literals.
If your string needs to be presented in multiple locales, you probably want to go a step further and use something like the ICU syntax and a proper parser and formatter rather than rely on manually formatting things yourself. Otherwise, that dynamic data is going to give you headaches when you have to deal with plurals and genders and such.
I’m not sure what you mean by manual formatting. You do need a place in your program where you fill in the parameters into the respective localized string template. I agree that the printf format syntax is somewhat limited for localization [0]. But whatever localization string format you use, you don’t want arbitrary expressions embeddable within it.
Are there any real-world time-series that are known to be easy to forecast? Something I could use as an example of "this is what forecasts look like when it's actually possible to predict your time-series and your model is actually doing it"?