HackerTrans
TopNewTrendsCommentsPastAskShowJobs

scottc

no profile record

Submissions

Ask HN: What do you think of my landing page copywriting tool idea?

2 points·by scottc·vor 4 Jahren·0 comments

VS Code extensions for web development in 2022

creativedesignsguru.com
56 points·by scottc·vor 4 Jahren·29 comments

comments

scottc
·vor 4 Jahren·discuss
This looks like just what I needed when I built my "admin ui" last year.

Instead of building an admin ui with Django or similar, I encourage you to just stick with a web-based spreadsheet for your internal users (if you have a small team, technical teammates, startup, etc).
scottc
·vor 4 Jahren·discuss
Lol glad I was not alone.
scottc
·vor 4 Jahren·discuss
What's the diff? I love regexr and credit that site to my finally understanding regex.

In fact, I was just on it this morning!
scottc
·vor 4 Jahren·discuss
Would anyone here want a cloud-hosted hosted version of node-red? Like a PaaS for node-red?
scottc
·vor 4 Jahren·discuss
In addition to this list, for those doing node monorepos in 2022, the extensions that I think you must use are:

  - Github copilot - like autocomplete on steroids.
  - peacock - change the workspace color - helps reduce mental load when working on different projects.
  - tag autorename - this should be built into vscode, saves a bunch of keystrokes
  - snippets - this is a category of extension. Find whichever snippet lib is out there for your stack.
scottc
·vor 5 Jahren·discuss
Interesting read. Do you recommend a resource to learn rails for the reactjs developer? Seems like only the opposite exist nowadays.

As someone who created their app in Next.js this year, I can tell you the Node.js ecosystem is in absolute shambles. We are making a WYSIWYG / ecommerce platform for authors, so we need the ability to make and preview live changes.

After finishing our MVP with a no-code solution, we decided to move to a custom Next.js app in as little time as possible. Big mistake. I had the urge to dig into Rails but I was much more comfortable in React. That being said, it's been a nightmare dealing with package upgrades, ESM vs CJS, running tests, adding Typescript, etc.

I believe, for example, creating the preview component would have been significantly faster in Rails than Next.js.

Recently we migrated to Next.js v12 for speed improvements. So many roadblocks. It took forever to debug. Again, mostly due to dependency resolution issues.

Blitz.js is supposedly going to be the Rails of JS but there is no way they'll ever have the support that either Next or Rails will receive.
scottc
·vor 5 Jahren·discuss
Anyone here more experienced than me in CQRS care to weigh the pros and cons betweens these two patterns?