Honestly wrapping code in a front end is enough of an “app” experience that people don’t care as long as it brings value. Perfect case I ran into last week, I had to convert a legacy .pst outlook file to .eml for new outlook. Only a handful of these tools exist and I picked the one that had a front end and a nice looking installer. $110 to that company for something I will likely never use again.
Not sure if the first video demo matches the hero statement. Professionals with deadlines doesn’t really map to “here is how to start a Minecraft server”
My experience with Claude 3.7 with thinking has been incredible for coding tasks. I did not find the same level of success with Gemini even though the context window is nice.
Before they rolled this out, I rarely hit usage limits. Now it seems the usage limits have been lowered for Pro to add more value to Max. That is a less than ideal experience for users.
I agree with what most comments here are saying, that there should be more than just usage limits and I hope this changes (as it likely will because the state of competition is still high)
I wonder who the audience is for the Mac Studio after they showcased some pretty serious workflows from industry leaders using a Mac Mini, Mac, and a MacBook Pro.
I kinda feel like Apple has been trying to say that for a long time, and finally got sick of people saying they abandoned the pro scene and said fuck it here's your massively overpriced "professional" version so you can feel like you're a pro.
As someone in the Software Supply Chain business. Yocto SBOMs are considered low quality because they include things that do and do not exist in the final compiled artifact. When you compare what exists inside, physically from a binary perspective, what is included in the manifest, and what is generated in the build root, you will find they will never align unless you get creative and map artifacts together. Today they are accepted as meeting the compliance checkbox, but once the industry matures, they will need to adjust their approach.
Since it is easy for me I prefer the Yocto SBOM, but the security side forces blackduck binary scanning on us which while finding most things on the binary constantly misidentifies a lot of versions, resulting in a lot of manual work.
It also does not know which patches Yocto has applied for fixing CVEs.
And none of these can figure out what is in the kernel and therefor triggers an ungodly amount of CVEs in parts of the kernel we don't have compiled in.
There is no tool at the moment that solves this, but it is being worked on amongst some players in the industry by those that fundamentally understand the problem. It is a very niche skill set that the greater compliance world doesn’t understand the need for yet. I would say we are 1-3 years away from solving the noise problem of SCA/BCA.
To be clear, it isn’t just a yocto problem. It is an industry wide issue and usually requires resolution between binary, build, and manifest or SCA. But at the end of the day developers are still very creative.
I made a random playlist generator for Spotify that truly gives back stuff you’ve never heard. I recommend removing the playlist from your taste profile and put on smart shuffle. Regenerate as many times as want. Open to suggestions/features as well.
It says daily but the auto generation feature is not enabled yet.
