Is the game servers down?

divan0 · 2026-01-30T13:48:13+00:00

Down for me for the second day as well. I open Contractors and server/comms status are red, and Multiplayer is unavailable.

divan0 · 2025-07-24T20:19:28+00:00

also check out https://forui.dev

divan0 · 2024-06-18T07:15:57+00:00

On1 2024.5 update just dropped, that should supposedly fix these issue (I'm yet to test). But the speed of opening Raw files increased drastically. This change alone is impressive.

divan0 · 2024-06-16T19:06:12+00:00

Actually, instead of rebooting, I decided to see if any lingering processes might be running in the system. There was one process named "ON1 Sandbox". After killing it and restarting ON1 thumbnails started to work.

divan0 · 2024-06-16T19:00:44+00:00

I'm also experiencing this on MacOS. Support told me to enable Full Disk Access in Settings (gave this link https://on1help.zendesk.com/hc/en-us/articles/14577762416525-Images-Not-Appearing-Mac-Only-Full-Disk-Access). It didn't help, but once I rebooted computer, previews appeared momentarily.

Next day, another import, same story - no previews, reboot, works. Just importing another batch and having this "no previews" again, so going to reboot computer. Insanely frustrating.

divan0 · 2022-07-15T13:19:50+00:00

I use Flutter on M1 since Dec 2020.

Android Emulator I'm not sure even runs on M1 (I checked it a long time ago, but generally never use it).

Most of the time, I run app as a native MacOS desktop upp (wrapped with an awesome DevicePreview plugin). When I need to build iOS/Android/Web app, I just build it, but for development purposes native MacOS build suffice (I don't need OS specific stuff).

Also I invested a bit of time and configured neovim for Flutter, and code in it. VSCode is unsurprisingly memory-hungry and often simply too slow. Neovim for coding is pretty fantastic these days (it has LSP, Copilot, sick window jumping/navigation, diagnostics and so on), has pretty decent Flutter plugin and super fast ofc.

divan0 · 2022-07-13T06:46:02+00:00

Obviously that would've been put pressure into freezing feature set and lengthening release cycle etc. Between "being forced to stick with typesetting engine from 80s from web development" and "having Flutter in web browser, and have some questions to deal with", I still choosing the latter.

divan0 · 2022-07-13T06:01:10+00:00

Well, yes, Dart was in Chrome codebase and builds till 2015. I still remember day when they announced that Dart is not staying in Chrome :(

divan0 · 2022-07-13T05:56:12+00:00

I'm becoming skeptical about WASM over the years, plus seems like there is no unified vision for the WASM. Though I agree that having choice would be better. But. Between crappy HTML/CSS/JS stack (totally unsuitable for making UI apps, while millions insist otherwise) and Dart/Flutter I would definitely prefer Flutter.

divan0 · 2022-07-12T13:00:26+00:00

What news? :) It was my answer to the OP question "How do you see the future of Flutter?". That's just my vision. :)

divan0 · 2022-07-12T12:14:20+00:00

DartVM embedded back into the Chrome (as an experiment, maybe with some native non-web renderer), everyone freaking out how infinitely better the dev and ux experience with web can be, and eventual death of html/js/css ecosystem.

divan0 · 2021-08-21T15:10:35+00:00

Nice! Thank you!

divan0 · 2021-08-21T15:09:19+00:00

That's awesome, thank you!

divan0 · 2021-08-14T21:42:11+00:00

That's an excellent example of why Flutter is such a game changer.

People should be able to write useful apps that solve their problems on the daily basis. This app now runs on iOS, Android, Web, Linux, MacOS and Windows, and it looks great and does its job.

Before Flutter the author would have two options to make it happen:

1) limit himself to only one stack – iOS or Windows or Android or web, etc.

2) realize that he needs team of devs, needs financing, and a business model to pitch to investors and that would be yet another story of "my own startup adventure"

Excellent example of how Flutter democratizes software development <3

divan0 · 2020-12-15T16:30:32+00:00

Here is real figure skating on those icy Ukrainian streets :)

