Even the venerable libraries like useQuery introduce as many surprises as they do benefits. The complexity cost of understanding what is going on under those 20 LOC is quite high – you need to understand "stable values" (which is only relevant to React components), re-renders and how they're triggered, maybe need to understand how graphql fragments are collated into one query document... maybe need to know when useRef is the right way to memoize over useMemo.

I agree with the author, that it feels insane. I would even add to the insanity the lack of quality when searching for help, and the weird rabbit holes that GPT can send you down if you don't already know what "good" looks like.

My guess is that you'll have some diehard fans early on - Ello did, and they stayed to the end (thanks!) and they'll bemoan every single change - just roll with it, trust yourself but also listen to them.

If you get some success you will have a spammer problem (esp porn), but if you limit (better: don't have) public feeds maybe you can avoid the worst of this. Mutual follow makes sense as a way to limit the blast radius of bad actors, but then people will get spammed by friend requests. It SUCKS. Maybe you punish accounts that blast lots of requests but get very few follows back. We did something like this.

Actually one idea that I think would work well: once you have a "this is a spam account" determination, hide those spam accounts from real users, but let them engage with other spam accounts. This will cost you some compute time, but it will give them the feeling that they are being successful without distracting users.

Good luck!

My god, sit down and just nod and say to totals "oh you like ObjC, neat ", or better yet try to understand what they're saying. You do not have to offer your trite condescension.

ObjC is a fantastic language, Swift is fine too but the compiler is slow and breaking changes to the language are painful.

The migration assistant? FFS it only goes so far, and only when it works.

Other favorites are Ted Chiang's stories, Children of Time, Dune, and if you want some real escapist but thoroughly fun pulpy hilarity: Dungeon Crawler Carl

Comments URL: https://news.ycombinator.com/item?id=9188251

Points: 1

# Comments: 1

I cut my teeth on app builder/interface builder about 10 years ago, back in college, and I have never learned to love the GUI approach to building UI (nor do I care for the XML/XAML approach of android/xamarin - just code, thank you).

Since then I learned python, ruby, and don't feel any desire to go back to strongly typed languages. Anyway, I hope more and more people get fed up with Swift and join us in the RubyMotion camp. It's a ton 'o' fun. ;-)

And to chrisdevereux's point, we've already got some Android support in MotionKit.

RubyMotion supports xib files, storyboards, xcdatamodel files, and Android XML files (and localization files, etc), so if you ARE interested in switching, you don't have to stop using those if you're already used to them.

Workflow is one thing, but then writing Ruby code is so fluid. Notice that there's not a lot of preamble (imports and such) that you need to take care of in the Ruby code, I think that's great. But, again, language and workflow are very personal, and I think every tends to "think they're right" ;-)

This is such a cool project, and Juan has been working is A off on it! Glad to see it released!

Reminds me somehow of Sinatra - e.g. Promotion : Cocoa :: Sinatra : Rails

I translated the models into Ruby, and pulled those out of the xcode lib. Eventually the entire codebase was converted (except the nibs).

f6908b2 - 2011-04-28 21:50:28 -0700 fixed a stupid bug in the Xcode4 template (Matt Aimonetti)