What metric would you use to define the leading frontend framework, and what is it?
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.
They said "leading innovative framework", and innovative is the key word. The biggest player is almost never innovating, they are usually performing some kind of undeserved market capture.
React isn't innovating, it's just improving what it already does, but it doesn't do it in a new way.
That makes it stable, and a safe choice for devs. But yeah indeed like the article says, it kind of stagnates innovation in the ecosystem. But yeah I guess that is because React is usually "good enough" in most cases. Not enough reason to use something else.
> Alexa+ costs $19.99 per month, but all Amazon Prime members will get it for free.
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.
It works out for them because bandwidth gets cheaper over time but inflation eats away at that. $70 today is like $50 back in 2010 when GFiber first launched.
The same way I would with any of my own code - I would test it!
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.
This mostly solves the unpacking problem. Thus, there are only two problems left:
1. I need to handcraft the tuple type myself, and make sure it matches the function declaration. (In other words, I don't want to manually write tuple<char, short>. I want to write foo::arg_tuple.)
2. This provides no support for named parameters. Tuples in C++ are numbered, not named.
Is Shazam really ML/AI/DL? I thought it was more of a signal processing and search engine system. You transform snippets of audio signals into text, pump it into a distributed database, and then perform a search against that.
Maybe there is some AI involved in noise reduction, but that seems like a rather small component.
"Music information retrieval" is what researchers call the overarching field. You might say the Shazam algorithm is akin to those fields in the sense that it relies on feature extraction. It's possible they may train a classifier to do the matching, but yeah, probably not purely ML/AI/DL.
They do something that gets results. It doesn't matter if it's ML, AI, DL, linear regression, or just fingerprint+cosine similarity. There's some talent for getting some complex shit done.
I stopped using browser based password managers and switched to KeePass. It's a bit more work to pull passwords and back them up, but for me it beats trusting cloud services with security critical data.
This! I love my setup. I use KeePassXC and sync my password db with NextCloud. I love having an open source password manager that is useful across all of my devices, be it Android, Linux, Mac or Windows.
I was introduced to Lua via writing a Wireshark plugin for packet verification. It was hard in the beginning but dove right into working with a C backend. I'd say that's an approachable side project if you want to explore Lua.
I wonder if anyone would ever be willing to link this up to a personal website and publicly display all transactions live. That would take transparency to a whole new level. Call me crazy but I feel compelled.
Talk to people who run usability studies and ask how many users know that the browser can do these things.
People joke about "my grandfather opens his browser and types 'Yahoo' into Bing, clicks the link and types 'Google' in to Yahoo, clicks the link and types 'Facebook' into Google to get to Facebook", but it's not that wild an exaggeration of how much of the developed world -- which is not computer-literate -- uses the web. That's part of why walled gardens and native-feeling app experiences are so successful.
Adoption of Chrome likey erases that pattern. As more and more people adapt to searching from the address bar, autocomplete is also used more and more.
You'd be surprised how often people do in fact do exactly that. I know two personally. I don't have overall figures but it's definitely greater than zero.
Isn't there a service which shows popularity of search terms? That would be one way to get a handle on frequency.
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...