Similar in go: golazy.dev
1,365 karma · joined April 19, 2010
It has been so many attempts to run Linux on this chips without any collaboration from Qualcomm. Companies even drop support after years of development.
Qualcomm provided efficiency (battery life). But intel is catching up fast to make Qualcomm irrelevant.
Welcome, but too late.
If you focus only on economic exploitation: Of course, with customer protection, companies can't do whatever they want. Of course business will develop less in comparison to countries where companies are free to do whatever.
If you try to sell to China, Australia, UUSS and Colombia and Russia for example, you also need to comply with the regulations of each of those countries (and pay Tarifs in some).
To ease the collaboration between humans the European Union was created. But the European Union is not a country. Is the earth only collection of countries that agree to collaborate together to levels no other countries have in the world History.
It's success is so big, that people expects to act as an independent country, and complain when discovering Europe is indeed several countries. WTF!
Turbo comes from a progressive-enhancement philosophy: start with proper HTML and add richer behaviour on top. HTMX is a JavaScript library in much the same sense that React is. There is nothing inherently wrong with that, but it makes this anti-pattern easier to fall into.
Honestly, “the site should work without JavaScript” is no longer the strongest argument. Server-rendered, semantic HTML matters more for accessibility, SEO, and increasingly for LLMs and other automated tools.
Of course, you can write excellent HTML with HTMX. It just requires more discipline—or enough experience to recognize when you are quietly building a JavaScript application in HTML attributes.
Spain have lower levels of vitamin d than Denmark.
I used to play with omarchy. It is good enough for a lot of use cases. For powerful work I just connect to remote session.
Perfect for planes in economy
I would love that the size of the article is based on the number of upvotes (hardcoded).
* > 500 => take full width or 3. * 500 > 100 => Show it as right now. * > 100 => Just show the title.
This is common when processing PII. Lawyers, doctors our similar should not be using cloud solutions.
Also it's harder to setup and always more expensive than any cloud solution.
The UX pyramid but applied to DX.
It basically states that you should not focus in making something significant enjoyable or convenient if you don't have something that is usable, reliable or remotely functional.
The prompt is normally larger than the content generated.
We are moving to a point in time, where we don't care if the PR was written by AI. We care that the author understand what is about, that it tested it and in general, we want the ownership.
With articles is the same. I don't care if it was written by AI, if the content is interesting, and ai make it easier to digest... That's a win win.
The problem is not the presentation. Is the content.
LLM helps me communicate my ideas better.
Thinking in different angles, focus on the main idea, structure in a post series... It constantly challenge my mess.
Opus and I, iterate over 20 times a single blog post.
Until now, ideas were only relevant when the owner was able to communicate then regardless of the impact of the idea.
LLM "democratize"(VC term) sharing ideas, as people with low communication skills can be heard.
One command, and you are running the models even with the rocm drivers without knowing.
If llama provides such UX, they failed terrible at communicating that. Starting with the name. Llama.cpp: that's a cpp library! Ollama is the wrapper. That's the mental model. I don't want to build my own program! I just want to have fun :-P
So this coming from google... it's funny. Welcome, but funny.
I’ve been asking myself the same thing for years. My take:
1. Peter Principle: people get promoted to their level of incompetence.
2. In many companies, it’s the only way to increase salary.
3. Some developers think it gives them more leverage or impact.
But honestly, most of the time it’s simpler: stakeholders want more output, and the best dev gets pushed into leading because there’s no one else.
It’s often less a “promotion” and more a gap the company needs to fill.
If I apply my own bias I will call it:
American companies abuse their dominance my enforcing non documented requirements, making other companies not able to reach their users.If the project is even split in different parts that you need to understand... already makes the point.
https://nanovms.com/dev/tutorials/running-postgres-as-a-unik...
The fine was to protected the users from that scam.
I like paying taxes to protected the users that don't have the ability to detect scams as we all here have (most of the time).
EU miss the point equally to the Congress in uuss when non tech people believe they can rule (or just lobbied).
But on this case, there will be no problem if Twitter had decided to use another checkmark for pro accounts.
The closest free alternative is https://www.mitmproxy.org/ that is not even close.
And off course, https://www.wireshark.org/ but that is too generic and with a bigger learning curve.
Worth the money. And no subscription (or there weren't a subscription back then)
I concluded that better IO planning it's only worth it for "slow" I/O in 18.
Pretty sure it will bring a lot of learnings. Postgress devs are pretty awesome.
One classic case is user notifications - like the user icon in the corner. That's perfect as a permanent lazy frame, with a subscription watching for any user-related updates. This way you don't have to think about updating that widget across different pages, and you can centralize all user-related async events in
one controller.
Another pattern is real-time dashboards. You never know which part of the dashboard will change, and it's actually simpler on the backend: you just track what was updated and push that specific part. Clean and efficient.
Can't really see how making it more Rails-centric would help - more likely it'd just cause a fork for everyone using Hotwire without Rails/Ruby.