scoot
Go up one comment and you’ll see this was with respect to LG, not Samsung.
I do understand it from an artistic perspective, and who knows when and how an asset will be used in the future; but the premise doesn't appear to hold water under scrutiny.
From the article:
What's next? ...using PCB assembly...
Apparently hyphens seem to have gone out of fashion. Please can we bring them back?
Not to mention the title - the tapestry was embroidered, not woven (if you exclude the ground fabric, which by itself is just a piece of cloth).
Or more likely do, but hope that you don't...
"The HYSTER trademark is filed in the category of Education and Entertainment Services" [0], so you can safely ignore any demands to rename, as it doesn't conflict. Embarrassing for them that their lawyers don't understand even the basics of trademark law.
Edit to clarify as some folks here are as confused as sHyster's lawyers: Trademarks are not exclusive, they're restricted to a category or categories. You can be Apple in the category of computers, but not in music if there's already an Apple in that category (unless you have $500M to spare [2]).
[0] https://www.trademarkia.com/hyster-77843354
[1] https://tmsearch.uspto.gov/ for a more authoritative source than [0], but it doesn't allow deep linking
[2] https://en.wikipedia.org/wiki/Apple_Corps_v_Apple_Computer"Firms like Jeppesen have offerings in this space, but Scikit-decide, together with a narrow- and wide-body fuel consumption model built by a professor at the Delft University of Technology and wind data from NOAA, offer an open source solution."
So this is being positioned as an open source alternative to commercial offerings, which clearly it is not. If instead he made the limitations clear from the outset, that this is just a demonstration of what he/the tools are capable of and that this is not in any way intended for real-world use, it would put the rest of the article into better context.
I also don't see how Scikit-decide being developed by Airbus gives OP any domain authority. I use open source tools from all sorts of commercial ventures, and know nothing about how they themselves use them, or what for.
So what happens if you arrive home with a dead phone?
And possibly worse, they have a log of when you come and go?
They didn't say that - they said "the (exclusive speciality alloy) parts are literally ripping themselves apart". That sounds like a seriously flawed design to me
Directions weren't coming from my phone's speaker or the car, but testing audio in the Maps app did (from the car).
Still not sure what combination of connections it had managed to get itself into!
Germany, for example. Utterly bizarre and baffling that a democracy protects its politicians this way. /s
The underlying LLMs don't, but the agent frameworks around them do.
None of this would have been possible (or at least practical from a time-value perspective) for me to do without Claude driving the whole exercise.
That seems like a given. If you're curious, you'll soon see through any ideology you were spoon-fed as a child, religious or otherwise.
Season and weekly are different things (obviously). If you narrow your claim down enough, of course you can be the first (patents or Guinness book of world records being prome examples.)
But the article isn't about that, it's about the design of the tickets. And they are a thing of beauty.
Donkey Cut offers more functionality in less space, and everything is easy to find and understand. It isn't without bugs, but the structure is there for it to be great
Edit: Having played with both a bit, and with no disrespect to OP, yours is a significantly better product.
Not faulting your (necessary given today's reality) work, but sad to think that the Amiga still remains ahead of it's time some 36 years later (since ARexx was bundle with the OS), or closer to 40 years if you count when v1 was released separately.
ARexx allowed any application that supported it (and most productivity apps worth their salt did) to communicate with each other, and to be scripted - essentially a standardised API for applications.
We're slowly getting there (at least for SaaS apps) with MCP, but screen scraping shouldn't ever have been necessary.