Interesting to see the cost curve drop ... this always changes the market.
I have been watching the sensor space for a while. Cheap LIDAR units could open up weird DIY uses and not just cars. ALSO regulatory and mapping integration will matter. I tried to work with public datasets and it's messy. The hardware is only one part! BUT it's exciting to see multiple vendors in the space. Competition might push vendors to refine the software stack as well as the hardware. HOWEVER I'm keeping an eye on how these systems handle edge cases in bad weather. I don't think we have seen enough data yet...
> Cheap LIDAR units could open up weird DIY uses and not just cars.
Interestingly, there are already some comparatively cheap LIDAR units on the market.
In the automotive market, ideally you need a 200m+ range (or whatever the stopping distance of your vehicle is) and you need to operate in bright direct sunlight (good luck making an eye-safe laser that doesn't get washed out by the sun) and you need more than one scanning plane (for when the car goes over bumps).
On the other hand, for indoor robotics where a 10m range is enough and there's much less direct sunlight? Your local robotics stockist probably already has something <$400
Neato from San Diego has developed a $30 (indoor, parallax based) LIDAR about 20 years ago, for their vacuum cleaners [1].
Later, improved units based on the same principle became ubiquitous in Chinese robot vacuums [2]. Such LIDARs, and similarly looking more conventional time-of-flight units are sold for anywhere between $20-$200, depending on the details of the design.
Sounds like the quality isn't all that great but LD06 sensors look like they're about $20 and someone who works on libraries about this suggested the STL27L which seems to be about $160 and here's an outdoor scan from it: https://sketchfab.com/3d-models/pidar-scan-240901-0647-7997b...
Not sure if the ld06 is a scanner like this or if it's just a line (like you'd use for a cheaper robot vac).
Tune it out, come back in 6 months, the world is not going to end. In 6 months, you’re going to change your API endpoint and/or your subscription and then spend a day or two adjusting. Off to the races you go.
This is going to be a crazy month because the Chinese labs are all trying to get their releases out prior to their holidays (Lunar New Year / Spring Festival).
So we've seen a series of big ones already -- GLM 4.7 Flash, Kimi 2.5, StepFun 3.5, and now this. Still to come is likely a new DeepSeek model, which could be exciting.
And then I expect the Big3, OpenAI/Google/Anthropic will try to clog the airspace at the same time, to get in front of the potential competition.
one good thing vercel did, was indexing skills.md under a site skills.sh - and yes there are now 100s of these sites, but I like the speedy/lite approach from vercel's DX, despite me not liking vercel a whole lot
I don't like vercel design, its just huge list of abstract skill name and you have to click on every one to even have a clue what something does. Such a bad design IMHO.
Design of https://www.skillcreator.ai/explore for me it's more useful. At least I can search by category, framework, language and I also see much more information what some skill does at a glance. I don't know why vercel really wanted to do it completely black and white - colors used and done with a taste gives useful context and information.
I appreciate the mention of better browsable designs. I created Skly (https://skly.ai/browse) with a similar idea: categories, descriptions visible at a glance, and search. I would welcome any feedback on what could be improved.
i think i can guess this article without reading it: ive never been on major drugs, even medically speaking yet using AI makes me feels like i am on some potent drug that eating my brain. what's state management? what's this hook? who cares, send it to claude or whatever
It's just a different way of writing code. Today you at least need to understand best practices to help steer towards a good architecture. In the near future there will be no developers needed at all for the majority of apps.
> In the near future there will be no developers needed at all for the majority of apps.
Software CEOs think about this and rub their hands together thinking about all the labor costs they will save creating apps, without thinking one step further and realizing that once you don't need developers to build the majority of apps your would-be customers also don't need the majority of apps at all.
They can have an LLM build their own customized app (if they need to do something repeatedly, or just have the LLM one-off everything if not).
Or use the free app that someone else built with an LLM as most app categories race to the moatless bottom.
Literally no way to sign up to try. Put my email and password and it puts me into some wait list despite the video saying I could try the model today. That's what makes me mad about these kind of releases is that the marketing and the product don't talk together.
ALSO... the permission boundary is clearer. You can whitelist commands, flags, working dir... it becomes manageable.
HOWEVER... packaging still matters. A “small” CLI that pulls in a giant runtime kills the benefit.
I want the discipline of small protocol plus big cache. Cheap models can summarize what they did and avoid full context in every step...
reply