186 karma · joined December 23, 2023
I wish there were more people using these alternative, somewhat decentralized services that weren't just tech people. Whenever I see some cool new fediverse technology or alternative protocl (e.g gemini), 99% of the conversation is just people talking about the technology itself. I originally joined facebook because I had friends on there, not so we could talk about the tech behind facebook
SDL does in fact make system calls and have OS-specific code (DirectX implementation, Metal implementation), even if most of them don't directly manipulate OS UI controls, though it can initialize a window with a rendering context on any of its OSs.
I feel like you're missing the point that performance matters less than accessibility for UI frameworks. HTML and CSS are the most popular choices because a child can learn them quickly. Native apps aren't as popular because all the frameworks out there require you to be an engineer to use them.
> 1. the idea that it's "easier" simply implies lower understanding of what is being done and that you aren't considering any of the edge cases you still need to handle.
I don't see how that follows at all. HTML is declarative and powers most applications at this point.
> 2. Not sure what to say here, as I don't know your point? it seems more about the type system of your language and not at all related to the ui toolkit
Web browsers are very forgiving with HTML errors, native UI frameworks (especially those which simply convert the markup to imperative statements) often refuse to run entirely if there's a single markup error. A native framework which seeks to become as popular as HTML would need to be as flexible as HTML
> 3. html, css, and the DOM all have a very clear model for how and what a UI is, claiming it isn't means that you haven't apparently spent much time working in any other system. Much like I keep meeting people who say that they don't have an accent, everyone else does
You're not understanding what I'm saying. You can run an ajax request and get some data, but to put that data into the UI would require you to run a query on the dom and manually set the innerHTML of the element to the new data. Some other UI frameworks will force you to bind specific variables or lists to a control in order to auto refresh when the bound variable changes. This is an opinionated framework: one which tells you how to manage updating the UI rather than allowing the developer to do it themselves. Such an opinionated framework would become more difficult for people to learn
> 4. Application development is conceptually complicated unless your application is not doing anything interesting. I'm also curious what makes a browser ui more "simple" than say Cocoa?
I have no experience with cocoa because I don't use a mac, but from what I can tell it requires you to know Objective C and run XCode. HTML requires, at the very least, notepad to write. It is extremely easy to get setup with HTML and start learning it as a lay person.
> 5. Sandboxing is a part of the OS, not the UI framework. All applications on iOS are sandboxed, that vast majority on macOS are.
You would want to make sure that programs written in this framework are sandboxed away from any resources. On Windows this means AppContainers and on Linux there are different implementations (snap, docker). But the host which runs and loads the UI should run all applications sandboxed by default (i.e: like a web browser)
I can see native software making a comeback if it is:
1. Declarative: only software engineers like imperative UI systems
2. Flexible: some frameworks (like any of the XAML-based ones) are strongly typed and you can only combine certain XAML elements with other certain XAML elements, and will fail to compile entirely if you mess something up
3. Unopinionated: HTML, CSS, and Javascript don't require you to implement any particular paradigm for getting data on the screen; that is left up to the coder
4. Dead ass simple: the litmus test is that a 7th grader should be able to learn the basics of it on their own, and the tooling should be ideally no more complicated than a text editor
5. Totally sandboxed: You can't trust 99% of frontend devs with security
The people you need to appeal to are not hardcore software engineers, but hobbyists and newbies, since they end up being the majority of frontend devs anyways.
Honestly I think you could get pretty far with just adding declarative languages (read: XML) to existing native frameworks, like gtk and Win32.
Within Win32, it's similar though there's an overuse of HANDLEs. I like initializing things as structs and I like that ComPtrs provide built in memory management. A lot of posix APIs feel underpowered (semantically designed around reading files from tapes), and Microsoft often provides a safe _s version of most of them (Yes, some of which are part of the C standard library and some of which are not). There are various Win32 APIs I like (IOCP, for example), and it's all tied together with MSVC and the static analyzers available to the compiler (SAL). I don't think GCC has anything even close to SAL. I also haven't found a C++ IDE I like nearly as much as Visual Studio. I used to hate jetbrains UI but I actually tried IntelliJ recently and they redesigned the entire thing to be quite nice now, so maybe clion is nice (but I'm not willing to pay for it).
I also VASTLY prefer powershell to bash