Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

“It's The Future”

circleci.com

Post reply on HN
Print view View original

461–470 of 536 posts

Re: “It's The Future”

#461

Post by bertiewhykovich »

rjvir wrote: post #303

There was a time when Heroku seemed just as foreign to me as Docker does in this article. - So shared webhosting is dead, apparently Heroku is the future? - Why Ruby, why not just PHP? - Wait, what's Rails? Is that different from Ruby? - What's MVC, why do I need that for my simple website? - Ok, so I need to install RubyGems? What's a Gemfile.lock? None of these commands work on Windows. - I don't like this new text…

To be fair, a lot of these questions are valid. You arguably /don't/ need MVC for yours simple website, if Dreamweaver floats your boat you might as well use it, it's unclear why a small website needs an elaborate deployment infrastructure, using a VCS for personal code can be overkill, PGSql and SQLite aren't better than MySQL for every use case -- and so on.

Frameworks, orchestrations, even just new technologies -- these are great if they actually make your job easier or if they make your product better. Unfortunately, they often do exactly the opposite.

Re: “It's The Future”

#462

Post by matwood »

KurtMueller wrote: post #261
dirtyhenry wrote: post #168

Earlier quoted context omitted.

Totally agreed. As a freelance, it's really scary to invest time into a full stack of technologies. I should start a discipline to pick tools and not look back before n years went by. Maybe n = 2 or 3 ? (right now, I'm Objective-C - not even Swift - for native iOS, Ember for client, Rails for API/back-office and Heroku for deployment)

Honest question: How's that tech stack working out for you? What if you want to dev an Android mobile app? Have you looked at React Native at all? Thanks.

React native was not mature enough the last time I had to solve this problem. After writing and maintaining native clients in both Android and iOS for years, I decided to try something different. SPA app + Cordova + writing custom, native plugins for performance has worked out pretty well. Some things in the UI are not as fast as I would like, but develop/test/release cycle is so much faster (web, ios, android released nearly at the same time). It does help that I can write native Android or native iOS (obj-c/swift) to handle the plugins where needed. Cordova can also be a bit of a mess to deal with sometimes, but it is improving.

Re: “It's The Future”

#463

Post by scrupulusalbion »

JustSomeNobody wrote: post #274
liveoneggs wrote: post #265

Earlier quoted context omitted.

What other parts of getting old suck? :)

Having to work with people who see caution and wisdom as "getting old".

Virtues are generally disregarded by those who seek instant gratification.

Most of the times that I bring up the concept of virtue to my peers in age they seem either confused with the concept or contemptuous of it. They behave like virtue is a purely religious thing, yet caution in the face of possible danger is a very basic survival skill.

Re: “It's The Future”

#464

Post by bogomipz »

rajeshp1986 wrote: post #109

The article perfectly summarizes my frustration and sentiment. These days I hear these buzzwords all time. I work as a consultant for an enterprise product and most people whom I meet they somehow catch these buzzwords and blurt it out in front of everyone during meetings and discussions to either showoff that they know technology and things that are in the market these days(also latest iphone, apple news, tesla, spa…

This is not new. This industry has been about trends since the first dot com boom - remember Java Beans?, J2EE, 3 tier architectures, blade servers, virtualization, Rails, full stack, Nosql and big data, ad infinitum. It's an industry like any other with its own signal to noise ratio. You can get frustrated about it or accept it and accept that's also what makes it an interesting industry to work in.

Re: “It's The Future”

#465

Post by atoko »

axelfontaine wrote: post #70
djhworld wrote: post #11

One thing that I liked about Heroku was the ease of deployment for Java applications (or any language for that matter as long as you had the right build pack) Since they upped the cost of their small tier, I moved to Digital Ocean and installed Dokku, which gives me that Heroku-like deployment experience so managing my (admittedly very small) website isn't that much of a hassle.

We at Boxfuse ( https://boxfuse.com ) provide the same ease of deployment for running Java apps (as well as Go and Node.js ones) on AWS. All you need to type is literally: boxfuse run myapp-1.0.jar -env=prod And you automatically get things like auto-scaling, database auto-provisioning. easy debugging and more. Disclaimer: I'm Boxfuse's founder and CEO

Hey, it looks like your "center-iframe" is pointing to an invalid link. It threw me off while I was looking around. Hope this helps

Re: “It's The Future”

#466

Post by collyw »

shados wrote: post #202
mrhektor wrote: post #31

"-No, look into microservices. It’s the future. It’s how we do everything now. You take your monolithic app and you split it into like 12 services. One for each job you do. That seems excessive" A 100 times yes. We tried to split our monolithic Rails app into micro-services built in Go. 2 years and many fires later, we decided to abandon the project. It was mostly because the monitoring and alerting were now split in…

Yeah, we do micro services, the "real" kind. Not the "SOA with a new name kind", but the "some services are literally a few douzan lines of code and we have 100x the amount of services as we do devs" kind. The thing is, you need a massive investment in infrastructure to make it happen. But once you do, its great. You can create and deploy a new service in a few seconds. You can rewrite any individual service to be la…

So that sounds pretty much like a function call in a monolithic app. How do you store state? I assume you need to between all those microservices.

>The thing is, you need a massive investment in infrastructure to make it happen.

I thought that one of the selling points of microservice architectures was the minimal infrastructure. I am really struggling to see an advantage in this way of doing things. You are just pushing the complexity to a dev ops layer rather than the application layer - even further form the data.

Re: “It's The Future”

#468

Post by TeMPOraL »

lj3 wrote: post #458
TeMPOraL wrote: post #431

Earlier quoted context omitted.

Or learn about better wheels designed by smart people back in the 60s and 70s, when no one had the capability to just keep sticking wheels onto cars to see what works - so they had to rely on thinking and solid engineering practices instead.

Precisely why I've started buying technical books from ages past. I'm working my way through Algorithms + Data Structures = Programs by Niklaus Wirth , Constructing user interfaces with statecharts by Ian Horrocks and Practical UML Statecharts in C/C++, Event-Driven Programming for Embedded Systems . The last one has been especially enlightening. Do you have any suggestions for which 'better wheels' people should be…

SICP is a classic I can highly recommend. It made me aware of just how much the "new, smart" approaches to organizing code that people like to attribute to their favourite programming model (like "OOP is best because classes and inheritance means modularity") are actually rehashing of obvious and general ideas known very well in the past.

I generally like reading on anything Lisp-related, as this family of languages is still pretty much direct heritage of the golden ages.

The stuff done by Alan Kay, et al. over at PARC is also quite insightful.

Re: “It's The Future”

#470

Post by KurtMueller »

matwood wrote: post #462
KurtMueller wrote: post #261

Earlier quoted context omitted.

Honest question: How's that tech stack working out for you? What if you want to dev an Android mobile app? Have you looked at React Native at all? Thanks.

React native was not mature enough the last time I had to solve this problem. After writing and maintaining native clients in both Android and iOS for years, I decided to try something different. SPA app + Cordova + writing custom, native plugins for performance has worked out pretty well. Some things in the UI are not as fast as I would like, but develop/test/release cycle is so much faster (web, ios, android releas…

Another question... how do you like Ember for your web apps? :)
Post reply on HN