Hacker Newsnew | past | comments | ask | show | jobs | submit | pangolin1's commentslogin

KeeperDAO | Mid-level+ React Developer | https://www.keeperdao.com/ | Remote

We do efficient on-chain trade execution.

If you have worked on a reasonably complex modern React production app and are interested in working in crypto/web3, please reach out. You do not need any prior experience with crypto or finance.

Perks:

  - We won't waste your (or our) time with endless interviews and tests. NO live coding.
  - Great pay.
  - We're working at the bleeding edge of blockchain tech.
  - We work on discord and with voice calls. No video calls, very few enforced meetings.
Hit me up: pangolin at keeperdao dot com


> Indeed, we've started to notice that many newer developers aren't even aware of an alternative approach, as they've spent their entire career in a framework like React

This is exactly why it's often best to use React even if it's overkill. It makes recruiting and onboarding new devs to the codebase much easier. Given the rate of turnover for frontend devs, this is a significant advantage.


This is a tough stance for me to get on board with. You're not wrong to value SPAs for this reason, but I don't think picking the wrong architecture on purpose is defensible either.


There are no panaceas in technology stacks, but it does shock me sometimes how teams blindly jump to React (and sometimes Next) just due to perceived popularity and don't actually do any analysis on what their problem points are, and whether it would make sense for them.


A few months ago (around the Christmas break) I decided to build a web UI for something. The last time I personally touched “front end” HTML or JS was when IE5 was a thing, although I’ve done a lot with server side TypeScript and the Node ecosystem.

I spent a couple of days evaluating the options, coming at this with fresh eyes, but not as a beginner to programming or architecture, and found the following:

- Ember makes the most sense to me personally, but at the time the stable ember packages pulled in several dependencies npm called out as vulnerable, and editor support was not great. The webstorm plug-in basically didn’t do anything useful. Finally, it was not obvious that TypeScript was a first class citizen, which put me off.

- Vue seemed ok, if a little harder to reason about than Ember - I can see why people like it but there didn’t seem to be a compelling reason to put effort into it.

- React is hands down the “winner” of the ecosystem, is easy to get up and running with and has great editor support. As someone that generally likes functional programming, the concepts clicked nicely. TypeScript was first class, TSX seems nice enough.

In the end, the limited time I had meant I just wrote a native Mac app with SwiftUI, and resolved not to touch web stuff for another 2 decades if I could avoid it.

I have a huge amount of respect for people who can keep the front end web ecosystem straight in their head - I really don’t understand why people consider “back end” the more complex technical domain.


Especially for things that are for all intents and purposes, read-only.


And if a client asks why you are recommending an SPA, are you going to tell them the ignorance of your employees requires it?


Svelte is still the better choice. It compiles to much better optimized and smaller bundles, and a team of React devs can learn Svelte in a weekend thanks to how much leaner and more intuitive it is, as well as how true it stays to writing vanilla JS/HTML/CSS. The huge gains in dev speed and ability to plug and play any vanilla library without a framework wrapper make it hard to justify React over Svelte.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: