It’s reasonably easy to guess exactly what you paid for the game, since the only change in price since launch was a $5 bump in January last year. It’s never been on sale.
Just another Swedish programming sysadmin person.
Coffee is always the answer.
And beware my spaghet.
It’s reasonably easy to guess exactly what you paid for the game, since the only change in price since launch was a $5 bump in January last year. It’s never been on sale.
It releases while I’m on the way back home from a trip to Manchester, might have to bring my Deck so I can play on the flight/train.
It’s somewhat amusing how Itanium managed to completely miss the mark, and just how short its heyday was.
It’s also somewhat amusing that I’m still today helping host a pair of HPE Itanium blades - and two two-node DEC Alpha servers - for OpenVMS development.
Going to be really amazing to play Factorio again without knowing how to solve everything.
Go has a heavy focus on simplicity and ease-of-use by hiding away complexity through abstractions, something that makes it an excellent language for getting to the minimum-viable-product point. Which I definitely applaud it for, it can be a true joy to code an initial implementation in it.
The issue with hiding complexity like such is when you reach the limit of the provided abstractions, something that will inevitably happen when your project reaches a certain size. For many languages (like C/C++, Ruby, Python, etc) there’s an option to - at that point - skip the abstractions and instead code directly against the underlying layers, but Go doesn’t actually have that option.
One result of this is that many enterprise-sized Go projects have had to - in pure desperation - hire the people who designed Go in the first place, just to get the necessary expertice to be able to continue development.
Here’s one example in the form of a blog - with some examples of where hidden complexity can cause issues in the longer term; https://fasterthanli.me/articles/i-want-off-mr-golangs-wild-ride
Go really does do well in the zero-to-hero case, that’s for certain. Unfortunately it doesn’t fare nearly as well in terms of ease when it comes to continued development.
Especially if you - like Microsoft - consider “Unicode” to mean UTF-16 (or UCS-2) with a BOM.
Do you have WebP support disabled in your browser?
(Wasn’t aware my pict-rs was set to transcode to it, going to have to fix that)
To be fair, having to interact with MS Teams with any part of your body is painful.
I feel like this could go really well together with Piet.
Just imagine; an album consisting of a bunch of Velato programs with Piet code as the artwork.
Version requirements? No rules!
He won’t be allowed to perform at Eurovision with the Windows 95 name/trademark/logo, so it would be hilarious if he switches to a name like Linuxman during it.
Here’s a .jxl
JPEG-XL upload I did on Lemmy three days ago;
https://lemmy.ananace.dev/pictrs/image/ad4e745e-0135-4cc3-889c-052600828d82.jxl
The built-in Firefox support is only activated for unstable builds, so you can’t enable it on stable unless you manually enable it during compile-time.
Why is it .jpg
and not .jxl
? That’s the registered extension for JPEG-XL.
I can already imagine so many fun ways this could be used.
“We interrupt your regular scheduling to bring you this additional bit of Factorio hype.”
It could be interesting with something like the old Pharaoh game and its receding riverbed farming, but you’d have to balance that compared to costs of resourcing in Factorio - or offer some reasonably simple way for the player to protect their resourcing operations against the rising lava.
My guess is that drilling is going to cause the Vulcanus-version of pollution, since it makes sense that a volcanic planet wouldn’t have much problem with regular pollution.
I assume both the $20 and $25 prices were during alpha/early access. Was thinking entirely of release pricing.