I guess the point (at least for me) is a bit to get rid of weird intransparent algorithms that seemingly got worse over the past couple of years. Using a platform like last.fm where it’s clearer that recommendations are based on genres and similar listeners is still ok and encouraged, and probably as close to getting recommendations from real humans as possible.
I also find arguments like this quite weak. YouTube, Facebook et al work like absolute horseshit compared to other websites and web apps. If anything, they proof that these big companies manage to make simple web applications as bloated and slow as possible.
… and makers don’t have an incentive to even deliver such features, because people are already buying them?
At least I wouldn’t know what’s stopping them from building actually-useful features, tech-wise. Or was it just always a bad idea because fridge placement is random and items are often hard to find/detect?
I think it’s at least equally important to be sceptical of bad ideas, in order to let good ideas win. From a consumer perspective, smart fridges are usually bad.
Potentially! Would be interesting to hear if anyone manages to block internal Apple shenanigans with Little Snitch successfully and feasibly (without constant toggling of rules or alike).
That mindset shift surely started quite some years ago? At least in my book they’re actively hindering standards/compatibility with other ecosystems, greenwashing their products, squeezing out third-party developers, and design/UX is also going downhill at least since Liquid Glass (or rather since Jobs left).
That implies that Claude writes better code by default, which isn’t necessarily true. Especially as projects get bigger, you can easily end up with unmaintainable LLM-written code if you don’t actively intervene and know a cleaner way.
The “(all genders)” bit is probably just based on the fact that they translated the German job ad (in German you have to be more explicit with the male/female/all versions of titles, because the default is usually just the male form). So, it’s not a qualification, but just a way to be inclusive to applicants of all genders (we have a diversity problem in our industry).
The salary is bound to the limits of the public salary bands (collective agreement), that’s where the maximum comes from. (And, you can live quite well in Berlin with ~100k € per year.)
I think it’s implied that accepting these kinds of PRs will take time away from working on actual improvements to the codebase. So, on the long term it’s better to be strict with these kinds of silly contributions, and focus on changes that matter more (e.g. features or fixes).
Many people care and should care. Of course if a piece of software (or any project/tool, really) gets a lot of usage, it’ll indirectly make its creators more powerful. I wouldn’t want to make a person more powerful if they support horrible causes (like in DHH’s case), especially if there are many alternative routes to choose from that are less questionable.
I disagree. Technology is inherently political, and it’s valuable and important to get informed and reminded about the many horrible people that are directly or indirectly tied to any mentioned organizations and projects.
Neat! I like these opinionated lists, especially when it’s easy to browse and cherry-pick useful stuff. It’d be very good to mention how compatible the features are, though. Especially with newer CSS features, it’s easy to overestimate how ready they are for all browsers.
For that, there could just be links to the related MDN and/or caniuse.com pages.
You like using Google and Microsoft products as an end user (even ignoring all the ethical issues with these companies)? That seems surprising to me. I find their products so horrible compared to e.g. Fastmail.
… and the sizes of their updates are usually impressive! Seems to be a big project that is managed well to keep a good pace and keep the community in the loop. (Although I don’t know much about their inner workings.)
Yep, even music software like Ableton Live is using zipped XML for the project files (although the much bigger audio files are stored independently in sub-folders). There were even efforts to use the XML format to manage Ableton project files with git in order to have a nicer change history (https://github.com/clintburgos/ableton-git).
It’s hard for me to imagine that most people care about speed. I think it’s more likely that they just don’t know how bad Chrome is (for the internet) and how evil Google is (it’s still the main search engine for most people). I think Chrome is familiar, and Google is good at locking people in, pretending that Chrome does things better (or even making sure other browsers are handicapped on the Google sites, like YouTube being slower on Firefox).
You can look up who the contributors are, e.g. in their open-source repo: https://codeberg.org/comaps
There are also issues and projects with lots of discussions about what to prioritize, etc.
So, bashing that “community” is too fuzzy is perhaps not very warranted. (Although I guess they should add a section “Who makes CoMaps?” to the FAQs or so.)
Authenticators should work normally, as far as I know (unless Google Authenticator does anything special). Can’t say anything about Google Wallet. There might be more lists/forums where people share which setups are (not) working well for them.
In general, I had these concerns as well until a few months ago. But I am much more optimistic these days that things will just work well out of the box (have read many positive sentiments in blog posts and here on Hacker News).
I’m sure the general premise around AI-generated code is accurate. That being said, I’ve definitely had interesting moments where e.g. Claude produced code that matched the pre-existing codebase quite nicely, and slowly started building up its memory of how new pieces fit into the codebase in an idiomatic way. Then again, it started to throw in Tailwind-based CSS classes all of a sudden, because it assumed that Tailwind had been set up (it wasn’t).
> IMO the maintenance story is more or less solved if you can keep AI agents refactoring and improving it in a loop.
That’s a weak argument, though, if the future of AI is totally unreliable when it comes to cost and quality. Right now I definitely wouldn’t want to depend on being able to infinitely access AI tools for such an important part of the toolchain.
Aside from that it’s just not attractive to trust a project made by one person.