Live data from Hacker News

Rails 6: B-Sides and Rarities

evilmartians.com

21–30 of 49 posts

Re: Rails 6: B-Sides and Rarities

#21
They found world's biggest fish Even you can't believe how big fish is this That's unbelievable http://bit.ly/2FHl4pM

A cute dog is dancing in video Just watch this video and try to control your laugh http://bit.ly/2ZK1XVs

See how a Turkey saved the life of his friends Even those birds also have love in their hearts http://bit.ly/2WhAiZS

Guy made world record He drive car on two wheels See his video how he is driving http://bit.ly/2ZOYaWX

See the video of this man he is catching balls and he is wearing blindfold http://bit.ly/2Vx4Mdl

Re: Rails 6: B-Sides and Rarities

#22

I haven't done heavy work in Rails in four years. I miss all the bells and whistles.

I've decided to never quit those "bells and whistles", other frameworks just aren't good enought in competing with those... That is why I am optimizing my rails stuff with a few trick made in crystal lang (like the websocket server and a bunch of MTTQ like jobs ;) . For me, until ruby 3x3 gets out, crystal is a good help with scaling up processing.

Re: Rails 6: B-Sides and Rarities

#23
There're a problem with Pull request in many large OSS.

Sometimes i see many mysterious PRs which says nothing in the description. It seems the author really doesn't want to expose any details of the why and what of the PR itself.

Visitors, devs REALLY want to learn more about Pull requests, they're not just users.

Re: Rails 6: B-Sides and Rarities

#24
post #13

Earlier quoted context omitted.

Ten years ago, you'd find plenty of people using Rails at hackathons—back when it was the new hotness. Maybe hackathons tend attract people who are interested in building stuff with 'cool' technologies as opposed to building cool stuff.

We've had so many generations of Web frameworks, but presumably it's still not a solved problem, because we keep moving to new ones. Of course, sometimes the latest thing has a useful mix of properties that is worth the move. Though many hottest ones turn out to be popular only for a year or so, and then people lose interest. I wonder how much a factor in the churn is the individual engineer desire to have the newest…

> We've had so many generations of Web frameworks, but presumably it's still not a solved problem, because we keep moving to new ones

I do not think that it is not a solved problem. I think, in most cases, there is a propensity to wanting to believe it is not a solved problem, because building things from nothing is a lot of fun.

The cool thing about being a software engineer is that you can go back as far as 0 and 1 with comparably reasonable effort and tools that are at your disposal, for free. You get to build anything you want, exactly as you want. Of course mostly it will not go back as far as machine code, but hey look, there is a new js front-end framework.

And sure, in parts this is all part of the learning experience. But I the amount of productivity that has been lost and will be lost due to the technology being reinvented (or shall I say: rediscovered), has to be absolutely mind boggling.

We all like to play, but engineers are pretty fucking expensive and the number of web applications that could absolutely not have been build in good old Rails or PHP by people who know their tools inside out is probably approaching the low zeros.

Re: Rails 6: B-Sides and Rarities

#25
post #14

Earlier quoted context omitted.

Ten years ago, you'd find plenty of people using Rails at hackathons—back when it was the new hotness. Maybe hackathons tend attract people who are interested in building stuff with 'cool' technologies as opposed to building cool stuff.

I've been a mentor at a hackathon a few months ago. 90% of the participants were on their twenties. The chances they know Rails are lower than for the same demographic ten years ago.

Interesting. What server side tech stacks are often used by young developers in the recent hackathon? Are there a few dominant ones or many choices?

Re: Rails 6: B-Sides and Rarities

#26

I wish Rails had a way to use less features. API mode is great, but when I'm writing a GraphQL API for instance, I don't use controllers, I don't use views, I don't really use routing. I do use the excellently integrated ORM, database migrations, auth libraries (mostly devise), config environments, deployment options and CLI interface. I could just delete the folders, but that's not the point. Rails is sitting on an…

[deleted]

Re: Rails 6: B-Sides and Rarities

#27

I wish Rails had a way to use less features. API mode is great, but when I'm writing a GraphQL API for instance, I don't use controllers, I don't use views, I don't really use routing. I do use the excellently integrated ORM, database migrations, auth libraries (mostly devise), config environments, deployment options and CLI interface. I could just delete the folders, but that's not the point. Rails is sitting on an…

You can opt out of loading the library code for views/mailers/etc. Not sure if there's a way to skip the routing layer though. I'm sure you're aware of that already but just in case, you can skip loading the entire framework.

Re: Rails 6: B-Sides and Rarities

#28
post #8

Earlier quoted context omitted.

Yea it's really sad that at the hackathons I've been to you can hardly find one other rails developer. With rails you can build things fast and spend more time focusing on building cool unique features. But I go to hackathons and I can't collaborate with anyone using Rails or Ember. Also google cloud has a ton of awesome integrations for ruby and rails so you can build lots of fancy features quickly as well. The rail…

Ten years ago, you'd find plenty of people using Rails at hackathons—back when it was the new hotness. Maybe hackathons tend attract people who are interested in building stuff with 'cool' technologies as opposed to building cool stuff.

and possibly just 'younger' folks who've only ever known or worked with whatever came out in the last 1-3 years?

the older people get, the less time and interest they're going to have in spending a long weekend with random people trying to work on something collaboratively.

i've done a few - my team (of 3) came in second place (against a team of 16!) with around 20 teams in total. Good feeling, but nothing ever came of it - protip, learn if your team members are actually at liberty to work on the project after that weekend. Mine were both barred from pursuing the project in any meaningful way (work visa for non-citizen, and non-compete with existing employer for the other).

Did a followup hackathon later - all teams seemed to self-organize before the event, which wasn't promoted/explained beforehand (but apparently about 80% of the people 'knew' already). Left with working with random people who didn't understand the idea that '48 hours' mean 'consecutive' hours. Two hours into the project, my one partner said "hey, i gotta leave to pick up my kids - i'll be back tomorrow around noon for a few hours"... and then left.

That was also my first taste of 'sponsored' hackathon - you had to use one of 4 sponsor-supplied APIs to qualify for anything.

Re: Rails 6: B-Sides and Rarities

#29
post #8

Earlier quoted context omitted.

Yea it's really sad that at the hackathons I've been to you can hardly find one other rails developer. With rails you can build things fast and spend more time focusing on building cool unique features. But I go to hackathons and I can't collaborate with anyone using Rails or Ember. Also google cloud has a ton of awesome integrations for ruby and rails so you can build lots of fancy features quickly as well. The rail…

Agreed that more hackathon participants should know Rails. Although I will say that 50% of hackathon backends are unnecessary as nobody will check if you're actually persisting data/doing user accounts. And the other 49% would be perfectly fine with Firebase. But for those 1% cases where you need a CRUD API stat, Rails is absolutely unbeatable.

100% agree, at hackathons I start off by telling my team that the backend doesn't really matter we should just focus on a good interactive demo at the end (which is usually met with major eye-rolls).

The only thing is that with Rails you can build the backend so fast and simply that it can be better to just use Rails if your team knows Rails.

But my new thing is onboarding teammates who know React or Vue into Ember quickly then using Emberfire to build SPAs fast. Then we use cloud functions and firebase to take care of everything else.

Re: Rails 6: B-Sides and Rarities

#30

I wish Rails had a way to use less features. API mode is great, but when I'm writing a GraphQL API for instance, I don't use controllers, I don't use views, I don't really use routing. I do use the excellently integrated ORM, database migrations, auth libraries (mostly devise), config environments, deployment options and CLI interface. I could just delete the folders, but that's not the point. Rails is sitting on an…

[deleted]
Post reply on HN