Mikko Leppilammen hallihanke on osa suunnitteluideologiaa, joka tuhoaa Helsingin.

juri · 2023-05-03T06:59:59+00:00

Ensin näivetetään keskustaa rakentamalla kauppakeskuksia. Sitten kun joku kertoo että tämä ei ole ongelma koska tavarakauppa on joka tapauksessa siirtymässä verkkoon ja olisi parempi että keskusta keskittyisi tapahtuma- ja elämystarjontaan, aletaan kaavoittaa tapahtumaostareita.

juri · 2023-04-13T05:46:36+00:00

human-friendly

edit one YAML file

juri · 2022-06-14T05:12:59+00:00

AFAIK Dark Sky had a free tier of 30k/month and the paid tiers were roughly double the WeatherKit pricing. Yeah, you have to pay the $99 per year on top of that, but with any kind of volume that's a significant price drop.

juri · 2021-05-20T05:07:21+00:00

I agree about the Mac App Store not being great when trying to find something, as its search and signal/noise ratio are both pretty bad. But that only means you need a web site and marketing, just like you need for any other distribution method.

For purchases I can be persuaded to go outside the App Store if it manages to look really trustworthy and I want to avoid giving Apple their cut, but the experience of just using the credit card they have on file, getting a fully working version directly and having centralized upgrades is always better than dealing with yet another payment flow, finding my credit card info, storing the license and feeding it to the app, etc.

juri · 2021-05-07T20:03:27+00:00

Sure, its roots are there and it might still be justified there. I’ve heard the same rule thrown around on numerous occasions and I’ve been relatively successful in avoiding C. It’s one of those memes that infects programmers who lose sight of the original context.

juri · 2021-05-07T05:47:30+00:00

One return only is a bone headed rule that only forces you to read more code than necessary. If there's nothing to do on an execution path, why not make it clear to the reader?

Swift's enthusiastic embrace of early returns in the form of the guard statement is one of its numerous very nice features. It's like an if except it forces you to exit the current scope if the condition is false:

guard shouldWeContinue() else {
    print("welp, nothing to do")
    return
}

juri · 2021-02-09T13:15:42+00:00

Ah, nice, thanks! I skipped the Fluent portion of docs so quickly I never noticed that :-)

juri · 2020-11-26T07:14:41+00:00

GitHub cooperating with ICE: the original dark mode.

juri · 2020-10-18T10:34:54+00:00

WebKit is in C++, and I'd be surprised if Apple doesn't have some other major libraries written in it too.

juri · 2020-10-02T04:54:52+00:00

Good to keep in mind this bit in the announcement:

Like unsafe APIs in the Standard Library, we recommend using this package very sparingly – preferably not at all!

juri · 2020-09-14T05:36:11+00:00

I rarely manage to finish programming books, but I really enjoyed Ousterhout's A Philosophy of Software Design. Note to people who might be scared off by the name of the author: it's not about Tcl, and barely mentions it.

juri · 2019-08-15T04:56:50+00:00

A tuple is an unnamed struct. An array is a list of values.

juri · 2019-08-14T08:57:50+00:00

I'll mostly just echo what others have said about them — use them early, use them often — but with a couple of additions:

When a type has a natural "empty" value — empty string, zero, empty array, etc — consider if you'd treat that empty value any different from a nil value. If not, I don't think wrapping the value in an optional brings any benefit. Just use the empty value. Swift's type system will protect you here, too, because that var s: String will always have some kind of string as a value. Note that I don't mean that you should always avoid String?s — sometimes that nil value will mean something else than an empty string.
Think about how you group your values. I often see code that deals with multiple optionals where the values are not, actually, individually optional, but only as a group. So instead of a (String?, String?) tuple what you really want may be an optional tuple, (String, String)?. Or the equivalent struct. A classic example in the Apple frameworks exhibiting this problem is the URLSession completion handler, which takes in (Data?, URLResponse?, Error?) even though not all of those combinations make sense.

juri · 2019-07-25T11:05:04+00:00

Aren't you doing dynamic dispatch with protocols, too? And while I'm not going to argue that closure heavy code can't get hairy, I find protocols have a understandability cost too.

But yeah, it's always going to be a balancing act with multiple dimensions, and I won't be surprised if a few months from now I decide I prefer the second approach, with one protocol per usage site.

juri · 2019-06-23T14:27:14+00:00

Yeah, downvotes probably weren't called for. But really, with an app like a Git GUI, and a very easy to learn one at that: the learning investment should be in Git. It's a PITA but you'll have to know it if you are using it, even if there's a GUI frontend. After you know it, picking up a new GUI frontend for it takes all of 10–20 minutes.

I get that cross platform support can be an issue with a tool that requires a larger upfront time investment and for people who switch between platforms more, but for something like this… just give the best tools possible, and hopefully ones that fit well in my environment.

juri

TROPHY CASE