It's one of those things that you don't realize how poor the performance is until you experience something better.
Mentioned from his blog: https://mitchellh.com/writing/ghostty-is-coming
61 karma · joined September 28, 2014
Interests: Web Development, Technology, Startups
---
It's one of those things that you don't realize how poor the performance is until you experience something better.
Mentioned from his blog: https://mitchellh.com/writing/ghostty-is-coming
I have a large application and I use next.js for the landing pages (landing, tos, privacy, blog, login, etc..) - but for the core application after login, I just use vanilla react with react router. For me I keep these as separate applications as I don't want to load the entire app just for the landing page or login box.
Every time I need to work in the nextjs part of the app I always run into problems and have to read the docs and troubleshoot, sift through which part of the docs apply to my setup versus the app router.
If your entire application needs to be indexed as a static site (e.g. content based versus a web application), then vanilla react isn't a good fit - so it depends on your needs.
Unrelated - but shout out to https://nx.dev. I always prefer using this for all of my projects - made it super easy to have my node backend, react frontend, nextjs landing page, chrome extension, cron jobs, etc.. all in the same codebase where I can share code between all of them via non-publishable libraries.
I normally just record the jam and get a link and paste it wherever, but I love the ability to have Jam create jira tickets for me. And THANK YOU for making it easy to choose the sprint! the Slack Atlassian plugin makes it impossible to find the sprint and shows all the closed sprints that cannot be used for new tickets.
Really an awesome tool. I have been using it to report bugs for any random open source project I am working on.
Likely an output of so many electron based apps which are memory hungry, but if the memory is supposedly "really fast" then I would expect better performance. Never had the issue with Intel.
But with a nice bit or memory, the performance is really nice.
I can write code once and run on many runtimes across many different programming languages.
I think the server use-cases are actually more compelling than the browser use-cases.
For example, Fastly's edge compute supports running WASM code at the edge. Similar to lambda, but in the language of your choice and with great sandboxing qualities baked in.
cmd+tab to change applications (like on every OS), but also cmd+~ on macos to change windows within active application (e.x. cycle through all web browser windows)
I don't use multi workspaces at all, so sorry if this comment isn't useful, but thought I would throw it out there just in case.
I recently purchased a 79 Lincoln Continental Mark V and it is that same length as my 2020 F150 - 40 year spread, same size vehicle.
People need to drive safe and not be stupid behind the wheel. I would guess that cell phone use while driving kills way more people than "big vehicles" do (most of us are guilty of this). I feel it is a technology+cultural issue.
This episode isn't 100% current, but still relevant and discusses this issue: https://changelog.com/jsparty/137
Safari works, but cannot access bitbucket.org in Chrome.
I also built a supporting tool to parse SOQL queries to support Jetsream because everything open source was broken and really sucked. https://paustint.github.io/soql-parser-js/
Thank you for sharing.