Pinned Tweet
It's a great honor to work on this with the fellas. Pretty incredible that we've gotten this far and there is more good stuff to come!
Moritz Falk retweeted
It's a great honor to work on this with the fellas. Pretty incredible that we've gotten this far and there is more good stuff to come!
Moritz Falk retweeted
Radical Pie handles equations brilliantly but still needs Word for a document's main text. That comes with annoying problems that will never be fixed. For years, I've dreamt of writing the whole word processor with the same level of craftmanship, and now that is going to happen.
Moritz Falk retweeted
Nice article!
Had strong deja vu while reading this to the UIPainter created at Guerrilla in 2014 or so that I did some work on back then, though at the time that didn’t have the caching layer described here.
So was funny to see this at the end. Time is a flat circle :-)
A look under the hood of Blick. @falk_moritz shares how our UI renderer works and some of the decisions that shaped it. blickeditor.com/blog/caching…
Moritz Falk retweeted
A lot of people don't understand that "immediate" in immediate UI refers to API that's exposed to the caller. There's no requirement that immediate UI has to always spin at refresh rate, or that it always has to redraw every pixel.
This is a great article article about cached rendering in a very complex UI (video editor) made in immediate style.
Moritz Falk retweeted
First Blick development blog post by @falk_moritz, if you're wondering how fast and resource efficient immediate mode UI can be for desktop applications, you can read about it here!
A look under the hood of Blick. @falk_moritz shares how our UI renderer works and some of the decisions that shaped it. blickeditor.com/blog/caching…
The UI renderer for Blick was cooking for some time now. I am very happy with how it turned out!
A look under the hood of Blick. @falk_moritz shares how our UI renderer works and some of the decisions that shaped it. blickeditor.com/blog/caching…
Moritz Falk retweeted
Added bloom to my engine.
I'm not a huge fan of super heavy post-processing, but some amount of bloom is needed to show high-dynamic range on an LDR display, and also to avoid harsh edges on bright objects.
Looks nice too!
This is rendering at 4k in about 0.1ms -
1/
Moritz Falk retweeted
SilverNode 0.9 is here 📸, the biggest update yet:
↩️ Undo for everything
🎨 Skin tones on the vectorscope
🖼️ Alternative edits
🎯 A white balance picker
✨ …and a lot more
Take the quick tour 👇
Free beta: silvernode.io
#photography #RAW
Using an M series MacBook feels like I am using a proper modern laptop for the first time.
I can just use it for a whole day without any worries or compromises.
Moritz Falk retweeted
the mode loc you have the more instructions your CPU has to run.
the more instructions your CPU has to run the slower it is.
lines of code are a liability.
Moritz Falk retweeted
PETAFAB: Teaser trailer is out!
youtube.com/watch?v=NDLACyme…
Music by Ari Pulkkinen (Resogun, Nex Machina, Super Stardust HD).
Video editing by Timo Vasara.
Moritz Falk retweeted
Blick 0.4 is out! Huge new features: We added scripting support!
Also image sequences, markers, clip sync, flip and mirror, and a long list of editing improvements.
Moritz Falk retweeted
If you build something nobody else can, you can avoid the rat race for the promise of marginally better efficiency. You can ignore fearmongering about "being left behind". Order of the Sinking Star proves this. A language, engine in that language, and an unimaginably massive game in that engine, all from scratch, all in ten years.
Economic sustainability is important, so efficiency is not to be ignored. But Thekla/Jon were not worried about someone beating them to the punch, because nobody else could've built that game, in the way it was built. They could've built a similar design in an existing language, or using a prebuilt engine, but it didn't matter, and now they've produced far many more artifacts than just the game itself, and they have far more control and ownership over all such artifacts.
Another excellent example would be Nintendo. Subtle intangibles of their organization make their work vastly more important to fans of their IP than knockoffs would ever be. So they aren't racing anyone. Again, efficiency is not *unimportant* to that organization, but they can't be "left behind".
Moritz Falk retweeted
I wanted to show how janky the AI slop is of the FilmCraft software.
I wanted to set the stage for how bad it is, and how little care there has actually been in implementing this tool, and most definitely the entire Craft suite too.
It's all AI slop that does not even work.
Moritz Falk retweeted
After TEN LONG YEARS, Order of the Sinking Star is out Now! On Switch 2, PS5, and ... it's at the top of Popular New Releases on Steam, already!
Thank you everyone for your support during this long, long, long, long, long development!
Moritz Falk retweeted
Dear God this is awful. So grateful for @Blick_Editor, which was made with actual care and attention to detail.
Todos los productos de Adobe reimplementados desde cero, gratuitos y de código abierto
→ getartcraft.com/apps
Moritz Falk retweeted
Zeiger Image Viewer 0.2.0 is released:
Support for RAW formats through Libraw, light controls with a histogram in the adjustments editor, support for DDS textures, cube maps and texture arrays, expanded color picker; source and wyswig, and much more!
completely free, link below
Moritz Falk retweeted
Odin just got a new MASSIVE update!
Huge speed ups in compile times for development builds, performance improvements to `map`s, allowing bit_set to be backed by arrays of integers, a complete parapoly rewrite, and so much more!!!
You won't believe it!
github.com/odin-lang/Odin/re…
Moritz Falk retweeted
There is one positive side effect of everyone jumping onto the AI / "never write or read code" boat:
You can more easily filter out the people who were genuinely interested in code architecture and cared about the craft.
For most others AI fills the same role previous tech inventions did. Automatic memory management, library abuse, the whole web abyss stack etc..
If you don't care about the technical aspects of your project and just want to ship as fast and as often as possible, then AI is simply more of the same.
That's not to say that good programmers should reject AI. But there's a difference between
"I don't care about the code"
and
Using AI to learn, analyze, find bugs, prototype, assist, etc.
























