mehh

I tried but it was too much, first I thought it was a spoof, then perhaps AI generated and then couldn't watch no more!

> In the UK people were arrested for saying thay all lives mattered.

ahh just seen your account was just created, so wasting my time, but no, no one in the UK was arrested for saying that.

It will probably really wind the old git up reading that despite all he his best efforts, I never even realised it wasn’t allowed, wanker (that’s just in case he reads this)!

Been swearing in Sam Smiths for 20+ years and never had a problem!

I cancelled mine today, as I’ve moved to cursor, so this is a great news as I’d still want to use it sometime.

I do think this slightly aggressive tactic, I’m sure they claim otherwise!

Problem with VSM, is where is the practical evidence of it working, if it's so great surely there would be more uptake of it?

I mean it sounds like a reasonable model, I'm sure there is a lot of nuance to it, but getting it up and running at an existing enterprise would be a very difficult to do, and at great risk without some solid case studies showing significant ROI.

Thanks for the feedback, and for joining the list.

I agree with your points, my plan is to get a basic version in front of some people and shape it on their feedback. Plan to have it available in a couple of weeks.

next.js reminds me of Ruby on Rails, main pain point is they keep changing how they do things, but docs, examples etc can't keep up so I'm constantly seeing the wrong answers to my problems.

An example of this is how they implemented sitemap.xml, but half arsed doing a sitemap index properly (which really wasn't much work), so they will end up doing it properly in some version, in the mean time you have to work around the framework (it would be better if they didn't even have this feature), and when the release a proper implementation new users will struggle to find the answers on how to do it.

This all adds friction to upgrade, I'd like to move to v15 as it has a feature I really need, but they have changed the bloody confusing caching system, not sure it's worth the work. Creating web frameworks that are volatile is fine if your just building short lived projects, but not anything more complex and longer lived, this is the same pain and why I gave up on RoR.

It’s not AI, it’s a collection technologies and practices within the domain of AI, symbolic and sub symbolic. Arguably classic search is another technology/approach/algorithm with the domain of AI.

I played around using genetic algorithms to design on fpga (Xilinx 6200 I think), about 25 years ago .. nothing came of that ...

I'm fine with it, I've forgotten more frameworks and libs for now dead devices/services/OS etc over the years that it's largely pointless memorising these things, I'm very happy for a machine to help me get to where I want to be, and less time faffing about with google/stackoverflow the better, like I said the failure rate is still fairly high, but still useful enough.

I’m working on a nextjs project, nextjs made a bunch of breaking changes and doesn’t document things consistently or comprehensively, I have a lot of grief using LLM on this framework.

This is something framework/libs/apis should factor in for future, how can you make your project LLM friendly in order to make it dev friendly.