Conversation
Notices
-
Embed this notice
Sexy Moon (moon@shitposter.club)'s status on Wednesday, 27-Sep-2023 20:20:24 JST Sexy Moon css-in-js exists because of need to integrate with total javascript frameworks like angular/vue not because programmers hate women. Many people are writing web applications and CSS isn't actually well suited to that, it was created for when the web was primarily static documents. - Haelwenn /элвэн/ :triskell: likes this.
-
Embed this notice
narcolepsy and alcoholism :flag: (hj@shigusegubu.club)'s status on Wednesday, 27-Sep-2023 20:23:37 JST narcolepsy and alcoholism :flag: @Moon idk man css is perfectly viable, there are some edge cases but those are somewhat rare. -
Embed this notice
Sexy Moon (moon@shitposter.club)'s status on Wednesday, 27-Sep-2023 20:28:43 JST Sexy Moon @hj it's viable but css-in-js can lower cognitive load. POTENTIALLY. I personally would rather have simple enough style that a static CSS is all that is needed but there are many web applications where I don't think a static style is sufficient -
Embed this notice
narcolepsy and alcoholism :flag: (hj@shigusegubu.club)'s status on Wednesday, 27-Sep-2023 20:29:57 JST narcolepsy and alcoholism :flag: @Moon idk it does the opposite for me. -
Embed this notice
Sexy Moon (moon@shitposter.club)'s status on Wednesday, 27-Sep-2023 20:30:35 JST Sexy Moon @hj Well the nice thing is a project can choose to use it or not. -
Embed this notice
narcolepsy and alcoholism :flag: (hj@shigusegubu.club)'s status on Wednesday, 27-Sep-2023 20:32:47 JST narcolepsy and alcoholism :flag: @Moon well, much like typescript. You might say it's nice that there's a choice, but you'll talk differently after a half a year of being forced to work with it and hating it but unable to do anything about it because it's not your choice and convincing others on the project is infuriatingly difficult Haelwenn /элвэн/ :triskell: likes this. -
Embed this notice
Sexy Moon (moon@shitposter.club)'s status on Wednesday, 27-Sep-2023 20:38:47 JST Sexy Moon @hj You are right but this is true for all technology choices. -
Embed this notice
Jezza™@threads.com (Official) (jeremiah@noagendasocial.com)'s status on Wednesday, 27-Sep-2023 20:45:23 JST Jezza™@threads.com (Official) @Moon the web isn't well-suited to writing web applications.
-
Embed this notice
Sexy Moon (moon@shitposter.club)'s status on Wednesday, 27-Sep-2023 20:45:23 JST Sexy Moon @jeremiah that is the point of frameworks, they mitigate but don't solve this. -
Embed this notice
Sexy Moon (moon@shitposter.club)'s status on Wednesday, 27-Sep-2023 20:48:49 JST Sexy Moon @mcread @jeremiah webapps work fine -
Embed this notice
MC Read ☦️ (mcread@noagendasocial.com)'s status on Wednesday, 27-Sep-2023 20:48:50 JST MC Read ☦️ @Moon @jeremiah the only mitigate the writing part ...not the functioning part
-
Embed this notice
narcolepsy and alcoholism :flag: (hj@shigusegubu.club)'s status on Wednesday, 27-Sep-2023 21:08:36 JST narcolepsy and alcoholism :flag: @Moon @jeremiah @mcread web kinda is the best thing we have, apart, say, macromedia flash and likes, which are dead.
When making a UI you'll most likely face 3 kinds of problems:
1) you need some custom component
2) you need to render a rich document (even just text with hyperlinks), possibly with formatting, i.e. chat messages, emails, etc.
3) your entire UI might as well be an Excel table or Access database that need to be accessed remotely or integrated into something else.
Custom components are incredible pain in the ass to make, imagine having to manually do canvas for something trivial. Meanwhile in web you have the versatile <div> that can do pretty much anything, there's barely anything like that in Delphi, Qt, WPF etc.
If you need to render something "rich" your only options really are either RTF component (very limited), embed a browser, or get some custom component that's bound to be proprietary and expensive and quickly outdated, so people stuck with browsers, email viewer is a browser, chat view in older messengers are often browser, and if you need to render multiple contents, it's more efficient to just use one browser for all instead of spawning separate browsers for each, especially for things like chat messages.
If your UI is a glorified excel table or database, it's much cheaper and convenient to make web ui than trying to make some sort of native application (or making remote MS Access forms or whatnot)
If you look at point 2, you can see how browser ends up overtaking the entire application as you need more and more from it.