Live data from Hacker News

Web Development: A Crazy World

rubiken.com

161–170 of 206 posts

Re: Web Development: A Crazy World

#161
I hope that there aren't any actual web developers who think like that on a daily basis and that it's meant as humor. You don't need to use technology invented yesterday to write good software. Infact, most of the "blue chip" technology out there: Java, Python, Ruby, PHP, and the relevant frameworks used in those languaes (Spring, Django, Symfony, Rails, etc...) is being updated all the time.

Another advantage of not using the latest, hottest, tech, is that there will be several gigs of mailing list archives out on the net of people's past problems (also, stack overflow will be filled to the brim) with answers, to your common pitfalls.

Go with X.js + HipsterDB and you're gonna have a bad time when you run into a problem, because it's just so new that you're likely one of the first to run into it.

The article ended with "I just used wordpress and copy pasted some jquery" -- I approve.

The bottom line is getting shit done, not being a hipster.

Re: Web Development: A Crazy World

#162

Earlier quoted context omitted.

I am amazed a rant can go English -> Mandarin -> English via half the world's tech forums, and still be recognised by its original author. But what really blows my socks off is how a tech forum in Beijing follows rants from Slovenian blog to a Californian forum and back again. And it actually matters to the Chinese because they liked it as much as we did. Welcome to the new global culture, sharing the same memepool.

This is scary, we are loosing diversity at an incredible rate.

Heh, not surprising that comment isn't popular among the group of people who are currently exporting their worldview.

Harder to see the harm in it when it's your culture that's becoming the monoculture. That's the "good one"!

Re: Web Development: A Crazy World

#163

To quote Jamie Zawinski: "At the end of the day, ship the fucking thing! It’s great to rewrite your code and make it cleaner and by the third time it’ll actually be pretty. But that’s not the point—you’re not here to write code; you’re here to ship products."

Yeah, I bet he'd say the same thing to his car service technician, just fix the f*king thing, use duck tape if needed...

Re: Web Development: A Crazy World

#164
post #30

I've found that a large subset of programmers share the same trait as a large subset of photographers: they become so obsessed with tools that they lose sight of the fact that the end product is what matters at the end of the day. For example: there are many people who spend thousands on cameras and gear, and still take terrible photos. There are many developers who spend a lot of time keeping up with what they think…

Beautiful. I think it's also important to recognize that all tools have their warts, and to stop trying to pursue The Perfect Language/Framework/Environment™, because aside from marginal slow improvements, many modern tools are not that much better than their peers.

Re: Web Development: A Crazy World

#165

Earlier quoted context omitted.

Really? transmitting just the data and letting the client handle the display and interaction seems a much more natural split. It alos makes my server software conceptually simpler - which is always nice

I agree. Separation of concerns is a very good design pattern. MVC server frameworks (like Rails and Django) have already separated out the concern of displaying data to the user with their template systems. its a very reasonable next step to just migrate the entire template system off the server and let the client do it. This has gigantic performance increases for servers under heavy load, and it puts the display lo…

Templates... ok - that's fairly convincing. I'm less convinced about keeping the model and controller client side, because they end up replicating stuff that still has to live on the server anyway, to some degree. That just seems to make things harrier than they were to begin with.

Re: Web Development: A Crazy World

#166
Adopting new technologies doesn't always mean you try to follow trends or be cool. There are plenty of reasons that new ways of doing things come up all the time(be more productive is one of them). You may start slowly, but with time it pays off. I mean teams that can evaluate new trends and see if they get any benefits or not...

I personally think "just ship the damn thing" is BS, I'm pro delivering often, but good quality of product/service starts in back-end, again I'm not saying it should be perfect, but it MUST be open for new changes and be ready to scale... no one wants to wake up and be impotent with number of users they have, if you don't expect to scale, why are you doing this in 1st place?

Re: Web Development: A Crazy World

#167
post #18

Wow. Fantastic piece. This is precisely how I see the ecosystem too. If I've learned anything: 1. Focus on something —Rails, Python, Javascript, WordPress, something 2. Learn to actually program — any language will do

Maybe this is a side effect of this current day and age being a specialist society? Everyone needs something to differentiate themselves from the crowd, and Javascript being such a recent growth in setting a "standard" with regards to frameworks and tools makes for a good incubator for specialists.

Re: Web Development: A Crazy World

#168

Earlier quoted context omitted.

alternative step 4: If something breaks, hammer it until it looks like a nail.

only for PHP developers

I almost thought nobody would make a PHP sucks blah blah comment. Almost...

Maybe someday I'll read a thread without one.

Re: Web Development: A Crazy World

#169

Yes, this The amount of 'meetoo.js' is amazing(ly bad) Because of course everybody has to have "MVC responsive html5 cascading containers with chocolate covering" Not to mention most of these are underdocumented, bug-ridden, too specific, etc Need a js library? JQuery. period (and don't get me started with mootools, I need to ship, not swim around their docs figuring out how to do what in jquery is easy ) And focus o…

mootools documentation is fine. It's just different and therefore "harder". Has nothing to do with your ability to "ship" it's you're lack of knowledge of the library that's the problem. Not the library.

If you can't work a saw it doesn't mean the saw sucks and scissors work better. It means you can't work a saw.

that was probably a bad analogy but I can't think of any better one atm.

Post reply on HN