Hacker Newsnew | past | comments | ask | show | jobs | submit | hilti's commentslogin

I will definitely give it a try. Terminal UI‘s are super interesting in my opinion, because I feel like they can improve productivity. Hopefully this library can be compiled into a single binary that exposes an application icon. That’s one of the biggest hurdles I experienced with „GUI only“ users - they want something to double click on to start.

I am learning C++ and ImGUI. My first app is a JSONL Viewer. Recently I‘ve added support to read parquet files (uncompressed) too.

https://iotdata.systems/jsonlviewerpro/

Next step is to integrate a visual data pipeline by using ImNodes. I‘m slowly making progress in my experiments, but C++ has a steep learning curve, especially when targeting MacOS and Windows at the same time.


First of all: Thank you for giving.

Giving 24 years of your experience, thoughts and life time to us.

This is special in these times of wondering, baiting and consuming only.


Really beautiful!

I am absolutely impressed by their design.

I really tried to read the comments on heise.de … but their website is the perfect example if ad revenue drives a company instead of providing value to their readers. Why do users have to create another page impression to read a comment?

To Heise's (slight) defense, their forum system is at least 24 years old, extrapolated from checking the date of my first comment on it. Probably even older. Apart from driving page impressions, there didn't seem to be an incentive to make the experience smoother, as user engagement is still very high.

You dodged a bullet there. Heise is infamous for incendiary, low quality discussion.

heise is older than online ads.

I’ve been burned by metadata platforms twice now and honestly, it’s exhausting.

The demo is always incredible - finally, we’ll know where our data lives! No more asking “hey does anyone know which table has the real customer data?” in Slack at 3pm.

Then reality hits.

Week 1 looks great. Week 8, you search “customer data” and get back 47 tables with brilliant names like `customers_final_v3` and `cust_data_new`. Zero descriptions because nobody has time to write them.

You try enforcing it. Developers are already swamped and now you’re asking them to stop and document every column? They either write useless stuff like “customer table contains customers” or they just… don’t. Can’t really blame them.

Three months in, half the docs are outdated.

I don’t know. Maybe it’s a maturity thing? Or maybe we’re all just pretending we’re organized enough for these tools when we’re really not.


I agree with your points about ImGui's intended use case, though I think the landscape is a bit more nuanced. You're right that ImGui excels for dev tools and that its non-standard UX isn't ideal for end-user apps. That said, devs reach for ImGui in end-user apps because lightweight cross-platform alternatives are scarce. Qt is heavy, Electron is heavier, native toolkits mean multiple codebases. I built a techy tool with ImGui (JSONL Viewer Pro) and it works well enough for users who care more about functionality than polish. Not saying it's right for consumer apps, but for technical tools it can be pragmatic.


> but for technical tools it can be pragmatic

I've thoroughly enjoyed using ImGui for tooling around image processing, computational geometry, a bunch of 3D projection stuff. The fact that it's based on OpenGL or Vulkan or whatever backend you want is a big win for this kind of work. I can just take a bunch of pixels, throw them into a texture, and render some quads with those textures painted on them after going through some 2D transformations or 3D projection/transformation. It's quite beautiful for all of this. ImPlot for doing basic data plotting and the built-in ImGui widgets for controlling the whole thing.


Exactly, I was working on a little client for a self-hosted server app. Imgui is a rare mix of fast, lightweight, trivially cross-platform and stable, so I went with it and had the client easily compiling for Windows, Linux and browser, while being trivial to work with.

I have otherwise mostly given up on making GUI applications because I simply don't have time to pick up a bunch of UI toolkits for all the different platforms, pulling a massive dependency into my project and requiring constant maintenance to keep the program working.


It also have bindings for a ton of languages, so for people who jump languages a lot, it's always nice to be able to reach for something more familiar that you can learn across different codebases but same concepts. Same thing for the backend/engine, UI code remains the same, but easy to switch to others or even wrapping it yourself for platforms that are under NDA.


I know that at least one modding framework for a certain online game makes use of ImGui (or some equivalent thereof). Given the use case it does make a lot of sense, considering they're essentially strapping a third party UI onto an existing 3D accelerated application, not sure what else you'd use for that. Since the users are technical enough to install the mod framework anyways, they tend to be the sort that can handle the UI.

It can be a bit wonky though, I regularly spot UI/UX decisions that seem to map more closely to what the developer is doing under the hood, or their own mental model of the problem, than what one might consider to be an intuitive way of interacting with the system.


Not the author but it‘s implemented in only two files which can be studied on Github.


Oh wow … I did this in the late 90s with PHP - roughly 30 years ago - and my websites worked without Javascript


I'm wondering if the people saying "php is bad" nowadays are not the same that keep reinventing php concepts in node.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: