anything is more accurate than the llms at generating images. chatgpt, google gemini, all of them... they're not optimized for image generation. it's why veo is an entirely different model from google for example. and even veo isn't the best video model either. people dedicated to images and video are just spending more time here (such as black forest labs). as a result, those specialized models are better.
I think it was foolish to buy it for so much money to be honest. I'm not sure how large its user base is, but that's more than likely something to do with it.
Remember that none of these tools can survive forever. Exiting was EXTREMELY smart of the founders here. Incredibly smart. I'd F off into the sunset now myself.
The reason is because they are built on top of VS Code and use Claude. So OpenAI can switch the LLM, cool, but at the end of the day there's no moat for the Cursors and Windsurfs of the world. OpenAI has the keys here because they have the proprietary LLM. This doesn't mean OpenAI will survive btw. I think Google will awkwardly win this race. They're so so so awkward though it'll take some time. It's painful to watch, but because they have the user base, they'll win. Hold that thought for a moment.
So new tools like Cursor and Windsurf will pop up all the time and do you think Microsoft will just sit by and watch? Nope. They'll update VS Code and Copilot and voila, the pendulum shift. As quickly as Cursor and Windsurf gained users, they'll lose them all again back to VS Code and Copilot. Copilot does indeed index your entire codebase - a rumor or misunderstanding by people. So as the dust settles, we'll see this change in usage. As LLMs trade places, we'll have a revolving door of fanbois and people arguing about what's better. What a rollercoaster.
What's really interesting here is that I think we're going to see a LOT of litigation. Back to Google. Look at what's happening with Google Chrome. Some genius thought they were in violation of anti-trust laws (well maybe they are). The reality is they are about to make it WAY WAY WORSE because Google Chrome was open source and should someone buy Chrome and decide they don't want to share...Well bye bye funding to virtual every other web browser. Congratulations brilliant legal system, you created a monopoly. It just wasn't Google's monopoly so I suppose that's alright.
So what I would bet is going to happen here is we're going to see OpenAI, Google, Microsoft, Anthropic, etc. all start to mess with one another here in a similar fashion. It's all going to be lobbying and legal battles. All over the place. It's going to make for an incredibly turbulent landscape. This is a very very expensive game.
THIS is why we're talking $3B. Someone is looking to protect something. It's not because of value. To think about it as a business value somewhere is wrong. Windsurf and Cursor aren't worth billions. Are you out of your mind? There's no justifiable way any rational human being would think that. When they're built on top of other tech and have absolutely no defensible position?? Heck no. It's not about their value individually, it's about their added value to these other companies. It's about bet placing. It's about protecting a larger business.
Take a moment to think what the world would look like if OpenAI must remain an open source business and or had to divest ChatGPT. They get Screwgoogled. Now ask why they're going to gobble up other businesses and why they keep raising all this money. I still think it's foolish, but it definitely seems like an existential threat that's lurking in there to me.
Really good point and I agree. This was intriguing at first glance because who doesn't want less JS on their site?! Of course! However, missing out on other events being tracked, advanced demographic information(?), and what else?? That's a huge miss - especially if you work with Google Ads and have your Analytics linked. Your ad campaigns won't be as effective and could potentially cost more money to save someone an unknown amount of loading time.
Til they lose your money I guess just like the options yesterday (actually, that really stinks for some developer somewhere and was completely horrible so wishing the engineers some good vibes over that and hopefully work out).
I agree. I actually referred people to Kimono. I'm so sorry I did. This is unacceptable behavior in this day and age. I mean seriously? Servers are cheap. Keep the thing up for existing users. Don't add new features. Don't invest any more time in the thing. But don't pull the rug from under people's feet. That's just bad form. If this is who Palantir acquires or acquihires, then they have some really bad judgement too. It reflects poorly on Palantir to not care about commitment and responsibility.
Very nice tool that saves a ton of time with the insane amount of configuration that goes into all this. I think Lambda has a really bright future and JAWS is breaking some serious ground here. Keep up the good work so I don't ever have to build a tool to do this =)
SoA is nothing new and there are definitely times to use it much like there are times to use MVC and times not. However, it's a "buzz" right now because of the nature of many of the apps we have out there right now. Big data is also a buzz and fits well with SoA / microservices. Docker fits in here as well. The entire way the hosting landscape is shifting nurtures an SoA and the notion of running apps as VMs sans operating system is yet another support for SoA.
No, it's not appropriate for your blog. But it IS appropriate for many applications out there and it's an incredibly beneficial way to scale a set of services and build a complex application in a cost effective manner.
I don't quite agree with the notion of being "stuck maintaining five apps, five APIs, etc." because it's not. It's really one app. You're doing something wrong if you feel that you have five different apps and APIs. In fact, your testing and debugging should become easier under such an architecture. Maintenance should be much better if done properly. Of course regardless of your software architecture, you can end up in "maintenance hell" so that's really an invalid argument against SoA. I certainly wouldn't let the fear of bad programming prevent me from using a specific design pattern or architecture.
