jurip

I don't know the details of the Berlin situation, but as long as someone lives in those new apartments (who would have lived in Berlin anyway), it helps with the housing shortage and prices. Someone moves to the new, most expensive apartment in the city, someone else moves to their now vacant slightly less expensive apartment, etc. At some point in the chain that means there's cheaper housing available.

This is a constant discussion in Helsinki, too. I think it's better to build expensive if that translates to good locations and high quality.

Yeah Apple doesn't seem to even try to cater to non-US users with their shortcuts. That's the first I've heard of a system-wide back shortcut. You can't type that in my layout. The default switch between windows of a single app shortcut is also impossible, IIRC. One that I always have to reconfigure when I switch editors is the line comment shortcut which defaults usually to something like cmd-/.

I wonder if it's any better on iOS or are you just completely out of luck there when you can't reconfigure the shortcuts?

The 52-star version looks slightly more balanced than the 51-star one. Probably best make DC a state too while you're at it.

The thick CRT case reminded me, again, of the unveiling of the current iMac design in 2012. Phil turning the computer to demonstrate its thinness, to an obviously very carefully selected angle so the bulge remained just out of sight.

It still feels a bit pointless, but what do I know.

Another thing related to tire pollution is asphalt dust. Road surface gets used up, too, especially in places where studded winter tires are popular, and it's a significant source of airborne particulate matter: https://grapevine.is/news/2020/11/30/winter-tires-have-huge-...

"Typical noisy OOP java code base", without a single class in the whole file, only value types. As for automated tools, I think you're giving Xcode too much credit. It'll help you a bit, but not much.

The showed Xcode multiple times during the M1 Mac release event and boasted about compile times so yeah, I'm pretty certain they do realize it.

Not the OP, but:

1. Value types

2. Tuples

3. Key paths

4. Checked exceptions (could be more powerful in Swift, but they are there, and when not used in excess they are actually pretty nice, and Swift's `try` syntax is excellent)

5. Swift's enums and `switch` feel both more straightforward and more powerful than Kotlin's sealed classes and `when` (I'm not sure about this, but I think there are situations where you get better coverage checking with Swift's pattern matching.)

6. Reified generics (I know that opinions on this vary, and it doesn't often matter, but I've been just writing some code where it's been nice to be slightly more type safe with Any values)

7. More principled null handling (Optional is just an enum, although with some extra syntactic support)

8. `if let`, `if case`, `guard let` and `guard case` allow for simpler handling of multiple values than Kotlin's `?.let` and null checks

I like Kotlin being more expression oriented, but in the end I often find my Swift code to be less contorted due to the more powerful conditional constructs. GC vs ARC isn't much of an issue, both work for me.

Signals and Threads has been a fantastic podcast thus far, I've really enjoyed all the episodes.

As a more realistic example, I think you can buy locally grown tomatoes in Finland all year round these days, or if not at least pretty close to it. A large portion of them are grown in Närpes, where day length dips below 5 hours in December. Keeping those greenhouses lit and warm is in no way ecological.

It's not just the dishes themselves, some which really are pretty great. It's also how they are prepared. I suspect the standard has risen substantially over the last 50 years.

Someone commented that it seems unlikely that Epic gets a legal victory out of this, but they may get a legislative victory. It's very possible Apple will win the case, but all the App Store fights that have been in the news more or less every day recently should at least be looked at when the US and EU consider new regulations.

Meaning assassination with polonium, I guess. I dunno if it's chemical warfare but not something I expect from a reasonable government.

I think Flipflop Solitaire is supposed to be always solvable. It's also very well made.

This doesn't really answer your question, but Amazon DE offers an English UI option.

As dmurray commented there's differences in what is counted. Another difference is that Paris proper has relatively small parks, whereas Berlin has several huge ones as well as lakes.

So yeah, Paris is dense, but if you compare block by block the differences are smaller.

Agreed about missing if and switch expressions in Swift. My preferred way of writing that would be:

    let foo: Int
    if x <= 0 {
        foo = 0
    } else if somethingElse > 50 {
        foo = 9000
    } else {
        foo = 42
    }

That way you get immutable foo and the compiler will shout at you if you forget to assign the value in one branch. It's not quite as nice as an expression, but it's less punctuation than the closure and the result is just as safe.

And of course the API side of logging, i.e. OSLog, is still unusable if you have exotic needs like, I dunno, sending the logs somewhere where you, the developer, might take a look at them. Feels like having sessions telling us about improvements to logging without solving that one first is a bit pointless.

I know what data detectors are, but I most certainly don't get any such tracking option for any of my messages containing tracking codes. I still need to copy those codes into Parcel, and find the automatic pasteboard reading useful. And UIPasteboard doesn't offer such an API, AFAICT.

Aren't they just checking with an UTI? So for example a package tracking app can't ask if it contains strings matching patterns describing common package tracking code formats?

I just had that yesterday. Not sure if I've ever seen it before, but yeah.

If a recipe is too hard to find, just move on. If there's a few paragraphs of things you don't care about before the recipe, press page down. Maybe let Dakota write what she wants on her own site.

One reason I haven't seen mentioned here for that personal content: it's also a question of building context and trust. If I go to Bon Appetit for a recipe, I know they've tested it a few times and it should be more or less OK even if I don't recognize the author. If I go to a barebones anonymous just-the-recipes site, I have no faith that it ever worked and if it did, it wasn't just a fluke and it was written down right.

Having some detail around a recipe from a previously unknown source allows me to build a connection to a persona in my head, genuine or otherwise. If a recipe doesn't work I'll know to avoid the site in the future. If it does work I can remember that connection and come back to the site again with some more confidence.

Swift 5.3 (i.e. the next minor version) will support Windows: https://swift.org/blog/5-3-release-process/

Feels like Apple could boost their ecosystem by making great iPhone/macOS webcam integration. There's Kinoni's EpocCam and it seems to work, but it is a bit rough and requires installing their driver which I don't love.

It's weird how both ReST and Markdown stumbled on that indentation thing. And ReST has the awkward header underlines, too. Both of those are annoying at the best of times and basically unusable with proportional fonts (and we're dealing with prose here, where there should be no reason to force people to use monospaced fonts if they don't want to.)

If I'm ever involved in designing a syntax like that, the first hard and fast rule will be that the user should never have to count anything, especially in relation to anything else.

It would be helpful to quantify "plenty dense" here. Paris has a population density of 21498/km2. Turning that around, that's roughly 46 square meters per person. That doesn't leave a whole lot of space for a potato plot if you're supposed to cook and eat those potatoes somewhere, too.

Not impossible indeed. Swift 5.3 will officially support Windows: https://swift.org/blog/5-3-release-process/

Ted Kremenek listed in his "On the road to Swift 6" post on the forums "Expand the number of platforms where Swift is available and supported" as the first item. (https://forums.swift.org/t/on-the-road-to-swift-6/32862)

Saleem Abdulrasool, who has been working on Swift on Windows, was also recently added to the core team.

So I don't know if it's actually on the roadmap, if one exists, but official support doesn't seem impossible.

Because people assume ARM would give us better performance and/or battery life. Hard to know if that would actually pan out in the laptop form factor (and if it would hold true forever), but at least right now iPads get better Geekbench scores than MacBook Air.

As for more money and time… I dunno, I make my living writing mostly iOS and Mac software and I can't recall the last time I did anything that was architecture specific. I'd imagine that applies to the vast majority of people working on ordinary application software on these platforms.

Duh. Thanks. Not my brightest moment.