I'm no expert, but I'm pretty sure this[0] is what RTO 5 is.
[0] https://www.phoenixcontact.com/en-pc/products/bolt-connectio...
I'm no expert, but I'm pretty sure this[0] is what RTO 5 is.
[0] https://www.phoenixcontact.com/en-pc/products/bolt-connectio...
[0]: https://www.aboutamazon.com/news/devices/new-alexa-generativ...
I'm curious if non prime members make up a big market for Alexa. I rarely use my smart devices for anything beyond lights, music, and occasional Q&A, and certainly can't see myself paying 20$/month for it.
I do wonder whether your code does what you think it does. Similar-sounding keywords in different languages can have completely different meanings. E.g. the volatile keyword in Java vs C++. You don't know what you don't know, right? How do you know that the AI generated code does what you think it does?
The key here is to spend less time searching, and more time understanding the search result.
I do think the vibe factor is going to bite companies in the long run. I see a lot of vibe code pushed by both junior and senior devs alike, where it's clear not enough time was spent reviewing the product. This behavior is being actively rewarded now, but I do think the attitude around building code as fast as possible will change if impact to production systems becomes realized as a net negative. Time will tell.
It's a pretty convincing fake, but it has one problem: the person who wrote the function needs to have written it that way. What I wish more languages had (C++, Java, etc.) is the following:
Suppose I write some function that take way too many parameters:
void foo(char a, short b, long c, float d, double e){}
What I want, as a caller, is for the language to let me get a struct corresponding to the argument list, something like this:
foo::args whatever;
whatever.e = 3.14;
// fill in the rest
And then add a bit of magic syntax so we can "unpack" that struct to actually call foo. (Extending this proposal to handle varargs is left as an exercise to the reader, because I have no idea.)It might be a bit verbose, but I think I would still prefer this over native syntax for unpacking.
This looks to me like an acquihire for the ML/AI/DL talent. So basically, yes they will be diverted to other projects.
I'm sure Lua has other sweet spots, but that's the one I'm most familiar with.
What it _doesn't_ take into account is mobile app usage, which might have been what sucked in all those people vs just total loss.
React has rather matured in dealing with it's own outdated Virtual DOM design, making it much more boiler platy than modern alternatives.
I'm familiar enough with Angular, React, Flutter, Vue, and Svelte as big names in the ecosystem, but have really only done scrappy development with React and not much with the others.
Google trends seems to show React is still a leader [1], and React has more than double the amount of Github stars than any of the others I've mentioned except Flutter, by which it still leads a healthy margin.
- [1] https://trends.google.com/trends/explore?cat=32&date=today%2...