11 ms·

Hackery*, and I'm not sure why the hate towards CSS3. With a few lines of code I can build a pretty good looking responsive UI that doesn't take hours to polish

by dimgl 8y ago

Hackery*, and I'm not sure why the hate towards CSS3. With a few lines of code I can build a pretty good looking responsive UI that doesn't take hours to polish.

pjmlp 8y ago
Yeah, when running on a specific browser version targeting a single OS.
- pcwalton 8y ago
  That's hardly true when it comes to CSS3 stuff that's been around for a decade. Moreover, it's unfair to insist on portability when comparing native vs. Web without doing the same on the native side.
  - pjmlp 8y ago
    Only if the only browsers one cares about are latest version of Chrome and Safari. There plenty of deployment scenarios with other kinds of browsers. Of course it is fair, using something like Qt, wxWidgets, or even roll our own was never as complicated to get pixel perfect UI across OSes.
    - crzwdjk 8y ago
      Is pixel perfect UI really what you even want these days? With high-DPI screens and screen scaling being a thing, not everyone's pixels are the same. And that's not even talking about accessibility for people with low vision who want text to be big and readable.
sireat 8y ago
I'd give my left toe to learn to do this in a few lines of code in HTML/CSS3. Desktop centric UI toolkits provide a set of widgets which lets me build up a UI in a predictable way that respects my sanity. Windows Forms, WPF, Qt, vxWidgets, tkinter, Java AWT, SWT etc they all have warts but ALL of them feel faster than building UI for the web. The problem with web is that there are no consistent set of widgets. Let's take a stupid date picker. A year ago for a project I thought I'd use the HTML5 <input type="date"/> way no Javascript needed! Sadly I couldn't figure out a way to keep the calendar in an always on state so had to resort to jQuery datepicker. So jQuery widgets was an attempt to do what desktop UI does but now that is no longer in vogue. Today on the web there is no consistency, there is no agreed upon toolkit. How many different approaches to widgets does React have? Ideally you would be able to import a web component into your project and use it without worrying about any abstractions leaking.

by dimgl 8y ago

Hackery*, and I'm not sure why the hate towards CSS3. With a few lines of code I can build a pretty good looking responsive UI that doesn't take hours to polish.

pjmlp 8y ago

Yeah, when running on a specific browser version targeting a single OS.

pcwalton 8y ago
That's hardly true when it comes to CSS3 stuff that's been around for a decade. Moreover, it's unfair to insist on portability when comparing native vs. Web without doing the same on the native side.
- pjmlp 8y ago
  Only if the only browsers one cares about are latest version of Chrome and Safari. There plenty of deployment scenarios with other kinds of browsers. Of course it is fair, using something like Qt, wxWidgets, or even roll our own was never as complicated to get pixel perfect UI across OSes.
  - crzwdjk 8y ago
    Is pixel perfect UI really what you even want these days? With high-DPI screens and screen scaling being a thing, not everyone's pixels are the same. And that's not even talking about accessibility for people with low vision who want text to be big and readable.

sireat 8y ago

I'd give my left toe to learn to do this in a few lines of code in HTML/CSS3. Desktop centric UI toolkits provide a set of widgets which lets me build up a UI in a predictable way that respects my sanity. Windows Forms, WPF, Qt, vxWidgets, tkinter, Java AWT, SWT etc they all have warts but ALL of them feel faster than building UI for the web. The problem with web is that there are no consistent set of widgets. Let's take a stupid date picker. A year ago for a project I thought I'd use the HTML5 <input type="date"/> way no Javascript needed! Sadly I couldn't figure out a way to keep the calendar in an always on state so had to resort to jQuery datepicker. So jQuery widgets was an attempt to do what desktop UI does but now that is no longer in vogue. Today on the web there is no consistency, there is no agreed upon toolkit. How many different approaches to widgets does React have? Ideally you would be able to import a web component into your project and use it without worrying about any abstractions leaking.