Thread replies: 6
Thread images: 1
Thread images: 1
How can anyone use bloated shit like dreamviewer for web development?
When I started getting into html/css I always dreamed of drag and dropping my sites together with some nice bootstrap and tons of js frameworks because I was too lazy to do anything myself, I quickly realized that all of that stuff actually costs way more fucking time than simple opening atom, opening index.html and style.css in seperate tabs, and ctrl+s'ing after every edit. When you do it often enough you automaticly do it after every little change and combining this with several monitors and a hotkey for refreshing your site, everything just becomes so freakin efficient.
Whats the fucking point of messing around with expensive ass adobememeware???
>>
>>59548299
dreamweaver was relevant in early 2000s
>>
If you actually learn how to use Dreamweaver it also becomes "so freakin efficient".
>>
Because it gives a sense of superiority to the stupid people who buy it.
>>
>>59548759
>If you actually learn how to use Dreamweaver it also becomes "so freakin efficient".
Efficient your ass.
Webpack + hot reload IS efficient!
>>
I started with dreamweaver. And I always struggled to get all the sizes right. Because I used it as a wysiwyg editor without knowing what I was doing.
Then I once jokingly followed a css tutorial using notepad. And I had a pretty neat but basic site within a day. Everything went so smooth I never looked back. Since then I never touched dreamweaver again.
Then I tried to use Wordpress. Where they recommended to modify using a child theme. That didnt work at all. I had no idea how the theme of the other person worked. Then I made a theme myself, learned some very basic php and javascript while doing it, and the results were great.
You advance so fast if you just build shit manually. But its hard to foresee what you will be learning before you start doing it.
Thread posts: 6
Thread images: 1
Thread images: 1