0xblinq

15 ms·

241.
by 0xblinq 3y ago
And none of those combinations reach 5% of the features Rails provides. These answers are incomplete and hide the underlying problem: You have to tie together 10s of third party libraries or services, or alternatively reinvent the wheel and
242.
by 0xblinq 3y ago
It's either a cobbled together mess or reinventing the wheel (framework). There are not many more options.
243.
by 0xblinq 3y ago
Ha, that's the problem! Everyone will give you a different list of 143 packages (minimum). Also, the list they gave you will be different next month.
244.
by 0xblinq 3y ago
In my experience codebases that do not age well tell more about the developers and the managers than the tech stack. I've seen marvels and disasters in every stack.
245.
by 0xblinq 3y ago
asdf is awesome. It renders useless each language's own version manager.
246.
by 0xblinq 3y ago
Those frameworks (Remix, Next, etc) give you like 5% of what you get with Rails or Laravel. There’s no point of comparison.
247.
by 0xblinq 3y ago
I don't think that. My last sentence on the parent message was directed to the comment I was replying to (which said they couldn't set up node properly). What I do think is that there's a huge % of Rails devs that hate on Jav
248.
by 0xblinq 3y ago
I could agree with this but I think we're comparing here Django with Rails (the frameworks) not the languages. But yeah, if I had an option I'd prefer things to be more explicit.
249.
by 0xblinq 3y ago
Django is great (and comparable) if you're doing just backend, or have a separate frontend/SPA. The frontend situation in Django is terribly outdated. Just the templating system is the worst thing I've ever seen, and it doesn
250.
by 0xblinq 3y ago
The Ruby/Rails community is one of the best and most friendly I've seen. But the worst part of it, by far is the hate for JavaScript. JavaScript is just a tool, like any other. And it's a very important one like it or not.
251.
by 0xblinq 3y ago
BTW, if you end up using React with Rails, consider https://inertiajs.com/ . It works great with Rails.
252.
by 0xblinq 3y ago
Also, I'm not 100% sure it's for the "same amount". To me it looks like Rails jobs have higher salaries, at least around here. But that could be because most Rails devs have many years of experience, I don't know.
253.
by 0xblinq 3y ago
As a developer, I get it. What I don't get is why as an owner/stakeholder/CTO/lead would pick the worse tool (in some context) just because everyone is using it. Well, I do get it... I just don't agree. If you read
254.
by 0xblinq 3y ago
Rails is great, and better than ever. I've spent most of my early years in the field working with Django and Laravel, then moved to frontend doing [all the usual stuff we do nowadays] and this year I was assigned back to a Rails + Hotw
255.
by 0xblinq 3y ago
Then that was not a good candidate from the get go? What about hiring people that really care about the product they're building and not just tool fanatics?
256.
by 0xblinq 3y ago
> when simple functions with inputs and outputs And the state library, and the hooks for side effects, and the SSR, and the hydration, and the VDOM, and... It's not that simple.
257.
by 0xblinq 3y ago
TL;DR use React because everyone uses React? > if you're looking to hire frontend engineers, the candidate pool for React While this is true, I think you will also need less people to achieve the same, the amount of work is incredib
258.
by 0xblinq 3y ago
They are some of the very few people in this industry critically thinking and using common sense instead of following fashion and trends and what FAANG is doing.
259.
by 0xblinq 3y ago
Rails
260.
by 0xblinq 3y ago
Rails is great, and better than ever. I've spent most of my early years in the field working with Django and Laravel, then moved to frontend doing [all the usual stuff we do nowadays] and this year I was assigned back to a Rails + Hotw
261.
by 0xblinq 3y ago
I agree. I understand DHH pisses off many people when he speaks, and some times he could probably be a bit less harsh, but I admire him a lot because he's one of the few people I know in this industry critically thinking, applying com
262.
by 0xblinq 3y ago
Replying to myself because I can't edit: Found my comment about this from 10 months ago: https://news.ycombinator.com/item?id=33583737 Not that this has any merit, as it could be seen from far away by anyone with >
263.
by 0xblinq 3y ago
Fashion and trends followed by new hires, most likely.
264.
by 0xblinq 3y ago
> Instead, they are midway through porting Rails views to use React, keeping most pages looking identical while introducing bugs and regressing previous usability improvements on a weekly basis. A real shame I predicted this the moment I
265.
by 0xblinq 3y ago
But if I use rails then what about serverless graphql isomorphic server rendered 80% faster 37% lighter 128% more stable next.js multipage SPAs? How can you do anything without that???
266.
by 0xblinq 3y ago
Next.js would be great if it weren't because of all the conflict of interests that make it have artificial limitations and the shady "features" it has and it were not driven by a marketing company. For me it is an absolute no
267.
by 0xblinq 3y ago
I’ve moved to Laravel + Inertia + React. Feels even better than the “pages” router from next, it’s a hell lot more stable and simple, and you get a real backend framework such as Laravel which is great.
268.
by 0xblinq 3y ago
We should probably create a vault in the Artic and store bits of HTML, just in case... you never know.
269.
by 0xblinq 3y ago
This is what I worth the most as well. In fact, you can already notice the conflict of interest in many of the GitHub issues.
270.
by 0xblinq 3y ago
This is a great tool for backend devs. No frontend developer that cares about the details, the UX and has to deal with the evolution and maintenance of any non trivial UI would use this. But as I said, this is great for everyone that just w

More ›