tov_objorkin

5 ms·

1.
by tov_objorkin 5mo ago
The product has a typical lifespan of 3–5 years, they just don't need LTS. RKISP(ImageSignalProcessor) is piece of code glued to the kernel, fast and cheap. The mainstream version provides proper integration with Linux multimedia subs
2.
by tov_objorkin 10mo ago
In my case, only part of the program is recompiled and re-evaluated. The rest is located in a "committed" frozen area. Users can try new changes and throw them freely. The editor performs an evaluation/rollback on every keyst
3.
by tov_objorkin 10mo ago
Nice, the main problem is a broken state. I use immutability at the language level to prevent disaster code changes. So, the program during live coding is literally unkillable, and you can jump back to the saved checkpoints without restarts
4.
by tov_objorkin 10mo ago
The tool uses a Forth-like language with immutable data structures and persistent memory snapshots. It also uses Clojure style meta-data and compile-time meta-programming. I have no luck convincing people that a language without curly brack
5.
by tov_objorkin 10mo ago
Maybe this is some kind of art that doesn't need to be useful.
6.
by tov_objorkin 10mo ago
I wish to have the skills to explain my work as well as Bret Victor does. Editing, reverting, and committing parts of a running program feel alien to users.
7.
by tov_objorkin 10mo ago
I was greatly inspired by his work. After getting enough skills, I even built my own IDE with live coding and time traveling. Its practical use is questionable, and it seems like nobody is really interested in such tools. Playground: https
8.
by tov_objorkin 10mo ago
Bold plus, making PLs is a lifestyle, not a business. Most PLs clones each other and absorb features. The only difference is QOL and tooling. Users expect to have a full set of batteries, an IDE/LSP, jobs, OOP style, and minimal effort
9.
by tov_objorkin 10mo ago
Disagree, there is no types in Forth, only cells. User is acting as a compiler. Comparing to C, imagine that every keyword like for/while/break is implemented as a macros using setjmp/longjmp. And this is a strong part of the
10.
by tov_objorkin 10mo ago
Factoring is good way to reduce the complexity but writing math is painfull experience. To be fair, the infix version of Forth exists as an extension library.
11.
by tov_objorkin 10mo ago
Forth is pretty lowlevel, i don't think it can compete with the highlevel languages. Postfix notation and stack juggling is just boring.
12.
by tov_objorkin 3y ago
One very stupid reason is the Qt itself, graphics application can't live without the QScreen instance. If user unplug every screen from the system, in order to prevent crash qt create the fake screen and hang in the headless state.
13.
by tov_objorkin 3y ago
LLVM have MSIL translator back in 2007 [1], it was abandoned die to lack of interest. 1. https://discourse.llvm.org/t/msil-backend/8480
14.
by tov_objorkin 4y ago
I have backend for the Hisilicon SoC from 2016, its about 1500 lines of C code, few calls to 2D API and copypasta of the triangle rasterizer. Dunno about modern version requirements.
15.
by tov_objorkin 4y ago
Borrow checker is fine. But from the library writer perspective its pain and take enormous amount of time to make it sound. One does not simple checkout "nom" and test thing in few minutes.
16.
by tov_objorkin 4y ago
Oh, please, making reasonable good DSL might take a month or even years. Also wrestling with parser and borrow checker not an easy task for average user.
17.
by tov_objorkin 6y ago
We're social animals, this is hardcoded part of our brain. Managing solitude require training as anything else.
18.
by tov_objorkin 7y ago
You're technically right, i mean if user aim for durable code then using unwrap is not desired behavior most of the time. For example pointer deference in C is implicit operation. In Rust user must choose explicitly how to handle Optio
19.
by tov_objorkin 7y ago
unwrap() or expect() unconditionally smash program execution in case of error. Properly written program should handle such errors or use unwrap_or_* as fallback. The point is that unwrap/unsafe is breaking safety rules, user writing on
20.
by tov_objorkin 7y ago
About JS, i made wrong assumption that we entered v8 era and my number crunching code should work reasonable fast everywhere.
21.
by tov_objorkin 7y ago
About five years ago i have a dream, that i can abandon all this peasant C/C++ development and jump into mono/xamarin train. As a main product we have Linux ARM/MIPS karaoke machine with optional remote control via desktop&#x
22.
by tov_objorkin 7y ago
Once i have a dream about RN application for iOS/Android without Xcode and AndroidStudio. Started with Expo, great tool if you don't have native modules. But i have, very complex search library in Rust. After few attempts the code
23.
by tov_objorkin 7y ago
Empire nailing Assange to the cross. Take your seats, enjoy the show...
24.
by tov_objorkin 7y ago
In the Herbert Dune, civilization collapsed because of smart machines. So after renaissance they are completely banned for the future use.
25.
by tov_objorkin 8y ago
FlatAssembler is amazing. I remember people making fractal images using only preprocessor [1], JVM bytecode compilers and a lot of other cool stuff. Also it is a powerful editor, you can abuse 'file', 'load', 'store
26.
by tov_objorkin 8y ago
If you need fast small function use NIF, for large logic blocks better use C node its safe and isolated.
27.
by tov_objorkin 9y ago
Oh, ti c/c+ compiler is such a joke, not event c99 supported. I was thinking about rust to C compiler [1], but thats require c11 support. 1. https://github.com/thepowersgang/mrustc
28.
by tov_objorkin 9y ago
The horrible thing about QtCreator is plugins support. Most of them unstable and crashing IDE. Dependency on Qt SDK private sources killing all my attempts to maintain my own plugins.
29.
by tov_objorkin 11y ago
This one https://en.wikipedia.org/wiki/Ternary_computer incompatible with everything ahaha
30.
by tov_objorkin 12y ago
CHICKEN Scheme is not a purely functional its allow mutations and inline C code http://wiki.call-cc.org/man/4/Accessing%20external%20objects...

More ›