Earlier quoted context omitted.
I think your use of "minimum" is wrong here. If you're using React running on Node and Webpack as your task-runner you just need Javascript and that's it. Node allows you to run isomorphic JavaScript that runs on both your server side and client side (to ensure you don't end up with the Angular-style skeleton pages coming from the server), You can pick a nice ORM (like sequelize) to abstract away SQL, and Webpack all…
> ... to abstract away SQL SQL already is an abstraction, why would I want to abstract it away? Why not abstract JS away instead?
Ask HN: Is web programming a series of hacks on hacks?
401–410 of 688 posts
Re: Ask HN: Is web programming a series of hacks on hacks?
#402Re: Ask HN: Is web programming a series of hacks on hacks?
#403Earlier quoted context omitted.
> why I've always been puzzled by the urge to move more and more logic to the frontend. This is usually about a mix of scalability, responsiveness, and partition resilience; with the level of importance of those being dependent on the application. * Scale: if the client makes fewer request of the server(s) then you have reduced server and network requirements. As server resources get cheaper (and the cheap options mo…
>This is usually about a mix of scalability, responsiveness, and partition resilience; with the level of importance of those being dependent on the application. I have never seen anyone make those arguments. I've seen people vaguely reference them in a hand wavey "I don't understand this but google facebook I am right" way. But that's as close as it gets. It is usually about following trends.
But this particular trend started from an effort to push things client-side for good reasons that are vital, or at least useful, to many projects. It being trendy doesn't necessarily mean it is wrong! Don't be so fast to dismiss something because to don't immediately see/understand the benefit.
There is often some confusion between "mobile first" and "offline first" - the two overlap considerably but being a good mobile app doesn't absolutely necessitate being able to operate offline and offline capability does not require or imply an app will be usable on mobile (it may be to large and/or fiddly in terms of UI on a small screen, not practical to use in a touch manner, or too demanding of CPU and memory resources). Some of the hand-wavey-ness is people who know they are driving for "mobile first" and think that means they have to drive for "offline first" without really understanding the benefits & implications of that.
Re: Ask HN: Is web programming a series of hacks on hacks?
#404One thing I haven't seen mentioned is that while the developer experience is getting more complex, the user experience is getting better and better. That, in my opinion, makes all the messiness worth it. I'm not saying that there's nothing wrong with the state of web dev now, but it's not without reason that we are here today. Remember the days of table-based layouts in HTML? shudder
I don't think the complexity of the web caused better UX. I think we just happen to care a lot more about UX in 2016 than we used to in this industry.
If we were satisfied with our HTML tables, we would never have moved on to jQuery, HTML5/CSS3, React etc.
Re: Ask HN: Is web programming a series of hacks on hacks?
#405Earlier quoted context omitted.
CSS is not impossible to manage if you keep things modular and avoid specificity issue (basically, use something like BEM and pretend the "C" in "CSS" doesn't exist). re: HTML: layout and positioning is the domain of CSS, not HTML. HTML's purpose is to provide semantic structure to the content and non-semantic styling hooks (divs and classes) for CSS. It's true that layout has sucked for a long time (more accurately,…
We use BEM and Sass at work and our CSS is still an unwieldy mess.
I tend to use a combination of BEM component based rules and AtomicCSS inspired class-style, and my Sass tends to be pretty damn clean.
I think a lot of the problems with "web dev sucks!!12" mentality is that people come to it thinking that it should be easy, but it really isn't, and it's not going to be anytime soon.
Trying to build applications for multiple browsers to be used on multiple devices on multiple OSs that look good and work well isn't an easy job.
No, it's not perfect, but if you pay enough attention and do things right then it's quite a nice experience.
If your CSS sucks, maybe don't blame your tools before you blame yourself.
Re: Ask HN: Is web programming a series of hacks on hacks?
#406Yes. I feel like we're in the dark ages right now. JavaScript - Dynamically typed, does not scale what so ever. Code written in it becomes 'read only' very quickly. Impossible to refactor. CSS - Also becomes impossible to manage. Who knows if the class you wrote is or isn't being used in HTML or JavaScript somewhere. Same problem, read-only, it only gets bigger and more unmanageable. HTML - At the heart of it, the fo…
I'm not saying it's the best thing ever, but we're not doing too badly all things considered.
The web is still young. Let's work together to make it what we want it to be - what it should be - instead of moaning about what it isn't.
Re: Ask HN: Is web programming a series of hacks on hacks?
#407Haters are missing the big picture...
Re: Ask HN: Is web programming a series of hacks on hacks?
#408Earlier quoted context omitted.
CSS is not impossible to manage if you keep things modular and avoid specificity issue (basically, use something like BEM and pretend the "C" in "CSS" doesn't exist). re: HTML: layout and positioning is the domain of CSS, not HTML. HTML's purpose is to provide semantic structure to the content and non-semantic styling hooks (divs and classes) for CSS. It's true that layout has sucked for a long time (more accurately,…
The thing that makes me dubious of this claim is the number of years for which we've been reading variants of, "the upcoming (grid/flex/canvas/css3/html5/ecma spec/etc) will make things much better".
Re: Ask HN: Is web programming a series of hacks on hacks?
#409Earlier quoted context omitted.
Is it really square pegs for round holes? I don't think that the web as a mechanism for distributing applications would look much different even if it hadn't gone through the HTML stage. If not JS, it would have been Java applets. If not HTML, then some weird XML layout schema. There might have been a time where the web as a platform for applications was beyond silly, but this is not htat time. The platform is decide…
It's, but not by design.
Re: Ask HN: Is web programming a series of hacks on hacks?
#410In that world the "view" part of your system might as well be web based. Making front end look and feel good, is terrible in everything anyway.