Yeah, I was waiting for the DS1525+, but after it was announced and the HD restrictions were confirmed, I eventually decided to buy the DS1522+ instead.
Which when clicked, opens an alert with 2 lines like this:
Bookmarks.txt is a concept of keeping URLs in plain text files | Hacker News
https://news.ycombinator.com/item?id=45047572
I then paste this into my bookmarks.txt and have a simple text editor script to perform fuzzy searching on it and open a web browser tab with the found URL.
The initial version of my online Numeric Base Converter (https://apps.4fips.com/nubco/) was done in a day, mostly to try out Rust + egui. The app hasn't changed much since then, and I no longer have to search for some random online converter when I need one :)
No so long ago, around 2012 :), I was still using my Psion 3c + a short OPL program, to trigger my hacked time lapse camera over serial line. It worked quite reliably for years.
https://forums.4fips.com/viewtopic.php?t=717
Funnily enough, my next foray into coding (after OPL) would be scripting timelapses on my Canon PowerShot with CHDK [1] — wish I’d thought of doing it with a Psion though.
Here's mine: https://www.4fips.com (mostly tech topics, random projects & photography, basically anything I find interesting at the moment, I've been maintaining this page for many years)
Yeah, for example passing such an opaque typedef as const is a common trap and very often source of surprise (even for the author of the API), something like:
struct Opaque {
int data;
};
typedef Opaque *OpaqueRef;
void bar(const OpaqueRef ref) {
ref->data = 42; // compiles fine, ref is 'Opaque *const'
}
void baz(const Opaque *ref) {
ref->data = 42; // does not compile, ref is 'const Opaque *'
}
Text in labels and other controls is not selectable (unfortunately), in this regard egui behaves as a native app, so mostly just editable texts are selectable. This feels a bit unnatural on the web, but one must consider that egui uses a custom WebGL renderes, so the content is not backed by standard DOM.
The text in the textbox is selectable, so it's not like egui can't handle text selection. It's just following convention with making GUI text unselectable.
Non-copyable texts by default in "native" applications sounds reasonable but is actually one of those things that introduces unnecessary friction down the line when users try to write tutorials or reports and have to manually type out everything.
Yeah, I would like to see that behavior as an option, or even better allow to select the whole UI as a block of text (to feel natural and be searchable on the web). I belive any UI (incl. native) should not prevent you from copying any text.
Yeah, I believe accessibility is not addressed at all. Similarly when compiler for web, it would be great if the UI would actually behave as text (actual web page) and could be copied into the clipboard etc.
I'm using it for some of my little tools, and it's pretty seamless going between native and web, which I appreciate a lot, and unlike other non-native UI frameworks, navigating through egui feels pretty natural (the way input are handled etc).
At least C is a complete language and a solid building block which is possible to reason about, compared to C++ which is becoming more and more bloated in a modernization attempt, so C++ projects need to be constantly updated and rewritten to catch up, which rarely happens in practise. On the other end, C++ can hardly adopt things like memory model based on Rust's borrow checker, so in this regard C++ is a dead end.
In my mind, C++ is one of the only languages that is evolving with the times.
They don’t add features that break backward compatibility, or features that sacrifice runtime performance especially if you don’t use those features. Most new features added to C++ are actually just additions to the STL, which you aren’t forced to use.
It is an open standard, so there is plentiful competition in the realm of compilers. Rust only has 1 so you are SOL if you don’t like something or if the project goes bust one day.