141–148 of 148 posts
Earlier quoted context omitted.
Dreamweaver has existed for 25 years and it’s still around.
Well MS-DOS is still around. But nobody uses it because the industry moved to more efficient software after seeing there are better ways to solve the problem.
Bravo. Soon, developing point-and-click, drag-and-drop apps will be almost as easy as it was in 1998 with Visual Basic 6. I (mostly) jest, but yeah, this is marvelous. I'm developing a small React app this weekend, I'll use this and make sure to report any bugs or issues along the way. Thanks a lot for making something that makes other people (me!) excited!
Earlier quoted context omitted.
Yeah I can learn a lot from React Studio—I think a lot about keeping the learning curve down for growth, so I'm glad you pointed that out. I'm focusing on enterprise sales next and actively looking for people to help with that, so again I think you're right. Thanks for the feedback!
You're welcome, and I hope you crack this — the industry is stuck in a local maximum with tools based on what are essentially 1970s concepts (unstructured code-as-text and unstructured vector graphics). Two more random thoughts on this topic... I've long felt there's an important role missing in our industry. Architects don't draw a bunch of façade sketches, ask people if they look good, and then send them to constru…
You mean a UX Designer? I see that role a lot
Earlier quoted context omitted.
What are the advantages, really? I used to use tailwind for my site, but then I realized I was essentially writing plain CSS in some DSL. Writing the plain CSS directly and using a few CSS variables for things like color and spacing simplified the whole thing greatly.
For personal projects it might be overkill depending on the scope. But if 2+ people are working on a constantly evolving system, shipping new features, and want consistency in the design system? It’s a solid foundation.
I mean… i know it’s hard. I’ve tried discussing patterns and our self-made “dialect”, and it’s a hard conversation. Using some 3rd party’s tooling makes it easier because you can all defer to the higher authority. But what if you actually agreed on some patterns and made that part of your process? To start with, it would feel like you were writing an overly prescriptive style guide and people would look at you funny… but what’s the difference between using using a 3rd party dialect and making up your own?
Bravo. Soon, developing point-and-click, drag-and-drop apps will be almost as easy as it was in 1998 with Visual Basic 6. I (mostly) jest, but yeah, this is marvelous. I'm developing a small React app this weekend, I'll use this and make sure to report any bugs or issues along the way. Thanks a lot for making something that makes other people (me!) excited!
or winforms and C#! tbf, building a ui with an absolutely-positioned, pixel-bound presentation engine was AWFUL without a designer. anyone work with Win32 APIs back in the day? 60 lines of code just to open a window without even drawing anything on it! building a ui in code is a lot easier with flow layout and a good component library
Bravo. Soon, developing point-and-click, drag-and-drop apps will be almost as easy as it was in 1998 with Visual Basic 6. I (mostly) jest, but yeah, this is marvelous. I'm developing a small React app this weekend, I'll use this and make sure to report any bugs or issues along the way. Thanks a lot for making something that makes other people (me!) excited!
VB6 is awesome, and I wish it could remain in use. Unfortunately, being proprietary and closed, it was and continues to be at the mercy of its owner.