Having written a JavaScript runtime in Rust in the past - Rust is an excellent choice. Not just due to the development experience, but also for embedders who want to consume the project as a a library (rather than a binary, e.g. node).
Not sure about vibe-coding it. While they aren't using v8, LLMs made it easier to understand v8 quirks and update v8 as they make weird changes every now and then. It couldn't write the runtime without help though.
They describe themselves as an "established startup" lol. It's just an industry-tailored CRM so it's a form-heavy application, nothing about it is ground breaking.
IMO if you're profitable and have been around longer than a decade, you're no longer shipping features for survival and should have bandwidth allocated to improve the product reliability and performance.
No observability/monitoring, no automated testing, no CI/CD, a 30 second - 5 minute login time, and a 20mb JavaScript bundle is a pretty poor customer and developer experience.
I spoke to the head of sales / product to understand customer retention and the factors on failed sales - it looks like our customer retention is unaffected by a slow or unreliable the product.
Luckily I am about as frugal as they come (humble beginnings) - but also I'm in Australia and big tech here pays about as much as an average Sr salary in a non big-tech company in the states.
At my last job, I was on 220k/y USD TC as a Sr.
This role is 140k/y USD, which is close to the top end of non big tech salaries here.
Appreciate the balanced feedback. It echos what some of the longer tenured engineers have advised me.
One colleague whom I have worked with in a previous role and has a similar mindset to me said that he just does the 1 PR a day and spends the rest of his time on OSS for satisfaction.
I took that onboard and have been ramping up my PR count over the last week without making suggestions - but I suspect the reputational damage has been done and I have soured relationships as, contrary to the 1 PR a day metric, my manager quizzed me on what I was doing after submitting my PRs in our 1:1.
Appreciate it and will certainly keep that advice in mind for the next role
I think there is a strong case that "the right to repair" includes software. If that doesn't mean drivers must be open source, it should at least mean hardware is documented such that a driver can be written from it.
But the US still doesn't have the right to repair hardware, haha.
I hope the EU is listening. They won't get far with their sovereign software push if hardware cannot be used. Even on the Android side, you can't write an alternative to Android because all of the hardware has locked bootloaders and hidden drivers. Good luck reverse engineering the hardware/drivers on a Samsung Galaxy - let alone an iPhone or MacBook.
I agree that MacOS is more polished. However overall, Linux is a better complete package - especially for power users, gamers and engineers.
Linux GUIs are _fine enough_ though the jank is still present. The good news is they will get better with more users entering the chat.
The thing to note is that, we don't want to confuse "it's not as good right now" with "It's bad so I will never use it" because that signals a lack of interest.
There is a non-zero chance that Apple could be compelled to support it if enough people express interest (historically, they have with bootcamp).
Competition is good, even if the competition is bad right now. We must encourage it.
How nice would it be if there were ReadAsync and WriteAsync traits in the standard library.
Right now, every executor (and the futures crate) implements their own and there are compat crates to bridge the gaps.
reply