What unpopular webdev opinions do you have?

  1. Learning JavaScript before you can build a basic website with server side rendering is going to stunt you for life.

  2. CSS is massively underrated by a large number of front end devs. They'll use JS to do something that could very easily be done in CSS.

  3. True, BUT: This only works with scoped CSS in a component, and even then, I do prefer JS oftentimes. It's much easier to miss some cool and funky CSS shenanigans than missing a function call.

  4. The internet having a lot of shit for free on it is both amazing and ruinous to people's expectations. On the plus side, I find that paid services are absolutely worth it. I use Laravel Forge for deploying and managing a site and it's utterly ridiculously easy. Like "one click to add SSL for free" type easy

  5. The most enjoyable when center divs, adding beautiful box-shadows, and border radius to give it that clean floating div with slightly rounded corners!

  6. The aesthetic of your IDE matters, this is probably not unpopular but I went to school for CS for a bit and man the IDE’s were awful looking… outdated and white, no colors for different tags or variables, as someone with ADHD that makes it painful to sit there and enjoy it. Give me dark mode with colorful code all day. I’ve also found changing your theme every once in awhile can spice things up a bit.

  7. Firefox devtools are better than chrome, Firefox in general is better than chrome and Mozilla's dev resources are a better read than W3School. Safari is the new IE

  8. Yup, making the switch back to Firefox from Vivaldi today in part because of the dev tools. More so because of the extension changes coming down the pipeline for Chromium browsers, but I really find Chromium's devtools to be a pain in the ass to use.

  9. The one thing that keeps me coming back to chrome devtools is the custom network latency. Super helpful for looking at loading states. But the firefox dev tools work well for everything else

  10. Design tools are way too focused on pixels and not focused enough on structure. Designers should be aware of the tag structure they are asking for and have basic awareness of its effect on accessibility and styling.

  11. So in this case, the most downvoted posts are what most people agree that they're unpopular opinions, right?

  12. Jetbrains tools are fantastic. I do freelance and independent contracting work, and pay for the All Products Pack for myself.

  13. I'm using PHPStorm now because of my new workplace. It's insane how good it is. It does everything right.

  14. At my new job everyone is using it and they suggested to try it and see if I like it... And I absolutely love it after literally couple of days of using it - I don't think I'll be able to use VSC now!

  15. Most people that don’t use an IDE never really tried a good IDE. It seems they just like to work everyday until 8pm instead of just being productive with the right tools.

  16. Ad. 1. - literally my previous client. Simple landing page, but don't even think about not using React.

  17. 80% of react code you write (less the JSX which we can largely equate to HTML) is to make react happy. The other 20% is actual web dev and business logic.

  18. Tailwind is messy but if you are using it with components (react, svelte etc…) then your code is more readable atleast for me cuz i dont have to write css into different files and switch between .tsx and .css

  19. Got a new job 1y ago. I wasn't really sure if I should accept it because PHP was one of the main requirements for the position I applied for. The interviewer/boss convinced me that PHP nowadays is not that bad anymore and it's sort of comparable to java. He couldn't have been more right.

  20. Laravel is freaking incredible, PHP 8 makes perfect sense to me. I've never worked on legacy PHP so I guess I'll never understand the hate, but good lord have I learned a lot just seeing how Laravel is structured and taking lessons on Laracasts

  21. Dammit you took all of mine. Maybe these opinions are more popular than the increasingly Saas driven blogosphere would have us believe.

  22. If the site is navigable, responsive, and does not hurt the eyes. A much much much better design will barely affect conversions.

  23. That's comparing apples to oranges. If you need a complex site or single page app that you needs to scale well, then you either use a JS UI framework, or you end up making your own.

  24. to also add its ok to have the mindset when building a website to you don't have to use the shiny new frameworks or library's if you can do the job in vanilla HTML CCS and JS then do that.

  25. It's better to use a website that looks like Yahoo in 1998 and easy to find what you are looking for than a modern website with animations and all but it's a pain in the ass to find what you need because it's hidden under many pages, sections and drop down menus

  26. The fact that most site will be accessed from a mobile device prevents freedom. Mobile-first is just a mindset for building with those limitations in mind. The circumstances are what they are, and all we can really do is build around them.

  27. My personal opinion is that it depends on what project you are doing.. if you know that 90% of users will use the mobile version why wouldn’t i go for mobile-first design?

  28. Class-based CSS frameworks... Oh my fucking god I've never seen this much DOM noise in my life than with these. They make nested divs with no classes look like masterpieces

  29. I accept the trade-off of dom noise (not gonna deny it) in exchange for not having to think a lot about class names, not having "append only" stylesheets, the reduced resulting css size, and the speed of development.

  30. That’s not an unpopular opinion, there’s a “I don’t like tailwind” post like almost every day in this sub.

  31. I greatly prefer Angular to React. It's easier to stay organized, it uses TypeScript by default, it uses MVC and separates its services (i.e. HTTP calls) from the main logic, and it doesn't have dozens of third party libraries clogging it up.

  32. Agreed. Opinionated frameworks allow for development to be consistent across projects / teams / and orgs. Sure it can be faster to get up and running with React. But at the end of the day I’d rather make less decisions on what router, state manager, etc to use and focus more on building features

  33. Came here to say this. Angular feels like it was designed as the logical next step in web development organization. Everyone says, “Learn html, css, vanilla JavaScript, and then learn React,” but i feel like Angular gives you a better understanding of component and framework structure, and React tries to mesh so many things together that it actually makes it more difficult to understand than Angular.

  34. Angular is fine, I'm not sure why it's become super unpopular. If I had to build a SPA with a large team I'd probably go Angular all day over React.

  35. Front-end webdev is not unnecessarily overcomplicated. People often complain about how you need a gazillion tools (like webpack) to do simple things. It's true that it's complicated, but it's not without a good reason. These complex tools weren't created to make your life harder.

  36. This right here. Most people feels like front end is complicated too much. In fact, doing front dev without any tools is now more complicated than using tools. Why the hell someone would care about how to make a pretty button CSS, when your soft/client mostly want the same button cool they see anywhere else ? For web app dev, tools just increase the production. Hell I could using Quasar frameworks replicate an app for web use and native app using electron in a very easy manner. I never cared about what webpack is, babel, and such. I just use these as a tool, it works, it updates if needed, and that's it.

  37. The tech stack of your site generally does not matter if the design and the content are poor. Users don’t care if you have DIV soup.

  38. After reading through this thread, i feel like saying anything good about tailwind is controversial at this point sheesh.

  39. Like with almost any language, framework, library etc mentioned here, you can safely assume that 99% of those who outright claim it "sucks" just suck at using it themselves.

  40. Breakpoints are hacky and fluid design has always been superior to fixed width with breakpoints.

  41. Now with component container queries, it's better than ever to create fluid designs. Media breakpoints should only affect the main layout.

  42. - Lighthouse is actually important (because google uses it to determine rankings) and it's not hard to get 100s on everything, why does this sub think it's impossible? I saw some homie on here be like `No website of substance gets a 100 in performance`. Yeah you fucking can, they L I T E R A L L Y tell you step by step how to get a 100, follow it?!?!?!?!

  43. Microservices are painful to maintain, secure and deploy. There’s nothing wrong with a monolith no matter how big the project is.

  44. I saw a quote “Hire generalists to build and specialists to scale” that I think applies to the monolith/microservices debate quite well. Obviously, you can build much faster with monolith architecture. However, horizontal scaling is simply easier when you have microservices. So, you only really need microservices if you’re running into limits that can’t be easily addressed by your monolith.

  45. As someone who works at a company with probably one of the largest monolith applications, I disagree. It’s a huge pain.

  46. This kind of architecture is more organisational relevant. If you have multiple teams that focus on specific areas then microservices make sense. If you're a small team then stick to monolith.

  47. Quite... People used to have to focused on efficiency because computers were much slower back then. As a results, software written in those days flies.

  48. PHP is great for web development. People are still imagining 20 year old php codebases when they talk about how shitty it is. It's just accessible so a lot of new people make a lot of shitty projects with it.

  49. Agree. I've been using PHP and Laravel lately (after many years of Django like a decade ago, and then like 10 years of everything in node/JavaScript) and it is a pure blessing. Feels like cheating actually.

  50. It’s just a bit inconsistent because it has to be backwards compatible. For example, the ordering of inputs is sometimes different than what you would expect. But it’s not as bad as everyone makes it out to be.

  51. Most devs would rather do anything than learn CSS. They’ll act like CSS is basic and uncomplicated and then flail around with Tailwind or Bootstrap or some other BS bolt-on framework, write unusable code, and then get mad at CSS for causing all of their problems.

  52. You need to know CSS to use atomic frameworks like Tailwind. If you don't understand the properties Tailwind classes map to, how do you know which one to use?

  53. More general programming related opinion, but Agile sucks. On any given day I have 3-5 meetings, almost all related to Agile. I can't work consistently during work hours, so I have to get up early and start 3 hours before standup to get anything done. Yes, I've mentioned we have too many meetings, and my huge company isn't changing it anytime soon

  54. Web developers should understand basic design principals (like space and contrast and typography) and they are equally responsible for the outcome of the project.

  55. To add to this, you also don't necessarily need to be very good at CSS. It all depends on what you are working on.

  56. I don't know if this is an unpopular opinion. But HTML sucks. It sucks to write, has too much redundancy, too many brackets, too many features that clutter the design.

  57. “Modern” application development is entirely too complicated with little benefit. All the ssr stuff is basically recreating php and it’s mostly unnecessary. The setup of all of it requires way too many tools and dependencies and that is why things are often so brittle.

  58. A Web Developer should have basic knowledge of how to manipulate the dom with vanilla js, should be able to write a simple correct HTML 5 page and should know things like prototyping in js and reflow.

  59. I've been a professional web developer for more than 10 years now and I don't think I could write a simple HTML head section without some form of reference. I can't remember the necessary tags for the head and what the right syntax is. I've had a template saved as a snippet for years that I always use to start a new project. I haven't done it by hand for ages. I can still do the job.

  60. BEM is designed by and for people who really should learn about structure rather than inventing a difficult to read way of naming things that are easily solved by using features CSS has had since version 1

  61. Frameworks are overused and many would do better using vanilla code after mastering it instead of using tools that require 1000 libraries and end up being in most cases detrimental to quality work.

  62. I never understood the hate/fear of CSS when spoken about alongside HMTL/CSS/JS. Like, how is CSS the one out of these that people have problems with? It is all written in mostly plain English, and you get immediate feedback to any changes you make.

  63. The results you achieve with html,css and js alone are much more beautiful than anything a backend-only developer can make on their own.

  64. Programming web applications isn't nearly as difficult as programming your own brain to sit down and work through difficult problems / without reaching for something outside of your body to speed it up. (it's basically baby talk...)

  65. Web dev is too focused on abstracting layers of the stack (fancy navel gazing) and less than it should be on product and deliverables. Your competitive advantage is translating business needs to web apps, not upgrading to Typescript.

  66. building your website from the ground up and not using libraries that bloat and slow down ur site is worth the extra time and work.

  67. Backend devs can get a little haughty when talking to us Frontend devs. Sure I might not know how a particular API works, but at least I know how to center things.

  68. I wish web development would stay just that. All these bullshit Blazors and whatever else to get work done as if it’s not in a browser are a waste of time. Learn CSS and vanilla JS I’d you want to be a web dev. If you don’t get CSS, you’re not a web dev. If you don’t know what semantic markup is, you’re not a web dev. If you don’t know how to write decent JS without a framework, you’re not a web dev. See ya later.

  69. I’m a software engineer and that’s not my whole personality. I don’t write code on the weekends. I don’t spend free time reading and watching tech influencers. I pretty much don’t think about anything related to dev work unless I’m at work. It feels like 90% of devs eat/sleep/breathe writing code and I was always insecure that I wasn’t like that. I’m really just doing it for the money lol.

Leave a Reply

Your email address will not be published. Required fields are marked *

Author: admin