A Googler who benefits from GOOG RSU going brrr says Google is better than a competitor. OK? Are you authorized to speak on Google's behalf publicly?
He even started his comment like it had been approved by lawyer first lol
Readit Newskyruzic commented on Google Cloud now has a dedicated cluster of Nvidia GPUs for YC startups techcrunch.com/2024/08/01... · Posted by u/Astroboy007
kyruzic commented on The A.I. Bubble is Bursting with Ed Zitron [video] youtube.com/watch?v=T8Byo... · Posted by u/grugagag
By 2025 the majority of applications will use AI in some way (mostly to allow for sloppy user input), in 5 years there will be no non-AI applications.
For example, in healthcare (because... day job), you will be interacting with an AI as the first step for your visits/appointments, AI will work with you to fill out your forms/history, your chart will be created by AI, your x-ray and lab results will be read by AI first, and your discharge instructions will be created on the fly with AI... etc. etc. etc. This tech is deploying today. Not in a year, today. The only thing that's holding it up is cost and staff training.
2025 is 6 months away. There is absolutely no way a majority of applications will use it.
kyruzic commented on The A.I. Bubble is Bursting with Ed Zitron [video] youtube.com/watch?v=T8Byo... · Posted by u/grugagag
My cost is $20 a month for ChatGPT Plus, and the value I get out of that far exceeds $20. That is value creation, not destruction, right now. Not some imagined AGI future hypothetical.
And OpenAPI is spending more than $20 to provide you that service...
kyruzic commented on Google SGE Says Drink Urine to Pass Kidney Stones Quickly seroundtable.com/google-s... · Posted by u/arromatic
Could be worse. Urine is sterile, so nobody will die or explode following this advice.
No it's not.
https://www.healthline.com/health/is-urine-sterile
You aren't gonna die from drinking it, but it isn't sterile.
Many companies are not throttled by server language performance. Performance in many cases will depend on your database, geolocation, and caching techniques over nodejs vs go. Nothing wrong with prioritizing developer experience.
I do agree with this, but I'd argue the developer experience of nodejs with Typescript is far worse than that of rust/go
i don't agree at all. nodejs backends are as performant as you build them. the whole premise of node was async io, so if you're doing a bunch of blocking stuff then yeah, you're going to have issues. otherwise there's nothing innately non-performant about the platform.
it's impossible to debate more without going into details on your performance issues. typical backend architecture for any platform these days is the scalable container model, if you wanted scale-to-zero i wouldn't necessarily use node because of cold starts.
prisma can be great, can be slower than writing your own query, but that's the whole point of it. most of the time, it works and you can forget about queries and typings. when it doesn't, you can just eject to raw sql anytime you want.
i'm not a total nodejs fanboy, and have used more jvm (java/kotlin/scala) in my life, but if i was building a web-app today i'd absolutely consider node for all the reasons the author listed
Nodejs backends are not "as performant as you build them" nodejs is slow! This is an undeniable fact. If you ever have to do anything computationally intensive, which every backend at some point will nodejs will become the bottleneck.
This sounds weird to me. What kind of scale / traffic did you have? Must be incredible read write heavy with millions of users?
I'm saying this because i myself have, and lots i know, have launched production sites with 100s of thousands of users on ready-made stacks like, Laravel, Rails, Flask (Php, Ruby, Python). But it's my impression that these fall short on millions of users and enormous concurrent traffic, but then you're already at huge evaluation, years into your project, or have 200+ positions, ie. you've already refactored your project multiple times.
That's why you shouldn't use slow backend technologies in the first place because you get to the point where you need preformance and it's impossible because your limited by extremely slow runtime you chose initially because it was flashy (not even easier to developer for) when you could have just chosen something better from the start.
Simple crud apps can get by fine with those technologies, but in the future I'd still never use it because you're leaving huge amounts of performance gains on the table for virtually no benefit. I don't buy the argument that javascript is just easier to develop for because it's simply not. The js ecosystem is a disaster.
Node.js backend performance is comparable to Java. Perhaps you had bad developers - trust me, if they screwed it up so bad they wouldn't be able to make your Java backend any faster, and probably couldn't get Go or Rust to work at all.
Go is perhaps the simplest language to learn there is. It's almost impossible to not get it to work because it has so few things you can actually do.
And nodejs only preforms well in hello world benchmarks, real world applications are nothing like that. Once you start having to manipulate large arrays or do any large amount of math nodejs preformance goes into the dumpster.
Typescript (nodejs) backends are not performant, and your ultra modern stack is going to just cause you issues going forward if you need to scale. Prisma is really bad too, slow queries and no flexibility. If you ever need to do any sort of complex query you will just have to write sql anyway. And typescript is only sort of static typing.
These technologies are great for prototyping and building a v1 release to see if what you're trying to achieve is actually possible, but you will regret it later on.
The reason I know this, I work at a startup where we literally had the same backend stack and its been nothing but preformance issue after preformance issue. And it all needs to be replaced. We would have been better off building everything with go/rust in the first place. Or even java.