I do like the idea of crowd-sourced collections of resources like skills.
It might be more useful if it was an index of skills managed in GitHub. Sort of like GitHub actions which can be browsed in the marketplace[1] but are ultimately just normal git repos.
> Paying more for programmers or parking machine processors would be a waste of money.
The rise of parking apps on mobile adds an interesting angle to this.
No doubt, many of us favour apps because the UX is so much better. Not quite sure if that affects the bottom line short-term, but long-term I’m sure it will.
I’ve wondered about this more generally (ie, simply prompting in different languages).
For example, if I ask for a pasta recipe in Italian, will I get a more authentic recipe than in English?
I’m curious if anyone has done much experimenting with this concept.
Edit: I looked up Sapir-Whorf after writing. That’s not exactly where my theory started. I’m thinking more about vector embedding. I.e., the same content in different languages will end up with slightly different positions in vector space. How significantly might that influence the generated response?
I just tried your experiment, first asking for a bolognese sauce recipe in English, then translating the prompt to Italian and asking again. The recipes did contain some notable differences. Where the English version called for ground beef, the Italian version used a 2:1 mix of beef and pancetta; the Italian version further recommended twice as much wine, half as much crushed tomato, and no tomato paste. The cooking instructions were almost the same, save for twice as long a simmer in the Italian version.
More authentic, who knows? That's a tricky concept. I do think I'd like to try this robot-Italian recipe next time I make bolognese, though; the difference might be interesting.
The italian counterpart of what english speakers call "bolognese sauce" would be "ragù alla bolognese". I've never heard anyone call it "salsa bolognese", it's mostly called "ragù" only as it's most common type.
Nonetheless ragù alla bolognese is made with ground beef and tomato sauce, so the italian version is simply wrong. Try and ask for ragù recipe instead. :)
That is the phrase Google Translate proposed: the exact prompt I used was "Come si prepara il ragù alla bolognese?"
I often consult several different versions of a recipe before cooking, and this feels like a normal degree of variation. Perhaps there are regional differences?
Just for kicks, I asked (in English) "what is an authentic Italian recipe for bolognese ragu?", and it produced a recipe similar to the version returned from the Italian prompt, noting "This version follows the classic canon recognized by the Accademia Italiana della Cucina". Searching on name of that organization led me to this recipe:
There are indeed regional differences, but at that point is not called "alla bolognese" anymore but "alla whatever place". People usually call it "ragù" and that's it.
Didn't know that the original recipe has pancetta too. It's good nonetheless. :)
FWIW, and tangential, the biggest (and time consuming) difference I ever found in making bolognese was hand cutting the meat instead of getting it ground.
The texture was way better. It's a pain to do (obviously) but worth trying at least once, IMO.
I think it’s more for Python libraries that depend on JavaScript.
Lots of packages rely on other languages and runtimes. For example, tabula-py[1] depends on Java.
So if my-package requires a JS runtime, it can add this deno package as its own dependency.
The benefit is consumers only need to specify my-package as a dependency, and the deno runtime will be fetched for free as a transient dependency. This avoids every consumer needing to manage their own JavaScript runtime/environment.
Over my 35 years of computer use, most hardware failures (very, very rare) happen during a reboot or power-on. And most of my reboots happen when installing updates. It actually seems like a very high probability in my limited experience.
Of course, it’s possible that the windows update was a factor, when combined with other conditions.
There's also the case where the hardware has failed but the system is already up so it just keeps running. It's when you finally go to reboot that everything falls apart in a visible manner.
This is one of the reasons I am not a fan of uptime worship. It's not a stable system until it's able to cold boot.
Say you have a system that has been online for 5 years continuously until a power outage knocks it out. When power is restored, the system doesn't boot to a working system. How far back do you have to go to in your backups to find a known good system? And this isn't just about hardware failure, it's an issue of configuration changes, too.
I also notice that people with lots of experience with computers will automatically reboot when they encounter minor issues (have you tried turning it off and on again?).
When it then completely falls apart on reboot, they spend several hours trying to fix it and completely forget the "early warning signs" that motivated them to reboot in the first place.
I've think the same applies to updates. I know the time I'm most likely to think about installing updates is when my computer is playing up.
I try to do the opposite, and reboot only as a last resort.
If I reboot it and it starts working again, then I haven't fixed it at all.
Whatever the initial problem was is likely to still present after reboot -- and it will tend will pop up again later even if things temporarily seem to be working OK.
> Whatever the initial problem was is likely to still present after reboot
You only know this after the reboot. Reboot to fix the issue and if it comes back then you know you have to dig deeper. Why sink hours of effort into fixing a random bit flip? I'll take the opposite position and say that especially for consumer devices most issues are caused by some random event resulting in a soft error. They're very common and if they happen you don't "troubleshoot" that.
He also seems to talk to a lot of people, and he has access to pretty much anyone given his stature. Imagine being passionate about business and then being able to spend every day talking to people about their businesses and their thoughts on business. I'm surprised he retired at all!
Always worth remembering that PDFs are basically a graphic design format/editor from the 70s. It was never intended for securely redacting documents and while it can be done, that’s not the default behaviour.
No surprise non-experts muck it up and I don’t see that changing until they move to special-purpose tools.
Honestly, I’d still be surprised to learn feathers in America are produced from American poultry. Far more likely the local ones get burned and everything for sale is shipped across the ocean because cheaper.
Fallout 4 is ten years old and just recently was sold again as a remake, basically a small update with pre-included mods. Skyrim is 14 years old and I'm sure it will be resold at least one more time before TES VI is released.
Moddable games are like prescription pills that add one ingredient to a patent-expired recipe, to repatent it as new.
I'd extend it to all copyright but instead of "active development" make it a nominal fee every 10 years, so anyone that doesn't mind their work becoming public domain 10, 20, 30, etc years later can easily let it go.
Most IP owners would pay the tiny fee just to hold onto IP rights and do absolutely nothing with it. If I were designing this hypothetical legislation I'd make it 10 years without a release that works on new hardware and the copyright is lost. This would at least incentivise the owners to do remasters just to hold onto the IP, something that would make them a few bucks anyway.
It might be more useful if it was an index of skills managed in GitHub. Sort of like GitHub actions which can be browsed in the marketplace[1] but are ultimately just normal git repos.
[1] https://github.com/marketplace?type=actions
reply