20 ms·
It doesn't have to be complicated, if you get support from above. A few weeks ago I launched a new web site for a health care company. HTML, PHP, CSS, and MySQ
by reaperducer 7y ago
It doesn't have to be complicated, if you get support from above.
A few weeks ago I launched a new web site for a health care company. HTML, PHP, CSS, and MySQL. No frameworks. No javascript. No garbage.
It replaced a site that was a mess of javascript libraries on top of frameworks on top of a half dozen jquery version and on and on and on.
The company administrators, doctors, practitioners, etc... are so happy with the new no-nonsense site that they raved to the parent company about it. The parent company's IT department looked into the site, asked me some questions about it, and yesterday I was been asked to do the same type of cruft-free rebuild of three other sites that the company owns.
Not buying into the framework-of-the-day hype just landed me job security for the next two years.
- bob1029 7y agoDamn, you broke into my top-secret consulting role ;) I completely agree with all of this. There is probably a billion-dollar market out there for rewriting garbage business apps that were developed using the hipster tech flavor of the week.
- popotamonga 7y agoI'm making top dollar remaking failed garbage react native apps to real native native. Clients love it
- buzzerbetrayed 7y agoOut of curiosity, how do you support both iOS and Android with this approach?
- cutler 7y agoHow do you identify these apps/clients?
- j88439h84 7y agoThe market may be large, but that seems like saying the market for cooks is large. The work required for doing 4 sites is double the work required for doing 2. Unless theres some scaling secret I dont know about.
- pgeorgi 7y agoThe idea isn't to capture the entire billion dollar market, but to navigate a market that is large enough to safely feed you and many more for the next decade+, precisely because it isn't scalable (so there won't be any FAANG-or-whatever coming along, eating your lunch)
- tlrobinson 7y agoWhich is more hipster: using the latest modern web framework, or bragging about how you don't use modern web frameworks?
- bsaul 7y agoThat's definitely something to consider : i don't want beginners to start coding in old school php with sql statement inside html templates because they read on HN to "not use modern frameworks". BUT, i don't think this "crude design" trend will ever have the same attractiveness to junior developers no matter how much hype it gets here. Being attracted to "new shiny things" is very intrinsic to human behavior, and tech companies will keep spending ads to sell their new tech to the market.
- zumu 7y agoAvoiding the latest mainstream trends is actually a very hipster sentiment.
- mr_toad 7y ago> hipster tech flavor of the week I’m not sure ActiveX, ASP, and SQL server were ever hipster. You’d be doing the world a favour by re-writing these apps. Literally doing a favour: there’s never any budget for it.
- deleted 7y ago[deleted]
- anthony_doan 7y agoYou don't even use a backend rendering framework? MVC PHP frameworks are very nice and they don't move as fast as those javascript frontend rendering. Also the ORM deals with any security problems and most framework deals with other security deals too including session handling.
- avgDev 7y agoThis seems odd to me. I have been working in .Net MVC/Core and while I could write an application that is simply HTML/CSS/C#, I would think it would be insane to do so. It takes a massive amount of resources to develop your own security, your own data access without any ORM tools, not cause memory leaks, properly disposing of resource. I'm all about creating reliable applications, but a good framework is a great tool.
- TomMarius 7y agoPHP is way more "batteries included" than C# without ASP.NET
- crumpets 7y agoYeah, unless you have workers, the whole "request is the lifecycle of the app" model of PHP makes it pretty damn hard to get a memory leak.
- anthony_doan 7y agoThat's true, I've done PHP for a long time and there are like 1000 functions polluting the global namespace.
- nfgu 7y agoIt is entirely possible to import things like EntityFramework, Razor and Identity Framework without using ASP.NET MVC itself. Just because the framework uses them by default it doesn't mean they can't be used separately. You can use Razor Pages or a router like Nancy[1] without having to roll your own ORM or View Library. [1] https://github.com/NancyFx/Nancy https://github.com/NancyFx/Nancy
- orf 7y agoDid you consider that the next developer might well come along and post a similar comment: > It replaced a site that was pretty much a home-grown PHP framework written by a single developer. Random mixed logic in templates, hard to update CSS and a poorly designed 'not-an-ORM' ORM. Not to say that your rewrite is like that, but one man's garbage is another man's treasure.
- TotempaaltJ 7y agoAnd here's the trick to not building shit software: don't build shit software. It's a crude way to put it, but the reality is that you can build bad websites in any framework (including old PHP stuff and new JavaScript hype). You can also build good websites in any framework. It depends way more on the organisation or team developing it than on the libraries you use.
- afarrell 7y agoThe trouble is that "don't build shit software" isn't actionable advice on how to avoid building shit software. For someone seeking to be a more skillful web software engineer, there's no information there.
- justbaker 7y agoIt means the underlying problem is not the tooling, but the use of the tooling. In other words, "I can choose the correct tool but still fail from poor approach of problem."
- orf 7y agoIf the tool allows you to shoot yourself in the face without warning, and has a reputation/history of doing it to a lot of other people, then the tooling is indeed the problem.
- chrshawkes 7y ago
- Townley 7y agoRecognizing the right tool for the job landed you job security for the next two years (and you're deserve it!) But it could have very easily gone the other way. If your website had complicated validation rules on multi-page forms (not unheard of in healthcare) the site would be better off for some basic state management interacting with a standardized authentication/authorization framework that you didn't have to write. From what you're describing, it sounds like you did right by the client in this circumstance. But sometimes, it does have to be complicated. And in those circumstances, frameworks and javascript (unlike garbage) have an important place.
- wolco 7y agoIf it is just validation a js framework would be overkill. jQuery would fit well here.
- dsego 7y agoYou missed the multi-page forms part. As soon as you have state of some fields affect how other fields or parts of the page display it becomes complex really quickly. There is an explosion of possible states. If you've ever seen code like this, you know why more modern js frameworks were invented: onSomethingChanged() { $('#foo').prop('disabled', true); $('#spinner').removeClass('invisible'); $('#error-1').prop('hidden', true); $('.buttons').hide(); if (value) { $('#btn-2').show(); } else { $('#btn-2').hide(); $('#btn-3').show(); } // etc ... }
- scarface74 7y agoMy favorite combination for dead simple sites is HandlebarsJS. 1. Render model from your JS object. 2. attach events 3. Change model 4. Go to step 1
- minism 7y agoYou're just describing MVC which is essentially what most frameworks contain at their core on some level.
- onion2k 7y agoWhat tech you use is much less important than the way you use it. If you build great stuff that works well your clients will be happy, and they'll give you more work. It's not complicated.
- diminoten 7y agoYeah, because the people hiring you have no clue what kind of a maintainability hellscape you're leaving for the next person... Also I'm 97% sure I could own your site in under a day, based on how home-baked you just said it is, and I'm garbage at pen testing. Healthcare site, you say? Jesus Christ, I hope they have data breach insurance.
- reaperducer 7y agoAlso I'm 97% sure I could own your site in under a day, based on how home-baked you just said it is, and I'm garbage at pen testing. The internal and external security audits already performed by the billion-dollar healthcare company in question disagree with you.
- diminoten 7y agoI'm super glad to hear that happened, but please understand where I'm coming from when I said what I did; reinventing the wheel (as I'm sure you had to here) is straight up dangerous.
- noonespecial 7y agoIs it bad that the more spent on the audit and the larger the company the less I trust the results?
- tluyben2 7y agoNo, they just had to check that box to make sure that they did ‘everything in their power’ to make it secure.
- ceejayoz 7y agoI can't speak to your specific case, but I've seen a tool "pass" a billion-dollar company's auditing because the scanner they used never got past the login screen and their folks never noticed that fact.
- pojzon 7y ago
- theandrewbailey 7y ago> The company administrators, doctors, practitioners, etc... are so happy with the new no-nonsense site that they raved to the parent company about it. Any reason they liked it in particular? Faster? Better/cleaner UI?
- whiteopinions 7y agoThis sounds like you wrote something extremely limited. The client will inevitably ask for some modification to it, and if you're not there to do it the next developer is going to curse at you for writing such a brain dead application. I've seen comments like this on HN and then I've seen these types of applications in the wild. I call it the most dishonest form of consulting you can do. You've put a real shine on some inflexible shit and the clients obviously have no way of knowing what they've bought into. >It replaced a site that was a mess of javascript libraries on top of frameworks on top of a half dozen jquery version and on and on and on. These people are incapable of correctly evaluating work they contract out, or who is doing it. Why do you think you're an exception in this case?
- nfgu 7y agoI've seen countless unmaintainable applications written using popular MVC frameworks that required simple modifications, but the next person in line wasn't able to understand what the hell was going on. Popular frameworks are not silver bullets, but apparently it's popular on HN to think so.
- whiteopinions 7y agoNo one said they were silver bullets. No one.
- wolco 7y agoA simple custom php site is extremely easy to follow if you have a programming background. If I'm the next developer I would thank him. Ever deal with 5 versions of jQuery that are conflicting. Trust me life is easier in vanilla php.
- whiteopinions 7y agoYou know what's actually incredibly easy if you have a programming background? Consolidating versions of jQuery. >If I'm the next developer I would thank him. For what? You wouldn't know anything about the previous site implementation
- GordonS 7y agoI take a similar approach for 9/10 of the enterprise web apps I build, but use ASP.NET Core MVC instead of PHP, and I also favour SASS. Point is that SSR (Server-Side Rendering), with a sprinkling of simple JavaScript and XHR calls as required, is enough for almost everything I do, and it means build are really simple. Doubly so with a strongly typed language like C#. I've worked on Angular and Vue projects, and the complexity level was (subjectively) much higher, despite these particular web apps not requiring any real level of client-side functionality. I find JS tests to be much more complex and brittle than C# ones too. Honestly, I hated it! Now, some of this was undoubtedly because I'm more comfortable with what I know, but certainly not all of it.
- pixelrevision 7y agoPeople vastly underestimate how complex client side code can get and how much automatic functionality browsers hand you. Whereas a nice web framework has users, permissions, session management, templating, validations and forms all set up for you with battle tested out of the box behaviors. A frontend framework is great if you are a company that really needs to slim down bandwidth and can hire expensive devs to maintain it. But for a simple no nonsense business application it’ll just slow you down and will gravitate towards being a mess.
- elboru 7y agoHave you tried Razor Pages? I used it in my last project and I loved it, it was a lot simpler and subjectively more fun than using regular MVC.
- GordonS 7y agoI haven't tried it, but have read uo a bit and seen some examples. TBH, I'm not all that keen, possibly because it reminds me of the bad old days of webforms with code-behind files. Maybe I should try it in anger before I judge it though :)
- nsfwfavorites 7y agoDetermined gripping agama
- fizixer 7y agoQuestions for PHP, and MySQL folks (not meant in a negative way): - PHP: A few years ago I heard about how PHP was needlessly complex. I wonder what the recent status of the programming language is. Specifically, do experienced PHP programmers stick to a subset of PHP, as in "PHP: The good parts"? (similar to "Javascript: The good parts"). (side note: As a diehard python person frustrated due to latest versions becoming bloated in features, I fully acknowledge that I'm in the "Python: The good parts" camp right now). - MySQL is owned by a company lately. I wonder if PostgresQL is clearly a better alternative?
- CiPHPerCoder 7y ago> Specifically, do experienced PHP programmers stick to a subset of PHP, as in "PHP: The good parts"? See: https://phptherightway.com https://phptherightway.com Modern PHP development comes in the form of loading dependencies from Composer/Packagist, rather than offloading a lot of bloat to the language. Lots of things have been deprecated (and even removed, like ext/mcrypt).
- wolco 7y agoI think the discussion point was php was too easy and that encouraged new developers or less hardcore developers to adopt it. Some of the defaults like globals being turned on by default led to security holes. How people were creating sql statements at the time concating strings led to sql injection issues. There were never any bad parts . There are new features like the spread operator that are newer and not available in earlier versions. I try to stay away from them if I think the application will need to run on older versions but otherwise I feel like I can use any feature. Postgres needs to run under a specific os user. That alone makes it a poor MySQL replacement
- orf 7y ago> There were never any bad parts . There where, and continue to be, large numbers of bad parts. Magic methods that do random things in certain cases, terribly defined interfaces (array_search), ridiculous typing, an impossibly incoherent standard library, etc.
- 7y ago
- mstipetic 7y agoI don't think you're being fair. I certanly agree that a lot of things that should be simple are over-engineered simply for the sake of it, but there are a lot of things that are made possible by modern frameworks. I'm really not trying to plug our thing now, but if you look at this [1], a short tech demo of the platform we're building, there's no way it could have been built without modern frameworks with the amount of people we're building this [1] https://www.youtube.com/watch?v=SkjMUY_cAmw https://www.youtube.com/watch?v=SkjMUY_cAmw
- lhorie 7y agoThat looks pretty simple in terms of UI... There certainly are some types of apps that are mind-bogglingly complex (e.g. press play and scroll around on https://kepler.gl/demo/nyctrips https://kepler.gl/demo/nyctrips for one vivid example) but ironically, the real heavy lifting is mostly done with specialized libraries and super-close-to-the-metal code (GSLS), whereas the "modern" stack only powers the "simple" boxy UI glue stuff.
- eddieh 7y agoI once worked on a team of about 30 people building a website for a university that could have been a team of one dev and one designer and a static site generator.
- mixmastamyk 7y ago> PHP, MySQL Agreed in general, but there are better free/libre choices. I don't recommend these for greenfield projects.
- bgdkbtv 7y agoWhat would you recommend instead of those?
- ativzzz 7y agoRails + postgres!
- bsder 7y agoPostgreSQL is my database choice under practically all circumstances. I'd replace PHP with practically anything written by grownups. (Django, Rails, etc.)
- bgdkbtv 7y agoAgreed with PostgreSQL. But I'd go with Laravel rather than Django or Rails. More modern, more features, active development and constant new features are guaranteed for Laravel, in addition to growing community and abundance of learning resources.
- chaoticmass 7y agoI have a similar story. I got hired on to replace some PHP web apps, each one written using a different framework. Each one out of date, unpatched, unknown dependencies, no easy way to bring up to date-- tied to specific old PHP versions. A big mess. The IT director was pretty savvy and said he wanted a clean rewrite without frameworks, something I was all too happy to do.
- cutler 7y agoWhat did you replace it with?
- mattlondon 7y agoFor one-dev sized projects (i.e. simple crud type apps) this may well work. However I would be concerned about a couple of things if this were me and I was doing anything beyond the absolute most basic web app: - long term maintenance. Doing something only you understand and only you can maintain (that job security you mention) is a bit of an unprofessional dick move IMO. - if you need to get other people in to help, you now have to spend more time training then up on your custom system that they don't understand and keep an eye on them to make sure they are doing it right and not introducing security issues - When your client wants to integrate with some common third party thing ("hey can we put Google maps in here?"/"we need to integrate with stripe payments") you'll need to reinvent the wheel from scratch to do it using your custom system rather than just use a well-supported off the shelf library. - you'll need to stay 100% up to date on all security issues/approaches/classes of vulnerability to make sure your custom system is secure. Your audit was ok this time, but everytime you make a change to your custom library (e.g. to support Google maps or stripe) you're now going to need to go through the audits again to be sure you've not opened up any new security holes (and perhaps new ones you've not ever heard of because you are only working in this weird little custom system/thiefdom for the past 2 years) - how to support the INEVITABLE requests for extra features that require something client-side that cannot be easily done with only PHP and static pages. It is not the 90s any more - the cat is out of the bag regarding interactivity ... the requests for client-side nicities that users are used to in other things WILL COME! Clients always want more! :-) Still anyway I guess you don't need my good luck wishes as I am sure you are correct and that you really have out-thought and out-coded all of the well-supported and well-funded frameworks that have been built by many thousands of people and have been battle-tested in the field for years (e.g. Laravel, .net MVC, struts etc). Because otherwise if you hadn't totally out-smarted the entire industry, I'd be shitting myself and checking my professional liability insurance about now.
- xemdetia 7y agoI think people are assuming he wrote a pile of hot PHP garbage, but it's entirely possible he just wrote it using Symfony or Drupal and well understood PHP libs and just has no 'modern javascript' to do it, which if he did would cover all of your points. If you haven't gone back to current gen PHP in a while there are some quite solid models that are very maintainable, have security updates (via composer) and so on. It's entirely possible that he didn't do a crazy thing but we'll never know. A decently structured PHP application is often maintained by nontechnical people with a limited understanding of programming but they can get by with just a text editor and a codebase. I have not come across any nontechnical person who could easily get a react/modern js framework pipeline going to do a small change, not to mention dealing with npm changes. I would almost feel like it would be a jerk move to leave someone without a technical department a pile of react/npm soup right now.
- solitus 7y agoDid you build a CMS from scratch or is it simpler than that?
- scarface74 7y agoNot that I disagree with your approach technically, but if I did that, I would have felt like I wasted my time. No job is secure and you did hardly any Resume Driven Development. Also, if I were a team lead, I definitely wouldn’t have chosen that stack because it’s harder to recruit career driven developers who don’t want to work on tech that doesn’t help then build their resume. When it’s time to land the next job, using $cool_kids_stack of the day, you will be at a disadvantage. For context, when it comes to modern front end development, I’m barely above “not eat the chalk” level of competence so this is definitely not meant as a technical critique.
- hartator 7y agoWait that some manager hears about Angular 3000.
- mikekchar 7y agoI am reminded of the Picasso story where he meets a woman in a park and makes a 30 second sketch. The woman asks how much it would cost to buy it and he replies something like $1000 (insert large amount of money for 30 seconds of work). She asks him why so much money for 30 seconds of work and he replies that it took him 30 years to draw that sketch. It's easy to build a simple website with no frills that does exactly what the client needs -- if you know how to do it. Even then, it is rarely easy to figure out what the client needs! A colleague wanted to use a Javascript library for something I thought was probably pretty simple. I suggested we take a look at the library and see what it was doing and determine if it was worth the extra dependency. He joked, "If I wanted to know how it worked, I wouldn't have chosen a dependency". Luckily, it's not how my colleague really feels, but this is exactly what's happening most of the time. Things are over complicated because people don't know how to build them -- they glue together a patchwork of stuff so that they don't have to know. In the end, they tend to build something whose complexity is many orders of magnitude higher than the complexity of the problem they are working on. Your two years of job security was not for avoiding framework-of-the-day hype: it was for knowing how to do it. It's the simple 30 second, single line sketch that captures the picture perfectly with no extra complexity. That takes years and years of experience to develop -- and a desire to even get there at all.
- ekzy 7y agoIt is a good analogy. In essence, achieving simplicity is hard. Simple is not easy.
- bgorman 7y agoUnless you use Clojure ;)
- mattacular 7y ago"Simplicity is complexity resolved"
- deleted 7y ago[deleted]
- debaserab2 7y agoI wonder what your brand new greenfield project is going to look like in five years when it's been passed through the hands of a few interns and contractors and survived a couple different ownership shuffles. Think it will look as maintainable as it is today? Or do you think a new consultant will roll through and easily sell the client on another rewrite-from-scratch project?
- asark 7y agoFramework-dependent projects tend to go stale and become "ew I don't wanna touch that, it's so last year, we should probably replace it with [newer version of framework that's gonna end up being much harder to upgrade than expected / other framework]" surprisingly fast once eyes are off them, in my experience. Without someone competent doing continual upkeep, the next guy/gal's gonna try to sell the re-write anyway. May not succeed, but they'll try. Framework or no.
- jdnenej 7y agoPlain JS is the same. How often do you search something and find the 2012 way includes copying a 20 line util function and the latest way has it built in to the language.
- xyzzyz 7y agoEasy, just don't write JS. For most sites, there's hardly any need for it. On HN, for example JavaScript is only 150 lines[1]. [1] - https://news.ycombinator.com/hn.js https://news.ycombinator.com/hn.js
- bluedino 7y agoBut, can the marketing intern update it?
- oarabbus_ 7y agoCould you point me towards some modern-looking websites that don't use JS?
- foobar_ 7y agoBasecamp uses rails and turbolinks.
- flukus 7y agoThis one? The JS is very light and optional. And this site is far more interactive than most websites. I'm not sure why you need a modern "looking" site since JS is about the functionality not the looks.
- BlueTemplar 7y ago"Modern-looking" these days means shitty JS that tries to be a "WebApp" and breaks basic website conventions like open in a new tab middle click, and uses the same GUI both for small touchscreen and large desktop, so ends up working poorly on both. Why would anyone want that ?
- shams93 7y agoYeah everyone assumes you have to build out an SPA and then you need a rest or graphql service behind that. It rapidly gets out of hand for the benefit of having a native like experience you wind up serving sites with 1 gig of us framework content per page.
- dsego 7y agoOh but then you add code splitting. And we've come full circle.
- miguelmota 7y ago> HTML, PHP, CSS, and MySQL. No frameworks. No javascript. No garbage. Wait, PHP is not garbage?
- thewarpaint 7y agoJust a side note. Javascript does not strictly imply frameworks. Javascript does not strictly imply garbage.
- TelmoMenezes 7y agoIn theory, no. In practice, yes.
- rvn1045 7y agoThe point of using a good framework is that conventions and best practices are enforced. If your building a Rails sits there are a set of conventions everyone follows. When a new developer onboards onto the project they know how to extend the code base.
- nullwasamistake 7y agoEh, not using popular frameworks is a recipe for unmaintainable sites. You're missing a lot of features these provide for free. Accessibility Cross browser polyfills Easy translation support Automatic mobile view Developer mindshare The lack of polyfills is VERY concerning. Your site probably doesn't work on 10% of browsers. And getting from 90-99% is an excercise in futility. If you used a popular UI framework and transpilation you could easily write a super modern site that works on practically everything back to IE6. And with Vue or React the whole thing could be a few hundred KB, probably smaller than some of your images. If I was brought in to work on your site, I would immediately rewrite it if it's more than a few pages. Plain HTML with PHP becomes an unmaintainable rats nest if you try to do anything complicated.
- dpcan 7y agoVery similar thing is happening for me as well, only for a large property management company. Their old sites were weighed down with an incredible amount of confusing technology. I redid the whole thing with PHP/HTML/CSS/JS/MySQL as well, and it's incredibly easy for them to update and work with now. Super simple admin interface, attractive front-end, and the top brass at the company has taken notice.
- woutr_be 7y agoMy background is mainly frontend, but I'm well versed in backend as well. I've been actively advocating at my company to stop with this whole separate frontend and backend, and instead just return plain HTML and some basic JavaScript when needed. In most of my personal projects I've been following this approach too, and I must say, I'm so much more productive. I don't find myself constantly switching between browser-, terminal and VS Code-windows. I don't have to do validation twice anymore, and know perfectly where all my data is coming from.
- jdnenej 7y agoI built a SPA and found making the API and linking everything up to be needless overhead. The way I find works best is using rails templates to simply insert a div with all the data needed in the attributes and then having react render everything.
- woutr_be 7y agoThat's what we used to do years ago, just render a script tag with all the data required, and then use JavaScript to link it up in the views. But I feel if that's what you're doing, you might as well use a templating engine, and put all the data where it belongs.
- knocte 7y agoIs PHP still a thing?
- Nyandalized 7y agoPHP serves most of all web traffic: https://w3techs.com/technologies/overview/programming_language/all https://w3techs.com/technologies/overview/programming_langua...
- lmaophp 7y agoPHP in 2019 lmfao
- engineeringwoke 7y agoMy homegrown PHP framework is highly superior to these awful hipster JavaScript frameworks!
- hnarn 7y agoHonestly I think it's kind of worrying that this opinion is so popular. Aren't you essentially saying that frameworks are in most cases useless, and "job security" is something you should strive after? First of all, "job security" means that you're irreplaceable, and in the case of you actually being the architect/designer, that probably means you did a (perhaps intentionally) bad job to make yourself the linchpin. Not good. Secondly, regardless of the first point, programming is hard. Anyone that says otherwise should be avoided like the plague. It's beyond the scope of one individual to be able to keep up to date to all the security issues and gotchas prevalent in a language or ecosystem. This is why you use frameworks. They're democratic units that within themselves handle patches and development in ways that are often better than one "irreplaceable" developer on a unique object (of course, bad developers can still use frameworks and derail the product completely to the point where all benefits of the framework are negated, but that's beside the point).
- zwaps 7y agoI am one of those guys who were "left behind". I used to code in ASP and PHP back in the day, and that approach made a lot of sense. You'd have things that run on the server, and then those things throw out a website for the user to interact. If there's a need for reactivity, use some JS, but basically it all goes back to the same server program. I always found that this approach was good enough. You could do a lot, heck, I even wrote a browser game back in the day. Most importantly, it was simple, and it led to great web pages that would always work and could be used as such. No JS, no cookies? No issue, your code would just deal with it. A button was a button, and link was a link, and your browser did the rest. Text got sent as html, pictures were loaded or not depending on your preferences. Everything got faster and faster. This was years ago. In the meantime, I stopped doing web dev. Suddenly, in the last ten years or so, I noticed that websites became bad. The whole web just seemed to regress. Everything was JS, everything became single page, and if you didn't enable every single function in your browser, or if you pressed the "back" button, or reloaded the page - basically if you did not pretend that the website's UI was an actual native program - then everything breaks. News sites stopped loading text or images halfway through, buttons stopped working. Links were not clickable. Pictures would not show up. LOADING bars and circle-things appeared on websites that were already downloaded on my computer. Registration forms did not load default options, choice elements were empty. Once the page was loaded, everything was sloooooow. Scrolling became "different" and often laggy. Websites would load, then do something in the background to reload into garbled messes. Printing didn't work correctly. It's like Flash websites of my day (that everyone know were terrible and had very few good use cases) became the norm, but without Flash. What happened to the internet? Why is everything garbage? Did all web developers die out? I went back to make a simple website for myself. Reading tutorials, it was clear I had to use some framework. It was recommended to use JS, install some sort of server application and database, then a framework on top of that, and then something that runs in the user's browser. But everything was its own programming language, with no common denominator. You'd either need a PhD in JS and server development, or be happy to buy in to some framework that was usually not even very good. I did not understand anymore how web development works. I did no longer understand how the websites came to my customer, what the server did, how and when it did it... and everything was hard, even though this should all be really simple. And what came out was just... bad. I went back to using simple web dev tools if I need to, and thought "well my needs are just not so advanced". But given that most websites have become so terrible, I just can't help but feel it all went wrong. Whoever thought up this frameworks and JS revolution was probably really smart, and there are probably some really good websites out there. But I hate the internet now, and I don't understand web development anymore. I'm not even that old.
- okaleniuk 7y agoGood for you! I'm really glad to see that this no nonsense approach catches on.
- marcus_holmes 7y agoHow do you cope with copy changes from marketers? This is my problem at the moment. I have a nice static site, but I'm facing demands from the marketing team to use Wordpress so that they can make copy changes to the site without having to go through a developer (or learn any HTML).
- tuesdayrain 7y ago>HTML, PHP, CSS, and MySQL. No frameworks. No javascript. No garbage. The funniest comment I have read on this website.