10 ms·
I still think that "boring" is a wrong word. Choose the technology you know in and out, and are immediately productive with. Choose the technology which is su
by nine_k 6y ago
I still think that "boring" is a wrong word.
Choose the technology you know in and out, and are immediately productive with.
Choose the technology which is sure to be around in 5-7 years, preferably 10-15.
Choose the technology for which you are comfortable hiring the next 15 engineers.
This does not mean that you need to choose something unpleasant, unergonomic, or ancient. Neither does it mean that you need to choose exclusively among the top 5 most used in the field.
The key thing here is to avoid surprises, unknown unknowns. You won't have the time to learn from a novice level while building a new company.
A number of wildly successful MVPs were implemented with obscure (or then-obscure) technology which authors knew very well, and which boosted their productivity. ViaWeb was written in Lisp. YouTube was (and still largely is) written in Python, way before it was cool and well-known. The initial Rust compiler was written in OCaml.
- kitd 6y ago> YouTube was (and still largely is) written in Python, way before it was cool and well-known. I agree with you on just about everything, but python was well-known well before YT. Django was a staple of the early web.
- beerbajay 6y agoThe web has been around since the early 90's and Django was first released in 2005...
- TheDong 6y agoThe staples of the early web, in my mind, are html and perl CGI scripts. php might make the cut as early web, but web frameworks, like those in ruby and python, feel to me me much less like the early web, and much more like the web 2.0 days.
- iso1210 6y agoMatts Script Archive was mid 90s. Mod perl maybe just squeezes into 'early web', I think /. used it in the late 90s. Perl wasn't the only CGI in the early days - a large internal web application I encountered as late as 2004 had it's CGIs written in C, running on IRIX PHP is certainly the newcomer as far as I'm concerned
- ghaff 6y agoLike a number of languages, PHP was around for quite a while before it really took off. PHP is probably most associated with "Web 2.0" as it became the model for web interactions in the mid-2000s.
- iso1210 6y agophp 3 was the first php as we know it, and that wasn't until 97 - before then it was more like SSI. It didn't really compete with mod perl until zend
- ashildr 6y agoI feel old now, for me the early web was on Mosaic, shortly after I discovered gopher at uni. But seriously, the dynamically generated content of the early web was cgi, perl, later some python (as in scripts, not in django)
- jmchuster 6y agoDjango released July 15, 2005 YouTube founded February 14, 2005
- cmrdporcupine 6y agoIt's funny to call Django the "early web" when it first came out in 2005. That is really not early at all. Especially when you consider Rails, etc. predates that. I was an early Python adopter (1995/1996) and could not for the life of me find anybody who would consider letting me use it in 'mainstream' commercial software projects. Then all the sudden about 10 years ago it exploded in popularity big time. But I'd moved on to working on other things by then, I no longer enjoy writing in Python. Wow, this sounds like the classic "I was into that band before they popular" indie snob, hah!
- the-dude 6y agoWikipedia says Rails was released in Dec 2005.
- ghc 6y agoRails was popular before anyone ever heard of Django. Rails jobs were already common when it reached 1.0 at the end of 2005 (In early 2006 a law firm offered me $30 to do rails work as a summer job off campus). Django took another couple years before reaching 1.0, though I did do work for some early adopters (0.95) circa summer 2006.
- ikeyany 6y agoI think "early web" here refers to the popular technology used between 1995-2005.
- projektfu 6y agoI was using python with SCons back when it came out, sí around 2000. I was also surprised at the statement that python wasn’t well known, but I agree that the Java web scene was much more mature. It was, however, very focused on configuration. There was nothing like LAMP getting people up and running in under a minute. ASP was also a favorite of the early web.
- decompiled_dev 6y agoThis reminded me of Paul Graham's Python Paradox: http://www.paulgraham.com/pypar.html http://www.paulgraham.com/pypar.html Seems like Python is now in the camp of Java now given the current trends.
- ghc 6y agoI would classify early web (1.0) as 1993-2003 (pre-AJAX), and modern web (2.0) as 2004-on (post-AJAX). The biggest change since then has been on the backend -- moving from web frameworks in Python/Ruby to Single Page Applications with Javascript backends.
- pjmlp 6y agoZope fits that role, not Django.
- namelosw 6y agoThis is pretty much spot on. People usually missing the point of 'boring' because they would think of unpleasant and ancient stuff. The key value is indeed to avoid surprises. When I read WhatsApp used Erlang back in the day, I was pretty impressed. Not only the obvious things like Erlang was the forgotten secret weapon for massive concurrent apps, but also details like they used FreeBSD back in the day when there was no preemptive scheduling but Erlang has preemptive scheduling so it was okay. Those details reflect they were very confident and they know perfectly what they were doing.
- qznc 6y agoYes, "boring" as unpleasant associations and this is why it works much better as a title. Consider these two titles: * Choose boring technology * Choose well-known technology More people will click on the first one because it comes with a paradox suggestion. Why should I intentionally choose something unpleasant? That poses an interesting question. The second title sounds boring (how ironic). Why would I click that?
- pydry 6y agoWhenever I hear "exciting tech" I tend to think "hyped to kingdom come". I think of node, docker, mongo, golang, etc. - tech that was pushed with marketing $$$ or big names. I have an inbuilt bias against that stuff - not that it's necessarily worse than alternatives but that the marketing budget or big name backer instantly makes me more suspicious. For most developers it seems to work the other way around - big names and marketed heavily => it has buzz => it must be good. Under boring there are two types - PHP and postgres. Boring tedious and annoying and boring reliable workhorse. The 2nd type is my favorite type of tech.
- w7 6y agoI'd honestly consider Golang "excitingly boring". Simple C-ish syntax that's relatively familiar to most programmers, write once and compile to/from anywhere without arcane flags, easy to understand and use concurrency model with message passing, reference development tooling that can enforce standards out of the box. I don't think there is much new here other than removal of cruft.
- gcoguiec 6y agoMature Technology? (https://en.wikipedia.org/wiki/Mature_technology https://en.wikipedia.org/wiki/Mature_technology)
- lugged 6y agoYa'll seem to think "Choose Mature Technology" would result in the same amount of discussion and upvotes on hacker news.
- marcosdumay 6y agoNot quite. "Mature" doesn't describe what the article and the GP said, and what seems to happen on practice. It's even biased the wrong way, tech does become outdated at some point and best avoided, but "mature" only increases with time.
- ksec 6y agoErlang is a Mature Technology, and fits Pt 1 - 2 but not Pt 3.
- robert_g 6y agoThere should also be an explicit call out to both tooling and community. Even if a programming language ticks all the other boxes, Without a sizable and stable community to constantly push tooling languages will fade, not necessarily die. In my past job I was ColdFusion programmer for 15 years. ColdFusion ticks all the other boxes. * Created in 1995 and is a very mature platform * Easy to learn and productive * I was very comfortable hiring multiple ColdFusion engineers over the years But, the community moved on and the tooling is now nonexistent compared to other programming languages. ColdFusion will live on, but as a shadow of what it once was. Which is unfortunate because I actually enjoyed the language and platform.
- wilsonfiifi 6y agoDo you think open source colfusion engines such as lucee[0] are worth using/learning? [0] https://lucee.org/
- hoorayimhelping 6y agoNo. Avoid ColdFusion - it's a language from a bygone era when Adobe was trying to be what Microsoft is now. They failed and the ColdFusion community will die. The community, while made up of great people that I am still friends with, by and large was not interested in improving, learning new techniques, or growing beyond ColdFusion. They wanted to learn a skill and cash in on it for a long time. The language is dead and their skills are becoming useless as a result. Maybe in 15-20 years ColdFusion will become like COBOL or ADA, where there's a bunch of code running some necessary systems and nobody knows how to maintain them. But it's a long bet for a payoff that would be much higher if you spent your time somewhere else.
- robert_g 6y agoIf you're thinking of learning CF, only do so with the understanding that it's now a niche product mostly used in government and large companies. Learn it either as a hobby or look at the Lucee source for educational purposes. Even my last company is moving away from CF. About Lucee ... I actually helped the company migrate away from Adobe ColdFusion to Lucee due to a chance in Adobe's licensing. We migrated a large, 10yr old, application and all clients over to Lucee in about 1 year. Lucee is a nice platform but I'll warn that it's not as polished as Adobe CF and there's some difference in features. You'll run into rough edges in their documentation and language implementation (especially the scripting languages). One nice thing I really enjoyed was being able to download the source and figure out how my CF code was actually being compiled into Java. It took me a few days to understand the parts I needed but I actually figured out some issues I was having. I also was able to build Lucee from source, just for learning, which was really nice.
- theshrike79 6y agoExactly. If you know you need to cut a hundred trees to foot-long logs in a certain time-frame, you don't pick the new fancy gadget you just got from Kickstarter. You know, the one with a WiFi notification system and a cloud SaaS service etc. You go with a regular hand-saw, axe and a proper chainsaw. You'll get your stuff done - on time and on budget. You might not get the thrill of using the latest and greatest tools, but you'll get paid. After that you can grab the Solar/Hydrogen-powered Indiegogo-funded whizbang and go test in on a tree or two on your own time.
- limomium 6y agoChoose PHP.
- pdimitar 6y agoPHP silently transforming all string keys of a map to integers when they are all integer strings ("123", "456" etc.) is exactly one of the reasons I'll never choose a language that pulls the rug from below my feet and replaces it with parquet.
- limomium 6y agoIf you bother to read the manual [1], it explicitly states that this happens. Almost at the top of the page. Hardly "silent". [1] https://www.php.net/manual/en/language.types.array.php https://www.php.net/manual/en/language.types.array.php
- pdimitar 6y agoIt's not reasonable to expect such gotchas. It might have been a 20px red bold text on top of php.net and it would still be very not okay.
- galoisgirl 6y agoNo.
- tarkin2 6y agoYeah. Java is pretty boring but I wouldn’t recommend for the majority of cases.
- the_af 6y agoWhy not? Java is used to great success in the software industry. It's a good language and platform, fads to the contrary notwithstanding.
- pdimitar 6y agoWhen you are actually coding Java -- yes. But as a sibling commenter pointed out, there's a lot of "XML as code" in the Java world. That's really hard to work with.
- the_af 6y agoI haven't dealt with "a lot of XML" in Java for ages. I've been using it in my day job for a decade, and about the only XML I touch is pom.xml (that's the build file for Maven). This is like complaining about stuff in Java 1.4 -- sure, but we haven't been using it for ages. Please don't take it the wrong way, but the days of XML for everything are long gone, and for years in Java it's been XML for nothing as a counter reaction.
- pdimitar 6y agoYour experience doesn't nullify mine, and vice versa. There's a huge pile of legacy Java applications out there still needing maintenance and occasional new features.
- deleted 6y ago[deleted]
- the_af 6y agoYou cannot judge a language and platform merely by legacy software. By that token, almost everything today is horribly broken, even trendier technologies like NodeJS or Go. You'd have to judge C by K&R standards, and C++ as the horrible preprocessor it initially was. It makes no sense! You must judge Java by the developments of the last decade at the very least. Otherwise you're ignoring the practitioners. Java hasn't used XML in ages and you cannot fault it for legacy apps. You could similarly complain about the horror of EJBs -- sure, but the industry has moved on and acknowledged they were a mistake.
- _hardwaregeek 6y ago> YouTube was (and still largely is) written in Python, way before it was cool and well-known That's a good point. I wonder how many successful apps used tech that only appeared boring after the fact. Rails is a fairly boring stack today but back when GitHub started, it probably wasn't.
- d0m 6y agoPeople use "boring" in opposition to "hyped" or "trendy", which like you said totally misses the point. I jumped on react right away when it came out, but not because of it being trendy, but because like you said I could be productive with it right way, I knew it'd be around for 5+ years and that I could hire engineers.
- dahauns 6y ago>I knew it'd be around for 5+ years and that I could hire engineers. How could you have known that right when it came out?
- zpallin 6y agoAgreed. I find "boring" to be an unreliable metric for decision-making in software. A boring tool could result in damage to the long term development of software if it is inflexible, for example. Migrations between tools are easily some of the most expensive technical debt costs any software organization may face. I also agree that the better measurement of good software is that which is unsurprising. Code should be easy to follow, and the decisions for the software tools that are used should be given the same treatment. You should be able to explain your code or infra to most developers without any raised eyebrows. That doesn't make it boring. In fact, it's very interesting when a problem that looks complex on the surface can be solved by relatable means.
- lazyant 6y ago"boring" is OK "less surprises" is better, for me I think of it as "less risky". Everything is risk management.
- djmips 6y agoBut boring brings the views. Single word. Concise. Controversial.