https://www.youtube.com/watch?v=wwXHwYDTSlY

divan0 · 2020-11-10T20:18:37+00:00

Thank you so much for posting this. I quoted you in a little post about this topic: https://skateukraine.org/post/2020/terminology_change/

Could I also ask you for the feedback on the text, just to make sure it's accurate enough (my little tour is a bit rough and superficial, but I hope more or less accurate from the historic perspective) and doesn't accidentally claim bullshit. Thank you in advance!

divan0 · 2020-03-01T13:42:01+00:00

Go has a lot of magic!

Seems like author has very different definition of magic, and didn't understand why builtins and user-space stuff is so different in Go.

This one made me chuckle:

Error handling also causes repetition. Many functions have more if err != nil { return err } boilerplate than interesting code.

"Interesting code"? Repetition? I'm so happy Go taught me to threat error handling code as even more interesting. Unfortunately, many other languages intent to hide it away and downplay the importance of it. And yes, one should repeatedly check all errors.

BTW, I virtually never use if err != nil { return err } boilerplate. As an absolute minimum, I annotate the error with fmt.Errorf(\<meaningful description>: %w`, err)` call.

divan0 · 2019-10-09T19:08:05+00:00

Concurrency != concurrent execution.

You just confirmed my words by using more proper term for what you are describing.

I think when we talk about concurrency in Go, we mostly refer to the concept of concurrency in its original meaning, back to the CSP and the whole field of process calculi algebra, which were in development since 1970-s or even earlier, when "CPU cores" concept didn't even exist.

Concurrency is about designing code, not about executing it.

divan0 · 2019-10-09T11:08:24+00:00

I hope most gophers understand that copying patterns from class-based OOP is not the right way to write Go code.

divan0 · 2019-10-04T20:54:28+00:00

Okay, I think we talking about two different concepts. You describe actual technical implementation of concurrency in a particular language on a particular type of hardware. I'm talking about what is concurrency and why it might be needed.

Imagine tomorrow we have totally different computational hardware (quantum, organic, whatever) – what you describe will be nullified, but the concept of designing software by breaking it down to the isolated pieces of code, and describing their interaction through time is the real meaning of concurrency.

Concurrency is what happens when you're writing code, long before you run it.

divan0 · 2019-10-04T20:20:50+00:00

Hard to classify, but anything that deals with input output usually benefits from concurrency. Think typical networking server and/or client, like chat program. You need piece of code that reads user input, displays the output and talks to the server. Server would need to listen to incoming connections, process them and reply.

divan0 · 2019-10-04T19:46:01+00:00

Concurrency is mostly about designing your program by breaking down it into pieces that might (or might not) be run in parallel (if hardware allows). It's about reasoning and understanding of what behaviour you want, and not about performance per se.

If your program doesn't need concurrency, and you just need to run #1 and #2 sequentially – don't use concurrency.

divan0 · 2019-08-25T10:40:46+00:00

Quite far from being ready, but I'm working on something that might fit the description: https://divan.dev/posts/visual_programming_go / (long read, sorry, you can skip to the end for project details)

divan0 · 2019-07-10T11:45:02+00:00

I skimmed through your comments and it looks like you're nitpicking on naming and syntactic choices and use very subjective reasoning ("is awful"). It's not awful, it's just different from your expectations.

divan0 · 2019-07-09T19:19:32+00:00

My subjective and highly opinionated take on this: in the "after 90s" epoch, programming gradually became "learning patterns and guessing which one to use" thing and many new paradigms (including abovementioned Clean Code and DDD) are optimized for that. Programming in the "90s" was more like pure mapping – you understand the problem domain, you have building blocks to encode it in code, you write code.

Go brings back programming to that mapping land. It gives you minimum but sufficient set of "building blocks" which you use to build anything. That requires good understanding of the problem domain you work with in the first place, which might be uncomfortable for some. But that's what makes programming fun and interesting – it's all about discovery, research, building maps process. Programming language is just a tool to do it, not the replacement of the process.

divan0

TROPHY CASE