I was very surprised to open the gemfile and see a gem I wrote "s3_direct_upload" being used. Especially considering there is native support to upload files directly to s3 in rails 5.
Then I looked at the repo and realized, wow people are still using this gem, maybe I should maintain it.
I wrote a Java natural language processing library in 2003, which is hosted on sourceforge.
I found out a week ago that HP is apparently has a team not only actively using it, but trying to build their own version which outperforms it. It amuses me greatly to see them publishing, with my stupid toy library citation from 2003 sitting first and second on every benchmark they use.
I think this is a very common experience for maintainers.
I wonder if it would make sense to have a low friction way for people to notify maintainers that they’re using a library? I guess stars are a little bit like that but people star stuff they don’t use.
Or maybe have something that would automatically crawl github for you and find out how many projects depended on your library.
Not only is the content great on that site, the performance of it is absolutely spectacular. It's amazing how much people will jump to new fangled solutions when this site is a great example of what a well tuned Rails app can pull off from a UX perspective.
It's cool that it's open-sourced, but I've never been impressed with the content. Even when an article is about a topic I'm interested in, it's hard to get past the Buzzfeed-style "How do you do, fellow kids?" tone.
Yeah, I kinda feel the same way about the content. It's like 'coding, not programming', 'what was your biggest achievement today? Mine was no conflicts ;)' and other silly wholesome comments.
But yeah, the performance of the site is phenomenal.
It's not about tuning, the site just preloads content when you mouseover links, using a background service worker. That's pretty "new fangled" compared to most sites.
Hmm you're not wrong. Re the other comments here about preloading from mouse over events, it's very snappy on mobile too, so there's something else going on as well.
Very gratifying to see it's using Preact, since I've just chosen that for a project over React, largely due to smaller bundle sizes. Another post on HN today about Amp makes me feel it's the 90s all over again, with people shaving kB off here and there - and that's no bad thing!
"We run on a Rails backend with mostly vanilla JavaScript on the front end, and some Preact sprinkled in. One of our goals is to move to mostly Preact for our front end."
Got the same frustration just the other day this was here. Thehack was opening someother page and then was able to get to that link. Still don't understand much what the site is about. It feels like an interface to a specific subreddit.
Just whatever you do on dev.to don't ask hard questions to their AMA people. You'll get shadowbanned for that. (Even if the person handles the question well)
Instead of just dismissing all Javascript backends, can you tell me why using Ruby is better than Javascript here?
Personally I do prefer Rails over something like Express too, but that's more of a personal preference. I don't see why todays Javascript backends are all "shit"?
Seriously though, the language itself is a matter of preference, but you can’t dismiss that the ecosystem sucks. Projects with hundreds of packages in their dependency graph seem common. I’ve worked on a (front-end) React project with 1,7k packages involved in the build process. That’s madness.
I agree, left-pad was a mess, but while the huge amount of dependencies is the thing people most complain about, is it actually unique to Javascript? Looking at the Gemfile for this project, it seems like you're also going to have to install hundreds of gems if you want to get this up and running.
For some time I was looking for a discovery mechanism in database topics.. so combining the usual tags yielded already a good blog I can follow. People can use their blog rss to crosspost, and the text contrast is friendly.
I'm in my early 20s and can confidently say this is the first I've heard of Dev.to and hopefully the last. I like emojis as much as the next millennial but this website looks awful.
I've been following Dev.to before it became a website and was only a twitter handle. I found it to be a less hostile version of HN at times. It also is a bit more beginner focussed (helps by being more friendly). Also, most posts and comments are quite positive :)
The problem with "beginner-focused" sites IMO is they preach wrong advice. Just because experienced people tell you hard truths doesn't mean you should run away and hide in a beginner-friendly corner. I mean you can do that, but don't complain when you realize that the experienced guy was right and your mistakes cost you your entire business.
No, it is not. I am 49 and I have no problems using HN. Also often it is clear, that some of the amazing answer found here, are from people way older than in the their 20s, because some of those answers requires the poster to have many many years of experience in order to come up with that answer.
The problem with HN is that it has too many content not related to tech, like lots of politics and also is too american focused. Anybody not from america gets a feeling of being a little weirded out by some of the things and morals discussed around here. At least for me that's a problem. If that dev.to gets nice content and doesn't get all these america specific morally political stuff going around maybe I'll use it.
Looks like the standard rails mess :/ Don't get me wrong. From time to time i am going to look at other peoples rails code to learn, how they solved common problems in grown rails apps. Most oft the time i leave rather disappointed...
Can you be more specific? The modeling/models don't look TOO insane - need some refactoring, but not too far off.
If you think this is a rails mess - you haven't seen anything yet. I am still able to hop in and reason about what this codebase does with no onboarding - a key benefit of rails. I've worked on codebases where all those niceties were thrown out the window.
Then I looked at the repo and realized, wow people are still using this gem, maybe I should maintain it.